Oracle E-Business Suite Objects Mapping Between 11i and R12

Oracle E-Business Suite Objects Mapping Between 11i and R12

You can download the Oracle E-Business Suite Objects Mapping Between 11i and R12 files from the following link:

Oracle_E-Business_Suite_Objects_Mapping_Between_11i_and_R12_(11.5.10.2_12.1.3).rar

 

 

 

 

 

 

Advertisements

Viewer: Text Profile Option

Viewer: Text

The Viewer: Text profile option allows you to send report output directly to a browser window rather than using the default Report Viewer. Enter “Browser” in this profile option to enable this feature.

Users can see and update the Viewer:Text profile option.

This profile option is both visible and updatable at all four levels.

 
Level Visible Allow Update
Site Yes Yes
Application Yes Yes
Responsibility Yes Yes
User Yes Yes

The internal name for this profile option is EDITOR_CHAR.

JSP Pages Hanging in R12 After Removing Cached Class Files in _pages (Doc ID 433386.1)

Applies to:

Oracle Applications Technology Stack – Version 12.0.6 to 12.1.3 [Release 12.0 to 12.1]
Information in this document applies to any platform.
***Checked for relevance on 03-April-2013***

Symptoms

In Release 12 after removing a compiled class files from the JSP pages in the directory $COMMON_TOP/_pages and then bouncing the 10GiAS server, calling JSP pages results in a hanging ‘blank’ screen.

In Release 11i when performing the same steps, new class files are created automatically when the JSP page is called from a browser session and JSP was rendered fine.

In Release 12 it’s observed that when calling the JSP no class file is created in the directory $COMMON_TOP/_pages

Changes

Removing a class files from $COMMON_TOP/_pages

Cause

The root-cause of the hang is the fact that the JSP is not ‘translated’ into the associated class file in the _pages directory. This is a mandatory step for processing the JSP page.

The reason this is not happening in R12 is because of the following setting the $INST_TOP/ora/10.1.3/j2ee/oacore/application-deployments/oacore/html/orion-web.xml

<init-param>
<param-name>main_mode</param-name>
<param-value>justrun</param-value>
</init-param>
</servlet>

When main_mode = justrun the OC4J container running the OACoreGroup is told that no compilation on the fly is allowed and only (pre)compiled classes are picked up. Since these have been removed, the processing of the JSP page is blocked.

Solution

Use the ojspcompile.pl perl script to perform a manual pre-compilation of the JSP pages. The following command will compile all the JSP pages and build up the JSP cache again.

Unix: # perl $FND_TOP/patch/115/bin/ojspCompile.pl –compile –flush -p 2

Windows: C:> perl -x <FND_TOP>\patch\115\bin\ojspCompile.pl -compile -flush

This utility is also used by the AD utilities to perform this action such as when patches are applied that replace one or more JSP pages.  See Note:215268.1 for other command line options and examples.

An alternative is to change the value for the main_mode parameter to recompile (instead of justrun)

This can be achieved with the following steps

  • Use the Context editor to change the value for “s_jsp_main_mode” in the <SID>_<hostname>.xml file used by autoconfig and change value from justrun to recompile
  • Run Autoconfig to propagate the changes to the configuration files
  • Verify that now the $INST_TOP/ora/10.1.3/j2ee/oacore/application-deployments/oacore/html/orion-web.xml  has

    <init-param>
    <param-name>main_mode</param-name>
    <param-value>recompile</param-value>
    </init-param>

  • Test the scenario failing before.
  • See that now a new _<jspname>.class is created when the JSP page is called.
For production environment the manual ‘ojspcompile.pl’ method is recommended for the following reasons

  • With ‘justrun’ a fixed set of JSPs are used which will not automatically change. With ‘recompile’ the JSP pages replacing existing ones will recompile automatically while the environment is up and running.  This may lead to errors for the users when compilation fails or in having different versions of the JSP being used within a single session.
  • Using ‘justrun’ improves performance by skipping the check for compilation being needed.

How To Clear The Cache Using Functional Administrator? (Doc ID 759038.1)

Applies to:

Oracle iProcurement – Version 11.5.1 to 12.0.0 [Release 11.5 to 12]
Information in this document applies to any platform.

Goal

How can the ‘Clear all Cache’ be selected through the Functional Administrator responsibility to ensure newly changed profiles that pertain to iProcurement are now being considered?

Solution

WARNING: Clearing the OA Framework cache in a PRODUCTION instance can cause data issues if multiple users are engaged and transacting data in the application at the time cache is cleared.  Please only utilize this in Production if advised by Oracle Support Services or Oracle Development.

Many times when setting profile options that pertain to iProcurement, to ensure that the new profile values are invoked immediately, the following actions can be taken using the Functional Administrator.

Examples that may require this action to be taken are as follows:
–  iProcurement Preferences (these values actually are User level profile options)
– FND Diagnostics – to enable diagnostics
– FND Debug Log Enabled – which engages further debugging to FND_LOG_MESSAGES table
– Personalize Self Service Defn – commonly used profile to enable the Personalization Links
– Newly added responsibility is not visible in the list of Responsibilities after logging into the application

The following steps are to be utilized to clear all the cache, forcing a refresh and requery of all profile values for the user in question.

1. Login and choose the Functional Administrator responsibility – then choose Home.

image12.  Choose the Core Services Tab – then the Caching Framework Sub-Menu (In the dark blue region).
– Proceed to choose ‘Global Configuration’ from the left hand side menu that appears
– In the far right choose ‘Clear all Cache’ button

image23. A screen prompts and confirms that the action will clear all cache on the middle tier server – choose Yes.
Essentially, this just forces all user sessions to engage and validate – rather than using cached values.

