Form Personalization

With the Oracle E-Business Suite release 11.5.10, the Oracle has introduced a mechanism which revolutionizes the way the forms can be customized to fulfill the customer needs. For many years, Oracle Applications has provided a custom library using which the look and behavior of the standard forms can be altered, but the custom library modifications require extensive work on SQL and PL/SQL. In the release 11.5.10, Oracle has provided a simple and easy feature to implement the customer specific requirements without modifying the underlying forms code or CUSTOM library. Although CUSTOM library still can be used for forms customization to implement the complex business logic, the personalization feature provided in the latest release is easy, faster and requires minimum development effort.

Why Forms Personalization?

• Oracle Supports personalization unlike customization.
• Personalizations 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 stores 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.
• Can be applied to new responsibilities/users easily.
• Can be restricted to a function or form.

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

Personalization Tables:

FND_FORM_CUSTOM_RULES
FND_FORM_CUSTOM_ACTIONS
FND_FORM_CUSTOM_SCOPES
FND_FORM_CUSTOM_PARAMS
FND_FORM_CUSTOM_PROP_LIST
FND_FORM_CUSTOM_PROP_VALUES

Invoking the Personalization screen:

The personalization form should be used to implement the custom rules on a specific form. The specific form refers to the desired form on which you want to apply the custom business logic or modify the form behavior.
The personalization form is invoked by…
Menu Navigation: Help > Diagnostics > Custom Code > Personalize

Disable the personalization feature:

It is possible that a change you make completely breaks a form, to the point that it will not even run! Here’s how to recover:

• On the pulldown menu, choose Help > Diagnostics > Custom Code > Off
  • This will disable all callouts to Forms Personalization
• Run the form of interest
  • It should run now, because your changes were skipped
• Invoke the Personalization screen and correct the problem
• On the pulldown menu, choose Help > Diagnostics > Custom Code > Normal to re-enable processing of Personalizations

Limitations:

Although it is faster than a speeding bullet, it is not able to leap over tall buildings:

• You can only change what Forms allows at runtime:
  • Cannot create new items
  • Cannot move items between canvases
  • Cannot display an item which is not on a canvas
  • Cannot set certain properties
  • Cannot change frames, graphics, boilerplate
• You can only respond to certain Trigger Events:
  • WHEN-NEW-FORM-INSTANCE, WHEN-NEW-BLOCK-INSTANCE, WHEN-NEW-RECORD-INSTANCE, WHEN-NEW-ITEM-INSTANCE
  • WHEN-VALIDATE-RECORD (not in all forms)
  • Product-specific events
• May interfere with, or be overridden by, base product code
• Expected user is an Admin/Developer
  • Knowledge of Oracle Developer is extremely desirable
  • Knowledge of PL/SQL, Coding Standards and/or APIs required in some cases
• Normal rules for customizations apply
  • Extensive testing in a Test environment is required!

Relationship with CUSTOM library:

• CUSTOM is a stub library Oracle ships that receives Trigger Events. Customers are free to add any code they like to it.
• CUSTOM and Form Personalizations drive off the same Trigger Events.
  • Form Personalizations are processed first, then the event is sent to CUSTOM
• CUSTOM can do more because it has complete access to all PL/SQL and SQL.
• But for most changes, Form Personalizations is adequate and is significantly simpler.