If you're looking for Oracle EBS Interview Questions for Experienced or Freshers, you are at right place. There are lot of opportunities from many reputed companies in the world. According to research Oracle EBS has a market share of about 8.2%. So, You still have opportunity to move ahead in your career in Oracle EBS Development. Mindmajix offers Advanced Oracle EBS Interview Questions 2019 that helps you in cracking your interview & acquire dream career as Oracle EBS Developer.

Q1. What is purpose of applsyspub user in Oracle EBS?

APPLSYSPUB is an initial, pre-authentication user with minimal privileges to assist with APPS (FND) user authentication. Usernames and passwords are stored in the FND_USER table, we need to have a pre-connection to the database. This connection is established using APPLSYSPUB user. After successfull login, associated database login will switch to APPS user from APPLSYSPUB user. APPLSYSPUB has only Read-Only privileges on a few tables and views for signing on to Applications.

Q2. What is purpose of Applications Listener in Oracle EBS?

During concurrent managers startup ICM instructs Applications Listener to spawn FNDSM (Service manager) process.
You can confirm this by checking listener.ora configuration file on apps tier, which is located under directory





                ( ORACLE_HOME = /u01/app/apps/fs1/EBSapps/10.1.2 )

                ( PROGRAM = /u01/app/apps/fs1/EBSapps/appl/fnd/12.0.0/bin/FNDSM )



FNDSM_SCRIPT=/u01/app/apps/fs1/inst/apps/PROD_tvmdb19/admin/scripts/gsmstart.sh’ )
Q3. Is it possible to run two adpatch sessions simultaneously for one EBS instance?

It’s possible to run several adpatch sessions, but they will eventually fail. At different stages of work you may get different errors. One of them related to FND_INSTALL_PROCESSES table which is created to keep track of what jobs adpatch workers are doing. Sample error message:
The table FND_INSTALL_PROCESSES created by AutoPatch already exists.
If you are sure you do not want to keep the information from the failed
AutoPatch session,you may drop FND_INSTALL_PROCESSES table and
continue with AutoPatch.
If you choose not to drop FND_INSTALL_PROCESSES table, AutoPatch
cannot continue successfully.

Q4. What is procedure of patching in case of multi-node EBS installation and non-shared application tier?

In this case you have to apply patches on every application node. Also the answer depends on EBS release number. If it’s 11i, then you have to start patching from node where administration server is located. Reason for that  – adpatch runs database part of unified driver only on node where administration server is located.
Release R12 eliminated need for DBAs to pay attention at patching sequence. Here is quote from R12 concepts: “There is no concept of an Administration server in Release 12. By default, patching can be undertaken from any application tier node.”

Q5. Is it required to run autoconfig on all nodes in case of Shared Application Tier multi-node installation?

Yes. All configuration files created by AutoConfig are stored under the Instance Home. So to update all Instance Homes it’s required to run autoconfig on each node.

Q6. Does ICM (Internal concurrent manager) processes concurrent requests?

Subscribe to our youtube channel to get new updates..!

It does, but only specific ones. ICM controls other concurrent managers and executes queue control requests, such as ACTIVATE, DEACTIVATE, or ABORT

Check Out Oracle EBS Tutorials

Q7. If ICM is terminated abnormally (for example killed), will other managers continue to process requests?

Yes, other managers will continue to perform their usual work. However it doesn’t apply to the case when you stop ICM using Administer concurrent managers form. In this case, other managers will be shut down.

Q8. What is the Directory structure on the server ?

Application Directory
bin sql log srw mesg
lib rpt forms out plsql
( lang )
1. Bin : Contains executable code of your concurrent programs written in a programming language such as C, Pro*C, Fortran, or an operating system script.
2. Lib : Contains compiled object code of your concurrent programs.
3. Sql : Contains concurrent programs written in SQL*Plus and PL/SQL scripts.
4. Rpt : Contains concurrent programs written with SQL*Reports.
5. Log : Contains log files from concurrent programs.
6. Forms/(Language) : Each language has a subdirectory ( such as US ). The language subdirectory holds the forms .fmx files.
7. Srw : Contains concurrent programs written with Oracle Reports.
8. Out : Contains output files from concurrent program.
9. Mesg : Holds your application message files for Message dictionary.
10. PLSQL : Contains PL/SQL libraries used with Oracle reports.

Q9. What are the salient features of Aol and Sysadmin functions?

As evident from the name AOL i.e. Application Object Library is the Library that contains all the Objects of an Application. For Oracle Apps. To recognize any object, such object must be registered with this Library.

