Use FNDLOAD to upload and download apps setup data

As you asked me for a way to download a DFF (Descriptive Flex field) into an LDT file. Metalink note
274667.1 has the FNDLOAD Commands to Download Different Seed Data Types. Pasting the contents of the
note, just in case it disappears from metalink :)
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.
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"
Examples:
Note <274528.1> - Note How To Download Single Context Using FNDLOAD For Descriptive Flexfield.
Note <256573.1> - How To Download/Upload Descriptive Flexfield With Name $SRS$.
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"
Examples:
Note <247126.1> - How To Download Request Set Definition From One Instance And Upload On Another
Instance
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"
Oracle FNDLOAD Script Examples
In this article I wish to give real working examples of Oracle's FNDLOAD utility.
Besides that, I have included some useful notes on FNDLOAD utility
I have used FNDLOAD successfully in past for several different entities/data types within Oracle 11i for almost
all my previous clients, ever since this utility became available.
Some of the examples in this FNDLOAD article include:-
FNDLOAD to transfer Request Groups
FNDLOAD for moving Concurrent Programs
FNDLOAD to download and upload Forms Personalizations ( or Personalisations depending on where you are
located )
To FNDLOAD Web ADI, visit the link Web ADI FNDLOAD
Use FNDLOAD for transferring value set definitions.
-->Please note that when transferring Key Flex Fields and Descriptive flex fields the respective value sets
against each segment will be extracted and loaded automatically.
Also, FNDLOAD can be used to migrate Key FlexFields, Descriptive Flexfields, Responsibilities and almost
every other FND entity.
Please note that the text written down here could get wrapped in the browser.
Hence you may have to use \ to continue the single line command on Unix, in case you find the lines wrapping
In my case I am ensuring that $CLIENT_APPS_PWD has the apps password before running the scripts
------------------------------------------------------------------------------------------
##To FNDLOAD Request groups
FNDLOAD apps/$CLIENT_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="XXGMS"
##Note that
##---------
## <> will be your Application Shortname where request group is registered
## 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
FNDLOAD apps/$CLIENT_APPS_PWD O Y UPLOAD $FND_TOP/patch/115/import/afcpreqg.lct
------------------------------------------------------------------------------------------
##To FNDLOAD Concurrent Programs
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="XXGMS"
CONCURRENT_PROGRAM_NAME="XX_CUSTOM_ORACLE_INTERFACE_PROG"
##Note that
##---------
## XXGMS will be your custom GMS Application Shortname where concurrent program is registered
## XX_CUSTOM_ORACLE_INTERFACE_PROG
Will be the name of your request group
## 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
------------------------------------------------------------------------------------------
##To FNDLOAD Oracle Descriptive Flexfields
$FND_TOP/bin/FNDLOAD apps/$CLIENT_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'
##Note that
##---------
## PO is the Application Shortname against which descriptive flexfield against PO Headers is registered
## PO_REQUISITION_HEADERS
is the name of Descriptive Flexfield against PO Requisition Headers
## Use the SQL below to find the name of DFF, rather than logging into the screen (ooops via jinitiator)
########----->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 into another environment
$FND_TOP/bin/FNDLOAD apps/$CLIENT_APPS_PWD 0 Y UPLOAD
$FND_TOP/patch/115/import/afffload.lct XX_PO_REQ_HEADERS_DFF.ldt
## OK another example for DFF against FND_LOOKUPS
FNDLOAD apps/$CLIENT_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'
## OK another example for DFF against Project Accounting Expenditure Types
FNDLOAD apps/$CLIENT_APPS_PWD 0 Y DOWNLOAD $FND_TOP/patch/115/import/afffload.lct
XX_PA_EXPENDITURE_TYPES_DESC_FLEX_DFF.ldt DESC_FLEX
APPLICATION_SHORT_NAME=PA
DESCRIPTIVE_FLEXFIELD_NAME='PA_EXPENDITURE_TYPES_DESC_FLEX'
------------------------------------------------------------------------------------------
##To FNDLOAD Oracle Menus
$FND_TOP/bin/FNDLOAD apps/$CLIENT_APPS_PWD O Y DOWNLOAD
$FND_TOP/patch/115/import/afsload.lct ICX_POR_SSP_HOME.ldt MENU
MENU_NAME="ICX_POR_SSP_HOME"
##Note that
##---------
## 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
## OK, now to upload this file
$FND_TOP/bin/FNDLOAD apps/$CLIENT_APPS_PWD O Y UPLOAD
$FND_TOP/patch/115/import/afsload.lct ICX_POR_SSP_HOME.ldt
----------------------------------------------------------------------------------------------------------------------------
## Well, now for FND 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
## Or you may as well download all the messages within an 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='XXGMS'
## now to upload using FNDLOAD
FNDLOAD apps/$CLIENT_APPS_PWD 0 Y UPLOAD $FND_TOP/patch/115/import/afmdmsg.lct
XX_ICX_POR_LIFECYCLE_PAY_TIP.ldt
----------------------------------------------------------------------------------------------------------------------------
## Now it's the turn of Lookup values. Again, its not a rocket science
FNDLOAD apps/$CLIENT_APPS_PWD 0 Y DOWNLOAD aflvmlu.lct XX_TRX_BATCH_STATUS.ldt
FND_LOOKUP_TYPE APPLICATION_SHORT_NAME ='XXGMS'
LOOKUP_TYPE="XX_TRX_BATCH_STATUS"
## Note that
## 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
----------------------------------------------------------------------------------------------------------------------------
## You can also move the User definitions from FND_USER
FNDLOAD apps/$CLIENT_APPS_PWD 0 Y DOWNLOAD $FND_TOP/patch/115/import/afscursp.lct
./XX_FND_USER_PASSI.ldt FND_USER USER_NAME='ANILPASSI'
#Do not worry about your password being extracted, it will be encrypted as below in ldt file
#BEGIN FND_USER "ANILPASSI"
# OWNER = "PASSIA"
# LAST_UPDATE_DATE = "2005/10/19"
# ENCRYPTED_USER_PASSWORD = "ZGE45A8A9BE5CF4339596C625B99CAEDF136C34FEA244DC7A"
# SESSION_NUMBER = "0"
To upload the FND_USER using FNDLOAD command use
FNDLOAD apps/$CLIENT_APPS_PWD 0 Y UPLOAD $FND_TOP/patch/115/import/afscursp.lct
./XX_FND_USER_PASSI.ldt
Notes for using FNDLOAD against FND_USER:-
1. After uploading using FNDLOAD, user will be promoted to change their password again during their next
signon attempt.
2. All the responsibilities will be extracted by FNDLOAD alongwith User Definition in FND_USER
3. In the Target Environment , make sure that you have done FNDLOAD for new responsibilities prior to
running FNDLOAD on users.
----------------------------------------------------------------------------------------------------------------------------
## Now lets have a look at the profile option using oracle's FNDLOAD
FNDLOAD apps/$CLIENT_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"
## Note that
## POR_ENABLE_REQ_HEADER_CUST is the short name of profile option
## We aren't passing the user profile option name in this case. Validate using ...
########----->select application_id, PROFILE_OPTION_NAME || '==>' || profile_option_id || '==>' ||
########----->USER_PROFILE_OPTION_NAME
########----->from FND_PROFILE_OPTIONS_VL
########----->where PROFILE_OPTION_NAME like '%' || upper('&profile_option_name') || '%'
########----->order by PROFILE_OPTION_NAME
########----->/
## Now to upload
FNDLOAD apps/$CLIENT_APPS_PWD O Y UPLOAD $FND_TOP/patch/115/import/afscprof.lct
POR_ENABLE_REQ_HEADER_CUST.ldt
----------------------------------------------------------------------------------------------------------------------------
## Now for the request sets that contain the stages and links for underlying concurrent programs
## For this you will be firstly required to download the request set definition.
## Next you will be required to download the Sets Linkage definition
## Well, lets be clear here, the above sequence is more important while uploading
FNDLOAD apps/$CLIENT_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/$CLIENT_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"
## Note that FNDRSSUB4610101 can be found by doing an examine on the
########----->select request_set_name from fnd_request_sets_vl
########----->where user_request_set_name = 'User visible name for the request set here'
## Now for uploading the request set, execute the below commands
FNDLOAD apps/$CLIENT_APPS_PWD 0 Y UPLOAD $FND_TOP/patch/115/import/afcprset.lct
XX_GL_MY_INTERFACE_SET.ldt
FNDLOAD apps/$CLIENT_APPS_PWD 0 Y UPLOAD $FND_TOP/patch/115/import/afcprset.lct
XX_GL_MY_INTERFACE_SET_LINK.ldt
----------------------------------------------------------------------------------------------------------------------------
## Now for the responsibility
FNDLOAD apps/$CLIENT_APPS_PWD O Y DOWNLOAD $FND_TOP/patch/115/import/afscursp.lct
XX_PERSON_RESPY.ldt FND_RESPONSIBILITY RESP_KEY="XX_PERSON_RESPY"
## note that XX_PERSON_RESPY is the responsibility key
## Now to upload
FNDLOAD apps/$CLIENT_APPS_PWD O Y UPLOAD $FND_TOP/patch/115/import/afscursp.lct
XX_PERSON_RESPY.ldt
----------------------------------------------------------------------------------------------------------------------------
## OK, now for the forms personalizations
## For the forms personalizations, I have given three examples as below.
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"
FNDLOAD apps/$CLIENT_APPS_PWD 0 Y DOWNLOAD $FND_TOP/patch/115/import/affrmcus.lct
XX_HZ_ARXCUDCI_STD.ldt FND_FORM_CUSTOM_RULES function_name="HZ_ARXCUDCI_STD"
FNDLOAD apps/$CLIENT_APPS_PWD 0 Y DOWNLOAD $FND_TOP/patch/115/import/affrmcus.lct
XX_AP_APXVDMVD.ldt FND_FORM_CUSTOM_RULES function_name="AP_APXVDMVD"
## Note that the function name above is the function short name as seen in the Function Definition Screen
## Now to upload the forms personalizations that are defined against these forms functions....
FNDLOAD apps/$CLIENT_APPS_PWD 0 Y UPLOAD $FND_TOP/patch/115/import/affrmcus.lct
XX_PERWSHRG.ldt
FNDLOAD apps/$CLIENT_APPS_PWD 0 Y UPLOAD $FND_TOP/patch/115/import/affrmcus.lct
XX_HZ_ARXCUDCI_STD.ldt
FNDLOAD apps/$CLIENT_APPS_PWD 0 Y UPLOAD $FND_TOP/patch/115/import/affrmcus.lct
XX_AP_APXVDMVD.ldt
----------------------------------------------------------------------------------------------------------------------------
Notes :
1. Give special attention when downloading Menus or Responsibilities.
In case your client has several developers modifying Responsibilities and Menus, then be ultra carefull. Not
being carefull will mean that untested Forms and Functions will become available in your clients Production
environment besides your tested forms, functions and menus.
2. 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.
3. 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 filterations.
4. The list of examples by no mean cover all possible FNDLOAD entities.
5. FNDLOAD is very reliable and stable, if used properly. This happens to by one of my favourite Oracle
utilities.
4. 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.
5. 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.
Its all about FNDLOAD
What is Data Synchronization ?
Data Synchronization is a process in which some setup data would be synchronized, and this would be more
important when you are working in oracle application development/implementation project? The equally
important that AOL data Migration takes place necessary to synchronize the data across databases instance
during
Installations (New desc. flex field creations etc)
Upgrades (Apps upgrade etc)
Maintenance (Value set changes etc)
Then What.. FNDLOAD
Yes, that is one and only oracle solution. It can be defined as a concurrent program that can move Oracle
Applications data between database and text file representations. Or this can be defined as FNDLOAD can
download data from an application entity into an editable text file, which can be uploaded to another database.
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
Thenwhat are advantages when using FNDLOAD are :
1. Because downloaded data is stored in a text file, version administration is possible
2. There is nothing to worry to go to purchase because..Investment = 0$
3. No learning curve. this is relief for developer/dbas
4. Fully supported and recommended by Oracle
5. Capture the migrations in a file and use it during installations, clones etc. to migrate in batch
6. Pin-point when something happened and where (database) easily
7. Your AOL data migration process is now simplified and streamlined goal attained!!
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
FNDLOAD apps/pwd 0 Y UPLOAD ${FND_TOP}/patch/115/import/afcpprog.lct myfile.ldt -
CUSTOM_MODE=FORCE undocumented parameter
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 FNDLOADas 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)
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
FNDLOAD apps/apps@seed115 O Y DOWNLOAD $FND_TOP/patch/115/import/aflvmlu.lct file_name.ldt
FND_LOOKUP_TYPE APPLICATION_SHORT_NAME="prod" LOOKUP_TYPE="lookup name"
3 - Descriptive Flexfield with all of specific Contexts
FNDLOAD apps/apps@seed115 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="prod" DESCRIPTIVE_FLEXFIELD_NAME="desc flex name"
P_CONTEXT_CODE="context name"
4 - Key Flexfield Structures
FNDLOAD apps/apps@seed115 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="prod" ID_FLEX_CODE="key flex code"
P_STRUCTURE_CODE="structure name"
5 - Concurrent Programs
FNDLOAD apps/apps@seed115 O Y DOWNLOAD $FND_TOP/patch/115/import/afcpprog.lct file_name.ldt
PROGRAM APPLICATION_SHORT_NAME="prod" CONCURRENT_PROGRAM_NAME="concurrent
name"
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
FNDLOAD apps/apps@seed115 O Y DOWNLOAD $FND_TOP/patch/115/import/afscprof.lct file_name.ldt
PROFILE PROFILE_NAME="profile option" APPLICATION_SHORT_NAME="prod"
9 - Requset Group
FNDLOAD apps/apps@seed115 O Y DOWNLOAD $FND_TOP/patch/115/import/afcpreqg.lct file_name.ldt
REQUEST_GROUP REQUEST_GROUP_NAME="request group" APPLICATION_SHORT_NAME="prod"
10 - Request Sets
FNDLOAD apps/apps@seed115 O Y DOWNLOAD $FND_TOP/patch/115/import/afcprset.lct file_name.ldt
REQ_SET APPLICATION_SHORT_NAME="prod" REQUEST_SET_NAME="request set"
11 - Responsibilities
FNDLOAD apps/apps@seed115 O Y DOWNLOAD $FND_TOP/patch/115/import/afscursp.lct file_name.ldt
FND_RESPONSIBILITY RESP_KEY="responsibility
12 - Menus
FNDLOAD apps/apps@seed115 O Y DOWNLOAD $FND_TOP/patch/115/import/afsload.lct file_name.ldt
MENU MENU_NAME="menu_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
14. User/Responsibilities
FNDLOAD apps/apps@seed115 0 Y DOWNLOAD @FND:patch/115/import/afscursp.lct file_name.ldt
FND_USER Then UPLOAD FNDLOAD apps/apps@seed115 0 Y UPLOAD [UPLOAD_PARTIAL]
@FND:patch/115/import/afscursp.lct file_name.ldt FND_USER [<USER>]
References:
Oracle Applications Systems Administrators Guide
Metalink Notes: 117084.1, 228614.1 232029.1 , 274667.1
Moving Personalizations between instances FNDLOAD for Form Personalization
Most of developer always struggle when ever it come to migration of form personalization component, beacuse
of limitation of full access in Production box. Therefore, It's better to use oracle seeded Migration tool
!"#$%".
$nce you created and done testing for personalizations in your development&test instance, you can move them
to production instances.
%s discussed in last post, Personalization is per unction not per form therefore this can extracted by the loader
on a per'function basis.
(ou should ta)e a note that upon uploading, all prior personalizations for that function are first deleted, and then
the contents of the loader file are inserted. *o be careful..+
FNDLOAD - A pain killer for migration
you can either "ownload for a specific form or specfic function of the form. In both the case same affrmcus.lct
is used.
Download -specific form< /STRONG
!"#$%" ,userid-&,password- . ( "$/!#$%" 0!"1T$P&patch&223&import&affrmcus.lct
,filename.ldt- !"1$4M156*T$M146#7*
form1name8,form name-, &$!T-
Download -for all personali!ations, &$!T-
!"#$%" ,userid-&,password- . ( "$/!#$%" 0!"1T$P&patch&223&import&affrmcus.lct
,filename.ldt- !"1$4M156*T$M146#7* function1name8,function name-, &$!T-
unction1name is a re9uired parameter
(ou cann't download lct file with out any supplied value.
"pload
!"#$%" ,userid-&,password- . ( 6P#$%" 0!"1T$P&patch&223&import&affrmcus.lct ,filename.ldt-
"asge
!"#$%" apps&apps . ( "$/!#$%" 0!"1T$P&patch&223&import&affrmcus.lct xxapperiod.lct
!"1$4M156*T$M146#7* form1name8%P:*6MP*
!"#$%" apps&apps . ( 6P#$%" 0!"1T$P&patch&223&import&affrmcus.lct xxapperiod.lct
;ecause the architecture has built'in support for all languages, you don<t translate ldt files, but instead you enter
multiple %ctions for different languages.
FNDLOAD: .exporting Oracle Alert
hapters = and > of the $racle %lert 6ser ?uide covers Transfers Process.
These are command you can use@
2. 5ommand to download
!"#$%" apps1user1name&apps1password . ( DO#NLOAD 0%#41T$P&patch&223&import&alr.lct
my1file.ldt %#41%#74T* %PP#I5%TI$!1*A$4T1!%M78!" %#74T1!%M78%lert name to download
6sage
$FND_TOP/bin/FNDLOAD apps/apps 0 Y DOWNLOAD $ALR_TOP/patch/115/import/alrlct CMS.ldt
ALR_AL!RT" APPL#$AT#ON_"%ORT_NA&!'(AR( AL!RT_NA&!' ($&"!)$!PT#ON(
=. 5ommand to upload
!"#$%" apps1user1name&apps1password . ( "$LOAD 0%#41T$P&patch&223&import&alr.lct
my1file.ldt
6sage
$FND_TOP/bin/FNDLOAD apps/apps 0 Y DOWNLOAD $ALR_TOP/patch/115/import/alrlct CMS.ldt
(ou can use some additional parameters such as
%#41"I*T4I;6TI$!1#I*T* %PP#I5%TI$!1*A$4T1!%M78%" where
%PP#I5%TI$!1*A$4T1!%M7 represents the %pplication %lert owner
%#41#$$B6P*
%#41M7**%?71*(*T7M*
%#41$4%5#71M%I#1%55$6!T*
%#41P4$I#71$PTI$!*
%#41P74I$"I51*7T* %PP#I5%TI$!1*A$4T1!%M78%#4
I have already posted note on FNDLOAD utility for doing movement of application setup data from one
database to the other.There are instances when we need to move some %$# and seeded data from one
7nvironment to another 7nvironment, thus at that time it is necessary to understand what are different options
%vailable within the $racle. Aere is extensive list for some of the obCects , that should be migrated by
!"#$%".
FNDLOAD for AM!s
$racle %pprovals Management D%M7+ is a self'service /eb application that enables users to define business
rules governing the process for approving transactions in $racle %pplications .This enables development of
custom rules to manage transaction approvals that is integrated with multiple $racle 7;* applications such as
A4, P$, %P and 6M:.
If you want to migrate the %M7 setup li)e rules,conditions,approval groups etc. from one instance to another
instance, you can use some of them by mean of !"#$%" utility. The process is similar to what we are
regularly using for other %$# $bCects.
!"#$%" will have such ldt file through which you can use.
(ou should read the lct first before using any !"#$%" 5ommand. In the lct, there is an 7ntity section, where
the 7ntity details are mentioned.!ewcomer in $racle%pps if you are not familiar with lcts, i would suggest you
to go through the "$/!#$%" section and find the bind variables, which are mandatory.
Aere are the details steps for each setup's availability till date.
%ondition
The script that downloads %M7 conditions allows you to download all conditions for a given transaction type or
only those associated with a particular attribute or group of attributes.

FND_TOP apps/*apps pass+or,- 0 Y DOWNLOAD $P!R_TOP/patch/115/import/am.scon/lct *l,t
0il.nam.- A&!_$OND#T#ON" $OND#T#ON_1!Y'*con,ition /.2- TRAN"A$T#ON_TYP!_#D'*trans t2ps
i,- APPL#$AT#ON_"%ORT_NA&!'*application short nam.-

FNDLOAD apps/*pass+,-3,.stination,b 0 Y 4PLOAD $P!R_TOP/patch/115/import/am.scon/lct *l,t
0il.nam.-

FNDLOAD apps/*pass+,-3so5rc.,b 0 Y DOWNLOAD $P!R_TOP/patch/115/import/am.scon/lct
am.con,itionl,t A&!_$OND#T#ON" APPL#$AT#ON_"%ORT_NA&!'(P!R(
TRAN"A$T#ON_TYP!_#D'(%R""A( ATTR#64T!_NA&!'(PRO$!""_NA&!(
$OND#T#ON_1!Y'(718889::9;<<559(=
FNDLOAD apps/*pass+,-3,.stination,b 0 Y UPLOAD $P!R_TOP/patch/115/import/am.scon/lct
am.con,itionl,t
D&namic Appro'al gro(p /Appro'er Gro(ps
%n approver group can either be an ordered set of one or more approvers Dpersons and&or user accounts+ or it
can be a list, which is dynamically generated at rule evaluation time.

FND_TOP apps/*apps pass+or,- 0 Y DOWNLOAD $P!R_TOP/patch/115/import/am.sapp>lct *l,t
0il.nam.- A&!_APPRO?AL_@RO4P" APPRO?AL_@RO4P_NA&!'*nam. o0 approAal >ro5p-
TRAN"A$T#ON_TYP!_#D'*trans t2ps i,- APPL#$AT#ON_"%ORT_NA&!'*application short nam.-

FNDLOAD apps/*pass+,-3,.stination,b 0 Y UPLOAD $P!R_TOP/patch/115/import/am.sapp>lct *l,t
0il.nam.-

FNDLOAD apps/*pass+,-3so5rc.,b 0 Y DOWNLOAD $P!R_TOP/patch/115/import/am.sapp>lct
am.approAal>ro5pl,t A&!_APPRO?AL_@RO4P" APPRO?AL_@RO4P_NA&!'(D2n ApprA %5b
ApproAal @ro5p( TRAN"A$T#ON_TYP!_#D'(%R""A( APPL#$AT#ON_"%ORT_NA&!'(P!R(
FNDLOAD apps/*pass+,-3,.stination,b 0 Y UPLOAD $P!R_TOP/patch/115/import/am.sapp>lct
am.approAal>ro5pl,t
D&namic Appro'al gro(p config

FNDLOAD apps/*pass+,-3so5rc.,b 0 Y DOWNLOAD $P!R_TOP/patch/115/import/am.saa>clct
am.approAal>ro5p5sa>.l,t A&!_APPRO?AL_@RO4P_$ONF#@ APPRO?AL_@RO4P_NA&!'(D2n Post
%ROPs ApproAal @ro5p( TRAN"A$T#ON_TYP!_#D'(%R""A( APPL#$AT#ON_"%ORT_NA&!'(P!R(

FNDLOAD apps/*pass+,-3,.stination,b 0 Y UPLOAD $P!R_TOP/patch/115/import/am.saa>clct
am.approAal>ro5p5sa>.l,t
A)* R(le
%n approval rule is a business rule that helps determine a transactionEFGs approval process. 4ules are
constructed from conditions and actions.
The %M7 rules can be downloaded for information about the rule De.g. name, description, etc+ along with
associated conditions and rule type.

$FND_TOP/bin/FNDLOAD apps/*apps pass+or,- 0 Y DOWNLOAD
$P!R_TOP/patch/115/import/am.sr5l/lct *l,t 0il.nam.- A&!_R4L!" R4L!_1!Y'*R5l. 1.2 -
TRAN"A$T#ON_TYP!_#D'*trans t2ps i,- APPL#$AT#ON_"%ORT_NA&!'*application short nam.-
H (ou can find 4ule Bey in %M7146#7* table

!"#$%" apps&,passwd-Idestinationdb . ( 6P#$%" 0P741T$P&patch&223&import&amesrul).lct
amerule.ldt
FNDLOAD apps/*pass+,-3so5rc.,b 0 Y DOWNLOAD $P!R_TOP/patch/115/import/am.sr5l/lct
am.r5l.l,t A&!_R4L!" R4L!_1!Y'(718889::9;5<5:8( TRAN"A$T#ON_TYP!_#D'(%R""A(
APPL#$AT#ON_"%ORT_NA&!'(P!R(
FNDLOAD apps/*pass+,-3,.stination,b 0 Y UPLOAD $P!R_TOP/patch/115/import/am.sr5l/lct
am.r5l.l,t
A)* R(le Action T&pe "sage

FNDLOAD apps/*apps p+- 0 Y DOWNLOAD am.sact5lct *,o+nloa, 0il. nam.-l,t
A&!_A$T#ON_4"A@!" APPL#$AT#ON_"%ORT_NA&!'*FND application short nam.-
TRAN"A$T#ON_TYP!_#D'*A&! transaction t2p. short nam.- BR4L!_1!Y'*R5l. 1.2-C
H 4ule Bey is found in %M7146#7* table

FNDLOAD apps/apps 0 Y 6P#$%" am.sact5lct *,o+nloa, 0il. nam.-l,t

FNDLOAD apps/*pass+,-3so5rc.,b 0 Y DOWNLOAD $P!R_TOP/patch/115/import/am.sact5lct
am.action5sa>.l,t A&!_A$T#ON_4"A@!" R4L!_1!Y'(718889::9;5<5:8(
TRAN"A$T#ON_TYP!_#D'(%R""A( APPL#$AT#ON_"%ORT_NA&!'(P!R(
FNDLOAD apps/*pass+,-3,.stination,b 0 Y UPLOAD $P!R_TOP/patch/115/import/am.sact5lct
am.action5sa>.l,t
Transaction T&pes
%n application that uses %M7 to govern its transactionsEFG approval processes is termed an integrating
application. %n integrating application may divide its transactions into several categories where each category
re9uires a distinct set of approval rules. 7ach set of rules is called a transaction type. "ifferent transaction types
can use the same attribute name to represent values that are calculated in different ways or fetched from
different places.

FNDLOAD apps/*apps p+,- 0 Y DOWNLOAD am.scAarlct *,o+nloa, 0il. nam.-l,t
A&!_$ALL#N@_APP" APPL#$AT#ON_"%ORT_NA&!'*FND application short nam.-
TRAN"A$T#ON_TYP!_#D'*A&! transaction t2p. short nam.-

FNDLOAD apps/*apps p+,- 0 Y 4PLOAD am.scAarlct *,o+nloa, 0il. nam.-l,t

FNDLOAD apps/apps 0 Y DOWNLOAD am.scAarlct h5btrant2p.l,t A&!_$ALL#N@_APP"

APPL#$AT#ON_"%ORT_NA&!'"DLAP TRAN"A$T#ON_TYP!_#D'"6TRAN"TYP!
FNDLOAD apps/apps 0 Y UPLOAD am.scAarlct h5btrant2p.l,t
Attri+(te
%ttributes are business variables with a single value for a particular transaction. The typical example for
attributes in %M7 are@
transactionEFGs total amount
percentage of discount
an itemEFGs category
a personEFGs salary
!"#$%" apps&,apps password- . ( "$/!#$%" 0P741T$P&patch&223&import&amesmatt.lct ,ldt
filename- %M71%TT4I;6T7* %TT4I;6T71!%M78,attribute name- T4%!*%5TI$!1T(P71I"8,trans
typs id- %PP#I5%TI$!1*A$4T1!%M78,application short name-

!"#$%" apps&,apps pwd- . ( 6P#$%" amesmatt.lct ,ldt download file name-

!"#$%" apps&apps . ( DO#NLOAD amesmatt.lct hubattributes.ldt %M71%TT4I;6T7*

%PP#I5%TI$!1*A$4T1!%M78*J#%P
T4%!*%5TI$!1T(P71I"8 *;T4%!*T(P7 %TT4I;6T71!%M78*;156*T1%TT4I;6T7
!"#$%" apps&apps . ( "$LOAD amesmatr.lct hubattributeusages.ldt
Attri+(te "sage
!"#$%" apps&,apps password- . ( DO#NLOAD 0P741T$P&patch&223&import&amesmatr.lct ,ldt
filename- %M71%TT4I;6T716*%?7* %TT4I;6T71!%M78,attribute name-
T4%!*%5TI$!1T(P71I"8,trans typs id- %PP#I5%TI$!1*A$4T1!%M78,application short name-

!"#$%" apps&,apps pwd- . ( "$LOAD amesmatr.lct ,download file name-.ldt

!"#$%" apps&apps . ( DO#NLOAD amesmatr.lct hubattributeusage.ldt

%M71%TT4I;6T716*%?7* aPP#I5%TI$!1*A$4T1!%M78*J#%P
!"#$%" apps&apps . ( "$LOAD amesmatr.lct hubattributeusages.ldt