FNDLOAD

As the name suggests, FNDLOAD is useful for FND related objects. The FNDLOAD can download data from an application entity into a portable, editable text file. This file can then be uploaded into any other database to copy the data. Conversion between database store and file format is specified by a configuration file that is read by the loader.

From an 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 the same.

FNDLOAD can be executing from command prompt or as concurrent program (Generic Loader) as provided by Oracle. Data structures supported by the loader include master-detail relationships and foreign key reference relationships.

The FNDLOAD downloads data from a database according to a configuration (.lct) file, and converts the data into a data file (.ldt file). The FNDLOAD can then upload this data to another database using a configuration file.

The FNDLOAD operates in one of two modes: download or upload. In the download mode, data is downloaded from the database to a text file; in the upload mode, data is uploaded from a text file to the database.

What can be done?

1. Concurrent Programs, Executable 
2. Request Groups, Request Sets 
3. Profile Option 
4. Key and Descriptive Flexfields 
5. Menus and Responsibilitie 
6. Forms and Form Functions/Personalization 
7. Attachment 
8. Messages 
9. Value Sets and Values 
10. Lookup Types 
11. User Responsibilities 
12. Printer Definitions 
13. FND Dictionary 
14. Help Configuration 
15. Document Sequences 
16. Alerts 
17. Concurrent Manager Schedules 
18. Data Definition 
19. AME configuration
20. WebAdi

Advantages when using FNDLOAD

• Because downloaded data is stored in a text file, version administration is possible
• There is nothing to worry to go to purchase because Investment = 0$
• No learning curve. this is relief for developer and dba
• Fully supported and recommended by Oracle
• Capture the migrations in a file and use it during installations, clones etc. to migrate in batch
• Pin-point when something happened and where (database) easily 
• Your AOL data migration process is now simplified and streamlined goal attained

Disadvantages

• Applications patching mechanisms use FNDLOAD heavily possibility of negative impact is not zero 
• UPLOAD_MODE=REPLACE only for menus
•  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 Or run the following script on Command line:

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 is 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 be uploaded to the database. DOWNLOAD causes the loader to fetch rows and write them to the datafile.

<config file>
The configuration file to use (usually with a suffix of .lct, but not enforced or supplied by the loader).

<data file>
The data file to write (usually with a suffix of .ldt, but not enforced or supplied by the loader). If the data file already exists, it will 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 are used to provide bind values in the access SQL (both UPLOAD and DOWNLOAD). Each parameter is in the form NAME=VALUE. NAME should not conflict with an attribute name for the entities being loaded.