What is this?
Oracle Supplied forms are the seeded forms and have a standard functionality attached to them. Whenever there is a need to change the functionality or change the look and feel of the forms, we use Forms Personalization or Custom.PLL.
Custom.PLL or Forms personalization is used to alter the standard functionality of an Oracle Seeded form without affecting the base form and without altering its coding. In older versions, prior to 11i, Custom.PLL was most prominently used for adding additional features in the seeded form but the latest version of Oracle EBS comes with the feature called as Forms Personalization which allows even an end user to alter the seeded forms functionality using an user interface called the Personalization form.
Advantages of Forms Personalization over Custom.PLL
Forms personalization can be used by an user with limited PL/SQL knowledge.
Changes take place immediately on reopening the form.
Anything which can be done using Custom.PLL can be done using Forms Personalization also.
Personalizations are stored in base tables related to Form Personalization.
Restrictions of Custom.PLL and Forms Personalization:
It is not possible to create any new item in the Standard form using Custom.PLL or Forms Personalization.
How to
Normally a user with some basic knowledge of Oracle Forms and PL/SQL is allowed to modify a standard form. This can be achieved by setting the profile Option
FND: Diagnostics (Set to Yes at User Level)
Hide Diagnostics (Set to NO by default)
This enables the diagnostics menu when the particular user logs in and provides access to the personalization form. Once the form is open, the user can make any modifications for the specific form and then save and check the effect.
Custom.PLL is mainly used by the developers who have a vast knowledge of PL/SQL and can attach any logic using PL/SQL which in-turn will implement the business logic when the form opens. To achieve this, the developer has to first edit Custom.PLL and then add the code in it, compile and save it in the UNIX box and then deploy it in the applications. The changes will be reflected only the next time when the application is restarted.
Some typical uses
- Changing the property of an Item. It can be any property associated with the item.
- Calling a different form and passing a value from the calling form to the called form.
- Addition of special menus apart from the standard menu.
- Displaying custom messages for debugging purposes.
Feel free to post your comments and your queries.
2 comments:
great article..
"Anything which can be done using Custom.PLL can be done using Forms Personalization also."
this is incorrect....if popup msg ask for user input(yes,no..) and we want to conditionally execute a code based on user input....then this is not possible in FP but can be done in custom.pll...
Post a Comment