Oracle Form Personalization

© 2006 Oracle Corporation – Proprietary and Confidential
<Insert Picture Here>
Oracle Forms Personalization Without Coding

Bill Sawyer
Senior Principal Curriculum Developer
Management Challenges
Globalization creates unique challenges in managing…
Compliance Mandates Competitors

Increased and varying The Internet eliminated
regulatory / security borders making all
requirements exert additional markets global markets
burdens on businesses
Customers & Employees Suppliers

Manage employees and Margin pressures force
customers dispersed across companies to search for
geographic and cultural goods & services anywhere
in the world resulting in
boundaries
complex supply networks

To Meet These Challenges, Businesses
Must…
¾ Think Globally to make the right decisions
¾ Work Globally to be more productive
¾ Manage Systems Globally to lower cost and

increase performance

Program Agenda
• User Overview <Insert Picture Here>
• Technical Overview
• Demonstrations

User Overview

Have you ever wanted to …
• Remove fields, buttons, tabs, etc. from the screen because they
are not used in your implementation?
• Re-label fields, buttons, tips to match your corporate
terminology?
• Change or set default value of fields?
• Allow navigation from one form to another, passing context?
• Add additional business logic/practices/messages?
• Do any of the above for only a particular user or responsibility?
• Do any of the above only if certain conditions are true?
• Do all of the above in a upgradeable manner without writing
code, and without violating Support agreements?

Has this been personalized?

Menu changes
Add menu items, and

shortcuts to other
forms/URLs, with
data/parameter passing

Icon changes
Add/enable
icons

Default values
Change default values, auto-

fill or validate data based on
business rules, make fields
mandatory

Messages
Create pop-up messages

generated for/with specific
conditions and/or data

Field prompts
Modify prompt/field
title, remove fields,
change entry order.

Business logic
Support of additional
business logic/practices
(e.g. Hold Order)

What are the benefits?
• Change the product to match your business processes instead of

changing your processes to match the product.
• Implement your Security, your Navigation, your Defaults, your
Terminology.
• Changes can be built, tested and deployed in minutes.
• Most changes can be entered by functional experts.
• Actions can be associated with one language, or all languages
(multi-language support).
• Form Personalizations are not customizations.
• They are likely to survive upgrades (but not without testing).
• Can be developed on one instance, and deployed to others.

Navigation Example
Requirement: Navigate to
the Supplier screen for the
selected Supplier.

Navigation Example

Navigation Example

Navigation Example

Business Logic Example
Requirement: Place the line

on hold if margin goes below
30%.

Requirement: The Task Type

should be used to determine
Task Owner (and Owner Type)

Requirement: If item cannot be

shipped to a specific state (hazardous
materials), place the line item on hold
and warn the user.

Requirement: Display Workflow

status for PO.


Requirement: If the quantity for

an item is over a defined limit,
change the default shipping
warehouse.

Requirement: Map Address

of Service Request



Requirement: View the WIP Discrete Job

linked to this sales order to make this item


Requirement (Part 2): View the

material requirements for the
WIP Job



UI Changes Example
Requirement: Make a number of
cosmetic changes and add “Town of
Add a Zoom to “Personal Birth” validation
Benefits Balance”
(passing Employee
Number) Insure“Town of Birth” is entered if
“Country of Birth” = “United
Make Mandatory States”
Remove
Change prompt to
Move up “Marital Status”

UI Changes Example

UI Changes Example

External Websites Example
Requirement: Display tracking details

from Shipping Carrier for order line



Legacy Integration Example
Requirement: Lookup new

account number based on
number from Legacy system

Note ‘Legacy’ account number

is entered proceeded with a ‘!’

Note ‘Legacy’ account number

is entered proceeded with a ‘!’

Query Capability Example
Requirement: Add additional

item search/lookup capability


Any field of the Item Master can be

used to query items

Note fields are ‘grey’. No inserts or

updates are allowed

Closing Item Master returns item

number to Order Entry

Technical Overview

Technical Overview
• Allows you to make changes to a form without programming

(declarative vs. coding).
• Changes are applied at runtime when the proper trigger event
(e.g. field to field navigation) occurs.
• Change object properties (e.g. name/title).
• Display messages to the user.
• Activate additional menu entries.
• Execute certain Forms builtins (e.g. database procedure call,
‘Do’ key, open form/URL).
• Change occurs based on a definable condition(s).
• Changes can be defined to occur site-wide or for a given
responsibility, industry, or user.

Technical Overview
• Form Personalizations occur as a result of identified

navigation/form events.
• Forms Personalizations are accessed for a specific
function (i.e., function security rules apply).
• Forms Personalizations have two components.
• The personalization with it’s associated trigger event and
condition(s).
• The actions to be performed for when it is triggered.
• Form Personalizations are documented in Metalink
Note 279034.1.
• Also see the ‘11i Form Personalization’ in the Oracle
Education Online Library at www.oracle.com

The Personalization UI
• You don’t have to think like a developer.

• Objects with prompts, titles or labels can be selected by their current
on-screen text.
• But, textual values and conditions offer powerful capabilities if
you do want to think like a developer.
• :block.fields (current form and system values)
• SQL functions/procedures
• server-side functions
• SELECT statements
• All changes can be applied and validated immediately to see
their effect.
• Changes can be disabled at multiple levels, including all, rule, or
action levels.

Relationship to CUSTOM.PLL library
• CUSTOM.PLL is a stub library Oracle ships that

receives certain form events. Customers are able to
freely add any code they like to it.
• It is an Oracle Forms library, so you must use Oracle
Developer to edit and generate it.
• CUSTOM .PLL can do more because it has complete
access to PL/SQL and SQL.
• But Form Personalizations can and should handle the
vast majority of your changes.
• Form Personalizations and changes to the CUSTOM
.PLL library co-exist.

Making Personalizations

















Handling Values
Constant: Hi there World!
Expression: ='Hi there '||:po_headers.vendor_name
=SELECT vendor_name "A"

SQL
from po_vendors
Statement:
where vendor_id = :po_headers.vendor_id
Expression =SOME_DATABASE_FUNCTION(
(DB function): :po_headers.vendor_id )
Note: 2000 character limit (text length and return value)!

Development Scenario
PO_HEADERS.VENDOR_SITE_CODE
Scenario: Display a message when the

Supplier is entered that indicates the supplier
and how many open invoices they have.




Note: Column alias of “A”

and must be of type CHAR


Demonstrations

Appendix

For More Information
http://search.oracle.com
Personalization and Extension of Apps
or
http://www.oracle.com/technology/products/
applications/development_pesonalization/


Oracle Form Personalization

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Oracle Form Personalization

Uploaded by

Copyright:

Available Formats

© 2006 Oracle Corporation – Proprietary and Confidential

<Insert Picture Here>

Oracle Forms Personalization Without Coding

Compliance Mandates Competitors

Customers & Employees Suppliers

© 2006 Oracle Corporation – Proprietary and Confidential

¾ Think Globally to make the right decisions

¾ Work Globally to be more productive

¾ Manage Systems Globally to lower cost and

© 2006 Oracle Corporation – Proprietary and Confidential

• User Overview <Insert Picture Here>

© 2006 Oracle Corporation – Proprietary and Confidential

© 2006 Oracle Corporation – Proprietary and Confidential

© 2006 Oracle Corporation – Proprietary and Confidential

© 2006 Oracle Corporation – Proprietary and Confidential

Add menu items, and

© 2006 Oracle Corporation – Proprietary and Confidential

© 2006 Oracle Corporation – Proprietary and Confidential

Change default values, auto-

© 2006 Oracle Corporation – Proprietary and Confidential

Create pop-up messages

© 2006 Oracle Corporation – Proprietary and Confidential

© 2006 Oracle Corporation – Proprietary and Confidential

© 2006 Oracle Corporation – Proprietary and Confidential

• Change the product to match your business processes instead of

© 2006 Oracle Corporation – Proprietary and Confidential

© 2006 Oracle Corporation – Proprietary and Confidential

© 2006 Oracle Corporation – Proprietary and Confidential

© 2006 Oracle Corporation – Proprietary and Confidential

© 2006 Oracle Corporation – Proprietary and Confidential

Requirement: Place the line

© 2006 Oracle Corporation – Proprietary and Confidential

Requirement: The Task Type

© 2006 Oracle Corporation – Proprietary and Confidential

Requirement: If item cannot be

© 2006 Oracle Corporation – Proprietary and Confidential

Requirement: Display Workflow

© 2006 Oracle Corporation – Proprietary and Confidential

© 2006 Oracle Corporation – Proprietary and Confidential

Requirement: If the quantity for

© 2006 Oracle Corporation – Proprietary and Confidential

Requirement: Map Address

© 2006 Oracle Corporation – Proprietary and Confidential

© 2006 Oracle Corporation – Proprietary and Confidential

© 2006 Oracle Corporation – Proprietary and Confidential

Requirement: View the WIP Discrete Job

© 2006 Oracle Corporation – Proprietary and Confidential

© 2006 Oracle Corporation – Proprietary and Confidential

Requirement (Part 2): View the

© 2006 Oracle Corporation – Proprietary and Confidential

© 2006 Oracle Corporation – Proprietary and Confidential

© 2006 Oracle Corporation – Proprietary and Confidential

© 2006 Oracle Corporation – Proprietary and Confidential

© 2006 Oracle Corporation – Proprietary and Confidential

© 2006 Oracle Corporation – Proprietary and Confidential

Requirement: Display tracking details

© 2006 Oracle Corporation – Proprietary and Confidential

© 2006 Oracle Corporation – Proprietary and Confidential

© 2006 Oracle Corporation – Proprietary and Confidential

Requirement: Lookup new

© 2006 Oracle Corporation – Proprietary and Confidential

Note ‘Legacy’ account number

© 2006 Oracle Corporation – Proprietary and Confidential