Limitations of Forms Personalization (Doc ID 420518.1)

Last updated on JUNE 21, 2023

Applies to:

Purpose

With the Oracle E-Business Suite release 11.5.10, Oracle introduced a mechanism which revolutionized the way the forms can be customized to fulfill 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.

Scope

With the release of of 11.5.10 (and continuing in R12), Oracle Applications provided a user interface known as a "Personalization form" which can be used to define personalization rules. These personalization rules establish the custom actions to be performed by the forms during runtime. The actions may include changing prompts, showing custom messages or prevent the user from doing the transactions etc. This feature also provides a well-built controlling mechanism which restricts the execution of the personalization rules at different levels (Industry, site responsibility and user). The personalization does not violate the support from Oracle and these rules also conceded with the future upgrades without any additional effort.

Details

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.