Sunday, June 14, 2009


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 ...]

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.

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.

The configuration file to use (usually with a suffix of .lct, but not enforced or supplied by the loader).

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.

The entity(ies) to upload or download. When uploading, you should always upload all entities, so specify a "-" to upload all entities.

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.

For 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

For Upload

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

1 comment:

  1. Недавно был выпущен графический интерфейс для FNDLOAD. Его можно обнаружить на сайте -

    Видео презентация на