The Generic Loader (FNDLOAD) is a concurrent
program that can move Oracle Applications data between database and text file
representations. The loader reads a configuration file to determine what data
to access. For information on specific configuration files consult the Open
Interfaces Guide for your product group.
From an FNDLOAD perspective, there
is absolute no limitation on parallel execution. Parallel upload of
concurrent programs and responsibilities should through fine unless upload
logic in LCT file restrict the same.
There is no way to limit the
download of the value hierarchy data with the existing flexfield loader
logic.
If this data is removed manually from the .ldt file generated when downloading
data, the upload might error out as a result and this is NOT a supported method
of using fndload and the corresponding generated data.
Overview
The Generic Loader can download data
from an application entity into a portable, editable text file. This file can
then be uploaded into any other database to copy the data. Conversion between
database store and file format is specified by a configuration file that is
read by the loader.
The Generic Loader downloads data from a database according to a configuration
(.lct) file, and converts the data into a data file (.ldt file). The Generic
Loader can then upload this data to another database using a configuration
file.
The loader operates in one of two modes: download or upload. In the download
mode, data is downloaded from the database to a text file; in the upload mode,
data is uploaded from a text file to the database.
Data structures supported by the loader include master-detail relationships and
foreign key reference relationships.
In both downloading and uploading, the structure of the data involved is
described by a configuration file. The configuration file describes the
structure of the data and also the access methods to use to copy the data into
or out of the database. The same configuration file may be used for both
uploading and downloading.
When downloading, the Generic Loader creates a second file, called the data
file that contains the structured data selected for downloading. The data file
has a standard syntax for representing the data that has been downloaded. When
uploading, the Generic Loader reads a data file to get the data that it is to
upload. In most cases, the data file was produced by a previous download, but
may have come from another source. The data file cannot be interpreted without
the corresponding configuration file available.
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/Personalizations
· Attachments
· Messages
· Value Sets and Values
· Lookup Types
· User Responsibilities
· Printer Definitions
· FND Dictionary
· Help Configuration
· Document Sequences
· Alerts
· Concurrent Manager Schedules
The FNDLOAD: Concurrent Program –
FNDLOAD can be executed as a concurrent program.
Some advantages
when using FNDLOAD
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 and dba
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
Some
disadvantages when using FNDLOAD
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
Syntax
The Generic Loader is a concurrent
program named FNDLOAD. The concurrent executable takes the following
parameters:
FNDLOAD apps/pwd 0 Y mode configfile datafile entity [ param ...]
where
<apps/pwd>
The APPS schema and password in the form
username/password[@connect_string]. If
connect_string is omitted, it is taken in a platform-specific manner from the
environment
using the name TWO_TASK.
< 0 Y >
Concurrent program flags.
mode
UPLOAD or DOWNLOAD. UPLOAD causes the datafile to be uploaded to the database.
DOWNLOAD causes the loader to fetch rows and write them to the datafile.
<con g le>
The configuration file to use
(usually with a suffix of .lct, but not enforced or supplied by the loader).
<data le>
The data file to write (usually with a suffix of .ldt, but not enforced or
supplied by the loader). If the data file already exists, it will be
overwritten.
<entity>
The entity(ies) to upload or download. When uploading, always upload all
entities, so specify a "-" to upload all entities.
< [param] >
Zero or more additional parameters are used to provide bind values in the
access SQL (both UPLOAD and DOWNLOAD). Each parameter is in the form NAME=VALUE.
NAME should not conflict with an attribute name for the entities being loaded.
Modes of
Operation
This is important because it would
drive the whole flow, and it always be either Upload or Download.
Example of
download
FNDLOAD apps/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 are
FNDLOAD 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 entity 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
Where is
Configuration File Located
By default Oracle delivers most of
configuration files that can be used 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
FNDLOAD File Structure
· The configuration 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 - (Example)
Concurrent Program download.
· The data files (.ldt) have both entity definition and the data.
· It also shows the version and the location of the configuration file (.lct)
that was used.
· Without the configuration file, a data file is useless.
· Without the data file, a configuration file is meaningless.
FNDLOAD Files
· Key files: .lct and .ldt
· FNDLOAD must be run as the apps user not as applsys or any other user,
otherwise an Ora-6550 error will be received.
· Both are easily readable, editable and portable.
· Do not modify Oracle .lct files.
· Use a favorite editor 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 as: (Why can this be accessed? 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)
1 - Printer
Styles
FNDLOAD
apps/pwd@seeddb 0 Y DOWNLOAD $FND_TOP/patch/115/import/afcppstl.lct
file_name.ldt STYLE PRINTER_STYLE_NAME=”printer style name”
2 - Lookups
FNDLOAD
apps/pwd@seeddb 0 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/pwd@seeddb 0 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 - Multiple
Flexfields
Use a combination of
APPLICATION_SHORT_NAME and DESCRIPTIVE_FLEXFIELD_NAME names ie.
APPLICATION_SHORT_NAME=PER >> will download all PER flexfields
DESCRIPTIVE_FLEXFIELD_NAME=PER_% >> will download all flexfields that
start with 'PER_'.
FNDLOAD apps/apps O Y
DOWNLOAD $FND_TOP/patch/115/import/afffload.lct
file_name.ldt DESC_FLEX DESCRIPTIVE_FLEXFIELD_NAME="PER_%"
5 - Key
Flexfield Structures
FNDLOAD
apps/pwd@seeddb 0 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”
6 - Concurrent
Programs
FNDLOAD
apps/pwd@seeddb 0 Y DOWNLOAD $FND_TOP/patch/115/import/afcpprog.lct
file_name.ldt PROGRAM APPLICATION_SHORT_NAME=”prod”
CONCURRENT_PROGRAM_NAME=”concurrent name”
7 - Value Sets
FNDLOAD
apps/pwd@seeddb 0 Y DOWNLOAD $FND_TOP/patch/115/import/afffload.lct
file_name.ldt VALUE_SET FLEX_VALUE_SET_NAME=”value set name”
8 - Value Sets with values
FNDLOAD
apps/pwd@seeddb 0 Y DOWNLOAD $FND_TOP/patch/115/import/afffload.lct
file_name.ldt VALUE_SET_VALUE FLEX_VALUE_SET_NAME=”value set name”
9 - Profile
Options
FNDLOAD
apps/pwd@seeddb 0 Y DOWNLOAD $FND_TOP/patch/115/import/afscprof.lct
file_name.ldt PROFILE PROFILE_NAME=”profile option”
APPLICATION_SHORT_NAME=”prod”
10 - Request
Group
FNDLOAD
apps/pwd@seeddb 0 Y DOWNLOAD $FND_TOP/patch/115/import/afcpreqg.lct
file_name.ldt REQUEST_GROUP REQUEST_GROUP_NAME=”request group”
APPLICATION_SHORT_NAME=”prod”
11 - Request
Sets
FNDLOAD
apps/pwd@seeddb 0 Y DOWNLOAD $FND_TOP/patch/115/import/afcprset.lct
file_name.ldt REQ_SET APPLICATION_SHORT_NAME=”prod” REQUEST_SET_NAME=”request
set”
12 -
Responsibilities
FNDLOAD
apps/pwd@seeddb 0 Y DOWNLOAD $FND_TOP/patch/115/import/afscursp.lct
file_name.ldt FND_RESPONSIBILITY RESP_KEY=”responsibility"
13 -
Responsibilities with all Security Groups
FNDLOAD
apps/<PASSWORD> 0 Y DOWNLOAD FND_TOP/patch/115/import/afscursp.lct
<USER>.ldt
FND_USER USER_NAME="<USER>" SECURITY_GROUP=% DATA_GROUP_NAME=%
14 - Menus
FNDLOAD apps/
pwd@seeddb 0 Y DOWNLOAD $FND_TOP/patch/115/import/afsload.lct file_name.ldt
MENU MENU_NAME=”menu_name”
15 -
Forms/Functions/Personalizations:
Refer to the System Administrator's Guide on dependencies
FNDLOAD
<userid>/<password> 0 Y DOWNLOAD
$FND_TOP/patch/115/import/affrmcus.lct
<filename.ldt> FND_FORM_CUSTOM_RULES form_name=<form name>
OR
FNDLOAD
<userid>/<password> 0 Y DOWNLOAD
$FND_TOP/patch/115/import/afsload.lct file_name.ldt FUNCTION
FUNCTION_NAME=<function_name>
OR
FNDLOAD
<userid>/<password> 0 Y DOWNLOAD
$FND_TOP/patch/115/import/afsload.lct file_name.ldt FORM
FORM_NAME=<form_name>
OR
FNDLOAD
<userid>/<password> 0 Y DOWNLOAD
$FND_TOP/patch/115/import/affrmcus.lct <filename.ldt>
FND_FORM_CUSTOM_RULES function_name=<function name>
16 -
User/Responsibilities
FNDLOAD apps/
pwd@seeddb 0 Y DOWNLOAD $FND_TOP/patch/115/import/afscursp.lct file_name.ldt
FND_USER
17 - Alert
FNDLOAD apps/pwd 0 Y
DOWNLOAD
$ALR_TOP/patch/115/import/alr.lct my_file.ldt ALR_ALERTS
APPLICATION_SHORT_NAME=FND ALERT_NAME=Alert name to downloa
18 - Blob
With Release 12.1.1, FNDLOAD
supports BLOB data (upload / download ) to better serve content-rich applications.
FNDLOAD
apps/pwd 0 Y mode configfile datafile entity [ param ... ]
19 - Overwrite custom
definitions
FNDLOAD apps/apps 0 Y
UPLOAD $FND_TOP/patch/115/import/.lct $
XX_TOP/import/.ldt CUSTOM_MODE=FORCE
20 - Load an NLS Language
FNDLOAD <APPS USR>/<APPS
PWD> 0 Y UPLOAD <controlfile.lct> <datafile.ldt> \
- UPLOAD_MODE=NLS CUSTOM_MODE=FORCE WARNINGS=TRUE
21 - Migrate the role registration process from one instance to another
a. Please navigate to the path:
$FND_TOP /patch/115/import/US/umxrgsvc.ldt
b. The following command can be used to download:
FNDLOAD
apps/<PASSWD>@(instance name) O Y DOWNLOAD
$FND_TOP/patch/115/import/umxrgsvc.lct umxrgsvc.ldt UMX_REG_SERVICES
REG_SERVICE_CODE UMX
c. The following command can be used to upload:
FNDLOAD apps/<PASSWD>@(instance
name) O Y UPLOAD $FND_TOP/patch/115/import/umxrgsvc.lct umxrgsvc.ldt
UMX_REG_SERVICES REG_SERVICE_CODE UMX
22 - Transfer
Custom Messages to another Instance
a. Download the message from the
source instance.
FNDLOAD apps/apps 0 Y
DOWNLOAD @FND:patch/115/import/afmdmsg.lct password.ldt FND_NEW_MESSAGES
APPLICATION_SHORT_NAME=FND MESSAGE_NAME=PASSWORD-INVALID-NO-SPEC-CHAR
b. Move the custom LDT file (password.ldt) over to the destination instance.
c. Upload the custom message to the destination instance.
FNDLOAD apps/apps 0 Y
UPLOAD @FND:patch/115/import/afmdmsg.lct password.ldt FND_NEW_MESSAGES
APPLICATION_SHORT_NAME=FND CUSTOM_MODE=FORCE
23 - Download
UMX Roles and Role Assignment data from one instance and upload to another.
To download from one instance:
FNDLOAD <username/pwd@sid> 0 Y DOWNLOAD
$FND_TOP/patch/115/import/afrole.lct
umxroles.ldt WF_ROLE ORIG_SYSTEM=UMX%
To upload to another instance:
FNDLOAD <username/pwd@sid> 0 Y UPLOAD
$FND_TOP/patch/115/import/afrole.lct
umxroles.ldt
