Record History and other

Personalizations in R12 Oracle

Applications Framework (OAF) Forms

Session ID#11324

Chris Tyner

AXIA Consulting

Carole Landgrebe

Intelligrated

• Introductions

• Record History in R11i

• R12 OAF pages

• OAF Personalization Primer

• How to add “Record History”

• Issues with the OAF pages

• Base Tables for an OAF page

• How to add your own Record History

Please ask questions!!!!!

2

AXIA Consulting, LLC

• Founded in 2005 in Columbus, Ohio, AXIA AXIA Consulting is a premier consulting

firm that provides technology and business consulting services to local middle-

market and Fortune 500 companies as well as government agencies. Focused on

real, business oriented results, AXIA consistently delivers tremendous value by

accomplishing projects on-time and on-budget while achieving our client’s strategic,

operational, and technology objectives

• AXIA founding members have been working together for over 20 years

– Management stability

– Common goal of client satisfaction

– Excellent track record of satisfied clients, 100% client reference-ability

• Oracle Partner - Gold Level

Chris Tyner, Senior Consultant, AXIA Consulting • 21 years in IT consulting in a variety of industries

• Working with Oracle Applications since 1993

• Release 9.4.2 through 12.1.3

• Presenter at OAUG (1999, 2008) as well as Open World 2011

• Lives in the Cleveland area

3

Intelligrated, Inc. • Founded in 2001 by executives from other conveyor companies, HQ in Cincinnati, OH

• Company brought up on Oracle EBS at founding, upgraded to R12 in 2010

• Grew rapidly to a leading provider material handling solutions in the following

industries:

• Warehouse & Distribution, Manufacturing, Postal & Parcel

• 2009 Acquisition tripled the size of the company to our current size • 1600+ staff associates

• 4 US manufacturing plants

• Canadian and Mexican operations

Carole Landgrebe, Senior Business Analyst, Intelligrated • Came into IT through the back door – originally a manufacturing and distribution

manager in the chemical process industry

• Working with Oracle Applications since 1997

• Oracle Consulting, 1997 – 2003, starting with 10.7 character

• Intelligrated since 2003

• Lives in the Cincinnati area

4

• Standard audit data on nearly every form

• Based on the “WHO” columns on database tables

• Also shows base table or view

While cursor is in a

form field, use

standard menu bar

navigation:

> Help > Record History

5

6

Several pages have been migrated from the

professional user interface to the new OAF technology

for R12:

• Suppliers

• Customers

• Bank Accounts

• Payments

• EB Tax

• Project Management

Plus others already existed…

7

Record History was added as a capability within the

features of OAF page Personalization

Released as a part of ATG patch in Release 12.0.6

• Still not turned on automatically in any page – you must

personalize each page page where this is needed

• The pages also need to be enhanced to use the Record History

Functionality, i.e., “Uptake” the new feature

• As a result many R12 OAF pages still do not work with this

functionality

8

Setups needed to Personalize an OAF page • Three profiles must be set to add Record History to R12 pages

9

Can implement many useful features on OAF pages for

these security levels, with the quick setting of a property • Field Labels

• Field Size

• Ordering Fields on a Page

• Hide Fields (Render = False)

• Apply Styles (CSS Class property), such as apply UPPER CASE

• Many more…

As a note, personalizations can be set at a variety of

levels • Site (most useful for the Record History feature)

• Organization

• Responsibility

10

Can only be added to the following components in OAF

pages • Header

• Table

• Advanced Table

Set those Profile Options, and then open up the OAF

page…

11

Demonstration on a new EB Tax form

Choose the Personalization link to open page that lists

objects available

12

Page to allow you to choose the right object in the region

Note the Document

Name for management of

your Personalizations

Choose the right

object from the

Personalization

structure List

13

Properties that can be “personalized” for the object selected

14

Set the value of ‘true’ at the desired level

Apply changes to return to Object list…

15

Click to return to the application, changes will be

immediately available

16

New Record History icon is available on the page

17

When the icon is clicked for a record

18

Sometimes when the Record History is added, it doesn’t work

19

The following pages have been tested to work with

Record History capabilities Module/Functional Area Record History Comments

EB Tax Works in certain page items

Payments Works in certain page items, such as Payment Process

Requests

Customers Does not work, see Enhancement Request information

at the end of this presentation

Suppliers Does not work, see Enhancement Request information

at the end of this presentation

Project Management Does not work

Employee Self-Service

(HR)

Does not work

Bank Accounts (Cash

Management)

Does not work

20

Standard Record History in OAF will only show the User

IDs, not the User Name (From FND_USER table)

21

Oracle has set up Enhancement Requests to address all of

these issues.

• User Name on Record History, not User ID

• ER 9342923, opened on Feb 2, 2010

• Record History “uptake” on Customer OAF page

• ER 7693621, opened on Jan 7, 2009

• Record History “uptake” on Supplier OAF page

• ER 8275824, opened on Feb 20, 2009

Please attach your company to these ER numbers!

22

The other component of the Record History in the

original forms is the listing of the base table (or view).

This can be discovered on OAF pages, and there is

much greater detail available.

Begin by setting the “Personalize Self-Service Defn”

Profile option to yes, or you could also just use the

“FND: Diagnostics” profile set to yes.

Then open the OAF page in question…

23

Open the Customers forms

Note the “About this Page” link now shows at the bottom

24

For our example, query up a Customer, click through to

the Customer Account page

25

After Clicking the “About this Page” link…

Use the Page Definition region to expand all components

26

This provides the following

Component list with View Objects listed

27

Some View Objects have hyperlinks to the definition,

such as the example from the previous slide

Full query for the View Objects is displayed

28

If the View Object name was not hyperlinked, note the

name and find it in the “Select a view object” drop down

Click the Get Details button to open the details for that

View Object

29

The full list of View Objects was also available from the

first page into the “About this Page” link.

Expand the Business Component Reference Details…

30

Full list of View Objects for the page are displayed

31

Once the OAF personalization skills have been

mastered, you can configure a version of record history

in most OAF pages.

• We compiled a white paper with several options, some of which

involve OAF page development skills

• First we’ll talk about a partial solution which only involves OAF

Personalization techniques (no custom development)

32

Going back to the View Object Definition, most of these

are defined with the WHO columns included from the

main table.

Go back to the Customer Account page:

33

Using the “About this Page” link, we see the View Object

includes Last Update Date, Last Updated By ...

34

Return to the application page, and then click the link to

“Personalize Create Account”.

We are going to add new fields to our page to display

the WHO columns.

35

Use the Create Item icon to add a new field to the area

of the page.

You also have a chance to re-order fields once the

additions are made.

36

Create Item page will display, choose the “Message Text

Input” item style (the Property List will change slightly).

37

Set the following Properties for our new “Creation Date”

field:

• Level = Site

• Item Style = Message Text Input (Note that we can not use the

Message Styled Text type here because this region was intended for

the update of data)

• ID = Creation_Date_Value (This is a unique name that you can make

up, must contain no spaces)

• Data Type = DATETIME (We want to see the date and time stamp)

• Prompt = Creation Date (Label for this field on the page)

• Read Only = true

• Rendered = true (This causes it to be visible on the page)

• View Attribute = CreationDate (The field as it is listed on the Attribute

list on the View Object description page)

• View Object = HzPuiCrUpCustActVO (The exact name of the view

Object)

38

Apply the changes and page component list is updated.

39

Click the Return to Application link and observe the new

field...

40

Repeat with other WHO columns to complete the result.

41

A more complete Record History solution would modify

the View Object to include joins to FND_USER.

Then you could display the user_name field.

This requires developer skills and JDeveloper.

The Whitepaper from this session will walk you through

an example of generating a custom View Object in

JDeveloper.

A View Object is generated based off an existing one.

Then a substitution of the new View Object is performed.

42

The new user name fields in the View Object are added

to the Supplier page as previously described.

A picture of a customized Supplier page...

43

Questions?

Comments?

44

THANK YOU

Chris Tyner

AXIA Consulting

chris.tyner@axiaconsulting.net

http://www.axiaconsulting.net

45