CUSTOM.

pll
CUSTOM.pll is used to add extensions to Oracle's form Functionality. Some of the
common scenario where CUSTOM.pll can be used are:1. Enabling/Disabling the fields
2. Changing the List of Values in a LOV field at runtime.
3. Defaulting values
4. Additional record level validations
5. Navigation to other screens.
6. Enabling Special Menu
Primarily there are two methods of extending Oracle Forms, and these are
CUSTOM.pll
FORMS Personalizations
In this article we will cover the basics of using CUSTOM.pll for extending Oracle
Forms
How and why does CUSTOM.pll work?
Every form in Oracle Apps is created using something called as TEMPLATE.fmb. But
some of the modules like HRMS have their own HR Specific
Templates[HRTEMPLT.fmb]. These template files have form level triggers that make
call to CUSTOM.pll. The triggers that can be trapped using CUSTOM.pll in HRMS
screen can be different than those which can be trapped for other modules.
Commonly used events that are trapped using CUSTOM.pll are:ZOOM
WHEN-NEW-FORM-INSTANCE
WHEN-NEW-BLOCK-INSTANCE
WHEN-NEW-RECORD-INSTANCE
WHEN-NEW-ITEM-INSTANCE
WHEN-VALIDATE-RECORD
However, for example in HRMS, you can also write code in CUSTOM.pll to trap below
listed events :PRE-DELETE and POST-DELETE
PRE-UPDATE and POST-UPDATE
PRE-INSERT and POST-INSERT
POST-FORMS-COMMIT
WHEN-CREATE-RECORD
KEY-DELREC