Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
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
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
How to identify which trigger is most suitable for writing your business logic?
You can either open the FMB itself, and see the triggers which are calling CUSTOM.pll.
However, there is a easier way to work out the most suitable triggers. You can navigate to
Help/Diagnostics/Custom Code/Show Custom Events
Once that radio button has been set, you will see the list of Events Displayed on the
screen.
2. Default a value
copy (TO_CHAR (n_person_id),'PERSON_BLOCK.PERSON_ID' );
As you may have gathered by now, almost any form related task can be done using
CUSTOM.pll
Action Type in CUSTOM
Allowed
Opening SQL Cursors
Yes
Executing pl/sql stored procedures
Yes
Referencing fields using bind notation like :block.field
No
Exception management
Yes