Oracle R12 Fndload to Upload Form Personalization
INTRODUCTION TO FNDLOAD
- The FNDLOAD command/loader is a general-purpose utility that moves structured data between a text file and a database.
- Structures supported by the loader include primary-detail relationships, and strange cardinal reference relationships, including arbitrary chains of said relationships.
- The loader operates in i of 3 modes: download, upload, or upload_partial. In the download mode, data is downloaded from the database to a text file; in the upload style and upload_partial mode, information 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 construction of the data but the access methods to use to re-create the data into or out of the database. The same configuration file may exist used for both uploading and downloading, and it is e'er read by the loader. The contents of the configuration file are authored past the user of the utility.
- When downloading, the loader volition create a 2d file, chosen the information file, that contains the structured information selected for downloading. The information file has a standard syntax for representing the data that has been downloaded. When uploading, the loader reads a data file to become the information that it is to upload. Near likely, the data file was produced by a previous download simply may accept come from another source. In whatsoever case, the data file may not be interpreted without the respective configuration file available.
- It is located in the $FND_TOP/bin directory
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 { detail }
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 3 elements (definition, download, and upload) defined exactly once. The entity definition must appear before either the download or upload access method for that entity blazon, but they need not be contiguous. There are no other restrictions on the ordering 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
Upon invocation, the FNDLOAD control reads the configuration file and proceedsto 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 information file.
UPLOAD
The upload operations of the loader are invoked in the following
fashion:
FNDLOAD logon [ 0 Y ] UPLOAD configfile datafile [- [param ...] ]
FNDLOAD logon [ 0 Y ] UPLOAD_PARTIAL configfile datafile [entity [param ...] ]
where
The FNDLOAD command starts by reads the configuration file, and and so gain to read the data file, i value at a time. When using the UPLOAD_PARTIAL mode, each value whose type is the 1 specified on the control 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 avert calamities in the center of long-running operations, the loader commits changes after each top-level value is uploaded. Thus, an upload method may fail without causing the unabridged performance to abort.
What are ldt and lct files
Steps to employ FNDLOAD Control
Footstep one: Log in to the apps server of the source environment and source the environment file. Then run the following command by supplying the parameters given in {} equally 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 to a higher place command volition generate ldt file in your working directory
Step 2: Copy the .ldt file to the destination case server
Step iii: Log in to the apps server of the destination environs and go into the directory where ldt file is copied
FNDLOAD apps/laissez passer 0 Y UPLOAD $FND_TOP/patch/115/import/afcpprog.lct {file_name}.ldt
Commonly Used FNDLOAD Commands
Download/Upload Form Personalization using FNDLOAD
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>
Download /Upload FND Users using FNDLOAD
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 merely
1. After uploading using FNDLOAD, user volition 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 Surroundings , make sure that you lot accept done FNDLOAD for new responsibilities prior to running FNDLOAD on users
Download /Upload 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>
Download /Upload Oracle Contour 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>
Download /Upload 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>
Download /Upload 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>
Download /Upload Menus:
Download:
FNDLOAD apps/<apps_pass>O Y DOWNLOAD $FND_TOP/patch/115/import/afsload.lct <file_name.ldt> Card MENU_NAME="CUSTMENUNAME"
Upload
FNDLOAD apps/<apps_pass>0 Y UPLOAD @FND:patch/115/import/afsload.lct <file_name.ldt>
Oracle Menus are non attached to applications. Hence no need to include application brusk proper noun CUSTMENUNAME is the bill of fare name. This tin can be validated via beneath SQL
select user_menu_name from fnd_menus_vl where menu_name = 'CUSTMENUNAME';
Download /Upload 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>
Download /Upload 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>
Download /Upload Asking Sets:
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"
UploadFNDLOAD 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>Download Lookups:
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"
Upload
FNDLOAD apps/<apps_pass>0 Y UPLOAD aflvmlu.lct <file_name.ldt>
Download 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>
Download 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 Control
1. Test FNDLOAD commands multiple times in multiple instances earlier running into PROD instances.
2. UPLOAD_PARTIAL is used to modify existed programs.
three. Execution sequence is important . If you are creating new responsibility with new class,role, menu. And so Upload commencement form,and so function, menu so responsibility
4) Always cheque the ldt files to make sure ,right data is extracted
More info on Apps
OA Framework Basics : Oracle Application Framework (OAF) is an architecture for creating web based pages with in Oracle EBS platform.OAF follows MVC architecture. MVC stands for Module View Controller Architecture
XMLImporter :XMLImporter is used for importing the folio or personalization into the database while FndXdfCmp for new schema definition and changes
Oracle concurrent Manager :How an E-Business Suite Concurrent Manager Process Works,Oracle Concurrent Manager,What is internal monitor,What is service managing director and troubleshooting
oracle R12 tutorial : Listing of articles for EBS DBA assistants
WFLOAD control : WFLOAD command tin can be used UPLOAD,DOWNLOAD workflow betwixt file and database. This is likewise used to migrate workflow across the surround
date functions in oracle :Bank check out this post for oracle date functions, oracle engagement difference in years,oracle appointment difference in days, oracle date difference in months
https://docs.oracle.com/cd/E18727_01/doc.121/e12893/T174296T206863.htm
Source: https://techgoeasy.com/fndload-command/
0 Response to "Oracle R12 Fndload to Upload Form Personalization"
Post a Comment