FNDLOAD

The Generic Loader (FNDLOAD) is a concurrent program that can transfer Oracle Application entity data between database and text file. The loader reads a configuration file to determine which entity to access. In simple words FNDLOAD is used to transfer entity data from one instance/database to other. For example if you want to move a concurrent program/menu/value sets developed in DEVELOPMENT instance to PRODUCTION instance you can direct use this command.

How it works
Conversion between database format and text file format is specified by a configuration file. Oracle does provide confirmation file and it is important to just pass the configuration file name and then just call the loader and leave everything .The schematic visual representation of the loader is like:

What can be done?

These are 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 Attachments Messages Value Sets and Values Lookup Types

User Responsibilities Printer Definitions FND Dictionary Help Configuration Document Sequences Concurrent Manager Schedules

The Syntax
To use FNDLOAD, the following syntax is needed. FNDLOAD apps/appspwd 0 Y mode configfile datafile entity [parameter1..] As you can see, some info is needed.- First you will need to know the Apps password. The mode is either DOWNLOAD or UPLOAD. The configfile is the file that Fndload needs to download on upload data. The data file is the output file, in which the downloaded data is written The entity is the entity you want to download, Parameters van is passed to download a certain Alert

Modes of Operation
FNDLOAD always have two modes Upload Download

Example of download: FNDLOAD apps/pwd O Y DOWNLOAD $FND_TOP/patch/115/import/afcpprog.lct myfile.ldt PROGRAM APPLICATION_SHORT_NAME =<application_short_name> CONCURRENT_PROGRAM_NAME = concurrent_program_short_name>

Example of Upload FNDLOAD apps/pwd O Y UPLOAD $FND_TOP/patch/115/import/afcpprog.lct myfile.ldt PROGRAM APPLICATION_SHORT_NAME =<application_short_name> CONCURRENT_PROGRAM_NAME = concurrent_program_short_name>

Load Options:
Application level OR single entity level download (Ex) Download all the profile options of Inventory or just the INV: Default Primary UOM

Entire OR Partial upload of a data file (Ex) Upload the entire myfile.ldt or just a single entity indicated by and mode UPLOAD or UPLOAD_PARTIAL Entity name required for UPLOAD_PARTIAL mode

Custom mode force update To override Oracles 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

Config File Location

By default Oracle delivers most of configuration files you can use to download certain entities. Configuration files with extension .lct On Unix - all the configuration files are in $FND_TOP/patch/115/import directory On Unix Oracle also places the original configuration files in $FND_TOP/admin/import directory

Data files with extension .ldt

FNDLOAD File Structures

The config files (.lct) are 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 - (Ex) Concurrent Program download

Take a note FNDLOAD File Structures

The data files (.ldt) have both entity definition and the data It also shows the version and the location of the config file (.lct) that was used Without the config file, data file is useless Without the data file, config file is meaningless

NOTES:
Key files: .lct and .ldt You must run the FNDLOAD as apps user not as applsys or any other, otherwise you will receive Ora-6550 Both are easily readable, editable and portable

DO NOT MODIFY Oracles .lct files Use your favorite editor (I would suggest Textpad or Editplus) to manipulate only the .ldt files but be 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 faster (Why cant I access that? What is that profile option name, value and level? What is the value set used for that DFF segment attribute10 etc.) Partial string searches (which value set has Priority something in its where clause? etc) Give special attention when downloading Menus or Responsibilities. In case your client has several developers modifying Responsibilities and Menus, then be ultra careful. Not being careful will mean that untested Forms and Functions will become available in your clients Production environment besides your tested forms, functions and menus. Be very careful when downloading flexfields that reference value sets with independent values for GL Segment Codes. By doing so, you will download and extract all the test data in GL Codes that might not be applicable for production. There are several variations possible for FNDLOAD, for example you can restrict the download and uploads to specific segments within Descriptive Flex Fields. Please amend the above examples as desired for applying appropriate filtrations. FNDLOAD is very reliable and stable, if used properly. This happens to by one of my favorite Oracle utilities. Last but not the least, please test your FNDLOAD properly, so as to ensure that you do not get any unexpected data. In past I have noticed undesired results when the Lookup gets modified manually directly on production, and then the FNDLOAD is run for similar changes. If possible, try to follow a good practice of modifying FNDLOADable data only by FNDLOAD on production environment. As the name suggests, FNDLOAD is useful for FND Related objects. However in any implementation, you will be required to migrate the Setups in Financials and Oracle HRMS from one environment to another. For this you can use iSetup. "Oracle iSetup". Some of the things that can be migrated using Oracle iSetup are GL Set of Books, HR Organization Structures, HRMS Employees, Profile Options Setup, Suppliers, Customers, Tax Codes & Tax Rates, Financials Setup, Accounting Calendars, Chart of Accounts, GL Currencies.

