In this Document
Goal
Solution
Some Tips about Fndload
Some Sample Examples
Diagnostics & Utilities Community:
Applies to:oracle User management-version 12.1.3 to 12.1.3 [Release 12.1]
Oracle applications Utilities-version 11.5.0 to 12.1.3 [Release 11.5 to 12.1]
Oracle application Object library-version 12.1.3 to 12.1.3 [Release 12.1]
Information in this document applies to any platform.
Checked for relevance on 12-apr-2011 Goal
To provide general understanding of Fndload program. Solution Some Tips about Fndload
Data synchronization?
Data synchronization is a process in which some setup data would being synchronized, and this would being more important when yo U is working in Oracle application Development/implementation project. The equally important, ATG data migration takes place necessary to synchronize the data across databases instance Duri Ng
· Installations (New descriptive flex field creations etc)
· Upgrades (Apps upgrade etc.)
· Maintenance (Value set changes etc.)
Generic Loader (fndload)
The Generic Loader (fndload) is a concurrent program that can move Oracle applications data between database and text file Representations. The loader reads a configuration file to determine what data to access. For information in specific configuration files consult the Open Interfaces Guide for your product group.
From a fndload perspective, there is absolute no limitation on parallel execution. Parallel upload of concurrent programs and responsibilities should through fine unless upload logic in LCT file restrict t He same.
There is no-to-limit the download of the value hierarchy data with the existing Flexfield loader logic.
If This data is removed manually from the. ldt file generated when downloading data, the upload might error out as a Resul T and this are not a supported method of using Fndload and the corresponding generated data.
Overview
The Generic Loader can download data from an application entity into a portable, editable text file. This file can and then is uploaded into any and database to copy the data. Conversion between database store and file format is specified by a configuration file, is read by the loader.
The Generic Loader downloads data from a database according to a configuration (. lct) file, and converts the data into a D ATA file (. ldt file). The Generic Loader can then upload this data to another database using a configuration file.
The loader operates in one of the modes:download or upload. In the download mode, data are downloaded from the database to a text file; In the upload mode, data was uploaded from a text file to the database.
Data structures supported by the loader include master-detail relationships and foreign key reference relationships.
In both downloading and uploading, the structure of the data involved are described by a configuration file. The configuration file describes the structure of the data and also the access methods to the. Copy the data into an or out of the database. The same configuration file is used for both uploading and downloading.
When downloading, the Generic Loader creates a second file, called the data file that contains the structured data selecte D for downloading. The data file has a standard syntax for representing the data which has been downloaded. When uploading, the Generic Loader reads a data file to get the data of the it is to upload. In most cases, the data file is produced by a previous download, and May has come from another source. The data file cannot be interpreted without the corresponding configuration file available.
What can is done?
These is the extensive list which can be done through fndload
· Concurrent Programs, executables
· Request Groups, Request sets
· Profile Options
· Key and Descriptive Flexfields
· Menus and Responsibilities
· Forms and Form functions/personalizations
· Attachments
· Messages
· Value Sets and Values
· Lookup Types
· User Responsibilities
· Printer definitions
· FND Dictionary
· Help Configuration
· Document sequences
· Alerts
· Concurrent Manager Schedules
The fndload:concurrent program–fndload can be executed as a Concurrent program.
Some advantages When using Fndload
1. Because downloaded data is stored in a text file, version administration is possible
2. There is nothing to worry to go to purchase because investment = 0$
3. No learning curve. This is relief for developer and DBA
4. Fully supported and recommended by Oracle
5. Capture the migrations in a file with use it during installations, clones etc. to migrate in batch
6. Pin-point when something happened and where (database) easily
7. Your AOL Data migration process is now simplified and streamlined goal attained
Some Disadvantages When using fndload
1. Applications patching mechanisms use fndload heavily possibility of negative impact are not zero
2. Upload_mode=replace only for menus
3. No validation against migrating database/instance sensitive data
Syntax
The Generic Loader is a concurrent program named Fndload. The concurrent executable takes the following parameters:
Fndload apps/pwd 0 Y mode configfile datafile entity [param ...]
where
<apps/pwd>
The APPS schema and password in the form username/password[@connect_string]. If
Connect_string is omitted, it's taken in a platform-specific manner from the environment
Using the name Two_task.
< 0 Y >
Concurrent program flags.
Mode
UPLOAD or DOWNLOAD. UPLOAD causes the datafile to being uploaded to the database. DOWNLOAD causes the loader to fetch rows and write them to the datafile.
<configfile>
The configuration file to use (usually with a suffix of. LCT, and not enforced or supplied by the loader).
<datafile>
The data file to write (usually with a suffix in. ldt, but not enforced or supplied by the loader). If The data file already exists, it'll be overwritten.
<entity>
The entity (ies) to upload or download. When uploading, always upload all entities, so specify a "-" to upload all entities.
< [param] >
Zero or more additional parameters is used to provide bind values in the Access SQL (both UPLOAD and DOWNLOAD). Each parameter are in the form name=value. Name should not conflict with a attribute name for the entities being loaded.
Modes of Operation
This was important because it would drive the whole flow, and it always be either Upload or Download.
Example of Download
Fndload apps/pwd 0 Y DOWNLOAD ${fnd_top}/patch/115/import/afcpprog.lct myfile.ldt \ Program Concurrent_program_name= Concurrent_program_short_name> application_short_name=<application_short_name>
Example of Upload
Fndload apps/pwd 0 Y UPLOAD ${fnd_top}/patch/115/import/afcpprog.lct myfile.ldt-custom_mode=force undocumented Parameter
What is Fndload Options?
· Application level OR single entity level download
O (Example) Download all the profiles options of Inventory or just the Inv:default Primary UOM
· Entire OR Partial upload of a data file
O (Example) Upload the entire Myfile.ldt or just a single entity indicated By-and mode Upload or upload_partial
o Entity name required for upload_partial mode
· Custom Mode Force update
O to override Oracle's upload algorithm and update the custom AOL data regardless, use custom_mode= force
o upload_mode= REPLACE (only for menus)
· Support for NLS uploads
o NLS data uploads for translated columns is supported, use upload_mode= NLS
Where is Configuration File Located
By default, Oracle delivers most of the configuration files, the can used to download certain entities.
· Configuration files with extension. LCT
O on Unix-all The configuration files is in $FND _top/patch/115/import directory
O on Unix Oracle also places the original configuration files in $FND _top/admin/import directory
· Data files with extension. ldt
Fndload File Structure
· The configuration files (. lct) is delivered and maintained by Oracle.
· IT has entity definitions, parent-child relationships and user input parameters identified by:name.
· Downloading a parent automatically downloads all children – (Example) Concurrent program download.
· The data files (. ldt) have both entity definition and the data.
· It also shows the version and the location of the configuration file (. lct) is used.
· Without the configuration file, a data file is useless.
· Without the data file, a configuration file is meaningless.
Fndload Files
· Key files:. LCT and. Ldt
· Fndload must be run as the and the apps user not as Applsys or any other user, otherwise an Ora-6550 error would be received.
· Both is easily readable, editable and portable.
· Do not modify Oracle. lct files.
· Use a favorite editor to manipulate only the. ldt files but is cautious about data type, length, delimiter placements etc.
· Use the log file outputs or. ldt file contents creatively for quick file comparisons and answer questions as: (Why can Thi s be accessed? What is the profile option name, value and level? What's the value set used for that DFF segment Attribute10 etc.)
· Partial string Searches (which value set has the priority something in its where clause, etc)
Some Sample Examples
1-printer Styles
Fndload Apps/[email protected] 0 Y DOWNLOAD $FND _top/patch/115/import/afcppstl.lct File_name.ldt STYLE printer_style_ Name= "Printer style name"
2-lookups
Fndload Apps/[email protected] 0 Y DOWNLOAD $FND _top/patch/115/import/aflvmlu.lct File_name.ldt fnd_lookup_type Application_short_name= "prod" lookup_type= "LOOKUP NAME"
3-descriptive Flexfield with all of specific contexts
Fndload Apps/[email protected] 0 Y DOWNLOAD $FND _top/patch/115/import/afffload.lct File_name.ldt Desc_flex p_level=:col _all:ref_all:ctx_one:seg_all? Application_short_name= "prod" descriptive_flexfield_name= "desc Flex name" p_context_code= "CONTEXT NAME"
4-multiple Flexfields
Use a combination of application_short_name and descriptive_flexfield_name names ie. Application_short_name=per >> would download all PER flexfields descriptive_flexfield_name=per_% >> would Download all Flexfields This start with ' Per_ '.
Fndload Apps/apps O Y DOWNLOAD $FND _TOP/PATCH/115/IMPORT/AFFFLOAD.LCT
File_name.ldt desc_flex descriptive_flexfield_name= "per_%"
5-key Flexfield Structures
Fndload Apps/[email protected] 0 Y DOWNLOAD $FND _top/patch/115/import/afffload.lct File_name.ldt Key_flex P_level=:col_ ALL:FQL_ALL:SQL_ALL:STR_ONE:WFP_ALL:SHA_ALL:CVR_ALL:SEG_ALL? Application_short_name= "prod" id_flex_code= "key FLEX CODE" p_structure_code= "STRUCTURE NAME"
Note: in 11i It's p_structure_code, in R12 it's renamed to Id_flex_structure_code
6-concurrent Programs
Fndload Apps/[email protected] 0 Y DOWNLOAD $FND _top/patch/115/import/afcpprog.lct File_name.ldt program Application_ Short_name= "prod" concurrent_program_name= "CONCURRENT NAME"
7-value Sets
Fndload Apps/[email protected] 0 Y DOWNLOAD $FND _top/patch/115/import/afffload.lct File_name.ldt value_set flex_value_ Set_name= "Value set NAME"
8-value sets with values
Fndload Apps/[email protected] 0 Y DOWNLOAD $FND _top/patch/115/import/afffload.lct File_name.ldt value_set_value FLEX_ Value_set_name= "Value SET NAME"
9-profile Options
Fndload Apps/[email protected] 0 Y DOWNLOAD $FND _top/patch/115/import/afscprof.lct File_name.ldt profile Profile_name= " Profile option "Application_short_name=" prod "
10-request Group
Fndload Apps/[email protected] 0 Y DOWNLOAD $FND _top/patch/115/import/afcpreqg.lct File_name.ldt request_group REQUEST_ Group_name= "Request Group" application_short_name= "prod"
11-request Sets
Fndload Apps/[email protected] 0 Y DOWNLOAD $FND _top/patch/115/import/afcprset.lct File_name.ldt req_set application_ Short_name= "prod" request_set_name= "REQUEST SET"
12-responsibilities
Fndload Apps/[email protected] 0 Y DOWNLOAD $FND _top/patch/115/import/afscursp.lct File_name.ldt fnd_responsibility resp_key= "Responsibility"
13-responsibilities with all Security Groups
Fndload apps/<password> 0 Y DOWNLOAD fnd_top/patch/115/import/afscursp.lct <user>.ldt
Fnd_user user_name= "<USER>" security_group=% data_group_name=%
14-menu (Refer to Appendix B within the Oracle e-business Suite System Administrator's guide-configuration the for loader s on more information.)
Fndload apps/[email protected] 0 Y DOWNLOAD $FND _top/patch/115/import/afsload.lct File_name.ldt menu Menu_name= "Menu_ Name
15-forms/functions/personalizations: Refer to the System Administrator's Guide on dependencies
Fndload <userid>/<password> 0 Y DOWNLOAD $FND _top/patch/115/import/affrmcus.lct
<filename.ldt> fnd_form_custom_rules Form_name=<form name>
OR
Fndload <userid>/<password> 0 Y DOWNLOAD $FND _top/patch/115/import/afsload.lct File_name.ldt FUNCTION Function_name=<function_name>
OR
Fndload <userid>/<password> 0 Y DOWNLOAD $FND _top/patch/115/import/afsload.lct File_name.ldt FORM form_ Name=<form_name>
OR
Fndload <userid>/<password> 0 Y DOWNLOAD $FND _top/patch/115/import/affrmcus.lct <filename.ldt> fnd_ Form_custom_rules function_name=<function name>
16-user/responsibilities
Fndload apps/[email protected] 0 Y DOWNLOAD $FND _top/patch/115/import/afscursp.lct File_name.ldt fnd_user
17-alert
Fndload apps/pwd 0 Y DOWNLOAD
$ALR _TOP/PATCH/115/IMPORT/ALR.LCT My_file.ldt Alr_alerts
Application_short_name=fnd Alert_name=alert NAME to Downloa
18-blob
With Release 12.1.1, Fndload supports BLOB data (upload/download) to better serve Content-rich applications.
Fndload apps/pwd 0 Y mode configfile datafile entity [param ...]
19-overwrite Custom Definitions
Fndload Apps/apps 0 Y UPLOAD $FND _top/patch/115/import/.lct $
Xx_top/import/.ldt Custom_mode=force
20-load an NLS Language
Fndload <apps usr>/<apps pwd> 0 Y UPLOAD <controlfile.lct> <datafile.ldt> \
-Upload_mode=nls Custom_mode=force Warnings=true
21-migrate The role registration process from one instance to another
A. Navigate to the path: $FND _top/patch/115/import/us/umxrgsvc.ldt
B. The following command can used to download:
Fndload apps/<passwd>@ (instance name) O Y DOWNLOAD $FND _top/patch/115/import/umxrgsvc.lct Umxrgsvc.ldt umx_reg_ SERVICES Reg_service_code UMX
C. The following command can used to upload:
Fndload apps/<passwd>@ (instance name) O Y UPLOAD $FND _top/patch/115/import/umxrgsvc.lct Umxrgsvc.ldt umx_reg_ SERVICES Reg_service_code UMX
22-transfer Custom Messages to another Instance
A. Download the message from the source instance.
Fndload Apps/apps 0 Y DOWNLOAD @FND:p atch/115/import/afmdmsg.lct Password.ldt fnd_new_messages application_short_name= FND Message_name=password-invalid-no-spec-char
B. Move the custom LDT file (Password.ldt) over to the destination instance.
C. Upload the custom message to the destination instance.
Fndload Apps/apps 0 Y UPLOAD @FND:p atch/115/import/afmdmsg.lct Password.ldt fnd_new_messages application_short_name= FND Custom_mode=force
23-download UMX Roles and Role assignment data from one instance and upload to another.
To download from one instance:
Fndload <username/[email protected]> 0 Y DOWNLOAD $FND _top/patch/115/import/afrole.lct
Umxroles.ldt Wf_role orig_system=umx%
To upload to another instance:
Fndload <username/[email protected]> 0 Y UPLOAD $FND _top/patch/115/import/afrole.lct
Umxroles.ldt
Note:
You can only use Fndload utility to download entire DFF/KFF and not the specific structure/context.
So there are no options to download specific context/structure so far.
References:
· Oracle Applications Systems Administrator guide-configuration
Notes:
1. Give special attention when downloading Menus or responsibilities. In the case for several developers modifying responsibilities and Menus, then be very careful. Not being careful would mean that untested Forms, Functions, and Menus would become available in the clients Production ENVI Ronment Besides the tested Forms, Functions, and Menus.
2. Be very careful when downloading Flexfields, reference value sets with independent values for GL Segment Codes. By doing so, downloading and extracting all the "test data in GL Codes", might not being applicable for production.
3. There is several variations possible for fndload. For example, restricting the download and upload to specific segments within descriptive flexfields.
4. Fndload is very reliable and stable, if used properly.
5. Please test the fndload properly, so as to ensure, no unexpected data occurs.
6. As the name suggests, Fndload is usedful for FND related objects. However, in any implementation, it's required to migrate the setups in financials and Oracle HRMS from one environment to another. Oracle ISetup can used for this. Some of the things that can be migrated using Oracle ISetup is GL Set of Books, HR Organization structures, HRMS Employee s, Profiles Options Setup, Suppliers, Customers, tax Codes & tax Rates, financials Setup, Accounting calendars, Chart o F Accounts, GL currencies.
Diagnostics & Utilities Community:
- Diagnostics
For the latest diagnostics, please reference Document 421245.1 e-business Suite diagnostics References for R12.
- Utilities Community
Visit the Utilities community for help from industry experts or to share knowledge.
@1080052.1, 602267.1, 566865.1, 252853.1, 364558.1, 270827.1, 434724.1, 745689.1, 316600.1, 1258975.1, 1213895.1, 409014. 1, 736971.1, 301019.1
Tips and Examples Using fndload (DOC ID 735338.1)