To implement Help Integration for Oracle E-Business Suite, you must install and compile two library files that are delivered with the Developer installation. To complete the integration, modify the HELP_WEB_AGENT profile on the Oracle server to point to the Player content. This causes the Player interface to launch directly from the Oracle Help menu.
Implement Context-Sensitive Help Integration
If you want to implement context-sensitive help for Oracle E-Business Suite applications, the correct Context IDs of the objects in Oracle must be captured while the content is recorded. To enable this in Oracle E-Business Suite 12.1.1 or earlier, you must deploy or modify the custom library (CUSTOM.pll) on the Oracle server you will use to record the content. This must be done before you begin to record content. To enable this in Oracle E-Business Suite 12.1.2 or later, you can add an entry in the System Profile form.
Enable Context Recognition in Oracle E-Business Suite 12.1.1 or Earlier
To enable context recognition, you must either deploy a custom library or modify an existing one, and then modify the HELP_WEB_AGENT profile. The custom library is required for recording content only. It is not necessary for deployment of context-sensitive content from Oracle E-Business Suite. If you use the different systems for development (content creation) and production (deployment), then the custom library configuration is not necessary in the production environment. If you use the same system for development and production, then custom library only needs to be installed while the content is being recorded.
Enable Context Recognition in Oracle E-Business Suite 12.1.2 or Later
In Oracle E-Business Suite 12.1.2 or later, you add a profile in the System Profile form.
To enable context recognition in Oracle E-Business Suite 12.1.2 or later:
Check Existing Custom Library Configuration
The .pll delivered with the Developer is written with SPECIAL7 as the default value. This default value is a suggestion. You can use anything between 1 and 15. If you have not created any Oracle specific applications that use the SPECIAL event, you can use the default. If you have created Oracle-specific applications that do use the SPECIAL event, the value of 7 may be taken, and you need to find another suitable unused value between 1 and 15.
You can use the following command lines to find an unused value instead of editing and recompiling the custom.pll file repeatedly:
cd $AU_TOP/forms/US; grep -i APP_SPECIAL.ENABLE `find . -name "*.fmb" -print`| grep SPECIAL7| grep -i PROPERTY_ON
cd $AU_TOP/resource; grep -i APP_SPECIAL.ENABLE `find . -name "*.fmb" -print`| grep SPECIAL7| g rep -i PROPERTY_ON
If you receive a result that looks like the statement below, the value is already being used.
Deploy a Custom Library
Use the following steps if you have not deployed a custom Library on your Oracle Applications server.
To deploy a custom library:
Modify an Existing Custom Library
Use the following steps if you have custom logic in your custom library (CUSTOM.pll) that you do not want to overwrite. You must place a line of code in the custom library that will call out to a new library (ODPN.pll). After doing this, you will only need to recompile your existing CUSTOM.pll if you receive new versions of ODPN.pll with software upgrades.
To modify a custom library:
Modify the HELP_WEB_AGENT Profile
You must modify the HELP_WEB_AGENT profile in Oracle to point to the oracle_gateway.html in the Player content deployed on the server.
For Oracle E-Business Suite 11i , the URL consists of two parts: the path for the oracle_gateway.html file located in the \oracle\hemi folder in the Player content, plus the path of the default dbc file for the Oracle server.
Following is an example for 11i:
URL=http://<server name>:<port>/oracle/hemi/oracle_gateway.html?dbc=d:\oracle\o11iappl\fnd\11.5.0\secure\<server name>.dbc
Following is an example for R12:
To modify the HELP_WEB_AGENT profile in Oracle E-Business Suite:
Table of Contents