All about FNDLOAD command and WFLOAD command



INTRODUCTION TO FNDLOAD

The loader is a general-purpose utility that moves structured data between a text file and a database.
Structures supported by the loader include master-detail relationships, and foreign key reference relationships, including arbitrary chains of said relationships.

The loader operates in one of three modes: download, upload, or upload_partial. In the download mode, data is downloaded from the database to a text file; in the upload mode and upload_partial mode,data is uploaded from a text file to the database.

In either case, the structure of the data involved is described by a configuration file. The configuration file describes not only the structure of the data, but 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, and it is always read by the loader. The contents of the configuration file are authored by the user of the utility.

When downloading, the loader will create 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 loader reads a data file to get the data that it is to upload. Most likely, the data file was produced by a previous download, but may have come from another source. In any case, the data file may not be interpreted without the corresponding configuration file available.

CONFIGURATION FILE

The contents of the configuration file are at the heart of the loader operation since they specify the structure of the data and the access methods to use to move the data between the data file and a database.

A configuration file has the form:

configuration_file ::= item { item }
item ::= definition | download | upload

A configuration file consists of a series of one or more items. Each item is either an entity definition, a download access method, or an upload access method.

Each entity type defined in a configuration file must have all three elements (definition, download, and upload) defined exactly once.The entity definition must appear before either the download or upload access method for that entity type, but they need not be contiguous.There are no other restrictions on ordering of items in the
configuration file.

DOWNLOAD

The download operation of the loader is invoked in the following manner:

FNDLOAD logon [ 0 Y ] DOWNLOAD configfile datafile entity [ param … ]

where

FNDLOAD Command

Upon invocation, the loader reads the configuration file, and proceeds to download data from the database beginning with the download access method provided for the entity named on the command line. The data is written to the data file.

UPLOAD

The upload operations of the loader is invoked in the following
manner:

FNDLOAD logon [ 0 Y ] UPLOAD configfile datafile [- [param …] ]

FNDLOAD logon [ 0 Y ] UPLOAD_PARTIAL configfile datafile [entity [param …] ]

where

FNDLOAD Command

The loader starts by reads the configuration file, and then proceeds to read the data file, one value at a time. When using the UPLOAD_PARTIAL mode, each value whose type is the one specified on the command line is uploaded to the database using the upload methods provided. When using the UPLOAD mode all values in the data file are uploaded to the database using the upload methods provided.

To avoid calamities in the middle of long-running operations, the loader commits changes after each top-level value is uploaded. Thus, an upload method may fail without causing the entire operation to abort.

What are ldt and lct files

Steps  to use FNDLOAD Command  

Step 1: Login to apps server of the source environment and Then Run the following command by supplying the parameters given in {} as per your need. I am using the example of concurrent program download

FNDLOAD apps/apps O Y DOWNLOAD $FND_TOP/patch/115/import/afcpprog.lct {file_name.ldt} PROGRAM APPLICATION_SHORT_NAME=”{application_short_name}” CONCURRENT_PROGRAM_NAME=”{concurrent_name}”

The above command will generate ldt file in your working directory

Step 2:  Copy the .ldt file to the destination instance server

Step 3: Login to apps server of the destination environment and go into the directory  where ldt file is copied

FNDLOAD apps/pass  0 Y UPLOAD $FND_TOP/patch/115/import/afcpprog.lct   {file_name}.ldt

FNDLOAD Command
Commonly Used FNDLOAD Commands

Form Personalization:

Download:
FNDLOAD apps/<apps_pass>0 Y DOWNLOAD $FND_TOP/patch/115/import/affrmcus.lct <file_name.ldt> FND_FORM_CUSTOM_RULES function_name=”CUSTFPNAME”
Upload
FNDLOAD apps/<apps_pass>0 Y UPLOAD $FND_TOP/patch/115/import/affrmcus.lct <file_name.ldt>

 FND Users:

