Working with FNDLOAD in Oracle Apps Introduction to FNDLOAD FNDLOAD is an oracle utility used to download AOL components data from an application entity into an editable text file, which can be uploaded to another database or the same database. This utility is extensively used to download any AOL components like the Concurrent Programs, Value Sets, DFF, Responsibilities, Request groups etc. The downloaded components can then be easily uploaded into any other database or the same database as per the requirement. This is particularly useful during the Instance refresh or patching or during installations. The major components of the FNDLOAD are: Configuration File (.lct file): The configuration file is an Oracle seeded file which is provided by the oracle. This file is used to upload or download the AOL components into the database. The Conversion between database format and text file format is specified by a configuration file. The .lct file or the configuration file is specific to each type of AOL component that is under question. Each type of AOL component has a different configuration file. These are found in the location ‘$FND_TOP/patch/115/import’. The exhaustive list of .lct files available in oracle for different AOL entities is: Oracle Applications Datafile or .ldt file: The .ldt file is the data file in oracle applications which contains the downloaded data from the fndload. When we download an AOL component from the database, we have to give the .ldt file. This will hold the downloaded entity. Process: The Generic Loader downloads data from a database according to a configuration (.lct) file, and converts the data into a data file i.e. (.ldt file). The Generic Loader can then upload this data to another database using a configuration file. The loader operates in one of two modes: Download or Upload. In the download mode, the AOL component like the Concurrent Program is downloaded from the database in the form of an .ldt file. In the upload mode, AOL component is uploaded from a .ldt file to the database. FNDLOAD is designated to transfer Oracle Applications "setup" entities (concurrents, flexfields, menues etc.) FNDLOAD can't be used to transfer forms, reports etc. FNDLOAD Options: • Application level OR single entity level download This downloads all the objects at the application level. (Example) Download all the profile options of Inventory or just the INV: Default Primary UOM • Entire OR Partial upload of a data file This is used to upload just an individual entity or all entities in the .ldt file (Example) Upload the entire myfile.ldt or just a single enity indicated by - and mode UPLOAD or UPLOAD_PARTIAL Entity name required for UPLOAD_PARTIAL mode • Custom mode force update To override Oracle's upload algorithm and update the custom AOL data regardless, use CUSTOM_MODE= FORCE UPLOAD_MODE= REPLACE (only for menus) • Support for NLS uploads NLS data uploads for translated columns are supported, use UPLOAD_MODE= NLS You can give the FNDLOAD commands by logging in to the server. We have to use only the ‘APPS’ user for FNDLOAD.

Working with FNDLOAD in Oracle Apps

Introduction to FNDLOAD

FNDLOAD is an oracle utility used to download AOL components data from an application entity into an editable text file, which can be uploaded to another database or the same database.

This utility is extensively used to download any AOL components like the Concurrent Programs, Value Sets, DFF, Responsibilities, Request groups etc. The downloaded components can then be easily uploaded into any other database or the same database as per the requirement.

This is particularly useful during the Instance refresh or patching or during installations.

The major components of the FNDLOAD are:

Configuration File (.lct file):

The configuration file is an Oracle seeded file which is provided by the oracle.

This file is used to upload or download the AOL components into the database.

The Conversion between database format and text file format is specified by a configuration file.

The .lct file or the configuration file is specific to each type of AOL component that is under question.

Each type of AOL component has a different configuration file.

These are found in the location ‘$FND_TOP/patch/115/import’.

The exhaustive list of .lct files available in oracle for different AOL entities is:

Oracle Applications Datafile or .ldt file:

The .ldt file is the data file in oracle applications which contains the downloaded data from the fndload.

When we download an AOL component from the database, we have to give the .ldt file.

This will hold the downloaded entity.

Process:

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

The loader operates in one of two modes: Download or Upload.

In the download mode, the AOL component like the Concurrent Program is downloaded from the database in the form of an .ldt file.

In the upload mode, AOL component is uploaded from a .ldt file to the database.

FNDLOAD is designated to transfer Oracle Applications "setup" entities (concurrents, flexfields, menues etc.)

FNDLOAD can't be used to transfer forms, reports etc.

FNDLOAD Options:

• Application level OR single entity level download

• This downloads all the objects at the application level.
• (Example) Download all the profile options of Inventory or just the INV: Default Primary UOM

• Entire OR Partial upload of a data file

• This is used to upload just an individual entity or all entities in the .ldt file
• (Example) Upload the entire myfile.ldt or just a single enity indicated by - and mode UPLOAD or UPLOAD_PARTIAL
• Entity name required for UPLOAD_PARTIAL mode

• Custom mode force update

• To override Oracle's upload algorithm and update the custom AOL data regardless, use CUSTOM_MODE= FORCE
• UPLOAD_MODE= REPLACE (only for menus)

• Support for NLS uploads

• NLS data uploads for translated columns are supported, use UPLOAD_MODE= NLS

You can give the FNDLOAD commands by logging in to the server.

We have to use only the ‘APPS’ user for FNDLOAD.