Forms Personalization
Forms Personalization
Forms Personalization
FP (Forms Personalization) was introduced starting from E-Business Suite version 11.5.10.2. Using FP,
you can navigate to any Oracle Formsbased screen in E-Business Suite and then click Help |
Diagnostics |Custom Code | Personalize. This will take you to the Forms Personalization screen, where
you can capture the details for your extension. When personalizations are saved, those details are stored
in database tables, and the personalizations and their associated actions can then be parsed and
executed by the FND libraries at runtime. As with CUSTOM.pll, the changes made via Forms
Personalizations are never overwritten by Oracle patches. Therefore,such extensions are upgrade safe,
unless the upgrade process replaces the fundamental design of the form altogether. You cannot use
Forms Personalization to create a new LOV (you can use Forms Personalization to change what the form
run).
Table 6-3: Components of Forms Personalization
Form to be personalized
Navigate to the form I question and click Help | Personalize. This will open the Form Personalization screen; this
screen is always opened in the context of the form being extended.
Form function
In the Forms Personalization screen, you can select either the Form or Function context. When Function is selected,
the personalizations are restricted to the form function from which the Personalization Screen was invoked.
Events
The events that can be trapped in Forms Personalization are the same as those in CUSTOM.pll. For Block and Item
Level events, it is possible to specify the block name and the item name. You will create one personalization for each
event that you wish to trap in a form.
Conditions
It is possible to specify the conditions that have constructs similar to IF..THEN..ELSE in PL/SQL. These conditions
can reference the value of the fields in the form being personalized. The extensions will take effect only when the
conditions specified are true in the context of data being entered.
Action
Actions can be either to display error messages, to change the navigation, to change the item properties, and so on.
As shown in Table 6-3, both CUSTOM.pll and Forms Personalization are called from the same set of
events and triggers. If extensions are present in both places for any given form, the extensions in Forms
Personalization are executed first, and after that the code in CUSTOM.pll is executed. To restrict
personalizations to one or more responsibilities or one or more users, entries can be made in the
Context Level region of the Forms Personalization screen.
BUILTINS
Launch SRS form
Launch URL
DO_KEY
Execute a Procedure
Here equals symbol should be there in argument and there is no semicolon at the end after end keyword. This block
is enclosed in single quotes.
GO_ITEM, GO_BLOCK
This builtin takes you to the item or block as specified in the argument.
Note: to know the block name click on ALT+H+D+E where it navigates to Help>Diagnostics>Examine