All about FNDLOAD
FNDLOAD is a tool used at patch-upgrade time to migrate data from the Oracle reference instance to your installation. Via fndload seeded responsibilities, menus, profile options and many many more are delivered.
FNDLOAD is a concurrent program that can move Oracle Applications data between database and text file. FNDLOAD can download data from an application entity into an editable text file, which can be uploaded to another database. Conversion between database format and text file format is specified by a configuration file.
Advantages of FNDLOAD:
Because downloaded data is stored in a text file, version administration is possible When uploading data, the original data is updated. So, no need for deleting the alert first.
The adjusted Alert for production is saved in a text file on the server, you don’t have to worry about changes by end users in the application
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 op 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, for example alr_alerts
- parameters van be passed to download a certain Alert
By default Oracle delivers some configuration files you can use to download certain entities. You can find these config files in $FND_TOP/patch/115/import
Use parameters to specify data to download.Loader config files support download parameters to filter downloaded data. If multiple parameters are specified, only rows that match all the parameters will be downloaded.
Use these parameters to reduce the downloaded data to the minimum necessary for your patch. Delivering more data than necessary adds overhead, and increases your exposure to unwanted dependencies.
Edit downloaded ldt file if necessary. Editing loader data files is discouraged, but possible if needed for unusual circumstances. If you choose to edit the data file, you must take care to follow the file syntax exactly. You are also responsible for maintaining any needed data references, and for thoroughly testing your edited file to be sure you haven't caused any collateral damage.
FNDLOAD utility uses the OWNER and LAST_UPDATE_DATE attributes to ensure data preservation. The data with OWNER=CUSTOM is always given preference over OWENR=SEED. That is the CUSTOM data will never be overwritten by the SEED data. In a case where the OWNERS are same the LAST_UPDATE_DATE is given preference that is a row with the LAST_UPDATE_DTE higher is inserted.
The FNDLOAD executable can be located at $FND_TOP/bin.
Oracle currently supports the migration of the following types of data using FNDLOAD
Printers / Print queues / Executables Printers / Print queues / Executables.Roles / Responsibilities / Forms Roles / Responsibilities / Forms.Menus / Users / Request Sets Menus / Users / Request Sets.Request Groups / Request Queues Request Groups / Request Queues.Work shifts / Programs / Libraries Work shifts / Programs / Libraries.Attachments / Help Files Attachments / Help Files.Mime Types Mime Types.Security Information.
How To move User/Responsibilities across instances is mostly used by Apps DBA
Use FNDLOAD executable to:
(1) DOWNLOAD user/responsibilities information from a another instance with the arguments:
FNDLOAD apps/apps 0 Y DOWNLOAD @FND:patch/115/import/afscursp.lct.ldt FND_USER
(2) Then UPLOAD (Use UPLOAD_PARTIAL to upload a specific entity)FNDLOAD apps/apps 0 Y UPLOAD [UPLOAD_PARTIAL] @FND:patch/115/import/afscursp.lct.ldt FND_USER []
The argument CUSTOM_MODE=FORCE is required when custom profiles need to be overwritten.
The reason why we need CUSTOM_MODE=FORCE -
Custom profiles are owned by USER and not by ORACLE or SEED. By default these custom profiles will be preserved by FNDLOAD because these are considered to be customizations.
Syntax will be like these for overwriting custom profiles :
FNDLOAD apps/apps 0 Y UPLOAD $FND_TOP/patch/115/import/afscprof.lct $XX_TOP/import/CUSTOM_PROF.ldt - CUSTOM_MODE=FORCE
what is lct file and what it is ?
See the sample afattach.lct file
afattach.lct - Attachment Setup data
FND_ATTACHMENT_FUNCTIONS Sub-Entities FND_ATTACHMENT_BLOCKS FND_ATTACHMENT_BLOCK_ENTITIES FND_DOC_CATEGORY_USAGES Download Parameters APPLICATION_SHORT_NAME FUNCTION_NAME FUNCTION_TYPE FND_DOCUMENT_ENTITIES Download Parameters DATA_OBJECT_CODE FND_DOCUMENT_CATEGORIES Download Parameters CATEGORY_NAME FND_DOCUMENT_DATATYPES
Few more FNDLOAD syntax for example and help users to use it.
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"
9 - 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_SETAPPLICATION_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 - Messages
$FND_TOP/bin/FNDLOAD apps/apps 0 Y DOWNLOAD $FND_TOP/patch/115/import/afmdmsg.lct AB_FL_MSG.ldt FND_NEW_MESSAGESAPPLICATION_SHORT_NAME='ABFL'
$FND_TOP/bin/FNDLOAD apps/apps O Y UPLOAD $FND_TOP/patch/115/import/afmdmsg.lct AB_FL_MSG.ldt
FNDLOAD is a tool used at patch-upgrade time to migrate data from the Oracle reference instance to your installation. Via fndload seeded responsibilities, menus, profile options and many many more are delivered.
FNDLOAD is a concurrent program that can move Oracle Applications data between database and text file. FNDLOAD can download data from an application entity into an editable text file, which can be uploaded to another database. Conversion between database format and text file format is specified by a configuration file.
Advantages of FNDLOAD:
Because downloaded data is stored in a text file, version administration is possible When uploading data, the original data is updated. So, no need for deleting the alert first.
The adjusted Alert for production is saved in a text file on the server, you don’t have to worry about changes by end users in the application
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 op 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, for example alr_alerts
- parameters van be passed to download a certain Alert
By default Oracle delivers some configuration files you can use to download certain entities. You can find these config files in $FND_TOP/patch/115/import
Use parameters to specify data to download.Loader config files support download parameters to filter downloaded data. If multiple parameters are specified, only rows that match all the parameters will be downloaded.
Use these parameters to reduce the downloaded data to the minimum necessary for your patch. Delivering more data than necessary adds overhead, and increases your exposure to unwanted dependencies.
Edit downloaded ldt file if necessary. Editing loader data files is discouraged, but possible if needed for unusual circumstances. If you choose to edit the data file, you must take care to follow the file syntax exactly. You are also responsible for maintaining any needed data references, and for thoroughly testing your edited file to be sure you haven't caused any collateral damage.
FNDLOAD utility uses the OWNER and LAST_UPDATE_DATE attributes to ensure data preservation. The data with OWNER=CUSTOM is always given preference over OWENR=SEED. That is the CUSTOM data will never be overwritten by the SEED data. In a case where the OWNERS are same the LAST_UPDATE_DATE is given preference that is a row with the LAST_UPDATE_DTE higher is inserted.
The FNDLOAD executable can be located at $FND_TOP/bin.
Oracle currently supports the migration of the following types of data using FNDLOAD
Printers / Print queues / Executables Printers / Print queues / Executables.Roles / Responsibilities / Forms Roles / Responsibilities / Forms.Menus / Users / Request Sets Menus / Users / Request Sets.Request Groups / Request Queues Request Groups / Request Queues.Work shifts / Programs / Libraries Work shifts / Programs / Libraries.Attachments / Help Files Attachments / Help Files.Mime Types Mime Types.Security Information.
How To move User/Responsibilities across instances is mostly used by Apps DBA
Use FNDLOAD executable to:
(1) DOWNLOAD user/responsibilities information from a another instance with the arguments:
FNDLOAD apps/apps 0 Y DOWNLOAD @FND:patch/115/import/afscursp.lct.ldt FND_USER
(2) Then UPLOAD (Use UPLOAD_PARTIAL to upload a specific entity)FNDLOAD apps/apps 0 Y UPLOAD [UPLOAD_PARTIAL] @FND:patch/115/import/afscursp.lct.ldt FND_USER []
The argument CUSTOM_MODE=FORCE is required when custom profiles need to be overwritten.
The reason why we need CUSTOM_MODE=FORCE -
Custom profiles are owned by USER and not by ORACLE or SEED. By default these custom profiles will be preserved by FNDLOAD because these are considered to be customizations.
Syntax will be like these for overwriting custom profiles :
FNDLOAD apps/apps 0 Y UPLOAD $FND_TOP/patch/115/import/afscprof.lct $XX_TOP/import/CUSTOM_PROF.ldt - CUSTOM_MODE=FORCE
what is lct file and what it is ?
See the sample afattach.lct file
afattach.lct - Attachment Setup data
FND_ATTACHMENT_FUNCTIONS Sub-Entities FND_ATTACHMENT_BLOCKS FND_ATTACHMENT_BLOCK_ENTITIES FND_DOC_CATEGORY_USAGES Download Parameters APPLICATION_SHORT_NAME FUNCTION_NAME FUNCTION_TYPE FND_DOCUMENT_ENTITIES Download Parameters DATA_OBJECT_CODE FND_DOCUMENT_CATEGORIES Download Parameters CATEGORY_NAME FND_DOCUMENT_DATATYPES
Few more FNDLOAD syntax for example and help users to use it.
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"
9 - 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_SETAPPLICATION_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 - Messages
$FND_TOP/bin/FNDLOAD apps/apps 0 Y DOWNLOAD $FND_TOP/patch/115/import/afmdmsg.lct AB_FL_MSG.ldt FND_NEW_MESSAGESAPPLICATION_SHORT_NAME='ABFL'
$FND_TOP/bin/FNDLOAD apps/apps O Y UPLOAD $FND_TOP/patch/115/import/afmdmsg.lct AB_FL_MSG.ldt
No comments:
Post a Comment