R12 and R11i Product Top decoded

Last updated on July 22nd, 2018 at 05:00 pm

EBS environment has many product directories inside APPL_TOP and Each Product directories has  many directory and files inside them. We have more than 200 product directories and Each of these has similar structure. I have studied them and here is my take on these directories.
General Directory Structure of any
Product_TOP . I have taken the example of FND_TOP
   |=> admin
             |=> driver
             |=> import
                       |=> US
             |=> odf
             |=> sql
             |=> template
   |=> bin
   |=> forms
             |=> US
   |=> help
             |=> US
   |=> html
             |=> US
             |=> jsp
                       |=> fnd
                       |=> wf
             |=> txkcsa
 |=> include
   |=> java
            |=> 3rdparty
                       |=> stdalone
             |=> jar
             |=> make
   |=> lib
   |=> media
             |=> US
   |=> mesg
   |=> patch
             |=> 115
                       |=> bin
                       |=> driver
                      |=> etc
                       |=> import
                                 |=> US
                       |=> odf
                       |=> readme
                       |=> xdf
                       |=> sql
                       |=> xml
                                 |=> US
                       |=> publisher
                                 |=> templates
                                 |=> defs
   |=> reports
             |=> US
   |=> resource
             |=> US
   |=> secure
   |=> sql
|=> out
   |=> usrxit
   |=> mds
   |=> perl


Now its turn to do deep dive into individual directories

ADMIN directory explained

Admin directory contains following folder.
driver :  AutoInstall driver files (.drv) tell AutoInstall what to do.
import : Import files (.dat and .dmp), DataMerge files (.ctl, .dat, and .exp), and Applications loader files (.slt, .plt, .vlt, .clt, .msg, .wft,.jlt) are used to install seed data.
odf : Object description files (.odf) are used to create the tables and other database objects like seq,index etc
sql : SQL scripts (.sql) and PL/SQL scripts (.sql, .pls and .plb) are used to create objects and install and upgrade data.
template: Autoconfig template for various Product configuration file are stored there
driver directory decoded
it contains Phase driver files that tell AutoInstall what to do during each step of the installation/upgrade process.The installation process is broken up into several phases. AutoInstall completes one phase for every product before moving on to the next phase.
Example filenames are
Explained using “ Module” as Example  ( The files xxseq.drv, xxplb.drv, xxfile.drv and xxdep.drv can be found under $XX_TOP/admin/driver )
“xxpls.drv”, which creates package specification
“xxplb.drv” , which creates package bodies during the package bodies phase.
“xxfile.drv” ( driver file ) which lists all the files you need to run the application  which is categorized by the type of file like
– form files
– report files
– concurrent programs
– message files
This driver is very important file and list all the product specfic files in the release
import directory decoded
This is more relavant in R11i
•  Import files (.dat ) Example :-  $PER_TOP/admin/import/pertime.dat
• DataMerge files (.ctl, .dat, and .exp), and
• Applications loader files (.slt, .plt, .vlt, .clt, .msg, .wft,.jlt)
odf directory decoded
$PRODUCT_TOP/admin/odf (Object Discreptor File)  : the files used to create tables and other database objects.Oracle supplies definition of Database objects in an ODF (Object Description File) file and sometimes they are supplied in individual script files.  An ODF file contains the definition of tables, views, indexes, sequences, and privilege sets for a building block within a product.
sql directorty decoded
sql   : the SQL scripts and PL/SQL scripts used to upgrade data.
template directory decoded
it contains the product specific Autoconfig configuration files .
Example FND_TOP
afmkinit.cmd                          registersessionwithlog.cmd            txkWebServicesCfg.sql
afmkinit.sh                           registersessionwithlog.sh             txkWfClone.cmd
afTk2Motif_UTF8.txt                   robots.txt                            txkWfClone.sh
afwdbsvr.cmd                          runcol.sh                             txkWfClone.sh.Old
afwdbsvr.sh                           runpref.sh                            txkWfClone.sql
afwebprf_nt.sql                       runses.sh                             txkWfClone.sql.Orig
afwebprf_ux.sql                       runssodatan.cmd                       txkxmlctx.tmp
afwebprf.cmd                          security_nt_ias1022.conf              unregistercollector.cmd
afwebprf.sh                           security_ux_ias1022.conf              unregistercollector.sh
afwebprf.sql                          soap_ias1022.properties               unregisterpreference.cmd
antisamy                              soapConfig.xml                        unregisterpreference.sh

The concurrent programs, other C language programs and shell scripts for each product are stored in its respective bin directory. Core Executables to Oracle Applications are the FND_TOP/bin and AD_TOP/bin directories.
FNDIMON: Internal Monitor (in FND_TOP/bin)
FNDLIBR: the concurrent manager (in FND_TOP/bin)
FNDSM: Service Manager start the concurrent manager (in FND_TOP/bin)
FNDCPASS: The utility to change password (in FND_TOP/bin)
FNDMDGEN: a message file generator (in FND_TOP/bin)
adadmin: the AD Administration utility (in AD_TOP/bin)
adpatch: the AutoPatch utility (in AD_TOP/bin)
GLPOS : General ledger Posting ($GL_TOP/bin)
If these files get deleted , we can always get it by adrelink utility
adrelink.sh force=y ranlib=y “FND FNDSM”
The include directory contains header (.h) files.
These files may be required by the files contained in the lib directory for the relinking process.
Note :- Not All Products have an include directory.$PRODUCT_TOP/lib
The lib subdirectory contains files pertinent to the process of relinking Applications programs:
object files  :  (.o files), one for each C program to relink.
library file    :  (.a file) the compiled C code common to that product’s programs.

Object files
library file
The adpatch gets the new version of these files  and it used adlibin  and adlibout utility to rebuild the .a file

-There are many SQL*Plus scripts used by Oracle Applications for concurrent  processing.
-These scripts are stored as .sql files in this subdirectory.
-These scripts typically produce reports or perform concurrent processing.


-The Applications Forms client applets display text and graphics in the form of .gif files.
-The media directory contains all product specific .gif files.


–To make the translation process easier, the messages that the forms and concurrent programs use are stored in message files, separate from the forms and programs
-The mesg directory holds those message files per product
-Applications forms display messages at the bottom of the screen and in pop-up boxes.
-Applications concurrent programs print messages in their log and output files.
.-Each product’s mesg directory contains one or more message files for the language-specific messages that the product uses:
-US.msb is the binary message file used at runtime.
-If you install a non-English language version of Oracle Applications, then you have an additional message file that contains the translated messages for that language.
-The file name is .msb
– We use adadmin to generate the messages files

There are two methods for storing log and output files:
1) in each product’s log and out directories, which is the default or. The default directory and the default file names can be changed by changing the APPLLOG and APPLOUT environment variables in the Application env file.By default, $APPLLOG is set to ‘log’ and $APPLOUT is set to ‘out’.
2) a common log and output subdirectory.You can consolidate all product log and out files into one directory by defining the APPLCSF environment variable in the application env

The log directory holds
1) concurrent log files from each concurrent request and
2)  the concurrent manager log files.
3) Log File Name of a Concurrent Request will be :- l.req ( small “L” )

The out directory holds
1. The concurrent report output files.
2 The default locations for these two files are _TOP/log and _TOP/out

Leave a Reply