Steps to Move a Concurrent program from one instance (Database) to other

Define your concurrent program and save it in first instance(for how to register a concurrent program click here) Connect to your UNIX box on first instance and run the following command to download the .ldt file FNDLOAD apps/apps O Y DOWNLOAD $FND_TOP/patch/115/import/afcpprog.lct file_name.ldt PROGRAM APPLICATION_SHORT_NAME="Concurrent program application short name" CONCURRENT_PROGRAM_NAME="concurrent program short name" Move the downloaded .ldf file to new instance(Use FTP) Connect to your UNIX box on second instance and run the following command to upload the .ldt file

FNDLOAD apps/apps 0 Y UPLOAD $FND_TOP/patch/115/import/afcpprog.lct file_name.ldt Note: Make sure you are giving proper .lct file in the commands and dont confuse with .lct and .ldt files

Sample Script Code for these Objects:

1 - Printer Styles
FNDLOAD apps/apps@seed115 O Y DOWNLOAD $FND_TOP/patch/115/import/afcppstl.lct file_name.ldt STYLE PRINTER_STYLE_NAME=printer style name

2 - Lookups
To Download FNDLOAD apps/APPS_PWD 0 Y DOWNLOAD aflvmlu.lct XX_TRX_BATCH_STATUS.ldt FND_LOOKUP_TYPE APPLICATION_SHORT_NAME ='TMPW' LOOKUP_TYPE="XX_TRX_BATCH_STATUS" XX_TRX_BATCH_STATUS is the name of FND Lookup Type in this example. This will download all the lookup codes within the defined lookup. To upload FNDLOAD apps/$CLIENT_APPS_PWD 0 Y UPLOAD aflvmlu.lct XX_TRX_BATCH_STATUS.ldt Lookup values To Download FNDLOAD apps/APPS_PWD 0 Y DOWNLOAD aflvmlu.lct XX_TRX_BATCH_STATUS.ldt FND_LOOKUP_TYPE APPLICATION_SHORT_NAME ='TMPW' LOOKUP_TYPE="XX_TRX_BATCH_STATUS" XX_TRX_BATCH_STATUS is the name of FND Lookup Type in this example. This will download all the lookup codes within the defined lookup. To upload FNDLOAD apps/APPS_PWD 0 Y UPLOAD aflvmlu.lct XX_TRX_BATCH_STATUS.ldt

3 - Descriptive Flexfield with all of specific Contexts

To Download $FND_TOP/bin/FNDLOAD apps/APPS_PWD 0 Y DOWNLOAD $FND_TOP/patch/115/import/afffload.lct XX_PO_REQ_HEADERS_DFF.ldt DESC_FLEX APPLICATION_SHORT_NAME=PO DESCRIPTIVE_FLEXFIELD_NAME='PO_REQUISITION_HEADERS'

PO is the Application Short name against which descriptive flexfield against PO Headers is registered PO_REQUISITION_HEADERS is the name of Descriptive Flexfield against PO Requisition Headers Another example for DFF against FND_LOOKUPS FNDLOAD apps/APPS_PWD 0 Y DOWNLOAD $FND_TOP/patch/115/import/afffload.lct XX_FND_COMMON_LOOKUPS_DFF.ldt DESC_FLEX APPLICATION_SHORT_NAME=FND DESCRIPTIVE_FLEXFIELD_NAME='FND_COMMON_LOOKUPS' Use the SQL below to find the name of DFF, rather than logging into the screen. SELECT application_id, descriptive_flexfield_name, application_table_name FROM fnd_descriptive_flexs_vl WHERE application_table_name like '%' || upper('&tab_name') || '%' ORDER BY application_table_name To upload $FND_TOP/bin/FNDLOAD apps/APPS_PWD 0 Y UPLOAD $FND_TOP/patch/115/import/afffload.lct XX_PO_REQ_HEADERS_DFF.ldt

