References:

Oracle E-Business Suite Development and Extensibility

Handbook
Chapter 6: Forms in Oracle Applications
Form_personalize.exe from oracle metalink
https://community.oracle.com/thread/2184016
http://kashif-oracle-forms.blogspot.in/2009/07/dokey-built-in.html
http://apps2fusion.com/apps/apps/296-stored-procedure-form-personalization
http://www.oracleerpappsguide.com/2011/10/calling-stored-procedure-throughforms.html
http://shivakumarkura.blogspot.in/2013/05/form-personalization-calling-plsql.html
http://jyotiprakash01.blogspot.in/

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.

Help>Diagnostics>Examine is used to the filed values.

Help>Diagnostics>Custom Code > Show Custom Events will show the details which are passed

The action type Property is commonly used to achieve the following:

n Initialize global variables and assign values to global variables.
n Assign a value to items or global variables or parameters.
n Change the list of values (LOV) properties; for example, change its record group.
n Hide, show, enable, or disable fields, tabs, canvas views, and so on.
n Change Navigation properties and default WHERE clauses of blocks.
n Make items mandatory.
The action type Builtin is commonly used to achieve the following:
1. Call other form functions (passing parameters).
2. Execute DO_KEY triggers, for example, EXECUTE_QUERY.
3. Execute a PL/SQL stored procedure by passing the form field values as parameters.
4. Create record groups that can be attached to the existing LOVs.
5. Raise FORM_TRIGGER_FAILURES to abort processing in case of errors.
The action type Menu is used to create new tools menus with the arbitrary labels.
The action type Message is used to display messages to the end users via a message box or as a hint in
the console window.
Changing prompts:
In Actions select Property Name as PROMPT_TEXT and give required value in Value field.
Make descriptions mandatory:
In Actions select Property name REQUIRED(APPLICATION COVER) and Value as TRUE
To remove certain fields
In Actions select property name as DISPLAYED(APPLICATION COVER) and value FALSE
To hide tabs
In Actions select property name as DISPLAYED and value FALSE, you will be able to see that tab once you move
your mouse there.
To Change label value of Tab
In Actions select Property Name as LABEL and give required value in Value field.
How to change the position of radio button.
In Actions select Property Name as X_POS,Y_POS and give required value in Value field.
How to set initial values to fields.
In Actions select Property Name as INITIAL_VALUE and give required value in Value field.
How to make fields not updatable.
In Actions select Property Name as UPDATE_ALLOWED and give required value in Value field.
How to make promised date > sysdate
In Conditions tab write the condition with WHEN-VALIDATE-RECORD Trigger event
How to add special men in actions.
In actions select special menu and give the label name. if want a line between seeded and custom menu select
render line before menu
How to change the value based on other filed.
Create a function or write dynamically in actions tab for the target object for which value need to be changed. In
Property Name select Value and in Value write the query or call the function.
Compile Security Menu is the concurrent program submitted to recompile the menu.

BUILTINS
Launch SRS form

Launch URL

_TOP, _PARENT, _SELF are other target values

Launch a function
This is a form function

DO_KEY

Below are the keys available for 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