FNDLOAD

Oracle provides a generic tool called FNDLOAD, which can be used for migration of FND entities from one instance to another. For example, the lookups and responsibilities created in development instance can be downloaded in a file and then uploaded into a test or production instance. This saves lot of time in configuration and is usually preferred over recreating the data manually in all the instances.
 
In an oracle implementation, usually setups are done in a development instance which need to be migrated to test and production instance. FNDLOAD can be used to create data files from the source instance and then this data file uploaded to target instance. The data file thus downloaded can be moved from one instance to another instance as a source controlled file.
 Some of the examples of the entities which can be migrated using FNDLOAD are:
· Attachment Definition
· Concurrent Programs
· Printers and Printer Styles
· Value-Sets
· Request Groups
· Request Sets
· Form Personalization
· Lookups
· Responsibilities
· Applications
· Profile Options
· Users
· Form, Functions and Menus
· Document Sequences
· Descriptive and Key Flex Fields


How FNDLOAD works

FNDLOAD is basically a concurrent program, run from command prompt. The script can either download or upload the data depending upon the parameter passed. To download data for a particular entity, it makes use of a definition file (called .lct file). These definition files are standard files (for each standard entity) and are available in the directory, $FND_TOP/patch/115/import/. For example, to download a concurrent program, a definition file afcpprog.lct is used.
Output data file is created with an extension .ldt. This data file can then subsequently be uploaded into other environment using FNDLOAD command with upload parameter.
For example, suppose there is a concurrent program defined in development instance. We want to migrate this concurrent program from development to Test instance. The can be achieved using the following two steps:

a. Run the FNDLOAD command (in Development instance) in DOWNLOAD mode, using definition file afcpprog.lct to create a .ldt file.
b. Run the FNDLOAD command (in Test instance) in UPLOAD mode, using the data file created in step (a) above.

FNDLOAD Command

FNDLOAD is run from Unix environment. It can be run for upload or download. The syntax of upload and download are as follows:

FNDLOAD logon 0 Y mode configfile datafile [ entity [ param ... ] ]

Logon is apps user and apps password, For example apps/apps.
Mode can be DOWNLOAD or UPLOAD
Configfile is a standard .lct file which is available in $FND_TOP/patch/115/import directory.
Datafile is a .ldt file which contains the downloaded data. The name of datafile can be any user defined name; however extension should be given as .ldt.
Entity is name of the entity (explained further).
Param is Name=Value string used for parameter substitution (explained further).

Standard Configuration files
Oracle has provided standard configuration files (.lct files) for migration of the standard entities. All of these configuration files are available at $FND_TOP/patch/115/import directory. The main configuration files are given below:

Entity	Configuration File
Attachment Definition	afattach.lct
Concurrent Programs	afcpprog.lct
Printers and Printer Styles	afcppstl.lct, afcpprnt.lct
Value Sets	afffload.lct
Request Groups	afcpreqg.lct
Request Sets	afcprset.lct
Form Personalization	affrmcus.lct
Lookups	aflvmlu.lct
Responsibilities	afrole.lct
Applications	afscapp.lct
Profile Options	afscprof.lct
Users	afscursp.lct
Form, Functions, Menus	afsload.lct
Document Sequences	afsncat.lct
Descriptive and Key Flex Fields	afffload.lct
Messages	afmdmsg.lct

Examples on Upload Download of Commonly used Entities

Concurrent Program

Download

FNDLOAD apps/<password> O Y DOWNLOAD $FND_TOP/patch/115/import/afcpprog.lct file_name.ldt PROGRAM APPLICATION_SHORT_NAME="<Short Application Name>" CONCURRENT_PROGRAM_NAME="<concurrent program short name>"

Upload

FNDLOAD apps/<password> 0 Y UPLOAD $FND_TOP/patch/115/import/afcpprog.lct file_name.ldt

Printer Styles
FNDLOAD apps/apps O Y DOWNLOAD $FND_TOP/patch/115/import/afcppstl.lct file_name.ldt STYLE PRINTER_STYLE_NAME="printer style name"
Lookups
FNDLOAD apps/apps O Y DOWNLOAD $FND_TOP/patch/115/import/aflvmlu.lct file_name.ldt FND_LOOKUP_TYPE APPLICATION_SHORT_NAME="FND"
LOOKUP_TYPE="lookup name"

Descriptive Flexfield
FNDLOAD apps/apps O 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="FND" DESCRIPTIVE_FLEXFIELD_NAME="desc flex name" P_CONTEXT_CODE="context name"

Key Flexfield Structures
FNDLOAD apps/apps O 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="FND" ID_FLEX_CODE="key flex code" P_STRUCTURE_CODE="structure name"

Value Sets with values
FNDLOAD apps/apps O Y DOWNLOAD $FND_TOP/patch/115/import/afffload.lct file_name.ldt VALUE_SET FLEX_VALUE_SET_NAME="value set name"
Profile Options
 FNDLOAD apps/apps O Y DOWNLOAD $FND_TOP/patch/115/import/afscprof.lct file_name.ldt PROFILE PROFILE_NAME="profile option" APPLICATION_SHORT_NAME="FND"
Request GroupsFNDLOAD apps/apps O Y DOWNLOAD $FND_TOP/patch/115/import/afcpreqg.lct file_name.ldt REQUEST_GROUP REQUEST_GROUP_NAME="request group" APPLICATION_SHORT_NAME="FND"
Request Sets
FNDLOAD apps/apps O Y DOWNLOAD $FND_TOP/patch/115/import/afcprset.lct file_name.ldt REQ_SET
APPLICATION_SHORT_NAME="FND" REQUEST_SET_NAME="request set"
ResponsibilitiesFNDLOAD apps/apps O Y DOWNLOAD $FND_TOP/patch/115/import/afscursp.lct file_name.ldt FND_RESPONSIBILITY RESP_KEY="responsibility"
MenusFNDLOAD apps/apps O Y DOWNLOAD $FND_TOP/patch/115/import/afsload.lct file_name.ldt MENU MENU_NAME="menu_name"
Forms PersonalizationFNDLOAD apps/apps 0 Y DOWNLOAD $FND_TOP/patch/115/import/affrmcus.lct file_name.ldt FND_FORM_CUSTOM_RULES function_name=FUNCTION_NAME