Salient Features –
1. Registering Tables with Oracle Apps.
2. Registering Forms with Oracle Apps.
3. Registering Concurrent Programs with Oracle Apps.
4. Building Menus.
5. Building Flexfields.
6. Enabling Zoom.
7. Building Message Dictionary.

1. Manage Oracle Applications security.
2. Manage Concurrent programs & Reports.
3. Manage Concurrent processing.
4. Manage Printers.
5. Manage Profile Options.
6. Manage Document Sequences.

Q10. How do you create a customized form in Apps?

You will find it in c:Apps10Fnd75FormsUs

Features –

Starting your form with TEMPLATE is the only way to ensure you get the following:
a) Applications Property Classes and Visual Attributes.
b) Toolbar.
c) Menu.
d) Calendar.
e) Required Form-Level triggers.
f) Required Procedures.
g) Applications color palatte.
h) Required Parameters.
i) Required LOVs and Record Groups.
j) And much more !

Q11. Which PlSql libraries are used in customization of form and for what purpose ?

Attached Libraries Used in forms development –

a) APPCORE – Supports Form and User Interface Features.
Packages and Procedures that support the menu, Toolbar and other standard behaviours.
Use APPCORE routines to enable fields to enable fields dynamically, maintain dependencies between items, and control specific window behaviours.
c) FNDSQF – Supports Many Application Object Library Features.
Most AOL extensions such as message dictionary, multicurrency, WHO information tracking.
Includes Flexfield packages and procedures.
d) JA
e) JL
f) JE
g) CUSTOM – Supports Zoom.
h) APPDAYPK – Supports the Calendar.

Q12. What is ZOOM ?

In certain cases, it is useful to be able to access one form directly from another. For example, it may be very convenient to be able to open the Customers form directly from the Sales Orders form, to allow entry of a new customer while creating a new order, or to view information about a customer that has already been defined. From within certain forms you can open another form directly by using the Special menu or, depending on how Oracle Applications has been customized at your site, by choosing Zoom from the Go menu.
Oracle Applications ship with no Zooms defined, and the Zoom entry on the Action menu is disabled. When this feature is available and how it behaves are determined by how Oracle Applications is customized at your site.
Zoom allows the addition of user-invoked logic on a per-block basis.

Explore Oracle EBS Sample Resumes! Download & Edit, Get Noticed by Top Employers!Download Now!
Q12. How do you register tables in Apps ? What is the PL/SQl package used for registering ?

With Release 10.6 and 10.7, you now register your custom application tables using a PL/SQL routine in the AD_DD package.
Procedures in the AD_DD Package

procedure register_table (p_appl_short_name in varchar2,
p_tab_name in varchar2,
p_tab_type in varchar2,
p_next_extent in number default 512,
p_pct_free in number default 10,
p_pct_used in number default 70);
procedure register_column (p_appl_short_name in varchar2,
p_tab_name in varchar2,
p_col_name in varchar2,
p_col_seq in number,
p_col_type in varchar2,
p_col_width in number,
p_nullable in varchar2,
p_translate in varchar2,
p_precision in number default null,
p_scale in number default null);
procedure delete_table (p_appl_short_name in varchar2,
p_tab_name in varchar2);
procedure delete_column (p_appl_short_name in varchar2,
p_tab_name in varchar2,
p_col_name in varchar2);
p_appl_short_name The application short name of the application that owns the table (usually your custom application).
p_tab_name The name of the table (in uppercase letters).
p_tab_type Use ‘T’ if it is a transaction table (almost all application tables), or ‘S’ for a “seed data” table (used only by Oracle Applications products).
p_pct_free The percentage of space in each of the table’s blocks reserved for future updates to the table (1-99). The sum of p_pct_free and p_pct_used must be less than 100.
p_pct_used Minimum percentage of used space in each data block of the table (1-99). The sum of p_pct_free and p_pct_used must be less than 100.
p_col_name The name of the column (in uppercase letters).
p_col_seq The sequence number of the column in the table (the order in which the column appears in the table definition).
p_col_type The column type (‘NUMBER’, ‘VARCHAR2?, ‘DATE’, etc.).
p_col_width The column size (a number). Use 9 for DATE columns, 38 for NUMBER columns (unless it has a specific width).
p_nullable Use ‘N’ if the column is mandatory or ‘Y’ if the column allows null values.
p_translate Use ‘Y’ if the column values will be translated for an Oracle Applications product release (used only by Oracle Applications products) or ‘N’ if the values are not translated (most application columns).
p_next_extent The next extent size, in kilobytes. Do not include the ‘K’.
p_precision The total number of digits in a number.
p_scale The number of digits to the right of the decimal point in a number.