Professional Documents
Culture Documents
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
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:
5
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
6
Record History was added as a capability within the
features of OAF page Personalization
7
Setups needed to Personalize an OAF page
• Three profiles must be set to add Record History to R12 pages
8
As a note, personalizations can be set at a variety of
levels
• Site (most useful for the Record History feature)
• Organization
• Responsibility
9
Can only be added to the following components in OAF
pages
• Header
• Table
• Advanced Table
10
Demonstration on a new EB Tax form
12
Properties that can be “personalized” for the object selected
13
Set the value of ‘true’ at the desired level
14
Click to return to the application, changes will be
immediately available
15
New Record History icon is available on the page
16
When the icon is clicked for a record
17
Sometimes when the Record History is added, it doesn’t work
18
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
19
Standard Record History in OAF will only show the User
IDs, not the User Name (From FND_USER table)
20
Oracle has set up Enhancement Requests to address all of
these issues.
21
The other component of the Record History in the
original forms is the listing of the base table (or view).
22
Open the Customers forms
Note the “About this Page” link now shows at the bottom
23
For our example, query up a Customer, click through to
the Customer Account page
24
After Clicking the “About this Page” link…
25
This provides the following
27
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
28
The full list of View Objects was also available from the
first page into the “About this Page” link.
29
Full list of View Objects for the page are displayed
30
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)
31
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:
32
Using the “About this Page” link, we see the View Object
includes Last Update Date, Last Updated By ...
33
Return to the application page, and then click the link to
“Personalize Create Account”.
36
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)
37
Apply the changes and page component list is updated.
38
Click the Return to Application link and observe the new
field...
39
Repeat with other WHO columns to complete the result.
40
A more complete Record History solution would modify
the View Object to include joins to FND_USER.
41
A View Object is generated based off an existing one.
42
The new user name fields in the View Object are added
to the Supplier page as previously described.
43
Questions?
Comments?
44
THANK YOU
Chris Tyner
AXIA Consulting
chris.tyner@axiaconsulting.net
http://www.axiaconsulting.net
45