Forms and OA Framework

Personalizations
The Top Ten Examples

Susan Behn
 Agenda

• Overview of Personalization Tools

• Forms Personalization
– Setup and Use
– Examples 1 – 5
– Tips
• OA Framework Personalization Examples
– Setup
– Examples 6 - 10
• Migration to other instances
• References

2
 Overview

• Personalizations – alter behavior or appearance

using tools provided by Oracle
– Supported and generally survive patches
• Personalization Tools
– CUSTOM.pll
– Forms personalizations
• Professional Forms 6i or 10g
– OA Framework Personalizations

3
 Overview – CUSTOM.pll

• Prior to 11.5.10, CUSTOM.pll is the only form

personalization tool
• Library in $AU_TOP/resource
– Use forms builder development tool to modify
package body
• Requires developer skills
• Generally survives patches
• Supported by Oracle **with limitations
• Documented in Application Developer Guide

4
 Overview – Forms Personalization

• Forms Personalizations declaratively alter the

behavior of Forms delivered with the E-Business
Suite
• Requires superuser with some sql skills
• Most changes traditionally done using
CUSTOM.pll can be accomplished using Forms
Personalization
• Effective immediately – no compiling
• Forms Personalizations fire prior to CUSTOM.pll
for the same event

5
 Overview – Forms Personalizations
and CUSTOM.pll – What you can do?

• Hide fields, tabs

• Make fields required
• Restrict insert or update
• Change prompts and labels
• Alter LOVs
• Set default values
• Create tool bar menu items
– Call other forms or web address
– Execute code

6
 Overview – OA Framework
Personalizations
• OA Framework Personalization is for self-service
applications
– Introduced with 11.5.9
• Apply Patch 3323690
– Standard with 11.5.10 and Release 12
• Requires functional superuser
– Minimal technical expertise required

7
 Overview – OA Framework
Personalizations – What you can do?

• Remove Buttons and Change Button Names

• Change Page and Section Headers
• Hide Columns
• Change Field and Column Names
• Set Initial Values
• Change Field Attributes
• Reorder Columns
• Add Items (Buttons, Fields, Tips and more)

8
Forms 6i and10g Personalizations
Setup and Use
Examples 1 – 5
Tips

9
 Setup – Profile Options – Form
Personalizations
• Hide Diagnostics menu entry
– Set to No to see the menu
• Utilities: Diagnostics
– Set to No to require apps password

10
 Accessing Forms Personalization

• Access the form or function needing personalization

• Help Æ Diagnostics Æ Custom Code Æ Personalize

11
 Forms Personalization

1 – 100
Reusable

Form/Function

Default = Function

Most often should

be Form

12
 Forms Personalization – Condition
Tab
• Trigger event determines when the rule fires
– Use standard trigger events (next slide)
– Use specific events unique to the form (With Caution)
• Find additional events using Help ÆDiagnostics ÆCustom Code
ÆShow Custom Events
• Trigger object depends on trigger event
– WHEN-NEW-BLOCK-INSTANCE requires block name

13
 Forms Personalization – Standard
Trigger Events
• WHEN-NEW-FORM-INSTANCE
– Security rules, Navigation rules, Visual attributes
• WHEN-NEW-BLOCK-INSTANCE
– Same as WHEN-NEW-FORM-INSTANCE
– Message rules
• WHEN-NEW-RECORD-INSTANCE
– Default values
• WHEN-NEW-ITEM-INSTANCE
– Message rules
– Default values dependent on entry of another item

14
 Forms Personalization – Standard
Trigger Events
• WHEN-VALIDATE-RECORD
– Populate hidden fields
– Additional validations
• SPECIALn
– Populate tools menu (SPECIAL 1-15)
– Populate reports menu (SPECIAL 16-30)
– Populate actions menu (SPECIAL 31-45)
• MENUn
– Populate tools menu (MENU1-15)

15
 Forms Personalization – Condition
Tab
• Condition
– Optional SQL code fragment to limit scope of rule
– Use bind variables (:block.field)
• Processing Mode
– How rule behaves in query mode vs entry mode

16
 Forms Personalization – Context

• Who does this rule apply to?

Site
Responsibility
User – Use this for testing
rules
Industry (For future use) Tip: For initial
development, set
context to your user id

17
 Forms Personalization – Property
Actions
• Sequence – non unique (1 – 100)
• Type – property, message, built-in, menu
• Description – (Optional)
• Language – use to change prompts for language

Prompts change
depending on
action type

18
 Top Ten Rule #1 – Display
Message
• GL Journal Entry – Remind users to change the
period name the first 20 days of the fiscal year
Enter
header
details
Condition is checked when the user accesses
the journal name field

Message appears
Feb 1 – Feb 20 every year

19
 Top Ten Rule #1 – Display
Message

Action type
= message

• Message Types
– Show – Informational Message
– Hint – Appear on status bar
– Error – Requires user response – raises form_trigger_failure
– Debug – Only displays if debug mode is set to Show Debug
Messages
– Warn – Informational message with caution symbol – raises
form_trigger_failure

20
 Top Ten Rule #1 – Display
Message
• Result

Click OK to
continue

21
 Top Ten Rule #2 – Data Access
Restrictions
• A user should not be able to enter or retrieve
their own invoice
– Enter header and condition tab details

22
 Top Ten Rule #2 – Data Access
Restrictions
• Change the default where clause for the invoice
block to prevent retrieval of employee invoices
based on user id

vendor_id NOT IN
(SELECT vendor_id
FROM po_vendors pv ,
fnd_user fusr
WHERE fusr.user_id = fnd_profile.value('USER_ID')
AND fusr.employee_id = pv.employee_id )

23
 Top Ten Rule #3 – Menu Entries

• Create a menu item to display the invoice id

– Helpful for workflow and approval troubleshooting
• Step 1 – establish the menu entry

Use WHEN-NEW-FORM-
INSTANCE for visual changes
Such as establishing menu entries

24
 Top Ten Rule #3 – Menu Entries

• Menu action type only displays menu

Use add block

button to choose
blocks where this
menu will be
enabled or leave
null for all blocks

25
 Top Ten Rule #3 – Menu Entries

• Step 2 – create the action for the menu entry

26
 Top Ten Rule #3 – Menu Entries

• Step 2 – create the action for the menu entry

Use validate button to

check sql fragment

27
 Top Ten Rule #3 – Menu Entries

• Result

28
 Top Ten Rule #3 – Menu Entries

• Result

29
 Top Ten Rule #4 – Masking Data

• Mask the tax id in 11i

– Supplier form has moved to OA Framework in R12

30
 Top Ten Rule #4 – Masking Data

• CONCEAL_DATA = TRUE - replaces data with *

• DISPLAYED = FALSE – hides field completely

Don’t need to
know object
name
Use Select By
Text button to
find correct
object by
prompt
31
 Top Ten Rule #4 – Masking Data

• Result

32
 Top Ten Rule #5 – Changing
LOVs
• Taxpayer ID is also on LOVs for find window

33
 Top Ten Rule #5 – Changing
LOVs
• Create a new record group replacing tax id with end date

Builtin
available in
11i RUP4
or later

Must have the

same number of
fields as existing
Record group 34
 Top Ten Rule #5 – Changing
LOVs
• Assign the new record group to the LOV used for
Supplier name

Record group
created in
previous slide
35
 Top Ten Rule #5 – Changing
LOVs

• Result

• Additional steps
– Mask the tax id on the find window
– Replace the tax id with the end date for the supplier
number LOV

36
 Forms Personalization – Other
Frequently Used Built-ins
• Launch SRS Form – runs concurrent request
• Launch a Function – call another form
• Launch a URL
• DO_KEY
– DO_KEY(‘NEXT_BLOCK’) will force query execution for find
window
• Execute a Procedure – use to execute any plsql code
• GO_ITEM, GO_BLOCK – change navigation
– Use to prevent update to a field where navigation is needed to
populate
• EXECUTE_TRIGGER
– Execute form trigger, not database trigger
– Use after setting default values to ensure internal code executes

37
 Forms Personalization – Tips

• If you disable a tab page, you may need to

disable items on the tab page
• Exit and re-open the form to see personalization
changes
• Use debug messages before and after events
• Apply Now button - see the results
– Does not always work if dependant on the results of
another action
• Turn custom code off - Help Æ Diagnostics Æ
Custom Code Æ Off

38
 Forms Personalization
Maintenance
• After upgrades, go to the personalization for each form
and choose Tools Æ Validate All
• Tools Æ Administration will show personalized forms

39
OA Framework Personalizations
Setup and Use
Examples 6 - 10

40
 Setup – Profile Options – OA
Framework Personalizations
• Personalize Self-Service Defn
– Yes to allow ‘Personalize’ button to appear at the top of the page
• FND: Personalization Region Link Enabled
– Yes to display all the regional links above each region
– Minimal to display key regional links
• Disable Self-Service Personal
– Yes will disable all personalizations at any level
• FND: Diagnostics
– Turns on ‘About this Page’
• FND: Personalization Document Root Path (new in 11.5.10)
– Required to migrate personalizations
– Set this profile option to a tmp directory with open (777) permissions

41
OA Framework Personalizations

Personalize
FND: Personalization Self-Service
Region Link Enabled Defn = Yes
= Yes

FND: Diagnostics =
Yes

42
 Top Ten Rule #6 – Remove a
button
• iExpenses - Remove Import Spreadsheet button

Start with
Personalize
Page

43
 Top Ten Rule #6 – Remove a
button
• Biggest challenge – finding the item to personalize

– Simple View

– Complete View

– Expand All

– <ctrl> F

– Collapse All

– Focus

44
 Top Ten Rule #6 – Remove a
button
• My favorite – expand all and use <crtl> F

Click pencil to
edit

45
 Top Ten Rule #6 – Remove a
button
• Set rendered = false and click Apply button

Options for
personalization
change based on
object type

46
Top Ten Rule #6 – Remove a
button results

Shown is now null

since rendered = false

Button is gone

47
 Personalization Levels /
Inheritance
• Personalizations at lower levels override
personalizations at higher levels
• Default values are defined in the first column
• Values inherit the definition from the level
immediately above unless changed
• Order of precedence from highest to lowest:
– Function
– Site
– Operating Unit
– Responsibility

48
 Top Ten Rule #7 – Change
Prompts
• Change Job to Job Short Name
• Click the Personalize Page button and find the
Job item using <ctrl> F

49
 Top Ten Rule #7 – Change
Prompts
• Change Prompt at the desired level – in this
case, site level

50
 Top Ten Rule #7 – Change
Prompts
• Result – prompt changed

51
 Top Ten Rule #8 – Hide/Reorder
Columns in a table
• Hide the Duplicate column to prevent users from
duplicating expense reports
– Click the Personalize Page button

52
 Top Ten Rule #8 – Hide/Reorder
Columns in a table
• The button to duplicate is called a Switcher
– Switchers allow users to “switch” to another function
• Finding tip
– Look for other columns in the table
• Report Total
• Purpose

Click pencil to
edit

53
Top Ten Rule #8 – Hide/Reorder
Columns in a table

Set Rendered
= false

Duplicate
column is gone

54
 Top Ten Rule #8 – Hide/Reorder
Columns in a table
• Find the table to reorder table columns
– Turn on region links to find tables easier

Click the reorder

icon at the table
level

55
 Top Ten Rule #8 – Hide/Reorder
Columns in a table
• Check personalization level
• Use arrows to move fields up or down

56
 Top Ten Rule #9 – Set Initial
Values
• Set the initial value for the Purpose

57
 Top Ten Rule #9 – Set Initial
Values
• Set the initial value
– In this case, the value is set at the responsibility level

58
 Top Ten Rule #10 – Add a field

• Add a required Buyer field and include an LOV

for buyer names to contractor request page

Go to about this
page to see if
buyer field exists

59
 Top Ten Rule #10 – Add a field

• Scroll down to find the view object

Expand All

Look for view object (ends with

VO) hyperlinks
Click on PoRequisitionLinesVO
This name will be needed later

60
 Top Ten Rule #10 – Add a field

• The suggested buyer id is available for this page

Database query
for page
Good info for
troubleshooting
• An LOV will translate buyer id to buyer name
Scroll down more
to find available
view attributes

61
 Top Ten Rule #10 – Add a field

• LOV for suggested buyer is on the checkout

page – need to retrieve for request page
– Note: If LOV not available, create in JDeveloper

To find the
LOV,
choose
Diagnostics

62
 Top Ten Rule #10 – Add a field

• Finding the LOV

– Choose Show Log on Screen with Statement (1) log
level

– Navigate back to the checkout screen and click on the

LOV

63
 Top Ten Rule #10 – Add a field

• Scroll down to see the diagnostics

• LOV path for suggested buyer is shown below

Look for the Suggested

Buyer item. Next line
This path will
defines LOV.
be needed
later

64
 Top Ten Rule #10 – Add a field

• Now add the field - click the Personalize Page button

• Find the table layout and click create item icon

Click create
item icon

65
 Top Ten Rule #10 – Add a field

• Enter the following values

Select Message
Lov Input to make
this a LOV
validated field

Enter any unique

name

LOV Path from

slide 63

66
 Top Ten Rule #10 – Add a field

• Scroll down and continue entering the following

values Enter Prompt

Enter View
Attribute from slide
60

Enter View Object

from slide 59

67
 Top Ten Rule #10 – Add a field

• The Suggested Buyor item is created, but the

LOV must be mapped
Click on the
mapping icon

68
 Top Ten Rule #10 – Add a field

• Create LOV Mappings for Buyer Name and

Buyer Id

69
 Top Ten Rule #10 – Add a field

• Click the create

icon again shown
on slide 64
• Create a Form
Value to store the
Buyer Id

70
 Top Ten Rule #10 – Add a field

• Result – Buyer with associated LOV

71
 Top Ten Rule #10 – Add Items

• Other Items that can be added

– Buttons
– Text and Images
– Messages (Data Fields) of many styles
– Tips
– Raw Text

72
 Customizations and
Personalizations
WARNING
Customizations or Personalizations, whether they are
protected or non protected, allow you to fundamentally
change the behavior of the application.

This could interfere with intended functionality.

Use with caution!

TEST! TEST! TEST! TEST! TEST!

73
 Customizations and
Personalizations

…THEN TEST IT AGAIN!

***BUT NOT IN PRODUCTION***

74
 Migration to Other Instances
Forms Personalizations
• Download for a specific form:
– FNDLOAD <userid>/<password> 0 Y DOWNLOAD
$FND_TOP/patch/115/import/affrmcus.lct <filename.ldt>
FND_FORM_CUSTOM_RULES form_name=<form name>
• Download all personalizations
– FNDLOAD <userid>/<password> 0 Y DOWNLOAD
$FND_TOP/patch/115/import/affrmcus.lct <filename.ldt>
FND_FORM_CUSTOM_RULES
• Upload
– FNDLOAD <userid>/<password> 0 Y UPLOAD
$FND_TOP/patch/115/import/affrmcus.lct <filename.ldt>

75
 Migration to Other Instances
OA Framework Personalizations
• Migrate OA Framework Personalizations from the
Functional Administrator Responsibility
– Export to directory defined in FND: Personalization Document
Root Path
– FTP to target instance
– Import from Document Root Path directory

76
 References

• Oracle Application Framework Personalization

Guide
• Oracle Applications User Interface Standards for
Forms-Based Products
• Oracle Applications Developer’s Guide
• Oracle Applications System Administrator’s
Guide
• Oracle Applications User Guide
• MetaLink note 279034.1 – Forms
Personalization

77
 Available at
Got Oracle?
www.solutionbeacon.com
Get the Books!

Installing, Upgrading and

Maintaining Oracle E-Business The Release 12 Primer –
Suite Applications 11.5.10.2+ Shining a Light on the
Release 12 World

The ABCs of Workflow for Oracle

E-Business Suite Release 11i and
Release 12 78
 Questions and Answers

Thank You!

Susan Behn
sbehn@solutionbeacon.com

www.solutionbeacon.com
Real Solutions for the Real World ®

Copyright 2008 Solution Beacon, LLC All Rights Reserved Any other commercial
product names herein are trademark, registered trademarks or service marks of 79
their respective owners.