Oracle Apps Notes

A collection of my random notes, primarily on Oracle Apps

Monthly Archives: January 2012

Long awaited goodbye to the Flash-based My Oracle Support

I came to know from Marc Fielding’s post that the Flash-based My Oracle Support is finally on the way out. Just the kind of good news to brighten up a Tuesday morning. Ever since it was introduced in 2009 with noble intentions, Flash-based MOS has had more critics than supporters. And with HTML5 starting to kill off Adobe Flash, it was about time MOS realised that the Flash-based version had to go.

The HTML version of MOS, supporthtml.oracle.com is available for user acceptance testing while the Flash-based version will continue to be available. As the kinks get ironed out MOS should finally transition into the HTML version in the near future.

Speaking of kinks, there already seems to be one since the HTML version does not work in Google Chrome(16.0.912.77). It works fine in Internet Explorer(8) and Firefox(7.0.1) though.

Update: Now, works on Google Chrome too 🙂

And here is an example of one of those annoying bugs in the Flash-version(observed using Firefox and Chrome):

1. Log on MOS, enter a search term in the search box on the top-right corner and click on the search icon.
2. After the results are displayed, another search box is displayed on the left hand side of the page. Click on the ‘Advanced’ link for this search box.
3. In the Advanced search section that is displayed, select a relevant ‘Product’ to refine your search and click on ‘Search’.
4. You will notice that the area of the page where the Advanced search section was displayed in the previous step is now blank and the search results are visible below the blank area.

Do I need to tell you explicitly that the HTML does not exhibit this buggy behaviour?

Thank you Flash-based MOS, your short-lived, bug-ridden life is almost over. Welcome HTML MOS.

Advertisements

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%

5. Select check boxes for PROFILE_OPTION_CACHE & PROFILE_OPTION_VALUE_CACHE

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.

Installing Oracle 11gR2 on RHEL 5(running on Oracle VirtualBox)

Finally completed installing Oracle database 11gR2(11.2.0.1.0) on a VirtualBox virtual machine running RHEL 5 after having postponed it for a number of times. I followed this document by Zahid Karim but there were some minor differences since his was a RHEL 5.5 system while mine is RHEL 5. Below are some notes regarding my installation process:

1. The RHEL 5 virtual machine was created with 20GB storage and 1.5GB memory

2. The allocations for the swap space and various partitions:

swap – 2250 MB
/tmp – 2048 MB
/boot – 100 MB
/root – 7168 MB
/u01 – 7168 MB

The minimum recommended space required in /tmp is 1GB. But note that the installer will check for 1GB available space in /tmp only after it is invoked, by which time the OS and the installer itself has used more than 300MB of space in that partition. This factor should be taken into consideration while creating the partition.

3. Pre-requisite packages elfutils-libelf-devel-0.125-3.el5.i386.rpm and elfutils-libelf-devel-static-0.125-3.el5.i386.rpm are dependent on each other and hence have to be installed together


[root@db11gr2 Server]# rpm -Uvih elfutils-libelf-devel-0.125-3.el5.i386.rpm elfutils-libelf-devel-static-0.125-3.el5.i386.rpm
warning: elfutils-libelf-devel-0.125-3.el5.i386.rpm: Header V3 DSA signature: NOKEY, key ID 37017186
[root@db11gr2 Server]#

4. The version of the sysstat package in RHEL 5 is of a lower version. Had to download and install the minimum required version, sysstat-7.0.2-1.el5.i386.rpm.

5. Other packages whose higher versions has to be installed are:

glibc-headers-2.5-24.i386.rpmglibc-devel-2.5-24.i386.rpmglibc-common-2.5-24.i386.rpmglibc-2.5-24.i386.rpm. These are dependent on each other and had to be installed in the same way as the elfutils* packages in step#3.

PS: The 10g client works fine with a 11g server.