Forms

Personalization

November 29, 201

Form PersonalizationOverview

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.
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. The
personalization feature provided easy, faster and
requires minimum development effort.

November 29, 201

Form Personalization- Overview

cont.

Forms Personalization allows to modify the look and feel of

Oracle Applications forms without actually modifying the form
coding and without risking to break the Support Agreements This
utility allows users to:
Change generic field labels to customer specific labels
Remove unused fields, tabs, etc
Add new form menu options to call new forms
Apply conditional logic to specific records or fields

November 29, 201

Forms PersonalizationOverview
Allows to change thecont..
behavior of form based screens
alter properties, execute built-ins, show messages,
add menus
Personalization can be applied to functions (default)
or to base forms
Each function can have one or more Rules that
consist of Events, Conditions (optional), Scope and
Actions.
Rules are applied at runtime when the trigger event
fires

November 29, 201

Personalize or Customize?
Personalization does not require

use of Oracle Forms Builder

compilation of the CUSTOM library
changes to the base form

CUSTOM library is able to support more complex

changes due to full access to PL/SQL and SQL
capabilities
Conclusion: whenever possible, one should utilize
Forms Personalization and only use CUSTOM
library when complex changes are required
November 29, 201

Invoking Form
Personalization
Personalization form is invoke by
Help->Diagnostics->Custom Code-> Personalize
By default the Personalize menu is visible to all the
users; this can be controlled with help of profile
options.

The profile options are

Utilities: Diagnostics = Yes/No

Hide Diagnostics
= Yes/No

November 29, 201

Personalization Form

November 29, 201

Personalization Rules
Header

Seq execution sequence value between 1 and

100.
Description define the personalization you are
making
Enabled checkbox used to temporarily disable a
rule

November 29, 201

Personalization Rules
Conditions

Trigger Event The event that causes the Rule to be

processed. This list is limited to the events that are
centrally processed and dispatched by APPCORE library
Trigger Object this field depends on the Trigger Event
and may be Disabled or Enabled and Required
(:block.field for WHEN-NEW-ITEM-INSTANCE event)
Condition - This is an optional SQL code fragment that is
evaluated when the Event occurs; if it evaluates to TRUE
then the Actions are processed

November 29, 201

Personalization Rules
Conditions

Fire In Enter-Query Mode Allow the Rule to fire in :

Enter Query Mode Only

Not in Enter Query Mode
Both

Level - Allows the rule to only apply to a specified

level: Site, Responsibility, User, Industry (not
currently used)
Value Based on the Level

November 29, 201

10

Personalization Rules
Actions

November 29, 201

11

Personalization Rules
Actions

Seq execution sequence value between 1 and 100

Type Type of action for the rule:

Property: allows you to select a specific object, a property of

that object, and specify a new value for that property
Builtin: allows execution of a standard Forms Builtin, such as
Launch a Function or DO_KEY
Message: displays a message in one of several styles
Menu: enables a menu entry, defines its label, icon name and
which blocks it applies to

November 29, 201

12

Personalization Rules Actions

cont.

Description used to describe the action

Language Specify All or a specific language
Enabled used to temporarily disable the
action

November 29, 201

13

Personalization Rules
Buttons

Add Parameter Only enabled for Launch a

Function built-in. Shows all parameters used for the
called function
Add Block Displays block names
Add Item Displays item names
Validate Used to test the syntax of the string. If
testing a non-SQL expression this function will display
the string as it will appear at runtime
Apply Now Allows to apply changes to the target
function immediately

November 29, 201

14

Type Action Property

Select By Text Allows to select an object based on

the prompt name
Object Type Item, Block, Tab, Canvas, LOV,
Window, Radio Button, View, GLOBAL and
PARAMETER
Target Object Depends on the field above. This is
the internal name of the object
Property Name Displays the list of properties that
can be personalized for the target object
Value The new value of the personalized property.
This value can be evaluated against Boolean
expression, set of values or a string

November 29, 201

15

Type Action Message

Message Type Popup message: Show, Hint,

Warn, Error or Debug (will only be displayed if Show
Debug Messages checkbox is checked). Message
type of Warn and Error will raise a
Form_Trigger_Failure exception if a user clicks the
Cancel button
Message Text Enter the text that will be displayed
by this message

November 29, 201

16

Type Action Builtin

Builtin Type The type of the action to perform:

Launch SRS Form

Execute Procedure
Execute Trigger
Launch a URL
Launch a Function
GO_ITEM, GO_BLOCK
DO_KEY
RAISE FORM_TRIGGER_FAILURE

Builtin Arguments/Parameters These are variable

fields that are dependant on the Builtin Type

November 29, 201

17

Type Action Menu

Menu Entry - One of 45 menu entries that can activate

- 3 sets of 15 each under the Tools, Reports and
Actions
Menu Label Text label of the menu entry as it will
appear on the form
Render Line Before Menu will create a line before
the menu to separate it from other menu entries
Icon Name Optional field. We can specify the .ico
file that will create an icon and add it to the toolbar

November 29, 201

18

Variables and Strings

Global Variables Size is limited to 255 bytes

Local Variables Size is limited to 4000 bytes
Strings can be processed as is or be evaluated at
runtime:

The string does not start with = > The exact value will be
used at runtime
The string starts with = > The text immediately after = will
be evaluated at runtime. This allows us to include references
to:
o
o
o
o

SQL Operators - ||, TO_CHAR, DECODE, NVL

Bind Variables - :block.field, :global, :parameter, :system
Calls to stored functions that do not have OUT parameters
Select Statements ( must return only 1 row)

November 29, 201

19

Limitations
We Can not change something that does not exist!
Forms Personalization allows users to only change what
Oracle Forms allows at runtime. The actions below can
not be done:

Cannot create new items

Cannot move items between canvases
Cannot display an item which is not on a canvas (DFF)
Cannot change Datatype of an Item
Cannot change frames, graphics, or boilerplate

November 29, 201

20

Limitations,
Cont.
Limited trigger events can be used:

WHEN-NEW-FORM-INSTANCE, WHEN-NEW-BLOCKINSTANCE, WHEN-NEW-RECORD-INSTANCE, WHEN-NEWITEM-INSTANCE

WHEN-VALIDATE-RECORD (not all forms).
MENU1-15
SPECIAL1 - 45
Product-specific events

Certain objects may not be available for changes and

can not be validated

November 29, 201

21

Migrating Personalizations

Function Level Personalization Loader:

FNDLOAD <userid>/<password> 0 Y DOWNLOAD
$FND_TOP/patch/115/import/affrmcus.lct <filename.ldt>
FND_FORM_CUSTOM_RULESfunction_name=<functionn
ame>

Forms Level Personalization Loader:

FNDLOAD <userid>/<password> 0 Y DOWNLOAD
$FND_TOP/patch/115/import/affrmcus.lct <filename.ldt>
FND_FORM_CUSTOM_RULES form_name=<form name>

November 29, 201

22

Migrating Personalizations,
Cont.

All personalizations (forms/functions) Loader:

FNDLOAD <userid>/<password> 0 Y DOWNLOAD
$FND_TOP/patch/115/import/affrmcus.lct <filename.ldt>
FND_FORM_CUSTOM_RULES

The Upload syntax for all styles:

FNDLOAD <userid>/<password> 0 Y UPLOAD
$FND_TOP/patch/115/import/affrmcus.lct <filename.ldt>

November 29, 201

23

Support, Upgrade and

Troubleshooting
Our personalization may jeopardize the integrity of
the data Test Thoroughly!
Our Personalizations are not supported by Oracle
make sure that it is not the cause of your data
problems
If our form stops running Disable all personalizations:

Help->Diagnostics->Custom Code->Off Run the form, open

Personalization and correct the problem

Upgrade personalization testing:

Run the form

Invoke the Personalization Screen
Select Tools->Validate All.
Locate and fix errors

November 29, 201

24

!! Important!!
Any changes we make may interfere with normal form
operation

Personalization is overridden by base form code

Personalization produces wrong results because it interacts
with base code in unexpected ways
Personalization may prevent the form from running at all

November 29, 201

25