Velcro Item Routing Attachments xFNDLOAD

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/valuesets developed in DEVELOPMENT instance to PRODUCTION instance you can direct use this command. 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 These following are the other entity data types that we can move with FNDLOAD 1 - 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" 2 - 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" 3 - Descriptive Flexfield with all of specific Contexts 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"

4 - 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" 5 - Concurrent Programs FNDLOAD apps/apps O Y DOWNLOAD $FND_TOP/patch/115/import/afcpprog.lct file_name.ldt PROGRAM APPLICATION_SHORT_NAME="FND" CONCURRENT_PROGRAM_NAME="concurrent name" 6 - Value Sets FNDLOAD apps/apps O Y DOWNLOAD $FND_TOP/patch/115/import/afffload.lct file_name.ldt VALUE_SET_VALUE FLEX_VALUE_SET_NAME="value set name" 7 - 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" 8 - 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" 8 - Request Groups FNDLOAD 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" 10 - 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" 11 - Responsibilities FNDLOAD apps/apps O Y DOWNLOAD $FND_TOP/patch/115/import/afscursp.lct file_name.ldt FND_RESPONSIBILITY RESP_KEY="responsibility" 12 - Menus FNDLOAD apps/apps O Y DOWNLOAD $FND_TOP/patch/115/import/afsload.lct file_name.ldt MENU MENU_NAME="menu_name" 13 - Forms Personalization FNDLOAD apps/apps 0 Y DOWNLOAD $FND_TOP/patch/115/import/affrmcus.lct file_name.ldt FND_FORM_CUSTOM_RULES function_name=FUNCTION_NAME

14 User Creation

FNDLOAD apps/apps 0 Y DOWNLOAD $FND_TOP/patch/115/import/afscursp.lct File_name.ldt FND_USER USER_NAME=user name'

13 Forms/Functions FNDLOAD apps/apps@seed115 0 Y DOWNLOAD $FND_TOP/patch/115/import/affrmcus.lct file_name.ldt FND_FORM_CUSTOM_RULES The Upload syntax for all styles: FNDLOAD apps/apps@seed115 0 Y UPLOAD $FND_TOP/patch/115/import/affrmcus.lct file_name.ldt

Note: UPLOAD command is same for all except replacing the .lct and passing any extra parameters if you want to pass FNDLOAD apps/apps 0 Y UPLOAD $FND_TOP/patch/115/import/corresponding.lct upload_file.ldt FNDLOAD is a built-in program that is located in our applications directory. e.g; C:\oracle\visappl\fnd\11.5.0\bin\fndload In case of Vision Install it will be in VISAPPL directory, while in case of production install it will be PRODAPPL directory. There are two steps of transferring data. 1. DOWNLOAD 2. UPLOAD We can download and upload responsibilities, value sets, profile options etc. There are two types of files that are used in this process that are .LCT & .LDT. Where .LCT are configuration files that are already located on our server. We have to find specific .LCT means configuration file of responsibility / value set or any thing we want to transfer. This is the script to download responsibility named XYZ_RESP INTO XYZRESP.LDT file $FND_TOP/bin/FNDLOAD apps/apps@VIS 0 Y DOWNLOAD $FND_TOP/patch/115/import/afscursp.lct XYZRESP.LDT FND_RESPONSIBILITY RESP_KEY=XYZ_RESP Similarly to upload

$FND_TOP/bin/FNDLOAD apps/apps@PROD O Y UPLOAD $FND_TOP/patch/115/import/afscursp.lct XYZRESP.ldt NOTE: i) We have to run these scripts into command prompt. ii) Instead of $FND_TOP/bin, we can write our path e.g; C:\oracle\visappl\fnd\11.5.0\bin -------------------------------------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 ---------------------------------------------------------

Thenwhat are advantages when using FNDLOAD are :

1. Because downloaded data is stored in a text file, version administration is 2.

3. 4. 5. possible There is nothing to worry to go to purchase because..Investment = 0$ No learning curve. this is relief for developer/dbas 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!!

6.
7.

And these are some Disadvantages also :

1. Applications patching mechanisms use FNDLOAD heavily possibility of

negative impact is not zero

2. UPLOAD_MODE=REPLACE only for menus 3. No validation against migrating database/instance sensitive data
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. T he 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 This is important because it would drive the whole flow, and it always be two mode .. Upload and Download Example of download: FNDLOADapps/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

apps/pwd 0 Y UPLOAD ${FND_TOP}/patch/115/import/afcpprog.lct myfile.ldt - CUSTOM_MODE=FORCE undocumented parameter

FNDLOAD WHAT IS FNDLOADLoad Options: Application level OR single entity level download o (Example) Download all the profile 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 enity 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 are supported, use UPLOAD_MODE= NLS

Then ..Where is Config File Located By default Oracle delivers most of configuration files you can use to download certain entities. Configuration files with extension .lct o On Unix - all the configuration files are 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

and..FNDLOAD File Structures is The config files (.lct) are delivered and maintained by Oracle It has entity definitions, parent-child relationships and user input parameters identified by :NAME o Downloading a parent automatically downloads all children - (Example) 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

..Remember regarding FNDLOAD Files 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)