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:

1. Back up your existing CUSTOM.pll to CUSTOM.pll.orig.
2. Copy the CUSTOM.pll from the $AU_TOP/resource folder on the Oracle Applications server to a client machine that has Oracle Forms Builder installed.
3. Copy the APPCORE2.pll from $AU_TOP/resource folder on the Oracle Applications server to a client machine that has Oracle Forms Builder installed. This should be the same folder you used for the previous step.
4. Locate the ODPNCustomPLL.zip file in the ORACLE folder where the Developer is installed and extract the ODPN.pll file. Copy it to the client machine into same folder as previous file copies.
5. Open CUSTOM.pll using Oracle Forms Builder and attach ODPN.pll. Place this file in the same folder on the client side as your CUSTOM.pll prior to the attachment.
6. Answer Yes, when asked to remove directory path.
7. Add the following code to the Event procedure:
   gkod_event (event_name, 'SPECIAL7');

   Note: You may use any number between 1 and 15 in the SPECIAL command as long as there are no conflicts. See Check Existing Custom Library Configuration for more details. Beginning wtih Oracle EBS 12.1, the SPECIAL command can be replaced with the MENUX command where X is a number between 1 and 15.

8. Ensure that no one is currently using Oracle Applications (Web Forms). Shut down the Oracle Forms Server service.
9. Copy the CUSTOM.pll and ODPN.pll files from the client to the $AU_TOP/resource folder on the Oracle Applications server.
10. Compile both the ODPN.pll and the CUSTOM.pll files using steps 5 and 6 in the previous section.