4 - Key Flexfield Structures

FNDLOAD apps/apps O Y DOWNLOAD $FND_TOP/patch/115/import/afffload.lct XXKFFNAME.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

5 - Concurrent Programs
To Download FNDLOAD apps/$CLIENT_APPS_PWD O Y DOWNLOAD $FND_TOP/patch/115/import/afcpprog.lct XX_CUSTOM_ORACLE_INTERFACE_PROG.ldt PROGRAM APPLICATION_SHORT_NAME="TMPW" CONCURRENT_PROGRAM_NAME="XX_CUSTOM_ORACLE_INTERFACE_PROG" TMPW will be your custom TMP Application Short name where concurrent program is registered. XX_CUSTOM_ORACLE_INTERFACE_PROG.ldt is the file where concurrent program definition will be extracted. To upload

FNDLOAD apps/$CLIENT_APPS_PWD O Y UPLOAD $FND_TOP/patch/115/import/afcpprog.lct XX_CUSTOM_ORACLE_INTERFACE_PROG.ldt

6 - Value Sets FNDLOAD apps/apps@seed115 O Y DOWNLOAD $FND_TOP/patch/115/import/afffload.lct file_name.ldt VALUE_SET FLEX_VALUE_SET_NAME=value set name 7 - Value sets with values FNDLOAD apps/apps@seed115 O Y DOWNLOAD $FND_TOP/patch/115/import/afffload.lct file_name.ldt VALUE_SET_VALUE FLEX_VALUE_SET_NAME=value set name

8 - Profile Options
To Download FNDLOAD apps/APPS_PWD O Y DOWNLOAD $FND_TOP/patch/115/import/afscprof.lct POR_ENABLE_REQ_HEADER_CUST.ldt PROFILE PROFILE_NAME="POR_ENABLE_REQ_HEADER_CUST" APPLICATION_SHORT_NAME="ICX" POR_ENABLE_REQ_HEADER_CUST is the short name of profile option. To Upload FNDLOAD apps/APPS_PWD O Y UPLOAD $FND_TOP/patch/115/import/afscprof.lct POR_ENABLE_REQ_HEADER_CUST.ldt 9- Request Groups To Download FNDLOAD apps/APPS_PWD O Y DOWNLOAD $FND_TOP/patch/115/import/afcpreqg.lct XX_MY_REPORT_GROUP_NAME.ldt REQUEST_GROUP REQUEST_GROUP_NAME= XX_MY_REPORT_GROUP_NAME" APPLICATION_SHORT_NAME= "TMPW" XX_MY_REPORT_GROUP_NAME Will be the name of your request group To upload this Request Group in other environment after having transferred the .ldt file. To Upload FNDLOAD apps/APPS_PWD O Y UPLOAD $FND_TOP/patch/115/import/afcpreqg.lct XX_MY_REPORT_GROUP_NAME.ldt

10 - Request Sets
To Download

There are two steps to download firstly required to download the request set definition. Next you will be required to download the Sets Linkage definition. FNDLOAD apps/APPS_PWD 0 Y DOWNLOAD $FND_TOP/patch/115/import/afcprset.lct XX_GL_MY_INTERFACE_SET.ldt REQ_SET REQUEST_SET_NAME= "FNDRSSUB4610101_Will_look_like_this" FNDLOAD apps/APPS_PWD 0 Y DOWNLOAD $FND_TOP/patch/115/import/afcprset.lct XX_GL_MY_INTERFACE_SET_LINK.ldt REQ_SET_LINKS REQUEST_SET_NAME= "FNDRSSUB4610101_Will_look_like_this" To Upload FNDLOAD apps/APPS_PWD 0 Y UPLOAD $FND_TOP/patch/115/import/afcprset.lct XX_GL_MY_INTERFACE_SET.ldt FNDLOAD apps/APPS_PWD 0 Y UPLOAD $FND_TOP/patch/115/import/afcprset.lct XX_GL_MY_INTERFACE_SET_LINK.ldt