image3
4.  A confirmation message is displayed, confirming that all cache has been cleared across middle tiers.

image4
5. Proceed to test and confirm whatever change was made to the preference, profile, etc….

WARNING: Clearing the OA Framework cache in a PRODUCTION instance can cause data issues if multiple users are engaged and transacting data in the application at the time cache is cleared. Please only utilize this in Production if advised by Oracle Support Services or Oracle Development.

How To Clear Caches (Apache/iAS, Cabo, Modplsql, Browser, Jinitiator, Java, Portal, WebADI) for E-Business Suite? (Doc ID 742107.1)

Applies to:

Oracle Applications Technology Stack – Version 11.5.9 to 12.2.2 [Release 11.5 to 12.2]
Information in this document applies to any platform.

Goal

Sometimes it is recommended by Support or Development to clear Apache, Browser, Java, Jinitiator or
other caches in E-Business Suite environment. This document simply provides you with the methods to accomplish this.
The users shouldn’t be connected to the Applications during this task.

Solution

Apache / iAS

For 11i and earlier versions:

– shutdown iAS server
– go to $OA_HTML (for 11.5.9) or $COMMON_TOP (for 11.5.10.x) directory
– backup the directory _pages and delete its contents by running for instance:

rm -rf $COMMON_TOP/_pages/*

– for modplsql caches remove contents of  $IAS_ORACLE_HOME/Apache/modplsql/cache directory
– restart iAS server

To clear middle tier cache in release 12:

– go to “Functional Administrator” responsibility
– select Core Services => Caching Framework => Global Configuration => Clear cache
(please review Note 759038.1 for details).

In case you have login issue after accidentally cleared the _pages instead of using the method above for r12
please review Note 433386.1 to recompile jsp files.

Cabo

Images and style sheets can be corrupted or out of sync in the cabo caches,
you may need to clear the related directories after backup:

$OA_HTML/cabo/images/cache
$OA_HTML/cabo/styles/cache

Web Browser

for Internet Explorer:

– go to menu Tools => Internet Options,
– select ‘General’ tab,
– click on button ‘Delete Files’ in ‘Temporary Internet files’ area
or
– click on button ‘Delete…’ then in ‘Delete Browsing History’ pop-up window click on ‘Delete Files…’
– close all IE windows and restart new browser session.

for Mozilla Firefox:

– go to menu Tools
– select ‘Clear Private Data…’ or ‘Clear Recent History…’ then check ‘Cache’
or
– go to menu Edit or Tools
– select Preferences or Options.
– expand the ‘Advance’ options and choose ‘Cache’ or Privacy
– click the button called ‘Clear Cache’.

for Safari:

– go to Safari menu
– select Empty Cache => Click ‘Empty’ in the dialogue box

for Netscape:

– go to menu Edit => Preferences,
– choose ‘Cache’ in ‘Advanced’ category,
– click on buttons ‘Clear Memory Cache’ and ‘Clear Disk Cache’.
– close all Netscape windows and restart new browser session.

Jinitiator

Two possibilities depending of the Jinitiator version:

for 1.1.8.x versions:

– delete all files in directory:

C:\Program Files\Oracle\Jinitiator <version>\jcache\

for 1.3.1.x versions:

– go to Start => Parameters => Control Panel
– double-click on “Jinitiator <version>” icon
– in the new pop-up window, click on “Cache” tab
– click on “Clear Jar Cache ” button. On prompt, click Yes.

(you can also delete directly all files under directory:
C:\Documents and Settings\<your user name>\Oracle Jar Cache)

Java

Java/JRE plug-in (Windows)

– go to Start => Parameters => Control Panel
– double-click on ‘Java’ icon
– in the new pop-up window, click on ‘General’ tab
– click on ‘Setting…’ button in ‘Temporary Internet files’ area then click on ‘Delete Files…’ button
(you can select Applets, Applications or other files)

JVM

– go to responsibility “Functional Administrator”
– click on “Core Services” tab then the “Caching Framework” sub-tab
– click on “Global Configuration” link then click on “Clear all cache” button to clear all of the Java Cache’s

Portal

– go to the url: http://<host.domain&gt;:<port>/pls/admin_/gateway.htm or cache.htm
– click on “Cache Settings” option and note the “Cache Directory”
– go to this directory and delete all the cache files in the directory and sub directories

See also modplsql caches in Apache/iAS section above.

WebADI / BNE cache

For instance when enabling BNE log

– go to url: http://<host.domain&gt;:<port>/oa_servlets/oracle.apps.bne.framework.BneAdminServlet
– click on the “clear-cache” link
– at the bottom of the page you should see ‘Cache Cleared’

Self Service Pages turn to complete Dark Blue in Release 12 (Doc ID 1054332.1)

Applies to:

Oracle Applications Framework – Version 12.0.6 and later
Information in this document applies to any platform.
***Checked for relevance on 04-Mar-2013***

Symptoms

Getting Dark Blue color on OA  Framework pages after stopping the instance for Backup

darkblue

Changes

Stopped the instance for taking a Backup

Cause

Incorrect setting for the Profile Option “Java Color Scheme”

Solution

Comments
——–
1-Change the value for the Profile Option “Java Color Scheme” to “Swan

2-Save your settings

3-Clear the Cabo Cache and Bounce Services.
Reference: Note:742107.1-How To Clear Caches (Apache/iAS, Cabo, Modplsql, Browser, Jinitiator, Java, Portal, WebADI) for E-Business Suite?

4-Retest the issue

References

NOTE:742107.1 – How To Clear Caches (Apache/iAS, Cabo, Modplsql, Browser, Jinitiator, Java, Portal, WebADI) for E-Business Suite?