Useful docs:
Note: 279034.1 - Information About the Oracle Applications Form Personalization Feature in 11i
Note: 468657.1 - How To Do Forms Personalization
Note: 395117.1 - Form Personalization in Oracle E-Business Suite (Release 12)
Note: 420518.1 - Limitations of
Forms Personalization
What is Forms Personalization? Where it is used? What For?
Forms Personalization is a standard
feature provided by oracle and supported by oracle to customize the forms.
With Forms personalization you can hide fields, make fields mandatory,
create zoom functionality, change lov dynamically etc.
What are different triggers that can be used in personalization?
WHEN-NEW-FORM-INSTANCE WHEN-NEW-BLOCK-INSTANCE
WHEN-NEW-RECORD-INSTANCE WHEN-NEW-ITEM-INSTANCE WHEN-VALIDATE-RECORD MENUS
SPECIAL EVENTS
What is the difference between having personalization at function level rather than form level?
A Form can have multiple functions.
Having the personalization at function level limits the scope of the personalization.
For example in Inventory for both “Master Item form” and “Organization
Item form” uses same form named INVIDITM where as both have different functions
linked to them.
Can you use global variables in forms personalization? If so How?
Yes.
Can you hide a text field using personalization? How?
Yes. In the actions set DISPLAYED
property to false.
Can you transfer the data from one form to another form using personalization?
Yes. Using global Variables.
How do you move personalization from one instance/database to other?
Form Personalization can be moved
easily through FNDLOAD from one instance to other.
What is personalization and what features can be achieved through personalization?
Personalization gives us the ability
to customize Forms in a very easy manner. The below customizations are
possible through Personalization: Zoom from one form to another Pass data
from one form to another through global variables Change LOV values dynamically
Enable/Disable/Hide fields dynamically Display user friendly messages when
required Launch URL directly from oracle form Execute PL/SQL programs through
FORM_DDL package Call custom libraries dynamically
At what level you can restrict personalization code?
FORM level and FUNCTION level
What can be implemented through Forms Personalization?
The below can be done using Personalization:
Zoom from one form to another Pass data from one form to another through
global variables Change LOV values dynamically Enable/Disable/Hide fields
dynamically Display user friendly messages when required Launch URL directly
from oracle form Execute PL/SQL programs through FORM_DDL package Call
custom libraries dynamically
What are the advantages/disadvantages of Forms Personalization when compared to CUSTOM.pll?
Advantages: Personalization are
stored in tables rather than files Will not have a bigger impact when you
upgrade or apply patches to the environment Can be moved easily through
FNDLOAD from one instance to other Can be restricted at site/responsibility/user
level Easy to disable/enable with click of a button. Personalization will
store who columns with which we have the ability to track who created/modified
it where as in CUSTOM.PLL we don’t have that ability. Disadvantages: Not
all can be customized using Personalization.
When you display a error message at WHEN-VALIDATE Trigger will the data will be saved into database?
No. If it is normal message or warning data will be saved but not for error message.
