Oracle AOL Interview Questions and Answers

The Oracle Diagnostic Tool is provided by Oracle to gather and analyze information from eBusiness suite to diagnose an existing data issue, transactional problem or setup error through a complete set up responsibility “Application Diagnostics”.

A field is a position on a form that one uses to enter, view, update, or delete information. A field prompt describes each field by telling what kind of information appears in the field, or alternatively, what kind of information should be entered in the field.

A flexfield is an Oracle Applications field made up of segments. Each segment has an assigned name and a set of valid values. Oracle Applications uses flexfields to capture information about your organization. There are two types of flexfields: key flexfields and descriptive flexfields.

fnd_profile.value(‘USER_ID’)

or

fnd_global.USER_ID

_ALL  Table holds all the information about different operating units in a Multi-Org environment. You can also set the client_info to specific operating unit to see the data specific to that operating unit only.

Oracle definition for Priority:  Priority is used to indicate the priority that the concurrent request will be assigned when it is submitted. If you do not assign a priority, the user’s profile option Concurrent:Priority sets the request’s priority at submission.

Token is used for transferring values towards report builder. Tokens are usually not case – sensitive.

The Scheduler enables database administrators to full fill business tasks in an organized and controlled fashion.

To achieve job scheduling Oracle provides a collection of functions and procedures in the DBMS_SCHEDULER package.

Below are the major this a Scheduler can do:

• Schedule job execution based on time or events
• Schedule job processing in a way that models your business requirements
• Manage and monitor jobs
• Execute and manage jobs in a clustered environment

Autonomous Transaction is a kind of transaction that is independent of another transaction. This kind of transaction allows you in suspending the main transaction and helps in performing SQL operations, rolling back of operations and also committing them. The autonomous transactions do not support resources, locks or any kind of commit dependencies that are part of main transaction.

Application Top is a physical folder on server which holds all the executable, UI and support files.

We have two different types of Application Tops

Product Top: Product top is the default top built by the manufacturer. This is usually called as APPL_TOP which stores all components provided by the Oracle.

Custom Top: Custom top can be defined as the customer top which is created exclusively for customers. According to the requirement of the client many number of customer tops can be made. Custom top is made used for the purpose of storing components, which are developed as well as customized. At the time when the oracle corporation applies patches, every module other than custom top are overridden.

There are two types of program incompatibilities, “Global” incompatibilities, and “Domain-specific” incompatibilities.

You can define a concurrent program to be globally incompatible with another program — that is, the two programs cannot be run simultaneously at all; or you can define a concurrent program to be incompatible with another program in a Conflict Domain. Conflict domains are abstract representations of groups of data. They can correspond to other group identifiers, such as sets of books, or they can be arbitrary.

• FlexRpt: The execution file is wrnitten using the FlexReport API.
• FlexSql: The execution file is written using the FlexSql API.
• Host: The execution file is a host script.
• Oracle Reports: The execution file is an Oracle Reports file.
• PL/SQL Stored Procedure: The execution file is a stored procedure.
• SQL*Loader: The execution file is a SQL script.
• SQL*Plus: The execution file is a SQL*Plus script.
• Spawned: The execution file is a C or Pro*C program.
• Immediate: The execution file is a program written to run as a subroutine of the concurrent manager. We recommend against defining new immediate concurrent programs, and suggest you use either a PL/SQL Stored Procedure or a Spawned C Program instead.
• Request Set Stage Function: PL/SQL Stored Function that can be uesd to calculate the completion statuses of request set stages.

There are 8 different types of Value Set Validations.

None: this is the indication of minimal validation.

• Independent: Input should be there in the list of – values that are defined previously.
• Dependent: According to the previous value, input is compared with a subset of values.
• Table: Input is checked on the basis of values that exist in the application table.
• Special: These are the values that make use of flex field.
• Pair: A pair can be defined as the set of values that make use of flex fields.
• Translated Independent: This is a kind of value that can be made used only if there is any existence for the input in the list that is defined previously.
• Translatable dependent: In this kind of validation rules that compare the input with the subset of values associated with the previously defined list.

Write a PL/SQL script to submit concurrent request using FND_REQUEST.Submit() API in a file and execute that file in shell script using SQLPLUS

Example

sqlplus -s  apps/apps @XX_SUBMIT_CP.sql

We can find Custom Application top physical path from Application Developer responsibility:

navigate to Application Developer –> Application –> Register. Query for the custom application

name. The value in the field Basepath, is the OS system variable that stores the actual directory info.

‘Run Alone‘check box should be enabled in Concurrent program definition to make it run one request at a point of time.

Syntax for log:

 FND_FILE.PUT(FND_FILE.LOG, <Text>);       

Syntax for Output:

 FND_FILE.PUT(FND_FILE.OUTPUT, <Text>);

US folder is nothing but a language specific folder. Oracle Apps uses american language by default and so is the US folder.

go to applcation developer responsibilitynavigation->Application/function.query the function name then goto form tab then goto parameters field then write the following code in that fieldQUERY_YES= YES save the changes and then see the forms get affected in query only mode.

Navigate to the Update System Profile Screen.

(navigate profile system)

Select Level: Site

Query up Utilities:Diagnostics in the User Profile Options Zone.

If the profile option Utilities:Diagnostics is set to NO, people with access to the Utilities Menu must enter the password for the ORACLE ID of the current responsibility to use Examine. If set to Yes, a password will not be required.

Navigate to the Concurrent Request Summary form

• Select a request
• In character, do a Quickpick on the Status column
• You can select Cancel or Hold
• In GUI, use the Cancel or Hold buttons
• The Sysadmin responsibility can cancel or hold any running request

FND_REQUEST.SUBMIT_REQUEST ( ‘ Parameters’);

It can be generated through submission of Concurrent Program from Application Developer responsibility.

Use: oerr ora XXXX

or: oerr tns XXXX

where XXXX is the error number

(This also supports a number of other error types. Use the 3-letter error prefix in place of ‘ora’)

GUI: Use Help->About Oracle Applications

Scroll down to find the form name

Character: Use Help->Version

We can also find out through Help > About Oracle Applications

SELECT release_name FROM fnd_product_groups

SELECT MULTI_ORG_FLAG FROM FND_PRODUCT_GROUPS

If MULTI_ORG_FLAG is set to ‘Y’ Then its Multi Org.

If MULTI_ORG_FLAG is set to ‘N’ Then its single Org.

Log file get following name by default: lRequest_id.req

and Output file get following name by default:

oRequest_id.out

Output files are stored at $APPLCSF/$APPLOUT

and Log files are stored at $APPLCSF/log

These paths may vary depending on the setups that sys admins perform at the time of Oracle Apps installation

We can also recover through the following steps:

Go to system administrator responsibility > Security > Responsibility > Define > Give the particular responsibility name query on it and then see the effective dates to field. If any date is there then that repsonsibility will expire on that date and if it is null then it will not expire on any date.

You can do this with Custom.pll and if ur using apps version greater than 11.5.9 then you can do this with form personlization too

In simple wordsOrg_id referes the operating unit and and organization id refers the InventoryOrganizationRegardsKarthikeyan

$Flex$ is used when we need to return the Flex value contained by any AOL Vlauset or AOL object .

For Ex . $Flex$. would return the value held by that valueset.

$profiles$. are used to get the values of environment variables like org_id or mfg_Organization_id etc which are related to the current apps environment.

Ex. $profiles$.org_id would return the operating unit which is active at that time for the user.