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, 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.
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.
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 1and 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.
./CSCCCCRC.fmb:app_special.enable('SPECIAL7', PROPERTY_ON);