A Roadmap To R12 - PPT

A Roadmap to R12:
Does Anyone Know the Way?

The Reimplement vs. Upgrade Decision
Helene Abrams
CEO
eprentise
habrams@eprentise.com
Session 8913
www.eprentise.com
Agenda
 Introduction
 E-Business Suite Trends and Drivers
 Definitions and Decision Factors
 Upgrade
 Reimplement
 Factors that Contribute to The Total Cost of Ownership (TCO) of Oracle E-
Business Suite
 Upgrade Considerations and Getting to R12
 Reducing the Total Cost of Ownership of EBS and Leveraging R12
 ( Software + Upgrade ) vs. Reimplement
 Scenario Analysis
 10 Reasons to Choose Upgrade Instead of Reimplement
www.eprentise.com 2
Copyright © 2011 eprentise. All rights reserved.
Introduction
 eprentise
 Established in 2006
 Transformation software for E-Business Suite
 Helene Abrams, CEO
 Who we serve
 Large and middle-market US-based and international customers from both
private and public sectors
 What we do
 Provide software that assists companies looking to upgrade to R12,
particularly companies that need to re-structure their business to change
configurations, consolidate instances, separate data, or address other
significant organizational changes they have experienced since originally
implementing EBS.
www.eprentise.com 3
Oracle E-Business Suite Customer Trends
 Create a single, global chart of accounts
 Reorganize entities, sets of books, and operating units.
 Consolidate multiple EBS instances
 Resolve duplicates and standardize
data.
 Eliminate customizations
 Add new modules
or functionality
and … Plan or Execute

Transition From 11i to R12
www.eprentise.com 4
Drivers
 Establish common business processes and standards
 Produce standard reports
 Operate a shared service center or a
centralized data center
 Rationalize suppliers,
customers, products
 Reduce Total Cost of
Ownership (TCO) of EBS
 Exploit new R12 functionality
 Establish a single source
of truth
www.eprentise.com 5
A Fork in the Road - Definitions
Upgrade Path Reimplementation Path
 Oracle supplied scripts ‘convert’  Configure a new instance
data from current Oracle
 Write scripts to extract data from
Applications release to R12.
existing instance, transform it to
 Supported tools, utilities, and new configuration parameters,
documentation used write scripts to load into new R12
 Entire data and application instance.
available after upgrade
 Generally bring over a year’s
 Clear, straightforward, proven worth of data and maintain “old”
method instance for history.
Has been the preferred path to new EBS

Many experts now advising this path
releases
www.eprentise.com 6
Why Experts are Recommending
Reimplementation
 Elimination of customizations
 Difficult to change underlying structures
 Chart of Accounts, calendar, currency
 Business Group, Ledger, Legal Entity, OU structure
 Desire to consolidate multiple EBS instances
 Early instability of Oracle upgrade process
www.eprentise.com 7
Reimplementation – Not Always a Good Choice
 Long project duration
 Generally 1-2 years
 Resource Intensive
 Technical resources to write extract scripts, transformation
code, and load scripts
 Technical resources to unit test the code
 Functional resources to make all new configuration
decisions, understand the new functionality of R12
www.eprentise.com 8
Calculating the Cost of a Reimplementation
To Implement Cost based on Assumptions
or $800/day
Reimplementation Reimplement
Tasks (person days)
3 Business Cycles (purchase-to-pay, order-to-cash,
hire-to-retire),
Configuration of New
Example
One month,2 functional resources per business
Instance 60 cycle
Create Extract Scripts 240 2 technical resources, 2 months per business cycle
for a single Create Transformation
Code 180 3 technical resources, 1 month per business cycle
instance Create Load Scripts

