Documentos de Académico
Documentos de Profesional
Documentos de Cultura
Question: Why does one need to use FNDLOAD FOR WEB ADI?
Answer : In any implementation that uses Web ADI, the setup for formatting letters and docments can be overwhelming.
More importantly, once configured on a development environment you would not like to repeat the tedious setup on test,
crp or other environment. Using FNDLOAD you can migrate 99% of your setup.
Question : What are the man steps when using FNDLOAD for Web ADI?
Answer :
First step
Identify the pieces that must be moved across using fndload. These can be:-
 Integrators
 Layouts
 Mappings
 Contents
This article covers the above listed components one by one.
Second step
Download the above web adi attributes into various ldt files. Basically we will create one ldt file for each of the above four
web adi entities.
Third step
Upload those ldt files into the new environment. For this we will run the fndload in upload mode.
Question: How do I execute Step 1, given that FNDLOAD requires the internal names of these entities, these internal
names are not visible from the Web ADI screens?
Answer: In this example,I will demonstrate using scripts how to recognize the web adi components Names for fndload.
SQL will be provided to identify the internal names.
This will return two internal codes, both in application PER (Application ID 800). Lets say the two internal codes are
HR_101_INTG & HR_41_INTG.
Answer :Â To identify the layout codes codes, run the below SQL.
Now in order to upload these into new environment, use below commands
FNDLOAD apps/$APPS_PASSWORD 0 Y UPLOADÂ $BNE_TOP/admin/import/bnelay.lct XX_C_O_F_T.ldt
To upload these files into a new environment, ftp the ldt files and run below commands on the new environment
For each content code returned by SQL above, we will now do FNDLOAD as below