Following is List of articles for Oracle Apps Technical Questions
Alternatively, Go through the following Top 10 Oracle Apps Technical Questions
List of Oracle Apps Technical Interview Questions – Part 6
1. What are steps to register a discoverer report?
2. How to repeat the header of the template on each and every page of the output?
3. How many ways we can display images in a BI Publisher Report?
4. What is dynamic SQL?
5. What are the differences between Function and Procedure?
6. What is the SQL statement used to display the text of a procedure stored in database?
7. Can you call a sequence in SQL Loader?
8. What is the impact of exclusion of a function from a responsibility.
9. How Concurrent Manager Manages the Requests with Different and Same Priorities?
10. What is the Life Cycle of a concurrent Request?
11. What is the Range of Priorities of Concurrent Programs and whats the default Value?
12. What is the Level of Priority in Profile Option among (Site, Application, Responsibility, User)?
13. Can we use Profile Option’s Value is Concurrent Program’s Parameters?
14. What is NOCOPY Compiler hint? What is the purpose to use it in OUT Parameters in Oracle Procedures?
15. How to stop processing for Errors in Oracle Forms PL/SQL?
16. How to stop processing for Errors in Oracle Stored Procedure?
17. What is datatype of Forms Global Variable?
18. How does the command POST differs from COMMIT in Oracle Forms ?
19. Which Method should be used for exiting the form ?
20. What are the replacement for set_item_property and get_item_property methods?
Following are the steps to register a discoverer report in Oracle Apps. Make sure you followed each and every one correctly.
1. Login to Application Developer–>Function
2. Enter Function, User Function Name, Description (Optional) in Description Tab.
3. In Properties Tab, Select Type “SSWA jsp function”
4. In Form Tab, provide following details in Parameter Field mode=DISCO&workbook= ¶meters=~*~*~
Note: Parameter is an option thing
5. In HTML Tab, write OracleOasis.jsp in HTML Call field
6. Now navigate to Responsibility which contains the Menu to which you added this function.
7. Click the Function Name to Display the report.
use in order to repeat that specific section in each page of the output and also to reset the page number.
It can be done in 5 different ways
1. Direct insertion into RTF template
2. URL Reference
3. OA_MEDIA directory reference
4. Images from BLOB datatype from database
5. Using UI Beans
Dynamic SQL allows you to construct a query, a DELETE statement, a CREATE TABLE statement, or even a PL/SQL block as a string and then execute it at runtime.
Function has to return a value where procedure does not return value. Function can be used in SQL statements and procedures cannot.
select text from dba_source where name = ‘Procedurename’
When you exclude a function from a responsibility, all occurrences of that function throughout the responsibility’s menu structure are excluded.
The priority of a concurrent request is determined by application username, and is set by the System Administrator using the Concurrent:Priority user profile option.
The first available concurrent manager compares the request’s priority to other requests it is eligible to process, and runs the request with the highest priority.
When choosing between requests of equal priority, the concurrent manager runs the oldest request first.
A concurrent request proceeds through three, possibly four, life cycle stages or phases:
Pending Request is waiting to be run
Running Request is running
Completed Request has finished
Inactive Request cannot be run
Within each phase, a request’s condition or status may change.
Priorities range from 1 (highest) to 99 (lowest). The standard default is 50.
site has the lowest priority, superseded by application, then responsibility, with user having the highest priority.
Profile option settings may be used as a default value for a concurrent program’s parameter or flexfield’s segment.
To use a profile option’s setting as a default value, navigate to the form’s Default Type field and select Profile. Then, enter the profile option’s internal name in the Default Value field
Oracle has two methods of passing passing OUT and IN OUT parameters in PL/SQL code:
Pass By Value: The default action is to create a temporary buffer (formal parameter), copy the data from the parameter variable (actual parameter) to that buffer and work on the temporary buffer during the lifetime of the procedure. On successful completion of the procedure, the contents of the temporary buffer are copied back into the parameter variable. In the event of an exception occurring, the copy back operation does not happen.
Pass By Reference: Using the NOCOPY hint tells the compiler to use pass by reference, so no temporary buffer is needed and no copy forward and copy back operations happen. Instead, any modification to the parameter values is written directly to the parameter variable (actual parameter).
Under normal circumstances you probably wouldn’t notice the difference between the two methods, but once you start to pass large or complex data types (LOBs, XMLTYPEs, collections etc.) the difference between the two methods can become quite considerable. The presence of the temporary buffer means pass by value requires twice the memory for every OUT and IN OUT parameter, which can be a problem when using large parameters. In addition, the time it takes to copy the data to the temporary buffer and back to the parameter variable can be quite considerable.
RAISE FORM_TRIGGER_FAILURE is used to halt the processing if any business rule fails in Oracle Forms PL/SQL.
Use FND_MESSAGE to display an error message,then to stop processing use following code:
IF (error_condition) THEN
If a failure occurs in a stored procedure and you want to stop further Processing, use the package procedures FND_MESSAGE.SET_NAME
to set a message, and APP_EXCEPTION.RAISE_EXCEPTION to stop processing:
IF (error_condition) THEN
Post writes data in the form to the database but does not perform database commit. Commit permanently writes data in the form to the database.
The Oracle Applications forms have special exit processing. Do not call EXIT_FORM directly;
always call do_key(’EXIT_FORM’). To exit the entire Oracle Applications suite, first call:
Replace with APP_ITEM_PROPERTY.SET_PROPERTY and APP_ITEM_PROPERTY.SET_VISUAL_ATTRIBUTE.
These APPCORE routines set the properties in the Oracle Applications standard way and change the propagation behavior. Some properties use the native Oracle Forms SET_ITEM_PROPERTY. For a complete list of properties that APP_ITEM_PROPERTY.SET_PROPERTY covers, see the documentation for that routine.
Use APP_ITEM_PROPERTY.GET_PROPERTY when getting Oracle Applications specific properties. Use the Oracle Forms built–in when setting or getting other properties.
Oracle HRMS Interview Questions
Question of the Day
9 Steps to become Oracle Apps Consultant
How to create backend logging mechanism
Steps for creating custom form in Oracle Apps
Clear Global Cache in Oracle Apps
Profile Values in Oracle Forms Personalization
2 simple Steps to make a responsibility read only
Step to Register Discoverer Report
Hierarchy of OLM Tables