FNDLOAD to transfer the menus concurrent programs personalization from one instance to other
|
|
|
|
Author |
|
Name:
|
prudhvi
|
|
E-mail:
|
prudhvi@erpschools.com
|
|
|
|
|
|
|
|
The Generic Loader (FNDLOAD) is a concurrent program that can transfer Oracle Application entity data between database and text file. The loader reads a configuration file to determine which entity to access. In simple words FNDLOAD is used to transfer entity data from one instance/database to other. For example if you want to move a concurrent program/menu/valuesets developed in DEVELOPMENT instance to PRODUCTION instance you can use this command.
|
Steps to Move a
Concurrent program from one instance(Database) to other
- Define your concurrent program and save it in
first instance(for how to register a concurrent program click here)
- Connect to your UNIX box on first instance and
run the following command to download the .ldt file
FNDLOAD
apps/apps O Y DOWNLOAD $FND_TOP/patch/115/import/afcpprog.lct file_name.ldt
PROGRAM APPLICATION_SHORT_NAME="Concurrent program application short name"
CONCURRENT_PROGRAM_NAME="concurrent program short name"
- Move the downloaded .ldf file to new
instance(Use FTP)
- Connect to your UNIX box on second instance
and run the following command to upload the .ldt file
FNDLOAD apps/apps 0 Y UPLOAD $FND_TOP/patch/115/import/afcpprog.lct
file_name.ldt
Note: Make sure
you are giving proper .lct file in the commands and don’t confuse with .lct
and .ldt files
These following
are the other entity data types that
we can move with FNDLOAD
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"
8 - 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_SET
APPLICATION_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 - Forms
Personalization
FNDLOAD apps/apps 0 Y DOWNLOAD $FND_TOP/patch/115/import/affrmcus.lct
file_name.ldt FND_FORM_CUSTOM_RULES function_name=FUNCTION_NAME
Note: UPLOAD
command is same for all except replacing the .lct and passing any extra
parameters if you want to pass
FNDLOAD
apps/apps 0 Y UPLOAD $FND_TOP/patch/115/import/corresponding.lct upload_file.ldt
|
Mark Mestetskiy
|
commented on
12/10/2009 12:25:26 AM
|
|
|
|
|
I like the introductory part and 2nd paragraph explaining migration of the concurrent program, espesially the sentence about the proper configuration lct file. This is the most common reason for error as well as wrong parameter values. To make the migration really simple, our company developed GUI for FNDLOAD. It makes the sentence about wrong configuration file and wrong parameter values obsolete. Everything done by the GUI. User only chooses the objects to migrate. Migration LogiK executes FNDLOAD and downloads both log and definition files to the client machint. User makes the decision on which objects to migrate. It clearly separates decision making process from the routine execution and file transfer acivities.
|
|
|
|
|
|
Mark Mestetskiy
|
commented on
12/10/2009 12:26:20 AM
|
|
|
|
|
Look at http://migrationlogik.com for more information.
|
|
|
|
|
|
sekhar
|
commented on
5/3/2010 1:34:12 AM
|
|
|
|
|
Hi,
this is sekhar, now iam facing a problem in fndload. How to open the lct and ldt file. Is it exist already in the ftp.
thanks in advance
Sekhar
|
|
|
|
|
|
Mark Mestetskiy
|
commented on
6/7/2010 12:23:50 PM
|
|
|
|
|
.lct and .ldt files are plain text based and easily readable through any text editors. Could you elaborate more on the issue you are facing in FNDLOAD?
MigrationLogiK has now XMLPubliser Data source and templates definitions available for download or upload.
|
|
|
|
|
|
Anirban
|
commented on
7/26/2010 3:22:06 AM
|
|
|
|
|
I will explain Sekhar's problem.
While I login to FND_TOP/admin/import directory,I am not seeing any lct or ldt file there.How to get all those files?
And also how can I understand which ldt is for which menu?
|
|
|
|
|
|
|
|
|
|
|
|