Unit Test Scripts/Code
240
180
2 technical resources, 2 months per business cycle
3 technical resources, 1 month per business cycle
Resolve Exceptions 90 3 technical resources, .5 month per business cycle
Implementation One month,2 functional resources per business
Conference Room Pilot I 60 cycle
Changes for Conference One month,.5 functional resource per business
Room Pilot I 30 cycle
One month, 2 functional resources per business
Integration Testing 60 cycle
Implementation One month, 2 functional resources per business
Conference Room Pilot II 60 cycle
Changes for Conference One month,.5 functional resource per business
Room Pilot II 30 cycle
One month, 3 functional resources per business
UAT 180 cycle
Production Go Live Cutover 45 3 resources 15 days
Total Person Days 1455 $1,164,000.00 Duration approximately 14 months
www.eprentise.com 9
Cost of an Upgrade
Total Tech
Duration & Func Staff Staff
Phase 3 - Technical Upgrade to R12
(work Needed for Functional Technical Functional Technical Resource
days) Phase Days Days Cost Cost Cost
Technical Upgrade Instance:

11.5.10 to R12 20 5 30 60 24,000 48,000 72,000
Subtotal - Resource Costs Phase 3 72,000
Example for a single instance
www.eprentise.com 10
Decision Factors – 11i to R12
 Reimplement – what do you do with:
 Existing business history data in the 11i instance(s)?
 Legacy instance(s) after R12 go-live?
 Decision Factors
 Each has widely accepted goals for the result in R12
 11i environment may already align with the R12 target
 11i factor may be upgraded easily
 Some conditions cannot be changed with the Oracle upgrade software by
itself
 Non-issues if you implement R12 – because you are not changing the 11i
environment
 Ideas from Oracle’s R12: Upgrade vs. Reimplement (Financials)
 Evaluate conditions, see what complicates achieving the target R12 goal
 Upgrading is better, if you can
New Route: Remodeling an 11i Instance
 Change Chart of Accounts
 Change Calendar, Currency
 Restructure Business Group, Sets of Books, Legal
Entities, Operating Units
 Consolidate Instances
Pros and Cons of the Two Approaches
Traditional Migration Approach Remodeling Approach
(Reimplementation) (software + Upgrade)
Pros Cons Pros Cons
Common No standard extract/transform Shorter project duration with Not widely understood
approach, often scripts. Very similar to a fewer resources translates among Oracle
recommended by custom development project to lower costs. Project can professionals. Customer
consulting requiring a more formal easily be completed in 3-8 needs strong sponsor.
organizations. development and testing months That means that
methodology including the savings of a single
documentation, error handling, instance are available
and development standards. sooner.
No need to More risk in extract, transform, Only testing that is required For consolidation,
upgrade Current and load (ETL) that will not be is functional testing. instances need to be at
11i to New R12 supported by Oracle. the same version/patch
due to straight level
data migration into
an R12 instance.
Pros and Cons, Continued
Traditional Migration Approach – Cons Remodeling Approach – Pros
Requires technical knowledge of all tables and usage in Repeatable results, reusable as requirements change. As
the E-Business Suite. requirements change, only need to add/change rules, a
step that is usually done by a functional user on a
specially designed user interface in the software In a very
short time.
APIs do not exist for all tables. There is a risk of All data integrity is maintained because the code is
compromising the data integrity by extracting and loading automatically generated.
data incorrectly. Oracle Support not available.
History is generally not converted. Generally a sunset All history is converted so there is no need to maintain a
instance is required for reporting, reconciliation, business sunset instance for reporting, reconciliation, etc. All the
intelligence, and audits. Every time the sunset instance is data is complete and consistent.
accessed, data must be transformed to align with the R12
instance.
Need to configure R12 instance No need to configure R12 instance
Scripts are written for the current state of the data. Any Full documentation of existing instance including
changes require re-writing of the scripts. comparison of instances
12-24 months duration 3-8 months duration
Upgrade Considerations: What Needs to Change?
 Fundamental Configuration  Number of COAs

Setups  Business Processes
 Legal Entity, Set of Books,  Data cleanliness and
Calendar, and Operating standards
Unit structures
 Customizations and
 Org Units structure enhancements
 Number of E-Business Suite  Obsolete data
Instances
 Business Intelligence
 Chart of Accounts Structure environment
(COA)
Reducing Costs
Location CCY Location Op Unit BalSeg BalSeg GPS Book BalSeg Bk Seg BalSeg GPN Book BalSeg Seg Bk
US 001
US USD Comerica NAm USD 002
Canada 005
CAD
Canada
and Complexity
USD Canada NAm CAD 006 025 GPS LKR 025
Sri Lanka AsiaPac LKR 025 027 027

LKR 001
USD Sri Lanka AsiaPac EUR 201 001 001 002 205 205
US SOB
Sri Lanka EUR 002 002 005
GBP Sri Lanka AsiaPac GBP 301 005 005 105 565 565
AUD 106 106
Sri Lanka AsiaPac AUD 401 105 105
SGD 103 GPS US 103
Singapore
USD Singapore AsiaPac SGD 023 107 107 027
GPN PHI 570 570
911 911 107
PHP Philippines AsiaPac PHP 027 912 912
Philippines
USD 913 913 912
GPN CHN 801 801
Sri Lanka 106 953 953 031
Maldives USD Maldives 105
Singapore 103 031 GPS CNY 031 913
GPN IND 802 802
CNY Philippines AsiaPac USD 107 029
China 029 GPS INR 029
USD Taiwan 911
China 912 911
030 GPS TWD 030 GPN TWN 803 803
INR India 913 030
India
USD
China AsiaPac CNY 031 022 GPS MOP 022 022 GPN MAC 545 545
TWD
Taiwan 028 GPS MYR 028
USD India AsiaPac INR 029 028 GPN MLS 804 804
Macau MOP Taiwan AsiaPac TWD 030 024 GPS BND 024 024 GPN BRU 505 505
Hong Kong HKD Macau AsiaPac MOP 022

006 CAN SOB 915 915
Malaysia MYR Hong Kong AsiaPac HKD 021 006 006
GPS CAD
955 955 025
Brunei BND Malaysia AsiaPac MYR 028 106
201 201 201 GPN SRL 585 585
GPS EUR
Brunei AsiaPac BND 024 952 952 301
201 401
GPS
UK Europe GBP 951 301 301 301
GPS GBP US
951 951 401
UK Europe EUR 952 US
401 401 SOB
GPS AUD
UK Europe USD 953 956 956 103
GPN SNG 575 575
023
GBP UK Europe SGD 954 023 023
GPS SGD
EUR 954 954 021 GPN HK 525 525
USD UK Europe CAD 955
SGD 021 021 953
GPS HKD
CAD UK Europe AUD 956 957 957 955
AUD 952
UK HKD UK Europe HKD 957 951
CHF 958 GPS CHF 958 956
DKK UK Europe CHF 958 954
JPY 959 GPS DKK 959 957 UK SOB 851 851
NOK UK Europe DKK 959 958
NZD 960 GPS JPY 960 959
SEK UK Europe JPY 960 960
961 GPS NOK 961 961
UK Europe NOK 961 962
962 GPS NZD 962 963
UK Europe NZD 962
963 GPS SEK 963
UK Europe SEK 963
Russia RUB GPN RUS RUS
DolEx US USD DOLEX US
DloEx Mexico MXN DOLEX MX DLX
DolEx Guatemala GTQ DOLEX GT
Eurofil EUR GPN EUR EUR
Muzo CZK GPN MZO MZO
Getting to R12: Remodeling + Oracle Upgrade
Getting to R12: Reimplementation + Migration
Reimplementation = Customer Implementation 11i
• Multiple instances, one active 11i
+ Data Migration • Historical data spans both, 11i
History
History
Restricted
History
but different formats Restricted
Access
Restricted
Access
Access
ccess
11i icted a
11i
11i
Not a d -on ly restr 11i Data
re
Not tance – 11i Data
set” ins 11i Data
Not
Upgradable • Read-Only
Upgradable “ s un • Read-Only
Upgradable Cre ate • History
• Read-Only
• History
• History
Customer Extract
Customer Extract 11i Data History Customer Load
11i Data & Transform
Customer Extract 11i Data History Customer Load
11iCustomer
Data History
R12
11i Data & Transform [partial?]
11i Data History Load
Selected 11i Data
& Transform 11i Data History Via Public API
11i Data Selected 11i Data [partial?]
[partial?] 11i Data History
Selected 11i Data & Interface
Tables
d
histo ry loa
Implement New R12 Fresh n ce before R12 Data
a
E-Business Suite Implementation mp ty inst • Seeded
R12 e
Clone • Configured
• History [partial]
R12 Data Custom SQL &