11 - Responsibilities
To Download FNDLOAD apps/APPS_PWD O Y DOWNLOAD $FND_TOP/patch/115/import/afscursp.lct XX_PERSON_RESPY.ldt FND_RESPONSIBILITY RESP_KEY="XX_PERSON_RESPY" XX_PERSON_RESPY is the responsibility key To upload FNDLOAD apps/$CLIENT_APPS_PWD O Y UPLOAD $FND_TOP/patch/115/import/afscursp.lct XX_PERSON_RESPY.ldt 12 - Menus To Download FNDLOAD apps/APPS_PWD O Y DOWNLOAD $FND_TOP/patch/115/import/afsload.lct ICX_POR_SSP_HOME.ldt MENU MENU_NAME="ICX_POR_SSP_HOME" Oracle Menus are not attached to applications. Hence no need to include application short name ICX_POR_SSP_HOME is the menu name. This can be validated via below SQL. select user_menu_name from fnd_menus_vl where menu_name = 'ICX_POR_SSP_HOME'; Also note that we do not pass in the User_menu_name in this example To Upload

FNDLOAD apps/APPS_PWD O Y UPLOAD $FND_TOP/patch/115/import/afsload.lct ICX_POR_SSP_HOME.ldt

13 Forms/Functions

Form
To Download FNDLOAD apps/pwd O Y DOWNLOAD $FND_TOP/patch/115/import/afsload.lct XX_MCCAAC.ldt FORM APPLICATION_SHORT_NAME="TMPW" FORM_NAME="XX_MCCAAC" To Upload FNDLOAD apps/pwd O Y UPLOAD $FND_TOP/patch/115/import/afsload.lct XX_MCCAAC.ldt

Function
To Download FNDLOAD apps/pwd O Y DOWNLOAD $FND_TOP/patch/115/import/afsload.lct XXFUNNAME.ldt FUNCTION FUNC_APP_SHORT_NAME="TMPW" FUNCTION_NAME="XX_FUNC_NAME" To Upload FNDLOAD apps/pwd O Y UPLOAD $FND_TOP/patch/115/import/afsload.lct XXFUNNAME.ldt

Note: - Download and Upload of function downloads the form itself. 14. User/Responsibilities
To Download FNDLOAD apps/apps@seed115 0 Y DOWNLOAD @FND:patch/115/import/afscursp.lct file_name.ldt FND_USER To Upload FNDLOAD apps/apps@seed115 0 Y UPLOAD [UPLOAD_PARTIAL] @FND:patch/115/import/afscursp.lct file_name.ldt FND_USER [<USER>]

Alerts:
To Download $FND_TOP/bin/FNDLOAD apps/apps 0 Y DOWNLOAD $ALR_TOP/patch/115/import/alr.lct OTA.ldt ALR_ALERTS APPLICATION_SHORT_NAME='OTA' ALERT_NAME= 'URALERT' To Upload $FND_TOP/bin/FNDLOAD apps/apps 0 Y DOWNLOAD $ALR_TOP/patch/115/import/alr.lct OTA.ldt

Forms Personalization:
To Download

FNDLOAD apps/$CLIENT_APPS_PWD 0 Y DOWNLOAD $FND_TOP/patch/115/import/affrmcus.lct XX_PERWSHRG.ldt FND_FORM_CUSTOM_RULES function_name="PERWSHRG-404" To Upload FNDLOAD apps/$CLIENT_APPS_PWD 0 Y DOWNLOAD $FND_TOP/patch/115/import/affrmcus.lct

Messages:
To download a single message FNDLOAD apps/$CLIENT_APPS_PWD 0 Y DOWNLOAD $FND_TOP/patch/115/import/afmdmsg.lct \XX_ICX_POR_LIFECYCLE_PAY_TIP.ldt FND_NEW_MESSAGES APPLICATION_SHORT_NAME='ICX' MESSAGE_NAME=XX_ICX_POR_LIFECYCLE_PAY_TIP To download a all message in the Application FNDLOAD apps/$CLIENT_APPS_PWD 0 Y DOWNLOAD $FND_TOP/patch/115/import/afmdmsg.lct \ XX_ALL_GMS_MESSAGES_00.ldt FND_NEW_MESSAGES APPLICATION_SHORT_NAME='TMPW' TO Upload FNDLOAD apps/$CLIENT_APPS_PWD 0 Y UPLOAD $FND_TOP/patch/115/import/afmdmsg.lct XX_ICX_POR_LIFECYCLE_PAY_TIP.ldt