How to use Barcode in Oracle E-Business Suite R12 XML Publisher

How to use Barcode in Oracle E-Business Suite R12 XML Publisher

 

This article explains how you can add barcode fields to your report using Oracle E-Business Suite R12 XML Publisher.

You can download the How to use Barcode in Oracle E-Business Suite R12 XML Publisher PDF Document from the following link:

 

How to use Barcode in Oracle E-Business Suite R12 XML Publisher

Advertisements

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

 

 

 

 

 

 

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.

Restart or Bounce Apache in Oracle Apps 11i

I find this script very handy for bouncing the Apache, specially when working on Self Service Applications.

Please find the two commands that I use for bouncing the Apache

$COMMON_TOP/admin/scripts/$TWO_TASK*/adapcctl.sh stop

$COMMON_TOP/admin/scripts/$TWO_TASK*/adapcctl.sh start

Of course this needs to be done in Middle Tier of Oracle Applications.

In case you have modified any java or class file in OAF ( Oracle Applications Framework ), then Apache bounce becomes mandatory for those changes to take effect.

In case you modify and load the XML Document in Oracle Framework, then it is noticed, for those XML changes to take effect, complete bounce of Middle Tier is required in Oracle Apps.

WebADI – Web Applications Desktop Integrator BNE_UIX_PHYSICAL_DIRECTORY is not configured Error in Release 11i and R12

Applies to:

Oracle Trade Management – Version 11.5.10.2 to 12.1.3 [Release 11.5 to 12.1]
Oracle Web Applications Desktop Integrator – Version 11.5.10.2 to 12.1.3 [Release 11.5 to 12.1]
Information in this document applies to any platform.

Symptoms

Oracle Web Applications Desktop Integrator Receiving Error BNE_UIX_PHYSICAL_DIRECTORY is not configured
This error can occur under several conditions:

  • Unable to open WebADI
  • After running Autoconfig on nodes not able to upload files
  • When selecting the ‘Desktop Integrator’ Responsibility the seeded menu options produces the error
  • After installing Oracle E-Business suite R12 and attempting to create a hierarchy using the create spreadsheet functionality(WebADI)
  • When creating a Layout as Trade Management Administrator
  • When attempting to do an Import inside the activity screen in Marketing Online the error occurs
Changes

Possible changes that will affect the setting for profile BNE_UIX_PHYSICAL_DIRECTORY:

  • Autoconfig updated or removed the existing settings for profile BNE_UIX_PHYSICAL_DIRECTORY
  • Cloned a new instance(11i) where the techstack has changed the value of the profile option
  • Upgrade from 11i to R12
  • Profile BNE_UIX_PHYSICAL_DIRECTORY configuration is incorrect based on the Application version
  • Functionality of profile BNE_UIX_PHYSICAL_DIRECTORY in version R12 is not required or needed
Cause
  • Autoconfig modified the existing settings for profile BNE_UIX_PHYSICAL_DIRECTORY
  • Web ADI Configuration Validation
  • Profile BNE_UIX_PHYSICAL_DIRECTORY is not properly defined with the correct value
  • Functionality of profile BNE_UIX_PHYSICAL_DIRECTORY in version R12 has changed
  • The cause of this problem has been identified in unpublished Bug 5240536 –  BNE_UIX_PHYSICAL_DIRECTORY IS NOT CONFIGURED. It is caused by autoconfig erasing the the BNE physical directory when autoconfig is run.
Solution

To implement the solution for Release 11i, please execute the following steps:

1. Go into the responsibility: System Administrator
2. Navigate to Profile -> System -> Profile: BNE%Directory%
3. Check the value for the profile BNE_UIX_PHYSICAL_DIRECTORY and verify it’s set to $COMMON_TOP/webapps/oacore/html/cabo/.
For 11i, the directory is: $COMMON_TOP/html/cabo
4. Bounce the web server and retest the issue.

And/Or

Apply Patch 5240536

This patch will stop autoconfig (concurrent/admin node) from updating profile option
BNE_UIX_PHYSICAL_DIRECTORY with the $OA_HTML/cabo directory from the
concurrent/admin node.

To implement the solution for Release 12, please execute the following steps:

1. Go into the responsibility: System Administrator
2. Navigate to Profile -> System -> Profile: BNE%Directory%
3. Remove any value in the profile BNE_UIX_PHYSICAL_DIRECTORY (null value is the default)
4. Bounce the web server and retest the issue.
Review R12 Web ADI Profile Options (Doc ID 553168.1) to get a list of Web ADI Profile Options which are supported in R12 of Oracle Applications. Any other previous BNE profile options from Release 11i are not supported in R12 and should not be used.

For more information on BNE profile options, refer to Set Profile Options section in the Oracle Web Applications Desktop Integrator Implementation and Administration Guide Release 12 – Part No. B31411-01

http://download.oracle.com/docs/cd/B40089_08/current/acrobat/120bneig.pdf

Deleted the following notes for consolidation and consistency:

  •  579102.1 – Upload Files Fails with Error “BNE_UIX_PHYSICAL_DIRECTORY Os Not Configured”
  • 1058772.1 – ANY WEBADI MENU OPTIONS GIVES ERROR “BNE_UIX_PHYSICAL_DIRECTORY IS NOT CONFIGURED”
  • 737620.1 – Bne Uix Physical Directory Profile Option Is Reset Incorrectly By Autoconfig

This note replaces the following notes:

  • 430991.1 – Error BNE_UIX_PHYSICAL_DIRECTORY Is Not Configured in R12 When Attempting To Use WebADI Spreadsheet To Create Hierarchies
  • 834333.1 – Bne_uix_physical_directory Is Not Configured.
  • 413289.1 – 11.5.10: WebADI Create Layout In Trade Management Error: “BNE_UIX_PHYSICAL_DIRECTORY is Not Configured.”
  • 888386.1 – BNE_UIX_PHYSICAL_DIRECTORY Is Not Configured Error
References

NOTE:553168.1 – R12 Web ADI Profile Options