• Seeded DB Utilities
• Configured
Path from multiple EBS 11i instances to a single 11i

11i
Obsolete
11i
Obsolete
Setups
Obsolete
eprentise
Transformation
11i
Upgradable
Oracle 11i 
R12 Upgrade
R12
global R12 instance plus multiple legacy instances

Setups
Setups
No data loss 11i Data No data loss R12 Data

11i Data
11i Data Transformed Transformed &
11i Data
R12 formats
For comparison: Remodeling plus Upgrade
Example Consolidation Scenario with
Getting to R12: Different Versions of EBS
1. Change EBS 1’s COA so both instances have new
EBS 1
standard global COA.
COA w/ Obsolete
2. Change EBS 2’s calendar so both have global
COA 11.5.10 calendar.
3. Consolidate the two 11i instances. Capture the
1.A Change
EBS 1 business process benefits.
4. Upgrade to R12, one instance only. Capture the
COA COA w/ Global
Ledger, Ledger Set, and Subledger Accounting
COA 11.5.10 benefits.
2. EBS 1 Global
Consolidation Global COA and
EBS 2 calendar
11.5.10
COA w/non-std
calendar 3. R12
11.5.10
EBS 1 Global
Upgrade
1.B
EBS 2 R12
Reorganization COA w/ Global No Reimplementation.

calendar Retain All History.
11.5.10
 EBS 1
 EBS 2
11.5.10 R12
19
10 Reasons to Choose Upgrade
1. Reduced schedule and 7. True single instance for past
technical risk. and future data.
2. You can change your Chart of 8. Avoid multiple custom
Accounts. conversions and legacy
3. You test new EBS setups in instances.
familiar 11i.
9. Upgrade offers the most
4. Transaction data will be direct path and shortest time
changed, too. to single instance R12
5. Your history matters. business value.
6. Avoid custom data 10. Upgrades cost less.
conversion.
You Don’t Have to Reimplement
Reasons That Customers Used To Think That Condition Removed by
Reimplementing Was The Only Option Remodeling Approach
Correct or update prior 11i setups “that are not easily

changed.”
Multiple instances. 
Obsolete non-global COA.

Want global COA.
Multiple COAs and want a single one or fewer COAs. 
Multiple different business processes. Want to realize

benefits of standard global business processes.
Data is inconsistent or dirty.

Data administration standards have not been enforced .
Many customizations and enhancements. 
QUESTIONS?
Thank You!
Helene Abrams eprentise habrams@eprentise.com
- One World, One System, A Single Source of Truth -

A Roadmap To R12 - PPT

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

A Roadmap To R12 - PPT

Încărcat de

Drepturi de autor:

Formate disponibile

A Roadmap to R12:

Does Anyone Know the Way?

and … Plan or Execute

Has been the preferred path to new EBS

instance Create Load Scripts

Technical Upgrade Instance:

Subtotal - Resource Costs Phase 3 72,000

Example for a single instance

Pros Cons Pros Cons

Need to configure R12 instance No need to configure R12 instance

12-24 months duration 3-8 months duration

 Fundamental Configuration  Number of COAs

Sri Lanka AsiaPac LKR 025 027 027

Hong Kong HKD Macau AsiaPac MOP 022

Russia RUB GPN RUS RUS

DolEx US USD DOLEX US

DloEx Mexico MXN DOLEX MX DLX

DolEx Guatemala GTQ DOLEX GT

Eurofil EUR GPN EUR EUR

Muzo CZK GPN MZO MZO

R12 Data Custom SQL &

Path from multiple EBS 11i instances to a single 11i

global R12 instance plus multiple legacy instances

No data loss 11i Data No data loss R12 Data

For comparison: Remodeling plus Upgrade

Reorganization COA w/ Global No Reimplementation.

- One World, One System, A Single Source of Truth -

S-ar putea să vă placă și