Download:
FNDLOAD apps/<apps_pass>0 Y DOWNLOAD $FND_TOP/patch/115/import/afscursp.lct <file_name.ldt> FND_USER USER_NAME=’USER_NAME’
Upload
FNDLOAD apps/<apps_pass>0 Y UPLOAD $FND_TOP/patch/115/import/afscursp.lct <file_name.ldt>
 Notes for using FNDLOAD against FND_USER:-
1) Password will be downloaded in ldt files in encrpyted format only
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 Destination Environment , make sure that you have done FNDLOAD for new responsibilities prior to running FNDLOAD on users

Printer Styles:

Download:
FNDLOAD apps/<apps_pass>O Y DOWNLOAD $FND_TOP/patch/115/import/afcppstl.lct <file_name.ldt> STYLE PRINTER_STYLE_NAME=”PRINT_STYLE”Upload
FNDLOAD apps/<apps_pass>0 Y UPLOAD $FND_TOP/patch/115/import/afcppstl.lct <file_name.ldt>

Profile Options:

Download
FNDLOAD apps/<apps_pass>O Y DOWNLOAD $FND_TOP/patch/115/import/afscprof.lct  <file_name.ldt> PROFILE PROFILE_NAME=”CUST_PROF_NAME” APPLICATION_SHORT_NAME=”CUST”
Upload
FNDLOAD apps/<apps_pass>O Y UPLOAD $FND_TOP/patch/115/import/afscprof.lct <file_name.ldt>

Forms:

Download:
FNDLOAD apps/<apps_pass>O Y DOWNLOAD $FND_TOP/patch/115/import/afsload.lct <file_name.ldt> FORM APPLICATION_SHORT_NAME=”CUST” FORM_NAME=”CUSTFRMNAME”
Upload
FNDLOAD apps/<apps_pass>0 Y UPLOAD @FND:patch/115/import/afsload.lct <file_name.ldt>

Functions:

Download:
FNDLOAD apps/<apps_pass>O Y DOWNLOAD $FND_TOP/patch/115/import/afsload.lct <file_name.ldt>  FUNCTION FUNC_APP_SHORT_NAME=”CUST” FUNCTION_NAME=”CUSTFUNNAME”
Upload
FNDLOAD apps/<apps_pass>O Y UPLOAD @FND:patch/115/import/afsload.lct <file_name.ldt>

Menus:

Download:
FNDLOAD apps/<apps_pass>O Y DOWNLOAD $FND_TOP/patch/115/import/afsload.lct <file_name.ldt>   MENU MENU_NAME=”CUSTMENUNAME”
Upload
FNDLOAD apps/<apps_pass>0 Y UPLOAD @FND:patch/115/import/afsload.lct <file_name.ldt>
Oracle Menus are not attached to applications. Hence no need to include application short name  CUSTMENUNAME is the menu name. This can be validated via below SQL
select user_menu_name from fnd_menus_vl where menu_name = ‘CUSTMENUNAME’;

 Responsibilities:

Download:
FNDLOAD apps/<apps_pass>O Y DOWNLOAD $FND_TOP/patch/115/import/afscursp.lct <file_name.ldt> FND_RESPONSIBILITY RESP_KEY=”CUSTRESNAME”
Upload
FNDLOAD apps/<apps_pass>O Y UPLOAD $FND_TOP/patch/115/import/afscursp.lct <file_name.ldt>

Request Groups:

Download:
FNDLOAD apps/<apps_pass>O Y DOWNLOAD $FND_TOP/patch/115/import/afcpreqg.lct <file_name.ldt> REQUEST_GROUP REQUEST_GROUP_NAME=”CUSTRQGNAME” APPLICATION_SHORT_NAME=”CUST”
Upload
FNDLOAD apps/<apps_pass>O Y UPLOAD $FND_TOP/patch/115/import/afcpreqg.lct <file_name.ldt>

Request Sets:

Download:

FNDLOAD apps/<apps_pass>0 Y DOWNLOAD $FND_TOP/patch/115/import/afcprset.lct <file_name1.ldt>  REQ_SET REQUEST_SET_NAME=”CUSTREQSETNAME”

FNDLOAD apps/<apps_pass>0 Y DOWNLOAD $FND_TOP/patch/115/import/afcprset.lct <file_name2.ldt> REQ_SET_LINKS REQUEST_SET_NAME=”CUSTREQSETNAME”

Upload

FNDLOAD apps/<apps_pass>0 Y UPLOAD $FND_TOP/patch/115/import/afcprset.lct <file_name1.ldt>

FNDLOAD apps/<apps_pass>0 Y UPLOAD $FND_TOP/patch/115/import/afcprset.lct <file_name2.ldt>

Lookups:

Download:
FNDLOAD apps/<apps_pass>O Y DOWNLOAD $FND_TOP/patch/115/import/aflvmlu.lct <file_name.ldt> FND_LOOKUP_TYPE APPLICATION_SHORT_NAME=”CUST” LOOKUP_TYPE=”CUST_LOOKUP_NAME”UploadFNDLOAD apps/<apps_pass>0 Y UPLOAD aflvmlu.lct <file_name.ldt>

Value Sets:

Download:
FNDLOAD apps/<apps_pass>O Y DOWNLOAD $FND_TOP/patch/115/import/afffload.lct <file_name.ldt>VALUE_SET FLEX_VALUE_SET_NAME=”CUSTVAL_SETNAME”
Upload
FNDLOAD apps/<apps_pass>0 Y UPLOAD afffload.lct <file_name.ldt>
 

 Concurrent Programs:

Download:
FNDLOAD apps/<apps_pass>O Y DOWNLOAD $FND_TOP/patch/115/import/afcpprog.lct <file_name.ldt>PROGRAM APPLICATION_SHORT_NAME=”CUST” CONCURRENT_PROGRAM_NAME=”CUST_CP_NAME”Upload
FNDLOAD apps/<apps_pass>0 Y UPLOAD @FND:patch/115/import/afcpprog.lct <file_name.ldt>
Important Note for Using FNDLOAD Command
1. Test FNDLOAD commands multiple times in multiple instances before running into PROD instances.
2. UPLOAD_PARTIAL is used to modify existed programs.
3. Execution sequence is important . If you are creating new responsibility with new form,function, menu. Then Upload first form,then function, menu and then responsibility
4) Always check the ldt files to make sure ,right data is extracted

INTRODUCTION TO WFLOAD:

The loader is a utility that moves workflow data between a file and a database. It is used to upgrade,upload and download the workflow data.

DOWNLOAD

The download operation of the loader is invoked in the following manner:

WFLOAD logon [0 Y ] DOWNLOAD []

where

UPLOAD

The upload operations of the loader is invoked in the following manner:

WFLOAD logon [ 0 Y ] UPLOAD datafile []

where

WFLOAD command

 There are some other level of upload in WFLOAD

UPGRADE – Protection and Customization levels of data

UPLOAD  – Only protection level of data.Not supporting customisation
FORCE   – Force upload, protection or customization not supported

Example of WFLOAD

Command to download

WFLOAD apps/apps 0 Y DOWNLOAD REQAPPRV.wft REQAPPRV

WFLOAD apps/apps 0 Y DOWNLOAD POAPPRV.wft POAPPRV

Command to upload

WFLOAD apps/apps 0 Y UPLOAD REQAPPRV.wft REQAPPRV

WFLOAD apps/apps 0 Y UPLOAD POAPPRV.wft POAPPRV

Command to upgrade

WFLOAD apps/apps 0 Y UPGRADE REQAPPRV.wft REQAPPRV

WFLOAD apps/apps 0 Y UPGRADE POAPPRV.wft POAPPRV

More info on Apps
OA Framework Basics
Profile OA framework


Leave a Reply