Debunking Upgrade Strategies

Using Accelerators for Re-implementing EBS R12

OVOAUG 10-22-2010

2

Introductions

Michael Wahl

Director, E-Business Suite Practice

mwahl@terillium.com847.371.1930

3

• Regional Oracle Platinum Partner

– E-Business Suite, JD Edwards

– OBIEE and BI Applications

– Application Integration Architecture

– Edge Products

– CRM OnDemand

– Agile

– Primarvera

– Implementations & Upgrades

– Managed Services

– Application Development & Integration

• Award Winning

– 2010 Central Region Partner of the Year

– Oracle Platinum & Accelerator Partner

– 2009, 2008, 2007, 2005: Titan Award Winner

– 2006: #1 Oracle Reseller in North America

Terillium

4

Upgrade Business Drivers

Upgrade Approaches

When to Upgrade?

When to Re-implement?

Accelerators

When to Use Accelerators?

Case Study

Agenda

5

Upgrade Business Drivers

Upgrade Approaches

When to Upgrade?

When to Re-implement?

Accelerators

When to Use Accelerators?

Case Study

Agenda

6

Upgrade Business Drivers

• Need to stay current and supported

• Ability to leverage improvements in the underlying technology� BI Publisher

� Personalization

� Business Event System

� SOA Integrated Gateway

• Opportunity to reduce cost of ownership or cost to support� Reduce or replace customizations

� Change support model to lower costs (outsource / in-source)

� Increase user self-sufficiency

� Restructure support agreement, relicense to save costs

• Minimize Upgrade Expense

• Opportunity to introduce process improvements

� Implement new functionality within existing module foot print

� Expand module foot print

� Improve upon existing processes, optimize processes

• Chance to receive training

• Opportunity to become more self-sufficient

� BI Publisher

� BI Applications

• Minimize Upgrade Expense

� Internal & External Labor

� Software

IT Perspective Business Perspective

7

Upgrade Business Drivers

Upgrade Approaches

When to Upgrade?

When to Re-implement?

Accelerators

When to Use Accelerators?

Case Study

Agenda

8

Upgrade Approaches

• Automated upgrade process

• Converts existing structures around MOAC, SOB, COA

• Moves over setups automatically

• Converts data automatically

• Requires certain pre-upgrade and post-upgrade steps

• Preserves personalizations, security

• Requires customizations to be migrated

• DBA intensive exercise

• Typically requires multiple iterations to perfect or tune the process

• Requires system downtime for length of upgrade during cutover

• Re-implementation of setups

• Allows for changes to existing structures around MOAC, SOB, COA

• Requires setups to be performed

• Requires data to be converted

• Requires personalizations to be re-performed

• Requires security to be re-created

• Requires customizations to be migrated

• Functionally intensive exercise requiring end user involvement

• Minimal system downtime during cutover

Technical Upgrade Re-implementation

9

Upgrade Business Drivers

Upgrade Approaches

When to Upgrade?

When to Re-implement?

Accelerators

When to Use Accelerators?

Case Study

Agenda

10

R12 Global Architecture

1. Ledger and Ledger Sets

2. Multi-Org Access Control

3. Sub Ledger Accounting

4. Tax Engine

5. Intercompany

6. Bank Model

BankModel

Tax Tax Engine

InterCompany

General Ledger General Ledger General Ledger General Ledger General Ledger General Ledger General Ledger General Ledger General Ledger General Ledger General Ledger General Ledger General Ledger General Ledger General Ledger General Ledger

Sub Ledger Accounting (SLA) Sub Ledger Accounting (SLA) DrDrDrDrDrDrDrDr CrCrCrCrCrCrCrCr

ProjectsProjects

PurchasingPurchasing PayablesPayables

Multi-OrgAccessControlMulti-OrgAccessControl InventoryInventory ReceivablesReceivables

WIPWIP

LedgersLedgers

ERROR: stackunderflow

OFFENDING COMMAND: ~

STACK: