R12 Forms Personalization

Oracle EBS R12 Forms Personalization
Training Guide
Table of Contents
Introduction.......................................................................................................................iv
Installing and Setting Up Forms Personalization...........................................................1
Enabling Form Personalization..................................................................................................1
Turning Form Personalization On and Off...............................................................................13
Creating Basic Form Personalization............................................................................19

Hiding a Field...........................................................................................................................19
Disabling a Field......................................................................................................................24
Changing a Field Prompt..........................................................................................................30
Creating Intermediate Personalizations........................................................................35

Using Form Personalization Conditions...................................................................................35
Using Form Personalization Events..........................................................................................37
Restricting Form Personalization Execution.............................................................................50
Displaying a Message...............................................................................................................55
Using a Form Built-in...............................................................................................................66
Creating a Menu.......................................................................................................................82
Creating Advanced Personalizations...........................................................................101

Creating a Zoom.....................................................................................................................101
Advanced Personalization Actions.........................................................................................152
Administering Form Personalizations.........................................................................165

Debugging Form Personalizations..........................................................................................165
Page ii
Training Guide
Introduction
The Form Personalization feature allows you to easily alter the behavior of Forms-based screens,
including changing properties, executing built ins, displaying messages, and adding menu entries.
For each function (a form running in a particular context based on parameters passed to it), you
can specify one or more Rules. Each Rule consists of an Event, an optional Condition, the Scope
for which it applies, and one or more Actions to perform. An Event is a trigger point within a
form, such as startup (WHEN-NEW-FORM-INSTANCE), or when focus moves to a new record
(WHEN-NEW-RECORD-INSTANCE). There are standard events that almost every form sends,
and certain forms send additional product-specific events. The Condition is an optional SQL code
fragment that is evaluated when the Event occurs; if it evaluates to TRUE then the Actions are
processed. The Scope is evaluated based on the current runtime context to determine if a Rule
should be processed or not. The Scope can be at the Site, Responsibility, User, or Industry level.
Each Rule can have one or more Scopes associated with it.
Each Action consists of one of the following:
A property, such as required or displayed
A built-in, such as GO_BLOCK, DO_KEY or FND_FUNCTION.EXECUTE
A message, such as an error, warning or confirmation
A special menu entry in one of 45 available slots
Once Rules are defined, when the target function is run then the Rules are automatically applied
as events occur within that form.
Although the Form Personalization feature is declarative, the intended audience is a person
familiar with Oracle Forms including the PL/SQL programming language, and the Oracle
Applications Development Guide. Additionally, any change made could interfere with the base
code of a form (the code that Oracle ships), thus you must fully understand the support
implications of such form personalizations.
Upon completion of this module, you will be able to:
Enable form personalization.
Turn form personalization on or off for a given form or completely at the site-level.
Hide a field on a form.
Disable a field on a form.
Change the prompt of a field on a form.
Change other common properties of a field on a form.
Display a message.
Use a form built-in function.
Create a custom menu.
Use form personalization events.
Use form personalization conditions.
Restrict form personalization execution.
Create a zoom.
Create a record group from a query to implement a modified LOV.
Personalizing forms with SQL and PL/SQL.
Restrict form personalizations.
Debug form personalizations.
Move form personalizations from system to system (e.g. development to production).
Page iii
Installing and Setting Up Forms Personalization

Before you can begin creating form personalizations, you must set some profile options to allow
the form personalization capability to be enabled for your user. Although the Form
Personalization feature is declarative, the intended audience is a person familiar with Oracle
Forms including the PL/SQL programming language, and the Oracle Applications Development
Guide.
Additionally, any change made could interfere with the base code of a form (the code that Oracle
ships), thus you must fully understand the support implications of such form personalizations.
This means that another critical skill is turning form personalization off, especially in the case
where your personalization has caused a failure on the form.
Upon completion of this lesson, you will be able to:
Enable your E-Business Suite user to create, modify, and maintain form personalizations.
Switch form personalizations off for a form, or if necessary turn off all form personalizations on
the site.
Enabling Form Personalization

Consider this scenario: You are part of a team implementing Oracle's E-Business Suite at your
company. The team has just learned about a powerful feature in the E-Business Suite, called form
personalization. You find online a couple of simple, yet powerful, examples of form
personalization. The teams asks you to take the lead in learning this new feature. But, when you
attempt to perform a form personalization, you are unable to get started.
Form Personalizations should only be done by experienced and trained developers and/or users.
Additionally, form personalizations should not be performed on the production instance. Any
form personalization should be created and fully tested on a test or development instance, and
then moved to the production instance. So, you will want some E-Business suite instances, like
test or development systems, to have form personalization creation, modification, and
maintenance enabled, while it would be disabled on the production instance.
Enabling form personalization enables you to set the profile options for your E-Business Suite
user that will allow you to create, modify, and maintain form personalizations.
In this topic, you will enable form personalization.
Procedure
Training Guide
Step
Action
1.
Begin from within any Oracle Forms-based responsibility. In the example, the
General Ledger, Vision Operations (USA) responsibility is selected, and the
Navigator page is open.
Click the Help menu.
or
Press [Alt+H].
2.
You should see an entry in the Help menu labeled, Diagnostics. It should be
located just above the Record History entry. But, it doesn't seem to be there.
Without this menu item, you can not create a form personalization.
3.
In order to see the Diagnostics menu item, you are going to have to set a profile
option. To do that, switch responsibilities to System Administrator.
Click the Switch Responsibility... button.
4.
The Responsibilities page allows you to easily switch between the various Oracle
Forms-based responsibilities assigned to you as an E-Business Suite user.
5.
Scroll down to the System Administrator responsibility.

Click the vertical scrollbar.
6.
Click the System Administrator list item.
Page 2
Training Guide
Step
Action
7.
Click the OK button.

or
Press [Alt+O].
8.
Double-click the Profile list item.
9.
Double-click the System list item.
10.
The Find System Profile Values page is a common "Find" page. It allows you to
specify query criteria for the underlying page, System Profile Values (in this
case).
Step
Action
11.
Enter the desired information into the Profile field. Enter "Hide%".
12.
Click the Find button.

or
Press [Alt+i].
13.
The System Profile Values page allows you to change the values of system-level
(as opposed to user-level) profile options.
Page 3
Training Guide
Step
Action
14.
Click the Site LOV button.
15.
Accept the default of No.

or
Press [Alt+O].
16.
Click the Save button.
17.
Click the Close button.
Page 4
Training Guide
Step
Action
18.
Switch back to the original General Ledger, Vision Operations (USA)

responsibility.
19.
Scroll down to the General Ledger, Vision Operations (USA) responsibility.

20.
Click the General Ledger, Vision list item.
21.

or
Press [Alt+O].
22.

or
Press [Alt+H].
23.
Notice that you now see the Diagnostics menu entry.

Point to the Diagnostics menu.
Page 5
Training Guide
Step
Action
24.
Point to the Custom Code menu.
25.
Click the Personalize menu.

or
Press [z].
26.
When you selected Personalize, it now asks you for the ORACLE password. The
default password for this is APPS. On most systems, this will have been changed,
and for security reasons, the system administrator(s) will not provide you with the
password.
There is a work-around. There is a profile option that can be set; so that, the
password is not requested.
Click the Cancel button.
or
Press [Alt+C].
27.

or
Press [Alt+O].
28.
29.
Scroll down to the System Administrator responsibility.

Page 6
Training Guide
Step
Action
30.
Page 7
Training Guide
Step
Action
31.

or
Press [Alt+O].
32.
33.
Page 8
Training Guide
Step
Action
34.
Enter the desired information into the Profile field. Enter "Utilities:Diagnostics".
35.

or
Press [Alt+i].
Page 9
Training Guide
Step
Action
36.
37.
Click the Yes list item.
38.

or
Press [Alt+O].
39.
40.
Page 10
Training Guide
Step
Action
41.
42.
Scroll down to the General Ledger, Vision Operations (USA) responsibility.

43.
Click the General Ledger, Vision... list item.
44.

or
Press [Alt+O].
45.
Double-click the Account Inquiry list item.
46.
The Account Inquiry page is a typical Oracle Forms-based page. It is possible to

apply form personalizations to any Oracle Forms-based page.
Page 11
Training Guide
Step
Action
47.

or
Press [Alt+H].
48.
49.
50.

or
Press [z].
51.
Notice that the form personalization window now opens without requesting the
ORACLE password.
This is the default Form Personalizations page. It is the entry point for making
form personalizations on your page.
52.
Page 12
You have now completed the procedures to enable form personalizations.

End of Procedure.
Training Guide
Turning Form Personalization On and Off

Consider this scenario: You are experiencing an issue with your E-Business Suite instance that
involves contacting Oracle Support for assistance. Oracle Support wants to be sure that the form
personalizations aren't causing the unusual behavior.
Consider this scenario: You have just created a complex personalization, and you have saved your
work. When you attempt to reload the form, the form generates an E-Business Suite error
message, and you are unable to return to the form personalization screens to correct your work.
In this topic, you will learn how to turn personalizations on and off at the site and form levels.
Procedure
Page 13
Training Guide
Step
Action
1.
Begin at the Navigator page within any Oracle Forms-based page.

In the first scenario, you can turn off form personalizations across the entire EBusiness Suite instance. This is a common practice when you are working to
Oracle Support to resolve a potential problem.
2.
3.
Choose the System Administrator responsibility to call up the forms needed to

change a System Profile value.
4.

or
Press [Alt+O].
5.
6.
7.
The Find System Profile Values page is a common "Find" page. It allows you to
specify query criteria for the underlying page, System Profile Values (in this
case).
Page 14
Training Guide
Step
Action
8.
Enter the desired information into the Profile field. Enter "Disable%".
9.

or
Press [Alt+i].
10.
The System Profile Values page allows you to change the values of system-level
(as opposed to user-level) profile options.
Page 15
Training Guide
Step
Action
11.
12.
Click the Yes list item.
13.

or
Press [Alt+O].
14.
15.
The second scenario is commonly used when you are creating personalizations,
and you find that a personalization you have just created is causing an error.
Sometimes that error will be so bad that it prevents you from getting back to the
form to undo your personalization. In that scenario, you can disable form
personalization processing on an ad hoc basis.
Begin at the Navigator page within any Oracle Forms-based page.
Page 16
Training Guide
Step
Action
16.

or
Press [Alt+H].
17.
18.
19.
Click the Off option.

or
Press [O].
20.

or
Press [Alt+O].
21.
Now, if you tried to go to a page with a personalization on it, that form

personalization would not operate.
Page 17
Training Guide
Step
Action
22.
You have now completed the procedures to turn form personalizations on or off
for your page.
End of Procedure.
Page 18
Creating Basic Form Personalization

Form personalizations are composed of rules, conditions, and scopes. The simplest form
personalizations are those in which only the rule is defined.
Using just rules, it is possible to create very useful and common form personalizations. The skills
learned in this lesson will also form the foundation for more complex form personalizations.
Hide a field on a form.
Disable a field on a form.
Change the prompt of a field on a form.
Hiding a Field
Basic form personalization enables you to hide fields.
In this topic, you will hide a field.
Procedure
Training Guide
Step
Action
1.
Begin at the Navigator - General Ledger, Vision Operations (USA) page.

One of the simplest form personalizations is to hide a field on a form. While this is
a easy personalization, it may cause unintended consequences. If you hide a
mandatory field, the form will still require a value, but the user will be unable to
enter a value. So, be certain to thoroughly test all form personalizations.
2.
The Account Inquiry page is a typical Oracle Forms-based page. It is possible to

apply form personalizations to any Oracle Forms-based page.
Note that the Summary Template field is displayed on the form.
Step
Action
3.

or
Press [Alt+H].
Page 20
Training Guide
Step
Action
4.
5.
6.

or
Press [z].
7.
This is the default Form Personalizations page. It is the entry point for making
form personalizations on your page.
Page 21
Training Guide
Step
Action
8.
Enter the desired information into the Seq field. Enter "1".
9.
Enter the desired information into the Description field. Enter "Hide a field on
the form".
10.
Click the Actions tab.
11.
12.
Enter the desired information into the Description field. Enter "Hide a field".
13.
Click the Select By Text... button.

or
Press [Alt+S].
14.
Enter the desired information into the Find field. Enter "Summary%".
15.

or
Press [Alt+F].
16.
Page 22
Click the Summary Template list item.
Training Guide
Step
Action
17.

or
Press [Alt+O].
18.
Click the Property Name LOV button.
19.
Click the DISPLAYED list item.
20.

or
Press [Alt+O].
21.
Click the Value LOV button.
Step
Action
22.
Click the FALSE list item.
Page 23
Training Guide
Step
Action
23.
24.
Click the Apply Now button.

or
Press [Alt+p].
25.
26.
Note that the Summary Template field is no longer displayed on the form.
27.
You have now completed the procedure to hide a field on a page.

End of Procedure.
Disabling a Field
Another method of protecting a field is disabling it by making it read-only.
I this topic, you will disable a field.
Page 24
Training Guide
Procedure
Step
Action
1.

Sometimes it is important to see the data in a field, but to disallow entry of data
into that field. This topic will show you how to disable a field on a form.
Navigate to the Account Inquiry form.
2.
Note that currently the Summary Template field is shown in WHITE, which
means that you could enter data into that field.
Page 25
Training Guide
Step
Action
3.

or
Press [Alt+H].
4.
5.
6.

or
Press [z].
Page 26
Training Guide
Step
Action
7.
8.
Enter the desired information into the Description field. Enter "Disable a field on
a form".
9.
10.
11.
Enter the desired information into the Description field. Enter "Disable a field".
12.

or
Press [Alt+S].
13.
14.

or
Press [Alt+F].
15.
Click the Summary Template list item.
Page 27
Training Guide
Step
Action
16.

or
Press [Alt+O].
17.
18.
Click the ENABLED list item.
19.

or
Press [Alt+O].
20.
Step
Action
21.
Click the FALSE list item.
Page 28
Training Guide
Step
Action
22.
23.

or
Press [Alt+p].
24.
25.
Note that the Summary Template field is now shown in BLUE, and the user is
prohibited from entering data into the field. If the record had data in it, that data
would be shown.
Note that the Currency field is shown in BLUE as well, but that it shows a
predetermined value of USD.
26.
You have now completed the procedure to disable a field on a page.

End of Procedure.
Page 29
Training Guide
Changing a Field Prompt

Field prompts allow you to help users identify fields.
In this topic, you will change a field prompt.
Procedure
Step
Action
1.

2.
Note that currently, the prompt on the Summary Template field is "Summary
Template". In the steps that follow, you will change the prompt.
Page 30
Training Guide
Step
Action
3.

or
Press [Alt+H].
4.
5.
6.

or
Press [z].
Page 31
Training Guide
Step
Action
7.
8.
Enter the desired information into the Description field. Enter "Change a field
prompt on a form".
9.
10.
11.
Enter the desired information into the Description field. Enter "Change a
prompt".
12.

or
Press [Alt+S].
13.
14.

or
Press [Alt+F].
Page 32
Training Guide
Step
Action
15.
Accept the default (first) value of Summary Template.

or
Press [Alt+O].
16.
Enter the desired information into the Value field. Enter "Account Summary
Template".
17.
18.

or
Press [Alt+p].
19.
20.
Note that the prompt has now change from "Summary Template" to "Account
Summary Template".
21.
You have now completed the procedure to change the prompt of a field on a page.
End of Procedure.
Page 33
Creating Intermediate Personalizations

Form personalizations are composed of rules, conditions, and scopes.
Use form personalization conditions.
Use form personalization events.
Restrict form personalization conditions.
Display a message.
Use a form built-in.
Create a menu.
Using Form Personalization Conditions

Forms personalization gives you the ability to restrict the execution of form personalization rules
with conditions. In fact, even simple rules have a condition. This topic will explore the full range
of conditions you can apply to your form personalization rules.
In this topic, you will using form personalization conditions.
Procedure
Training Guide
Step
Action
1.
Begin by navigating to the Form Personalizations (Users) page.

To this point, all the form personalization you have done have been done every
time, without any sort of conditional test. In order to accomplish more
sophisticated form personalizations, you need to understand conditions.
Enter a placeholder Seq and Description for this example.
Enter the desired information into the Rule Sequence field. Enter "1".
2.
Enter the desired information into the Rule Description field. Enter "Example of
testing for a condition".
3.
Enter the desired information into the Condition field. Enter "sysdate >
to_date('1-1-2008','DD-MM-RRRR')".
4.
This condition uses PL/SQL functions sysdate and to_date with a boolean
expression.
After you enter your condition, you should click the Validate button to test your
condition based on the current values in the form and on the server.
5.
Click the Validate button.

or
Press [Alt+a].
6.
The condition, because it is boolean, will always evaluate as either true or false.
There is one exception, if you have entered an invalid condition, testing will fail
will an error message.
7.

or
Press [Alt+O].
8.
Enter the desired information into the Condition field. Enter

":USER_RESP.RESPONSIBILITY_ID is null".
9.
In addition to PL/SQL functions, you can also test for values in the form. The
format for referring to form values is :BLOCK_NAME.FIELD_NAME. In this
sample, you are referring to the USER_RESP block and the
RESPONSIBILITY_ID field in that block.
10.

or
Press [Alt+a].
11.
Page 36
Training Guide
Step
Action
or
Press [Alt+O].
12.
Enter the desired information into the Condition Multiline field. Enter
":USER.USER_NAME is not null".
13.

or
Press [Alt+a].
14.

or
Press [Alt+O].
15.
You have now completed your exploration of conditions that can be applied to
personalizations on a page.
End of Procedure.
Using Form Personalization Events

There are numerous events available within form personalization. The various topics cover the
major events, and give you good examples. This topic will cover the remaining events, and
provide you will some additional techniques to consider.
In this topic, you will use form personalization events.
Procedure
Page 37
Training Guide
Step
Action
1.
Begin by navigating to the Forms Personalization (Users) page.

There are 5 primary events that cause a form personalization to execute (fire). In
addition, there are 45 other events corresponding to the 45 special menu items that
you can create.
Create a placeholder for the Seq and Description of your form personalization.
2.
Enter the desired information into the Rule Description field. Enter
"Personalization Rule".
3.
Click the Trigger Event LOV list.
4.
Click the WHEN-NEW-FORM-INSTANCE list item.
5.
WHEN-NEW-FORM-INSTANCE is the most commonly used event. It

encompasses all activities that would be done to a form prior to its loading for the
user. Typically, personalizations set on this event are either global changes or
personalizations that you want to automatically occur.
6.
Page 38
Training Guide
Step
Action
7.
Click the WHEN-NEW-BLOCK-INSTANCE list item.
8.
WHEN-NEW-BLOCK-INSTANCE is fired whenever a new block in created on a

form. Since this form does that during opening, the event who fire at the same
time as NEW-FORM.
9.
If you return to the form, you will note that the form has numerous logical areas,
the USER area, the DIRECT RESPONSIBILITY area, the INDIRECT
RESPONSIBILITY area, and the SECURING ATTRIBUTES area.
Blocks are not directly related to layout, but they most often be discerned from the
layout. A block is actually closely related to a TABLE, and it meant to represent
the interactions with that table.
Page 39
Training Guide
Step
Action
10.
When you set an event at the NEW-BLOCK level, you should tell it which block
you want to execute (fire) on. If not specified, it will execute (fire) on all new
blocks.
Click the Trigger Object LOV button.
11.
Note that as noted earlier, the form has four blocks. So, our logical analysis turned
out to be accurate. This won't always be the case, and you will need to explore and
test to fully understand the interactions of the form you are personalizing.
or
Press [Alt+O].
12.
Page 40
Click the Trigger Event list.
Training Guide
Step
Action
13.
Click the WHEN-NEW-RECORD-INSTANCE list item.
14.
WHEN-NEW-RECORD-INSTANCE directly corresponds to creating a new

record on a form. Because of this, you will need to specify the specific record to
which the event is linked. Note the Trigger Object is required, not optional.
Page 41
Training Guide
Step
Action
15.
Click the Trigger Object button.
16.
Note that in the case of this form, the records and the blocks are identical. This is
the most common case, but is not always this way.
or
Press [Alt+O].
17.
Page 42
Training Guide
Step
Action
18.
Click the WHEN-NEW-ITEM-INSTANCE list item.
19.
WHEN-NEW-ITEM-INSTANCE directly corresponds to creating a new record on

a form. Because of this, you will need to specify the specific record to which the
event is linked. Note the Trigger Object is required, not optional.
But, unlike NEW-RECORD, this event triggers on a specific item on the form. So,
it has a highly level of granularity, and should only be used when you need that
specificity.
Page 43
Training Guide
Step
Action
20.
21.
Note the numerous item objects on the form.

or
Press [Alt+O].
22.
Page 44
Training Guide
Step
Action
23.
Click the WHEN-VALIDATE-RECORD list item.
24.
WHEN-VALIDATE-RECORD is the event that is performed when the user tries

to save or validate the new record.
Page 45
Training Guide
Step
Action
25.
26.
Since you are validating a record, the Trigger Object list is the same as the NEWRECORD event.
or
Press [Alt+O].
27.
Page 46
Training Guide
Step
Action
28.
Click the MENU1 list item.
29.
MENU1 to MENU15 correspond to the Tools menu on the menu bar at the top of
the form. You will also see SPECIAL1 to SPECIAL15. These events are same as
MENU1 to MENU15. SPECIALxx was the older method for referring to these
items.
Likewise SPECIAL16 to SPECIAL30 refer to the Reports menu, and SPECIAL31
to SPECIAL45 refer to the Actions menu. These menu items are less commonly
used, and still use the older nomenclature.
Page 47
Training Guide
Step
Action
30.
Page 48
Training Guide
Step
Action
31.
32.
33.
34.
Every event can designate whether or not that event is operates when the form is
in Query mode. Query mode is a special mode on a form, and most
personalizations would not operate in that mode. This is why the default setting is
"Not in Enter-Query Mode". Change this as appropriate for your personalization.
35.
Click the Not in Enter-Query Mode list item.
36.
Finally, you can enable or disable a given personalization rule by clicking the
Enabled checkbox beside the rule.
Page 49
Training Guide
Step
Action
37.
Disable the rule.

Click the Rule Enabled option.
38.
Enable the rule.

Click the Rule Enabled option.
39.
You have now completed your exploration of the events that are personalizable on
a page.
End of Procedure.
Restricting Form Personalization Execution

Conditions are a powerful means to control a form personalization. But, there are common tests,
such as for a particular user or responsibility, that would commonly occur in an E-Business Suite
instance.
In this topic, you will restrict form personalization execution.
Page 50
Training Guide
Procedure
Step
Action
1.
Begin by navigating to the Form Personalizations (Users) page.

2.
Enter the desired information into the Description field. Enter "Sample for
Context".
3.
Click the Level LOV list.
Page 51
Training Guide
Step
Action
4.
Note the 4 levels, Site, Responsibility, User and Industry.

Industry is a very specific test that is only valid within a few products in the EBusiness Suite. Chances are you will not use this test often.
Click the Responsibility list item.
5.
Page 52
When you set the context to Responsibility, you have to tell your personalization
which responsibility is your context. You can also set multiple contexts to select
multiple responsibility, for example.
Training Guide
Step
Action
6.
7.
Note that the list of responsibilities on the system is quite large; so, you are asked
to limit the query.
Enter the desired information into the Find field. Enter "System%".
8.

or
Press [Alt+F].
9.
10.
11.

or
Press [Alt+O].
12.
Click the Level LOV list.
Page 53
Training Guide
Step
Action
13.
Click the User list item.
Page 54
Training Guide
Step
Action
14.
Just like for Responsibility contexts, you must set the specific user for a User
context.
Click the Value button.
15.
Enter the desired information into the Find field. Enter "OPER%".
16.

or
Press [Alt+F].
17.

or
Press [Alt+O].
18.
You have now completed your exploration of restricting form personalizations on

a page.
End of Procedure.
Page 55
Training Guide
Displaying a Message
Forms personalization enables you to display a message to the user as they enter a form. The
message itself is dynamic, and depends upon the state of the server.
In this topic, you will display a message.
Procedure
Step
Action
1.

Page 56
Training Guide
Step
Action
2.

or
Press [Alt+H].
3.
4.
5.

or
Press [z].
Page 57
Training Guide
Step
Action
6.
7.
Enter the desired information into the Description field. Enter "Display a
message on the form".
Page 58
Training Guide
Step
Action
8.
Page 59
Training Guide
Step
Action
9.
10.
Click the Type LOV list.
Page 60
Training Guide
Step
Action
11.
Click the Message list item.
Page 61
Training Guide
Step
Action
12.
Enter the desired information into the Action Description field. Enter "Display a
message".
13.
Click the Message Type LOV list.
Page 62
Training Guide
Step
Action
14.
Click the Show list item.
Page 63
Training Guide
Step
Action
15.
Enter the desired information into the Message Text field. Enter "='The date
today is '||sysdate".
16.
Why does the Message Text start with an = (equal sign)? The = (equal sign) is how
you tell form personalization that the value is not just a string. It is a string that
must be calculated. In this case, it is a simple concatenation (||) of a string with the
current date on the server.
Whenever you use a dynamic value, you should test or validate your text to make
certain that it is performing as expected.
17.

or
Press [Alt+a].
18.
When you validate your Message Text, the dynamic value is calculated, and the
current value is displayed for validation.
19.

or
Press [Alt+O].
20.
Page 64
Training Guide
Step
Action
21.
22.
Normally, you would see your simple personalization. But, the message that you
just created is only displayed once when the form is newly loaded. So, you must
close the form and reload it to see your message.
Step
Action
23.
Page 65
Training Guide
Step
Action
24.
25.
Now, you see your message. Note, the message is displayed before the form is
even loaded.
26.

or
Press [Alt+O].
27.
You have now completed the procedure to display a message on a page.

End of Procedure.
Using a Form Built-in

Form built-ins enable you to add functionality to forms.
In this topic, you will use a form built-in.
Procedure
Page 66
Training Guide
Step
Action
1.
Begin at the Navigator - System Administrator page.

Double-click the Users list item.
Page 67
Training Guide
Step
Action
2.

or
Press [Alt+H].
3.
4.
5.

or
Press [z].
Page 68
Training Guide
Step
Action
6.
7.
Enter the desired information into the Description field. Enter "Example of a
message and a built-in on a form".
8.
9.
10.
Page 69
Training Guide
Step
Action
11.
Page 70
Training Guide
Step
Action
12.
Enter the desired information into the Description field. Enter "Warning
message".
13.
Page 71
Training Guide
Step
Action
14.
Click the Warn list item.
Page 72
Training Guide
Step
Action
15.
Enter the desired information into the Message Text field. Enter "Do you want to
query a user?".
16.
At this point, you have only created the message. You need to create a 2nd action
that will be performed after the message is displayed.
Because you want the 2nd action to occur only if the user wants to query a user,
you selected the message type of Warn. Warn messages have two buttons, OK and
Cancel. If the user clicks the OK button, form personalization processing will
continue to the 2nd action. If the user clicks the cancel button, form
personalization will halt at that action for that rule.
17.
Page 73
Training Guide
Step
Action
18.
Page 74
Training Guide
Step
Action
19.
Click the Built in list item.
Page 75
Training Guide
Step
Action
20.
Enter the desired information into the Description field. Enter "Enter query
mode".
21.
Click the Argument LOV button.
22.
Click the ENTER_QUERY list item.
23.

or
Press [Alt+O].
Page 76
Training Guide
Step
Action
24.
Page 77
Training Guide
Step
Action
25.
26.
Remember, to see your personalization in action, you need to close and reopen the
form.
Page 78
Training Guide
Step
Action
27.
Page 79
Training Guide
Step
Action
28.
29.
As a first test, click the OK button to see what happens. In the second test, you
will click the Cancel button to test that response.
30.

or
Press [Alt+O].
Page 80
Training Guide
Step
Action
31.
Enter the desired information into the User Name field. Enter "OPERATIONS".
32.
Execute the query

Press [Ctrl+F11].
33.
Page 81
Training Guide
Step
Action
34.
35.
Test the response to the Cancel button.
36.

or
Press [Alt+C].
37.
Note that when the user clicks the Cancel button, the form is opened in its normal,
non-query mode.
38.
You have now completed the procedure to use a form built-in on a page.
End of Procedure.
Creating a Menu
Forms can have menus, made available to the user, if they want to perform some special bit of
processing.
In this topic, you will create a menu.
Page 82
Training Guide
Procedure
Step
Action
1.

Page 83
Training Guide
Step
Action
2.

or
Press [Alt+H].
3.
4.
5.

or
Press [z].
Page 84
Training Guide
Step
Action
6.
7.
Enter the desired information into the Description field. Enter "Create a menu
entry".
8.
9.
10.
Page 85
Training Guide
Step
Action
11.
Click the Menu list item.
Page 86
Training Guide
Step
Action
12.
Enter the desired information into the Description field. Enter "Create menu
entry".
13.
Click the Menu Entry LOV list.
Page 87
Training Guide
Step
Action
14.
15.
Page 88
Training Guide
Step
Action
16.
Enter the desired information into the Menu Label field. Enter "Query User".
17.
Now, you need to set your menu item so that it only operates when the user is in
the USER block of the form. If the user tried to query from any other block, the
query would fail (at least, as intended).
18.
Click the Add Block... button.

or
Press [Alt+B].
19.
Click the USER list item.
20.

or
Press [Alt+O].
Page 89
Training Guide
Step
Action
21.
Click the Condition tab.
Page 90
Training Guide
Step
Action
22.
23.
Enter the desired information into the Description field. Enter "Respond to menu
selection".
24.
Creating the menu and menu item needed to be done when the form was opened
(WHEN-NEW-FORM-INSTANCE). But, responding to the selection of that menu
item is an event unto itself. And, would only be responded to when selected, not
automatically at the opening of the form.
25.
Page 91
Training Guide
Step
Action
26.
27.
MENU1 is 1 of 45 special menu items that are available. MENU1 to MENU15

will appear on the Tools menu. MENU16 to MENU30 will appear on the Reports
menu. And MENU31 to MENU45 will appear on the Actions menu.
Page 92
Training Guide
Step
Action
28.
29.
Enter the desired information into the Action Sequence field. Enter "1".
30.
Page 93
Training Guide
Step
Action
31.
Click the Builtin list item.
Page 94
Training Guide
Step
Action
32.
Enter the desired information into the Action Description field. Enter "Do the
query".
33.
Click the Builtin Type LOV list.
Page 95
Training Guide
Step
Action
34.
Click the DO_KEY list item.
Page 96
Training Guide
Step
Action
35.
Click the Argument button.
36.
37.

or
Press [Alt+O].
38.
39.
Page 97
Training Guide
Step
Action
40.
Page 98
Training Guide
Step
Action
41.
42.
Note the Tools menu at the top of the form on the menu bar. It is there, but now it
actually has an entry on the menu.
Page 99
Training Guide
Step
Action
43.
Click the Tools menu.

or
Press [Alt+T].
44.
Note that your newly created menu item is now present.
45.
Click the Query User menu.
46.
47.
Execute the query.

Press [Ctrl+F11].
48.
You have now completed the procedure to create a menu on a page.

End of Procedure.
Page 100
Creating Advanced Personalizations

Create a zoom.
Use actions for advanced personalizations.
Creating a Zoom
In old versions of the E-Business Suite, there was a useful feature known as a zoom. It allowed
you to drill-down from one form into another. The old zoom had several limitations, and was
eliminated in the newer versions of the E-Business Suite. But, form personalizations allow you to
implement the functionality of a zoom without the limitations. The biggest limitation that it
overcomes is that you, as the form personalization developer, have complete control over the
form (or forms) that are zoomed to by the personalization.
In this topic, you will create a zoom.
Procedure
Training Guide
Step
Action
1.
Begin by navigating to the Users page.

What follows is an advanced form personalization. You must be familiar with the
basics of form personalization before attempting to understand this example.
In this topic, you are going to create a zoom. A zoom is an old name for a common
feature. The feature allows you to drill-down to details of a common item. The
reason it is called a zoom is because in the very old versions of E-Business Suite,
back in Release 10 and prior, that is what the feature was called.
Step
Action
2.
3.
4.
Page 102
Training Guide
Step
Action
or
Press [z].
Step
Action
5.
6.
Enter the desired information into the Description field. Enter "Create the menu
item for the zoom".
Page 103
Training Guide
Step
Action
7.
Page 104
Training Guide
Step
Action
8.
9.
Page 105
Training Guide
Step
Action
10.
Click the Menu list item.
Page 106
Training Guide
Step
Action
11.
Enter the desired information into the Description field. Enter "Zoom menu
item".
12.
Click the Menu Entry LOV list.
Page 107
Training Guide
Step
Action
13.
Page 108
Training Guide
Step
Action
14.
Enter the desired information into the Menu Label field. Enter "Zoom to
Responsibility Detail".
15.
Click the Add Block... button.

or
Press [Alt+B].
16.
Click the USER_RESP list item.
17.

or
Press [Alt+O].
Page 109
Training Guide
Step
Action
18.
Page 110
Training Guide
Step
Action
19.
20.
21.
Enter the desired information into the Description field. Enter "Handle condition
when Responsibility is NULL (not yet entered)".
22.
Page 111
Training Guide
Step
Action
23.
Page 112
Training Guide
Step
Action
24.

":USER_RESP.RESPONSIBILITY_ID is null".
Page 113
Training Guide
Step
Action
25.
Page 114
Training Guide
Step
Action
26.
27.
Page 115
Training Guide
Step
Action
28.
Page 116
Training Guide
Step
Action
29.
Enter the desired information into the Description field. Enter "Error message".
30.
Page 117
Training Guide
Step
Action
31.
Click the Error list item.
Page 118
Training Guide
Step
Action
32.
Enter the desired information into the Message Text field. Enter "You must enter
a Responsibility before drilling down to the details of that res".
33.
34.
35.
36.
Enter the desired information into the Description field. Enter "Handle condition
when Responsibility is not NULL (responsibility is OK)".
37.
Page 119
Training Guide
Step
Action
38.
Page 120
Training Guide
Step
Action
39.

":USER_RESP.RESPONSIBILITY_ID is not null".
40.
41.
42.
Enter the desired information into the Action Description field. Enter "Save to a
global variable".
43.
At this point, this is probably an unexpected action. Why is this done? You need to
have a means to communicate with the other form. The means to allow that is a
global variable that will be passed from the starting form to the drill-down form.
44.
Click the Object Type LOV list.
Page 121
Training Guide
Step
Action
45.
Click the Global Variable list item.
Page 122
Training Guide
Step
Action
46.
Enter the desired information into the Target Object field. Enter
"XX_RESPONSIBILITY_ID".
47.
Enter the desired information into the Value field. Enter

"=:USER_RESP.RESPONSIBILITY_ID".
48.
Enter the desired information into the Action Sequence field. Enter "2".
49.
Page 123
Training Guide
Step
Action
50.
Page 124
Training Guide
Step
Action
51.
Enter the desired information into the Action Description field. Enter "Launch
Responsibility form".
52.
Click the Builtin Type list.
Page 125
Training Guide
Step
Action
53.
Click the Launch a Function list item.
54.
Just a note about E-Business Suite security. Notice that you don't launch a form,
you launch a Function. An E-Business Suite Function is a specific form with a
specific set of parameters assigned to a particular responsibility. The user then has
the responsibility assigned to them. This insures that user has access to that form
normally. It the user didn't normally have access rights to that function (form), the
drill-down would fail.
Page 126
Training Guide
Step
Action
55.
Enter the Function Code of the Function you wish to launch, in this example that
is FND_FNDSCRSP.
Enter the desired information into the field. Enter "FND_FNDSCRSP".
56.
57.
Page 127
Training Guide
Step
Action
58.
Page 128
Training Guide
Step
Action
59.
Page 129
Training Guide
Step
Action
60.

or
Press [Alt+T].
61.
Note that the menu item is grayed out, and not accessible from this block on the
form.
Click the Zoom to Responsibility Detail menu.
62.
Click in the Responsibility field.
63.

or
Press [Alt+T].
64.
Note that in this block, the menu item is selectable.

65.
Page 130
Training Guide
Step
Action
or
Press [Alt+O].
66.
Click in the User Name field.
67.
Query the OPERATIONS user to give yourself some test data.

Press [F11].
68.
69.
Execute the query.

Press [Ctrl+F11].
70.
Click in the Responsibility field.
71.

or
Press [Alt+T].
72.
73.
Note that the Responsibilities form is launched, but that it has no data. Why? We
haven't yet handled the passing of the global variable.
To do this, you need to make personalizations to the drill-down form to handle the
global variable.
Page 131
Training Guide
Step
Action
74.

or
Press [Alt+H].
75.
76.
77.

or
Press [z].
Page 132
Training Guide
Step
Action
78.
79.
Enter the desired information into the Description field. Enter "Initialize the
global variable".
80.
81.
82.
Enter the desired information into the Description field. Enter "Initialize global
variable".
83.
Page 133
Training Guide
Step
Action
84.
Page 134
Training Guide
Step
Action
85.
86.
87.
The are two settings for a global variable, VALUE and INITIAL VALUE.
VALUE is used to create the variable and set the value. INITIAL VALUE will
create and set the value only if it does not exist. If it already exists, it will leave it
untouched.
88.
Select INITIAL VALUE.

or
Press [Alt+O].
89.
This will only set the global variable to null if it doesn't already exist. When would
that occur? Most times, actually. The only time the global variable is set is during
the zoom. If you just use the form normally, the global variable will not be set.
Enter the desired information into the Value field. Enter "=null".
90.
Page 135
Training Guide
Step
Action
91.
92.
93.
Enter the desired information into the Description field. Enter "If global variable
is not null, go into Query Mode".
94.

":GLOBAL.XX_RESPONSIBILITY_ID is not null".
95.
96.
97.
Step
Action
98.
Page 136
Training Guide
Step
Action
99.
Enter the desired information into the Description field. Enter "Enter query
mode".
100.
Page 137
Training Guide
Step
Action
101.
Click the DO_KEY list item.
Page 138
Training Guide
Step
Action
102.
103.
104.

or
Press [Alt+O].
105.
106.
107.
Enter the desired information into the Description field. Enter "If global variable
is not null, execute the query on the new record".
108.
Page 139
Training Guide
Step
Action
109.
Click the WHEN-NEW-RECORD-INSTANCE list item.
Page 140
Training Guide
Step
Action
110.
111.
Select the RESPONSIBILITY object.

or
Press [Alt+O].
112.

":GLOBAL.XX_RESPONSIBILITY_ID is not null".
Page 141
Training Guide
Step
Action
113.
Set the Processing Mode to "Only in Enter-Query Mode".

Click the Processing Model list item.
Page 142
Training Guide
Step
Action
114.
115.
116.
Enter the desired information into the Description field. Enter "Copy global
variable into form".
117.
"RESPONSIBILITY.RESPONSIBILITY_ID".
118.
Enter the desired information into the Property Name field. Enter "VALUE".
119.
Enter the desired information into the Value field. Enter

"=:GLOBAL.XX_RESPONSIBILITY_ID".
120.
121.
Page 143
Training Guide
Step
Action
122.
Page 144
Training Guide
Step
Action
123.
Enter the desired information into the Description field. Enter "Execute query".
124.
125.
Double-click the EXECUTE_QUERY list item.
126.
127.
128.
Enter the desired information into the Description field. Enter "Reset global
variable to null".
129.
130.
131.
Enter the desired information into the Description field. Enter "Reset global
variable".
132.
Page 145
Training Guide
Step
Action
133.
Page 146
Training Guide
Step
Action
134.
135.
Enter the desired information into the Value field. Enter "=null".
136.
137.
Close the form, and retest your zoom.

Page 147
Training Guide
Step
Action
138.
Page 148
Training Guide
Step
Action
139.
When you return to the Users form, retest the Tools menu to zoom to the
Responsibility.
or
Press [Alt+T].
140.
Page 149
Training Guide
Step
Action
141.
Note that it queried the proper responsibility. Also note that you are not locked
into this one responsibility. You can execute a blind query as a test.
Press [Ctrl+F11].
142.
Press [Down].
143.
Page 150
Training Guide
Step
Action
144.
Page 151
Training Guide
Step
Action
145.
Double-click the Responsibilities list item.
146.
Note that you can enter the Responsibilities form normally, and you will not
encounter any problems.
147.
You have now completed the procedures to implement a zoom on a page.

End of Procedure.
Advanced Personalization Actions

In this topic, you will learn about all the actions that are available to you in form personalizations.
Procedure
Page 152
Training Guide
Step
Action
1.
Begin by navigating to the Form Personalizations (Functions) page.

There are numerous capabilities inherent in form personalization. Let's walk
through the interface, and discuss a few of those advanced features.
Enter a placeholder Seq and Description to start.
2.
Enter the desired information into the Description field. Enter "Advanced
Personalization Actions".
3.
4.
5.
Note the variety of properties. This list will vary based on the object type being
selected.
6.
7.
8.
Page 153
Training Guide
Step
Action
9.

or
Press [Alt+C].
10.
Step
Action
11.
Item is just 1 of 11 different object types that can be personalized.

As a note, business justification and need should drive personalizations. Just
because an object can be personalized does not mean that there is a compelling
business justification to create a personalization.
Page 154
Training Guide
Step
Action
12.
Page 155
Training Guide
Step
Action
13.
As noted throughout the Form Personalization module, there are 4 action types,
Property, Message, Builtin, and Menu. Just like Property, each of the other Action
Types have numerous capabilities.
Review the Message type.
Page 156
Training Guide
Step
Action
14.
15.
A message has 5 types, Show, Hint, Error, Debug, and Warn. An Error message is
a dialog box with 1 button (OK), and it halts further processing of the form. A
Warn message is a dialog box with 2 buttons, OK and Cancel. A Show message is
a dialog box with 1 button (OK), but it doesn't halt processing like an Error
message. A Hint message appears at the bottom of the form, and is most often seen
during saves. Finally, a Debug message is only displayed with Debug Mode is set
to On.
16.
Page 157
Training Guide
Step
Action
17.
Page 158
Training Guide
Step
Action
18.
19.
An SRS Form is a "Standard Request Submission" form, and is most commonly

used to submit reports, along with other concurrent requests.
20.
A Function is a form with parameters and applied security within the E-Business
Suite. It is commonly interchangeably used (incorrectly) with form.
21.
A URL can be any URL accessible from the user's browser. So, it can be an EBusiness Suite browser-based, OA Framework page, or it can be any Internet URL
that you can to use.
22.
DO_KEY allows you to perform numerous keyboard actions common to the EBusiness Suite. This topic will return to DO_KEY for more details.
23.
A Procedure is an PL/SQL Procedure or Function stored in the database.
24.
GO_ITEM allows you to change the navigation order/path of the form.
25.
GO_BLOCK allows you to change the navigation order of the form.
Page 159
Training Guide
Step
Action
26.
The FORMS_DDL built-in available through Forms Personalization allows

PL/SQL blocks to be executed as an Action for a Forms Personalization rule. The
FORMS_DDL built-in has the following characteristics:
The FORMS_DDL argument is a PL/SQL block of code to be executed.
The block may optionally include a DECLARE section for any required
variables followed by a PL/SQL block beginning with BEGIN and ending with
END;.
The PL/SQL block or argument for the FORMS_DDL built-in within Forms
Personalization can contain a maximum of 2000 characters.
The Validate button will execute the FORMS_DDL argument immediately.
Values cannot be returned back from the FORMS_DDL built-in. (It is however,
possible to insert records with values into a custom table from within a
FORMS_DDL block and then use a Property action type to read them back from
the custom table, but that is beyond the scope of this document.)
Inserts/Updates to records are not committed unless there is a COMMIT; within
the PL/SQL block OR the users does a Save within the current form.
Uncommitted inserts/updates will be lost when the user closes the form, and the
form will not prompt the user to save the changes.
The FORMS_DDL built-in does not support bind variables. In order to pass
variables you must concatenate any bind variables you wish to use into the
FORMS_DDL argument, creating a single string that contains the PL/SQL block
of code to be executed.
Care must be taken to insure the FORMS_DDL is a properly formatted PL/SQL
statement, especially when single quotes (') are needed to appear within the
PL/SQL block itself (e.g. you need to define/use a constant/character value). A
single quote can be represented within a string as two successive single quotes in a
row.
27.
Call Custom Library allows the CUSTOM library to be called. Despite the
declarative interface of Forms Personalization it is still sometimes necessary to
write PL/SQL code within the CUSTOM library. To facilitate this we have
introduced a new builtin type of Call Custom Library which takes a single
argument of the event name. Within the CUSTOM library, code can then be
written to respond to this event.
Page 160
Training Guide
Step
Action
28.
It is possible to change the underlying where clause for query for an LOV. If one
needs to change the columns returned by the query, care must be taken to ensure
that the column names and data types match what was defined for the LOV that is
being changed.
The SQL may reference values from form fields, form parameters and globals. All
SQL statements used for this feature should be tested from SQL*PLUS to ensure
that the SQL is valid and will work as expected. If the SQL for the personalization
has references to bound variables, substitute values that would normally be
expected. To create a personalization to change the record group used by an LOV,
create a new personalization as follows:
Condition
Trigger Event: WHEN-NEW-FORM-INSTANCE level.
Actions
#1
Type: Builtin
Builtin Type: Create Group from Query
Argument: <the SQL statement to be used>
Group Name: <the new record group name>
#2
Type: Property
Object Type: LOV
Target Object: <the LOV to use the new record group>
Property Name: GROUP_NAME
Value: <the record group name created in action step 1>
29.
Select the Builtin Type DO_KEY, and look at the options.

30.
Any key that can be processed via E-Business Suite can be processed with
DO_KEY via a form personalization.
31.
32.
It is also possible to apply a form personalization to just a particular language.

This is especially useful for global E-Business Suite instances that are supporting
multiple languages.
Click the Language LOV list.
Page 161
Training Guide
Step
Action
33.
Click the American English list item.
Page 162
Training Guide
Step
Action
34.
And finally, just like Rules, individual Actions can be enabled or disabled by
clicking the Enabled checkbox.
Disable the action.
Click the Enabled option.
35.
Enable the action.

Click the Enabled option.
36.
You have now completed your exploration of the advanced actions that are
possible via personalizations on a page.
End of Procedure.
Page 163
Administering Form Personalizations

Upon complete of this lesson, you will be able to use the appropriate techniques to debug form
personalizations.
Debugging Form Personalizations

Upon complete of this topic, you will be able to use the appropriate techniques to debug form
personalizations.
Procedure
Step
Action
1.

Point to the Users object.
2.
Double-click the Functions list item.
Training Guide
Step
Action
3.

or
Press [Alt+H].
4.
5.
Page 166
Training Guide
Step
Action
6.
Click the Personalize list item.
7.
Click in the Action Sequence field.
8.
Click in the Action Sequence field.
9.
Click the Debug Mode list.
Page 167
Training Guide
Step
Action
10.
Click the Show Debug Messages list item.
Page 168
Training Guide
Step
Action
11.
Page 169
Training Guide
Step
Action
12.
Page 170
Training Guide
Step
Action
13.
Page 171
Training Guide
Step
Action
14.
15.

or
Press [Alt+O].
Page 172
Training Guide
Step
Action
16.

or
Press [Alt+O].
17.
Execute a query.
Press [Ctrl+F11].
18.

or
Press [Alt+O].
19.

or
Press [Alt+O].
20.
Press [Down].
21.

or
Press [Alt+O].
Page 173
Training Guide
Step
Action
22.

or
Press [Alt+O].
23.

or
Press [Alt+H].
24.
Go to the Form Personalizations page.

Step
Action
25.
Click the Debug Mode list.
Page 174
Training Guide
Step
Action
26.
Click the Step-by-Step list item.
Page 175
Training Guide
Step
Action
27.
28.
Page 176
Training Guide
Step
Action
29.
Page 177
Training Guide
Step
Action
30.
31.

or
Press [Alt+O].
Page 178
Training Guide
Step
Action
32.

or
Press [Alt+O].
33.

or
Press [Alt+O].
34.

or
Press [Alt+O].
35.
You have now completed the procedures that will enable you to debug a
personalization on a page.
End of Procedure.
Page 179

R12 Forms Personalization

Загружено:

Сведения о документе

Исходное описание:

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

R12 Forms Personalization

Загружено:

Авторское право:

Доступные форматы

Oracle EBS R12 Forms Personalization

Creating Basic Form Personalization............................................................................19

Creating Intermediate Personalizations........................................................................35

Creating Advanced Personalizations...........................................................................101

Administering Form Personalizations.........................................................................165

Installing and Setting Up Forms Personalization

Enabling Form Personalization

Scroll down to the System Administrator responsibility.

Click the System Administrator list item.

Click the OK button.

Double-click the Profile list item.

Double-click the System list item.

Click the Find button.

Click the Site LOV button.

Accept the default of No.

Click the Save button.

Click the Close button.

Switch back to the original General Ledger, Vision Operations (USA)

Scroll down to the General Ledger, Vision Operations (USA) responsibility.

Click the General Ledger, Vision list item.

Click the OK button.

Click the Help menu.

Notice that you now see the Diagnostics menu entry.

Point to the Custom Code menu.

Click the Personalize menu.

Click the OK button.

Click the Switch Responsibility... button.

Scroll down to the System Administrator responsibility.

Click the System Administrator list item.

Click the OK button.

Double-click the Profile list item.

Double-click the System list item.

Click the Find button.

Click the Site LOV button.

Click the Yes list item.

Click the OK button.

Click the Save button.

Click the Close button.

Click the Switch Responsibility... button.

Scroll down to the General Ledger, Vision Operations (USA) responsibility.

Click the General Ledger, Vision... list item.

Click the OK button.

Double-click the Account Inquiry list item.

The Account Inquiry page is a typical Oracle Forms-based page. It is possible to

Click the Help menu.

Point to the Diagnostics menu.

Point to the Custom Code menu.

Click the Personalize menu.

You have now completed the procedures to enable form personalizations.

Turning Form Personalization On and Off

Begin at the Navigator page within any Oracle Forms-based page.

Click the vertical scrollbar.

Choose the System Administrator responsibility to call up the forms needed to

Click the OK button.

Double-click the Profile list item.

Double-click the System list item.

Click the Find button.

Click the Site LOV button.

Click the Yes list item.

Click the OK button.

Click the Save button.

Click the Help menu.

Point to the Diagnostics menu.