You are on page 1of 2

UPGRADE Vs.

REIMPLEMENT
Ten Reasons Why the Game Has Changed

Oracle E-Business Suite (EBS) 11i customers who pair eprentise Transformation software with Oracle’s Upgrade
software change the game and redefine the R12 goal. Here are definitions with conceptual graphics, followed by ten
reasons to Upgrade.

REIMPLEMENT UPGRADE
Customer implementation of Oracle EBS R12 instance, configured Transformation to upgradable 11i instance that reflects current and
with prior 11i plus new business setups, coupled with selection, future business, plus standard Oracle upgrade to R12. Potential
extract, and transformation of 11i data, which is loaded via public post-upgrade R12 transformation for objects without an 11i
interfaces and custom scripts into R12. precursor.
Reimplementation = Customer Implementation 11i
Upgrade = eprentise Transformation
• Multiple instances, one active 11i
+ Data Migration • Historical data spans both, History
11i
History
+ Oracle Upgrade
Restricted
History • Business process changes • Instance you always wished for, AND • Single Global Instance
but different formats Restricted
Access
Restricted
Access • Business structure changes, incl. OUs it’s upgradable. • Lowest future cost
Access
• COA changes • Use it as long as you want, until you structure
ss
11i d acce • • Highest business value
11i ly restricte Clean data, compliant with standards need the valued-added R12 features.
11i
Not read-on 11i Data •
tance –
Not 11i Data Shared service centers
• Read-Only
Not
Upgradable
Upgradable “sun set” ins • History
11i Data
• Read-Only • Instance consolidation
Upgradable Cre ate • Read-Only
• History
• History
Customer Extract 11i
Customer Extract 11i Data History Customer Load 11i eprentise 11i Oracle 11i 
11i Data & Transform
Customer Extract 11i Data History Customer Load
11iCustomer
Data History
R12 Obsolete
11i R12
11i Data & Transform [partial?]
11i Data History Load Obsolete Transformation Upgradable R12 Upgrade
Selected 11i Data
& Transform [partial?] 11i Data History Via Public API Setups
Obsolete
11i Data Selected 11i Data 11i Data History
Selected 11i Data [partial?] & Interface Setups
Setups
Tables

load
h istory
efore
Implement New R12 Fresh nce b R12 Data No data loss 11i Data No data loss R12 Data
E-Business Suite Implementation emp ty insta • Seeded
11i Data
11i Data Transformed Transformed &
R12 11i Data
Clone • Configured R12 formats
• History [partial]
Upgrade enables R12 Features
R12 Data Custom SQL & • Centralized accounting architecture
• Seeded DB Utilities • Global tax engine
• Configured • New ledger and ledger
set architecture
• Multi-org access control features
Path from multiple EBS 11i instances to a single Path from one or more EBS 11i instances to a • Centralized banking model
global R12 instance plus multiple legacy instances single global R12 instance • Advanced global intercompany
system

EPRENTISE SOFTWARE
Includes REORGANIZATION, CONSOLIDATION, DATA QUALITY, and FLEXFIELD
software products.

© 2009 eprentise, LLC. All rights reserved. Page 1


UPGRADE Vs. REIMPLEMENT
Ten Reasons Why the Game Has Changed

Ten Reasons to Upgrade:


1. Reduced schedule and technical risk. UPGRADE relies on 6. Avoid custom data conversion. With REIMPLEMENTATION,
commercial EBS conversion software from Oracle and you are on your own to convert and migrate your 11i data
eprentise, rather than REIMPLEMENTATION’S technical into R12. Unless you load everything, compromises lead
analysts and data conversion programmers. to complexity, delays, and continuing expense.

2. You can change your Chart of Accounts. UPGRADE uses 7. True single instance for past and future data. With
FLEXFIELD to change one or more COA’s segments and UPGRADE the result is a single R12 instance, whereas with
values so you can adopt a single global COA. REIMPLEMENTATION you will have R12 plus the legacy 11i
instance in read-only mode as a reference to history and
3. You test new EBS setups in familiar 11i. UPGRADE uses the prior business structures.
EPRENTISE REORGANIZATION to change any fundamental EBS
setup you have postponed until reimplementation. The 8. Avoid multiple custom conversions and legacy instances.
setups Oracle says are “not easily changed” include: Legal For multi-national organizations with multiple EBS 11i
Entities, Sets Of Books (Ledgers), Operating Units, Key instances, REIMPLEMENTATION requires data migrations from
Flexfields, Calendar, Costing Methods, Inventory each legacy 11i instance into the single R12 instance. You
Organizations, and Asset Categories. will also retain all legacy 11i read-only instances.

4. Transaction data will be changed, too. UPGRADE uses 9. Upgrade offers the most direct path and shortest time to
EPRENTISE SOFTWARE to convert all 11i data to reflect all COA single instance R12 business value. The most powerful
and fundamental setup changes. UPGRADE advantage for multi-nationals is consolidation to a
single global instance with standard business processes
5. Your history matters. UPGRADE uses Oracle Upgrade to and all history data prior to the Oracle Upgrade to R12.
convert all 11i data to R12. Business users are happier
with all EBS history and current data in a single R12 10. Upgrades cost less. EBS customers pay for Oracle Upgrade
instance, rather than distributed between legacy and software even if they select REIMPLEMENTATION. Why leave
active instances. money on the table and pay extra to do it yourself?

If you use EBS 11i, we invite you to visit www.eprentise.com


to learn how to use EPRENTISE SOFTWARE to deploy R12 faster,
better, and cheaper.

© 2009 eprentise, LLC. All rights reserved. Page 2

You might also like