1. Get rid of all advertisements and get unlimited access to documents by upgrading to Premium Membership. Upgrade to Premium Now and also get a Premium Badge!
  1. talk2vinni
    Oracle Apps Technical Interview Questions
    Below is the list of question asked in Oracle Apps Technical Interviews.
    1. Explain Directory Structure of APPS?
    2. Oracle Application has a file system as shown in the below picture for the APPL_TOP Directory.
    4. GL_TOP: (APPL_TOP/GL/11.5.0) is one of the Module Directory of Oracle Applications. It consists of a release directory (i.e. 11.5.0) under which Forms, Reports, BIN, LIB, SQL, etc.,
    5. Forms/US: Forms directory to store all .FMX (Compiled) Form files of a specific module.
    6. Reports/US: Reports directory to capture all the .RDF (Compiled) Report files of a specific module directory.US is a language specific directory.
    7. BIN: Contains executable code of concurrent programs written in a programming language such as C, Pro*C, Fortran, SQL *LOADER or an operating system script.
    8. LIB: Contains compiled object code (.OBJ files) of your concurrent programs.
    9. SQL: Contains concurrent programs written in SQL*Plus and PL/SQL scripts.
    10. HTML: Contains all .HTML, .HTM web files.
    11. LOG: Contains all .LOG files of concurrent programs.
    12. OUT: Contains output files from concurrent program.
    13. Message: Holds your application message files for Message dictionary.
    {StickyNote}{/StickyNote}The root structure is HOME. Under HOME we have APPS and INST directory.APPS directory has APPL_TOP and the installation of forms OH and application server 10g.The E-Business suite and Application Server used is 10g.The directory 10.1.2 belongs to form oracle home and directory 10.1.3 belongs to application server oracle home.Since these are the underlying technology they are grouped under TECH_ST.APPS_ST contains the APPL_TOP and COMMON_TOP. In apps11i the APPL_TOP directory used to have format appl, where as in R12 this has been changed as simply appl directory.

    R12 Directory Structure:

    INST directory is an instance directory.We have a new environment variable in R12 called as INST_TOP, which points in this directory.It contains all the config files,log files,ssl certificates,document root ect.Multiple instances can easily share the same middle tier/DB by creating a new instance_top with proper config files and nfs mount the middle tier in the server.

    In 11i we have 3 top directory under HOME directory.appl which is APPL_TOP,comn which is COMMON_TOP and ora.In ora we hace 8.0.6 directory which is ORACLE_HOME for forms and iAS directory which is ORACLE_HOME for 9i Application Server.

    There is a change as well in the JAVA_TOP. In R12 $JAVA_TOP is $COMMON_TOP/java/classes which contains classes and archives in $COMMON_TOP/java/lib.Where as in 11i both the archives and classes are in $COMMON_TOP/java.

    In 11i release all the config/log files were in COMMON_TOP. This has been shifted to INST_TOP.The admin directory is in the $INST_TOP in R12 and the same is in $COMMON_TOP in 11i.

    2. How to activate, deactivate and run Concurrent Managers?
    Oracle Apps Configuration Tutorial - Concurrent Manager

    Here we will see in details how we can define concurrent manager in oracle R12. As you are aware a concurrent manager itself is a concurrent program which runs other concurrent manager. So, lets see how we can define this manager.

    The following steps are involved during defining a concurrent manager.
    1. Assignation of predefined library of concurrent programs with the new concurrent program.
    2. Assigning the work shift with new concurrent manager which determines the work time of the manager.
    3. maximum number of OS processes need to be attached with the work shifts.
    4. Define some specialization rules to read only some specific requests.

    There are two predefined manager with Oracle apps R12.

    1. Internal concurrent manager
    2. Standard manager = This concurrent manager is up and running all the time and has no specialization rule.

    Transaction Manager
    While normal concurrent manager runs the conc program in asynchronous mode[it may not run the request on immediate basis], but, the transaction manager runs conc request in synchronous mode that means while a client request comes, it executes immediately.

    Defining Work shifts [System administrator > Concurrent > Manager > workshifts]
    For defining the conc manager you need to first define the work shift which defines when a conc program will run. If there are overlap of workshifts time, then priority will be given as per the following rule.
    Priority Work Shift Definition
    1 Specific date and range of times
    2 Specific date and no range of times
    3 Range of days and range of times
    4 Range of days and no range of times
    5 Range of times and no date and no range of days
    6 Standard work shift. No date, days, or time defined.
    If there are still overlap in same priority level, workshifts with largest target processes will be selected.

    Creating or defining a new Concurrent Manager
    System administrator > Concurrent > Manager > Define
    The important field definition in this form is as follows.
    Cache size = If the cache size is 4 and workshift process is 2, then it will read 4 reqs but run only 2 reqs at once.

    Rules field during defining a concurrent manager
    Rules are used to run only certain types of requests.

    [For more specific details about "Define Conc Manager" and "workshifts" form check R12 chapter 7 in "System administrator's Guide Configuration" ]


    The following commands are used to control internal concurrent manager from OS level.
    Activate concurrent manager = STARTMGR (syntax may vary with platform)
    Verify concurrent manager status = CONCSUB FND VERIFY
    Deactivate concurrent manager = CONCSUB FND DEACTIVATE
    Terminate requests and deactivate manager = CONCSUB FND ABORT

    As an example, the following command can be used to start the internal concurrent manager.
    $ startmgr sysmgr="/" mgrname="std"
    printer="printer1" mailto="myname" restart="N"
    logfile="mgrlog" sleep="100" pmon="6" quesiz="10"
    The CONSUB utility is used to shutdown the managers. This OS based utility is useful if we need to schedule the shutdown of conc manager from OS level at certain time.


    Parallel Concurrent Manager
    Since Internal Conc Manager requires high fault tolerance, in parallel conc processing Internal Monitor Process is used. Internal Monitor Process runs on every node, if any IMP notices that internal conc manger has failed, it starts the ICM in its own node.


    Important Screens for Concurrent Manager
    System administrator > Concurrent > Administrator = This form is used to check the status details of conc manager and control the manager
    System administrator > Concurrent > Define = Used to define a new manager
    System administrator > Concurrent > Workshifts = Used to define the workshifts

    Most of the fields of the above forms are self explanatory. For any confusion, check page 240-265 of R12 "System administrator's Guide Configuration".


    Starting the Concurrent Manager from OS level
    Use the following command to start conc manager after setting applmgr env file.
    $ startmgr \
    sysmgr="/" \
    mgrname="" \
    PRINTER="" \
    mailto="" \
    restart="N|" \
    logfile="" \
    sleep="" \
    pmon="" \
    quesiz="" \
    restart = the number of minutes the manager waits before restrt after abnormal termination. The default value is "N" which means it will not restart automatically after abnormal termination.
    sleep = The number of seconds internal conc manager waits between checking the ques for status of conc requests.
    pmon=Number of sleep cycle internal conc manager waits to check if conc manager have failed.
    quesiz=Number of pmon cycles (integer) the internal concurrent manager waits between times it checks for normal changes in concurrent manager operation.
    diag=whether to turn on or off diagonistic logs.

    Concurrent Manager Log files location and name
    All the conc manager log files are located in the dir $APPLCSF/$APPLLOG. The following are the specific log file names.
    ICM log = .mgr
    Concurrent Manager Log = w.mgr
    Request Log = l.req
    Request Output = o.out

    3. What is the location for concurrent request or manager logfiles and output files?
    4. Specify the standard naming conventions for the logfile and output file?
    5. How to write LOG information from PL/SQL block to log file?
    6. What is Request Group?
    7. What is Request Set?
    8. What is difference between the Request Group and Request Set?
    9. What are the steps to develop a simple Oracle Apps form?
    10. What are the important Libraries in Template.fmb?
    11. Which Concurrent Manager will run when you run the report in Oracle Application ?
    12. How to create a Multi-org report in Apps?
    13. State the mandatory parameters while developing Multi-org report in Apps?
    14. What is the Schema for AOL?
    15. What is the significance of :$FLEX$ ?
    16. State some of the FND tables?
    17. How to create Query-only form in Oracle Apps with out touching the fmb file?
    18. What is the profile option pertaining to Operating Unit?
    19. What is the difference between Applsys and Apps?
    20. How to Register Shell Script Program in Oracle Applications? How to use parameters while registering shell script as a concurrent program?
    21. How to Register PL/SQL Stored Procedure in Oracle Apps? What are the Mandatory thing we need to do for creating PL/SQL Procedure before Registering into Apps?
    22. What is Zoom? How to enable zoom feature using Custom.pll?