Oracle Apps Notes

A collection of my random notes, primarily on Oracle Apps

Handy Notes-II

1. Use of <PROPERTY_NAME>(APPLICATIONS COVER) in Form Personalization

You are personalizing a Form and you want the DISPLAYED property to be set to FALSE for an item. While you are at it you will notice that there are two versions in the Property Name field- one is the normal ‘DISPLAYED’ and the other is ‘DISPLAYED (APPLICATIONS COVER)’. Ever wondered what is the difference between these two? Well, the difference is explained in the  Developer’s Guide.

Oracle E-Business Suite provides a cover routine to the Oracle Forms built-in routine SET_ITEM_PROPERTY. This cover routine, APP_ITEM_PROPERTY.SET_PROPERTY, modifies or augments the native Oracle Forms behaviors for specific properties. Using APP_ITEM_PROPERTY.SET_PROPERTY helps your forms adhere to the Oracle E-Business Suite user interface standards and helps simplify coding. Using this routine also helps to protect your form from future changes in the native Oracle Forms SET_ITEM_PROPERTY built-in routine.

In short, ‘DISPLAYED (APPLICATIONS COVER)’ makes use of the EBS cover routine APP_ITEM_PROPERTY.SET_PROPERTY while ‘DISPLAYED’ uses the Forms built-in SET_ITEM_PROPERTY. For more details you can check the ‘Setting Item Properties’ section of the Developer’s Guide.

2. Changes to profile options not taking effect

Sometimes it is observed that changes made to profile options do not take effect until Apache server is bounced. The culprit in such a scenario might be Java Caching. Java caching provides a powerful, flexible, easy to use mechanism for storing database results and other Java objects in-memory for repeated usage. This minimizes expensive object initializations and database round-trips, thereby improving application performance. The profile option issue can be solved by clearing the cache by following the following steps:

1. Log into the application with the the Functional Administrator responsibility

2. Choose the Core Services Tab > Caching Framework subtab

3. Click on ‘Total Cache Components’ hyperlink

4. Search for code : PROFILE%OPTION%


6. Click on ‘Clear Cache’ button

Further information on Java Caching:

1. Metalink Note#275879.1 -Oracle Applications Java Caching Framework Developer’s Guide Release 11i
2. Metalink Note#395439.1 -Oracle Applications Java Caching Framework Developer’s Guide Release 12
3. Metalink Note#455194.1 -Diagnosing database invalidation issues with Java Cache for eBusiness Suite

3. Controlling access to the Diagnostics menu and submenu items

Utilities: Diagnostics – Utilities: Diagnostics determines whether a user can automatically use the following Diagnostics submenu items: Examine, Trace, Debug, Properties, and Custom Code. If Utilities:Diagnostics is set to Yes, then users can automatically use these features. If Utilities:Diagnostics is set to No, then users must enter the password for the APPS schema to use these Diagnostics features.

Hide Diagnostics Menu Entry – If this profile is set to Yes, the Diagnostics menu is hidden from the user.


One response to “Handy Notes-II

  1. Pingback: Enabling access to Oracle Forms-based Applications Diagnostics Menu « Oracle Apps Notes

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

%d bloggers like this: