Upgrading to R12.

2 Lessons
learned and tips that you need to
know to be successful
Session ID: 10538
Information you need to know
whether upgrading from 11.i or
12 0 X / 12.1.x
12.0.X
12 1 x to R12
R12.2.X
2X

Prepared by:
Art Dowd
Consulting Director
O2 Works

Overview / Agenda

Introductions and Audience survey

Upgrade vs
vs. re
re-implement
implement
Why upgrade?
Types of Upgrade
Repeatable Methodology
Upgrade planning
Lessons learned when Upgrading
pg
g from 11i to R12
R12.2.x Whats so different and what are the
concerns
Information sources
Upgrading to the cloud
Contact information

R12 Upgrade Introduction

Art Dowd,, Consulting
g Director,, O2Works

Former VP of IT for Hospitality Company

Extensive business background
Implemented / Upgraded Oracle eBus Suite
16 years with Oracle Applications
Experience with Oracle Consulting and two well
regarded
d dO
Oracle
l A
Applications
li ti
consulting
lti fi
firms

Audience survey
Role
Technical DBA
Technical Developer
Project Manager
Business Process
Owner

Apps Release level

10.7
11.0.3
11.5.1

11.5.9

11.5.10

Super user

12.0

End user

12.1

Upgrade vs. re-implement

Back in the dark ages (pre 11i) there were technical
concerns about upgrading (tech. stack and apps.)
and people opted to re-implement
Due to the significant changes to the apps in going
to R12 the question is surfacing again
Recommendation = upgrade unless there is a
significant reason causing you to have to reimplement
Upgrade process, technology, tools, and scripts are
significant improved
Re-implementation
R i l
t ti = much
h more extensive
t
i project
j t
Data conversion / testing will be an issue

Re-implementation considerations
You might need to re-implement if:
You have changed your basic business /
organization structure and your application
configuration does not still fit your business
Single instance consolidation
Your original implementation was really screwed up
and it is basically unusable
You have tons of really, really bad data
You have tons of customizations that you would like
to retire in order to use current features and
functionalities and streamline your operations >>>
You can upgrade with customizations

Why Upgrade

Business reasons
Oracle support dates and documents

Why Upgrade?
Per Oracle, when there is compelling business
reason to do so
New features and functionality to assist business
Change in business direction; keep IT aligned
Replace customizations and bolt
bolt-ons
ons with standard
features

Take advantage of Tech. stack improvements

Obtain better support when patched current
Stay in support

Key Support As it Relates to R12

Release

GA Date

Premier
Support
Ends

Extended
Support
Ends

Sustaining
Support
Ends

11.5.10

Nov 2004

Nov 2010

Nov 2013*

Indefinite

12

Jan 2007

Jan 2012**

Jan 2015

Indefinite

12.1

May 2009

Dec 2016**

Dec 2019

Indefinite

12.2

Sep 2013

Sep 2021

Not Available

Indefinite

*ForSustainingSupportforOracleEBusinessSuite11.5.10,providedfromDecember2013December2015,Oraclewillcontinuetoprovide:
Severity1fixes,criticalpatchupdatesandUnitedStatesTaxForm1099updatesforthe2013and2014taxyears.Duringthis period,payroll
regulatorytaxupdateswillonlybeprovidedforthecountriesandtaxyearsspecifiedbelow.
Country

2013 Tax Year

2014 Tax Year

United States and Canada

January 1, 2013 December 31, 2014

January 1, 2014 December 31, 2014

United Kingdom

N/A

April 6, 2013 April 5, 2014

Australia

N/A

July 1, 2013 June 30, 2014

Customers must have the indicated baseline patches (or above) for new Severity 1 production bug fixes as per Patch Requirements for
Customersmusthavetheindicatedbaselinepatches(orabove)fornewSeverity1productionbugfixesasperPatchRequirementsfor
ExtendedSupportofOracleEBusinessSuiteRelease11.5.10(seeDocID883202.1).
**FormoredetailedinformationonEBS12.0and12.1bugfixingandforExtendedSupportminimumpatchprerequisites,pleasereferto
theEBSErrorCorrectionSupportPolicy(DocID1195034.1).Foradditionalinformationregardingtheabovepoints,pleasesee theEBS
SupportPoliciesFAQ(DocID1494891.1).
CustomersrunningOracleFusionMiddleware10gR2and10gR3intheOracleEBusinessSuiteversion12internaltechnologystackwill
remainsupportedforthedurationofthesupportperiodforOracleEBusinessSuite12.

Oracle Application Support

**ForSustainingSupportforOracleEBusinessSuite11.5.10,provided
fromDecember2013December2015,Oraclewillcontinuetoprovide:
Severity1fixes,criticalpatchupdatesandUnitedStatesTaxForm1099
updatesforthe2013and2014taxyears.Duringthisperiod,payroll
regulatorytaxupdateswillonlybeprovidedforthecountriesandtax
yearsspecifiedbelow.
*ForSustainingSupportforOracleEBusinessSuite11.5.10,providedfromDecember2013December2015,Oraclewillcontinueto
*For
Sustaining Support for Oracle E Business Suite 11 5 10 provided from December 2013 December 2015 Oracle will continue to
provide:
Severity1fixes,criticalpatchupdatesandUnitedStatesTaxForm1099updatesforthe2013and2014taxyears.Duringthis period,
payrollregulatorytaxupdateswillonlybeprovidedforthecountriesandtaxyearsspecifiedbelow.

Customersmusthavetheindicatedbaselinepatches(orabove)fornewSeverity1productionbugfixesasperPatchRequirementsfor
ExtendedSupportofOracleEBusinessSuiteRelease11.5.10(seeDocID883202.1).
**FormoredetailedinformationonEBS12.0and12.1bugfixingandforExtendedSupportminimumpatchprerequisites,please
**
For more detailed information on EBS 12 0 and 12 1 bug fixing and for Extended Support minimum patch pre requisites please
refertotheEBSErrorCorrectionSupportPolicy(DocID1195034.1).Foradditionalinformationregardingtheabovepoints,pleasesee
theEBSSupportPoliciesFAQ(DocID1494891.1).

Customersmusthavetheindicatedbaselinepatches(orabove)fornewSeverity1
p
productionbugfixesasperPatchRequirementsforExtendedSupportofOracleE
g
p
q
pp
BusinessSuiteRelease11.5.10(seeDocID883202.1).

10

Support Timeline

April,
2016
Formoreinformationcheck:
MyOracleSupportNote1494891.1 EBusinessSuiteReleases Support
PolicyFAQ
MOSNote1195034.1
MOS Note 1195034 1 EBS12.0and12.1ExtendedSupportminimum
EBS 12 0 and 12 1 Extended Support minimum
patchprereqs
11

Support Information
OracleLifetimeSupportPolicy
OracleApplications
Goto:www.Oracle.com
Query:lifetimesupportapplications
Fillin:annoyingOraclesigninscreen
Fill in: annoying Oracle sign in screen

12

Types of Upgrades

Type of Upgrades
Technical upgrade only

Focus on the tech stack / less expensive option

Led by
y DBA / Tech team with little functional support
pp
Functional impact = testing and possibly training.
Common with dot release upgrades (i.e. 11.5.9 to
11.5.10)
M
Management
t / Executive
E
ti Sponsor
S
Project Manager
Success = NO CHANGE on go-live Monday

DBA / Sys.
Admin

Technical
Lead

Developer /
Analyst
y

Super Users
Users

B/A Fin

B/A SC &
Other

Business
Process
Owners

Trainer

Help Desk / Network Support

End Users / Testers

S
Success=NOCHANGEongoliveMonday
NO CHANGE
li M d
14

Types of Upgrade
Full Business-Aligned Upgrade
Aligned with Business objectives / ROI
expectation
Inclusive,
Inclusive wide-ranging project across IT and
Business
Requires more Executive Sponsorship
Change Management Project; not just technical
Management / Executive Sponsor
Project Manager
DBA / Sys.
Sys
Admin

Technical
Lead

Developer /
Analyst

Super Users

B/A Fin

B/A SC &
Other

Business
Process
Owners

Trainer

Help Desk / Network Support

End Users / Testers

i
f
&
li i
On11itoR12,UserInterface&application
changesmustbeaddressed;thereisnooption
15

Repeatable Methodology

Eight components that are critical to every upgrade

How to Ensure Success - Build a

Repeatable Process

Secure - Active
S
A ti E
Executive
ti sponsorship
hi and
d supportt
Communicate Transparent reporting on Progress
Gather - Proper Materials
Recruit - The Right Team Members
Organize - Create and Update Critical documents
Analyze and Plan Use Iterative Method (minimum
= three rounds)
Execute -A
A Serious and Dedicated Testing Process
Experience - Have a leader, bring back the vets

17

Secure Executive Sponsorship

Who is the 800 lb. Gorilla?

High visibility buy-in
Support active is better
When you really have to have a decision
Helps control scope creep
Does the project have legs?
Is it aligned to the current business objectives
Strategic
Return On Investment
CAUTION: When seeking Executive Sponsorship, expect
the question of What is the ROI?
The
Th bad
b d news iis th
thatt th
there iis no return
t
on an upgrade
d
project investment
Best approach is to reduce customizations in order to
reduce the Total Cost of Ownership (TCO)

18

Communication
Have a comprehensive plan
Understand the frequency
q
y
By what method / means

Know your audience

What are they interested in
Share relevant knowledge

Set the tone

Be transparent
Positive
Recognize the value
Focus on what upgrade will provide to business

19

Gather Proper Materials

From My Oracle Support:
Release Content Documents for releases between
where you are and where you want to be (for module
leads only).
Latest Implementation guides for each module in
production or moving to production
Latest User guides for each module in or moving to
Prod.
Secure Passwords and Access for whole team
New release information:
E-Business Suite Upgrade Guide [ID 461705.1]
Upgrade Advisor: E-Business Suite (EBS) Upgrade
f
from
11.5.10.2
11 5 10 2 tto 12
12.1.3
1 3 (D
(Doc ID 269
269.1)
1)
Oracle E-Business Suite Release 12.2 Information
Center - Upgrade (Doc ID 1583158.1)

20

Gather Customizations
List of Customizations and Extensions
Include all reports, forms, views, extracts, triggers, etc
List of custom reports (in all forms)
Interfaces
Workflow/Account Generator Definitions
Oracle supported extensions
Personalizations (screens, prompts)
Configurations (profile options, flex fields)
Extensions (new pages, new apps)
Disconnected Spreadsheets

Detailed design documents for all of above

Be prepared for some unknown customizations

21

Custom code change quagmire

Oracles R12 Upgrade: Most code upgraded
seamlessly, but
Custom Code Requiring Changes during :

Forms: ~10% of forms and libraries needed touching

Reports:
p
~1% of reports
p
needed touching
g
C code: ~20% of C code needed touching
Java code: ~1% of overall Java code needed
touching
g
JSPs: ~50% of JSPs needed touching
AutoConfig Configuration Customizations
Development
p
Tools: compilers,
p
, Forms/Reports
p
Builder 10.1.2, JDev10.1.3

Source:RayLin CustomerServiceSupportManager:OracleEBusinessSuite
Release12Upgrade
l
d

22

More on Customizations
Look in aaplcust.txt for customizations
Part of Oracle application library
Located in $AAPL_TOP/admin directory

Other options:

CEMLI Services tool Oracle subscription service

Custom scripts
Panaya acquired by Infosys in Feb., 2015
Ringmaster

Customization
C t i ti
strategy:
t t
Identify / Assess (R12 Upgrade Considerations by
Product Doc. 889733.1)
Retire as much as possible
Upgrade what you can
Re-implement what is left (only what you need)

23

Customization Strategy
http://searchoracle.techtarget.com/tip/Workingwith-custom-code-in-E-Business-Suite-upgrades
Minimize EBS custom code
phase out obsolete
analyze concurrent requests
Migrate only what's
what s necessary
take a new copy from new
release and reintroduce the
modifications
main
i iinterface
t f
may nott have
h
been greatly modified but
test additional lookups or
validations or extra data
t
transformations
f
ti
that
th t were
added
Forms involve tricky custom

code
start with fresh menu from

Oracle & make changes

24

Proper Materials - Hardware

Hardware, Software, and Network

Space for Test

Test, Dev
Dev, Training Environments
Cloning skills
Scale-able instance strategy
Ad
Adequate
t high
hi h speed
d storage
t
/ recovery capabilities
biliti
Shared Project Folder or Space
Ability for Oracle Support Access if Necessary (ODC
or Net meeting)
Adequate network bandwidth / throughput
Remote access via secure VPN

25

Proper Materials Hardware (cont.)

Definition of Current State of Production
All components of the tech stack

Browser Version
Database
App server
Discoverer
Self Service Framework
Approvals Manager
Desktop OS
Version off ADI
Version on tools

Pay attention to certification for all tech stack

elements
http://blogs.oracle.com/stevenChan/resource/certifications.html

Certifications tab on My Oracle Support

26

Recruit Team for 11i to R12

Management / Executive Sponsor
Project Manager

Technical Lead

Business
Analyst Fin.
Apps

Business
Analyst SC &
Other

Trainer

DBA / Sys.
Admin

Developer /
Analyst

Business
B
i
Process
Owners

Super Users

H l D
Help
Desk
k/N
Network
t
kS
Supportt

End Users / Testers

27

Recruit Team for 12.0/12.1 to 12.2

Management / Executive Sponsor
Project Manager
DBA / Sys.
Admin

Technical Lead

Developer /
Analyst

Super Users

Business
B
i
Analyst Fin.
Apps

Business
B
i
Analyst SC &
Other

Business
B
i
Process
Owners

Trainer

H l D
Help
Desk
k/N
Network
t
kS
Supportt

End Users / Testers

28

Organize Two Critical Documents

Master Checklist Build a Master list for the
upgrade and list every step.
TIP: Download Maintenance Wizard to a
spreadsheet. Capture timings for pre, during,
and post patching.
LIST and Assign EVERYTHING.

Master Impact List Complete full listing of all

potential changes that should require investigation
or retesting
Drives new features use and all testing
Applies to standard Oracle features and Customer
Customercreated impacts

29

ExampleofMasterImpactList

30

Some Master Impact List Items

Some Examples:
3rd Partyy Check Printing
g System
y
may
y need to be
retested or replaced with XML / BI Publisher
Custom Form may need to have customization
reapplied to standard Oracle form
Account Generator changes might get overwritten, and
it may be necessary to reapply changes
New Report available as standard functionality
functionality, we may
want to review as a potential business solution
Standard Interface may have new parameters, may need
to resubmit for recurring submission (scheduling)

31

Analyze and Plan Iterative Method

Analyze, Plan, Estimate,

Repeat
UseasaTooltoBuildyourProject
Plan

32

Upgrade Process Flow

Startthe
process

Atleast3iterationsbeforeGoLive
l
i
i
b f
i

Evaluatenew
release

Upgrade
?

No

Make
adjustments

Stayput

No

Yes
Installnew
release

Performinitial
pg
p
upgradepass

Test/make
j
adjustments

Performtest
movetoProd.

Test

Acceptable

Yes

Go
Live

Yes

Ready?

FinalTesting

Schedulecut
overdate

No
Makefinal
adjustments

33

R12 Upgrade High Level Time Line

34

The Process Go Live & beyond

Cutover / War Room
Post Cutover Support (DON
(DONT
T test in
Production)
Update and File Library of Test Cases and
Scripts for future use
Keep updated and available all Training
information (how
(how-to
toss, FAQ
FAQss, tests)
Archive:
Master Impact List
Materials for next upgrade
Redevelopment timings, etc

35

Execute Dedicated Testing

Process
Have a library of Test Cases
Detailed test scripts
Include and use cases from past 11i Implementation
or upgrades
Be prepared to add some test cases for new features
or functionality
Modify test cases to reflect new or changed
functionality
Make sure your test cases have specifics about test
data and expected results
Check them back in to the library for next time
More testers = more familiarity with application prior
to go-live > less productivity loss

Track every item and assign accountability

36

Experience Have a leader & Bring

back the vets
There is no substitute for experience
Veteran users will p
pick up
p on anomalies more easily
y
Experienced testers know what they are looking for
and what constitutes a material issue

In the 11i to R12 upgrade, the leader will need to

understand
d t d th
the F
Functional
ti
l concerns as wellll as th
the
Technical issues.
Must be able to communicate with the Functional and
Technical resources
Will need to communicate effectively with
management

The 11i to R12 upgrade is a much more substantial

project and will require a greater change
management focus

37

Upgrade Planning

Upgrade Process flow

Key planning components

Upgrade Process Flow

Startthe
process

Criticalstrategyand
planning stage occurs
planningstageoccurs
here

Evaluatenew
release

Upgrade
?

No

Make
adjustments

Stayput

No

Yes
Installnew
release

Performinitial
pg
p
upgradepass

Test/make
j
adjustments

Performtest
movetoProd.

Test

Acceptable

Yes

Go
Live

Yes

Ready?

FinalTesting

Schedulecut
overdate

No
Makefinal
adjustments

39

Upgrade Planning
Planning process needs to be
comprehensive and inclusive
of Business alignment and
technical aspects

Areas to evaluate include:

Upgrade extent
Business alignment
Hardware / platform / network
capacity
Human resource availability >
who and when
Training capacity and tools
Application
pp
support
pp
Testing strategy and experience
Oracle product strategy
Project planning & management
capacity

40

pg
g
Lessons learned when Upgrading
from 11i to R12

User interface & navigation changes effect everyone

Lots of Functional changes to acclimate to

Why 11i to R12 is not your standard upgrade

User Interface overhaul will

change to look and feel of the
applications for everyone
Certain modules had
significant modifications and
enhancements to features and
functionality
General Ledger
Accounts Payable /
y
Payables
Accounts Receivable
Procurement services
generally the modules with
the most users
Reporting tools have been
impacted

42

R12 Lessons learned

Finance / GL
Sub ledger Accounting (SLA) for Operating Unit
flexibility
EBusiness tax setups for each financial module
have been removed and are now centralized.
Multi-Org Access Control (MOAC) - Provides role
based access to Operating Units. It can be confusing
and dangerous to set up due to access to multiple
operating units
Check out the critical reports early - Trial
balances, sub ledger accounting, etc. are different
with the XML /PDF output. Many reports no longer
exist New setups are needed in Sub Ledger
exist.
Accounting (Open balance definitions) and some new
templates

43

R12 Lessons learned

Accounts Payable
Invoice workbench and Invoice Processing.
Processing New
look and feel for the workbench.
iPayment functionality now included and affects
vendor consolidation for AP
AP, CE
CE, and Advanced AR
iSupplier portal integration had been rough when
product was first released. Has been cleaned up, but
test thoroughly
thoroughly.
Significant patching requirements early in release
Information expansion (TCA arch.) led to long
upgrade steps and blown table extensions

44

R12 Lessons learned

Oracle Business Intelligence Enterprise
Edition
C
Confirm
fi
OBIEE environment
i
t technical
t h i l
requirements for Web Server, Portal, Oracle Internet
Directory (OID), OS

Web ADI
Lost functionality/issues: Desk Top ADI > WEB ADI
When moving from Desktop ADI to Web ADI, you lose
the ability to create financial statements in ADI
Will need to learn / use Report Manager

Discoverer
Due to changes in underlying data model, many
discoverer reports will need to be fixed
fixed. Check out
EBS Data Model Comparison Report (MOS Note
1290886.1)

45

A Word or Two about AP

Most problematic module
Redesign
R d i h
has lled
d tto d
data
t corruption
ti iin almost
l
t
every upgrade
Good news
MOS has scripts that can fix data issues
Preventative Tool: Oracle Payables 11i Accounting
Health Check ID 416699
416699.1
1
Download SQL script package and run it
Flags various issues that will cause a problem and
generates SRs
SR s.
Resulting scripts from MOS must be run to clean up
data

46

Other R12 functionality to consider

Significant functionality
improvements to SC
SC, PO
PO,
and HCM
Good info in MOS:

Procurement
Procurement
Application
s
Technology

Financials
& Projects

Supply
Chain

E-Business
Suite
12.1
Customer
&
Customer
&
Master
Data
Master
Managemen
Data
t
Manageme
g
nt

H
Human
Capital

806593.1 R12.1 Info

Center
269.1 - Upgrade Advisor:
E-Business Suite (EBS)
Upgrade from 11
11.5.10.2
5 10 2
to 12.1.3
740966.1 Advisor
Webcasts
804373.1 R12.1 Value
Proposition documents

47

R12.2.x Whats so different and

what are the concerns

On-line patching = Holy Grail for DBAs

DBAs will need retraining
Hardware considerations
Development standards
Where the risk is

A few words about R12.2

Available as of Open World, 2013

Represents
p
the HOLY GRAIL of Patching
g minimal
downtime (middle tier re-boot only)
Makes use of Edition-Based Redefinition (EBR) feature of
the 11g
g Database
Had been delayed for more than 2 years for extensive
testing due to potential risk
Beta testers consisted primarily of Oracle partners and
integrators so the initial testing did not necessarily hold up
to full use environments
The future ability to avoid outages is critically important to
24 hour shops (i.e. world-wide operations and 3 shift
manufacturers) who cant accommodate down-time.

49

R12.2 System requirements

1

Cutover

Two complete file systems are

always present
Run Edition - Used by the running
Application
Patch Edition Either:

P
Prepare

Prepare

Cutover

Currently being patched

or
Waiting for the next patching cycle

The two files systems are rotated

g
between Run and Patch during
every patch cycle

Source:KevinHudson OnlinePatchingwithOracleEBusinessSuite12.2

50

R12.2 Online Patching Resource

Considerations
Database
SYSTEM tablespace requires double its current space
allocation
25GB increase to 50GB

SEED tablespace requires double its current space

allocation
5GB increases to 10GB

File System
2 file systems require double the space of 1 file system

Database Objects and code must follow a new set of

standards
St
Standards
d d mustt b
be ffollowed
ll
d tto successfully
f ll patch
t h
objects Online

Review customizations for Online Patching

standards
Database check report ( ADZDDBCC.sql))
Scans the data dictionary for violating objects and code

File System check report (gscc.pl)

Source:KevinHudson OnlinePatchingwithOracleEBusinessSuite12.2
51

R12.2 Adoption planning

Understand your risk profile
Conservative or bleeding edge
Higher risk on this due to technical implications

Consider the support extensions (slides 9 11)

12.2 increases technical complexity
p
y
DBA will need to re-learn how to patch
New development standards
If you are coming from 11i, youre
you re taking a double hit!

Consider the hardware requirements if making

changes
MOS ability to support effectively is lagging
Not many DBAs with R12.2 project experience

52

R12.1.3 v. R12.2 Risk

Considerations
Risk area
Riskarea

R12.1.3

R12.2
X

Applicationmaturityandstability
Functional:learning/participationrequired

Functional:testingsupport

Developer:significantcoderemediation

DBA: upgrade skillsoverhaul

DBA:upgrade
skills overhaul

Externalapplicationsupportexperience

Increasedhardwarerequirements

possible

=Riskcovered/moderated
X=Riskexists

53

Information sources

12.1.3
12.2
Miscellaneous
About O2 Works
Contact information

For More Information

My Oracle Support (Metalink)
OTN R12 upgrade forum
http://forums.oracle.com/forums/forum.jspa?forumID=39
5&s tart
tart=0
0

Online Help (New Features Section)

Reference Manuals
Blogs: Steven Chan, Oracle:
http://blogs.oracle.com/stevenChan/
User Groups / Conferences

55

More Information on R12.1.3

Upgrade Advisor: E-Business Suite (EBS)
Upgrade from 11.5.10.2 to 12.1.3 (Doc ID 269.1)

56

More Information on R12.2

UpgradeAdvisor:EBusinessSuite(EBS)11i
Upgradeto12.2(DocID1614508.1)

57

Upgrading to the Cloud

Upgrading to the cloud

For EBS customers who run or host their own
platform (according to Oracle that is a Private
Cloud) and think they have an option to Upgrade
to the cloud think again!
It is a full-on, heavy duty re-implementation project
that will require that any customizations are
redeveloped as part of the Platform as a Service
(PaaS) offering in addition to the Software as a
Service (SaaS) component
Transitioning EBS to the cloud will reduce users
flexibility to customize their applications
Be certain that that the cloud footprint features and
functionality
f
ti
lit will
ill serve allll off your application
li ti needs.
d
Dont be fooled by the manic push to get everyone
to think the Cloud is now. It is still years away.

59

About O2Works
O2Works

is one of the leading E-Business Suite

services providers offering the most experienced teams of
functional and technical consultants in the industry. Our
hands-on resources average 18+ years of experience
f
focused
d exclusively
l i l on implementing,
i l
ti
upgrading,
di
i t
integrating,
ti
and extending Oracle's E-Business Suite. Stop by and talk to
us about our large portfolio of successful projects.

R12Presentations,WhitePapers,andother
informationsharedonlineat:
www.o2works.com/knowledgeworks

Presentation Available
O2Works Knowledge Base:
www o2works com
www.o2works.com

A Q ti ?
AnyQuestions?

Th k
Thankyou!
!

ArtDowd
ConsultingDirector
O2WorksLLC
OracleApplicationsConsulting
Dallas
Dallas Chicago
Chicago Denver
2147252828
adowd@o2works.com
Web:www.o2works.com

61