CSS

Overview
prepared for:

NCOAUG

Agenda
1 Introductions
2 R12 Upgrade Considerations

Introduction : R12 Upgrade

R12 Release

Focus on enabling the Global Business Model

Major Functional Release

18 New Modules with GA

2443 Enhancements

Fundamental Design Changes in Financials

11.5.10 Premier Support Ends
November 2010

EBS
12

EBS 12.1

11.5.10 Extended Support Ends

November 2013

EBS 12.x

R12: Common Recurring Themes

Multi Org Access Control : User profiles can be defined for multiple organizations enabling
access, inquiry and reporting on information across the enterprise

Ledgers : Replaces the set of books concept of 11i. Ledger sets can be used to manage multiple
ledgers which share common accounting characteristics

Sub Ledger Accounting : Engine enabled for all Subledger systems allowing clients to assign
accounting rules that drive transactions to the general ledger and standardize corporate wide

TCA : Trading Community Architecture allows E-Business Suite users to share supplier, customer,
bank and operation information across the enterprise
11i Responsibilities

R12 Responsibilities

User

User

R12: Not Strictly a Technical

Upgrade
Traditional Approaches to an E-Business Suite release upgrade

Technology : Technical Process with little design change or functional

implementation

Full Functional : Functional implementation of new features or the inclusion

of scope for new modules

At a minimum, the R12 Upgrade is a combination of both so plan for training in
either a Scripted Upgrade or Implementation model

The R12 Upgrade is best considered a business initiative

R12 Upgrade Approaches

Traditional Methods of Delivery

Scripted Upgrade: Prepare upgrade environment based on a clone, apply pre/post patches
and migrate data. Modules are configured based on existing setups and data. Retrofit
customizations, integrations and reports

Implementation: Proceed with a fresh installation and configure Oracle E-Business Suite to meet
current business requirements leveraging the latest features and functions. Convert transaction
history using APIs, retrofit customizations, integrations and reports

Less Complex

Scripted Upgrade

More Complex

Re-Implementation

The question of business requirements that must be met may lead to an answer that is blended in the middle

Upgrade
Typical Upgrade Candidate

E-Business Suite currently is meeting business needs As

Deploy

Configured

Single Instance of E-Business Suite supporting business operations

Minimal Customizations to E-Business Software were required to

Train
R12.1.x

support business requirements

Data is generally clean and free from duplicates and other

11.5.x

data integrity issues

OATM

Archiving strategies are in place and only necessary Active

history is included in E-Business Suite production data

Budget is tight and the upgrade is considered a necessity for

11g

compliance but not viewed as a strategic requirement

10g

Re-Implementation
Typical Re-Implementation Candidate

Business users seek improved functionality across the board

Current business is run on multiple instances of E-Business Suite

Business Processes are decentralized and consolidations

Deploy
Train

support parent level financial reporting

E-Business Software was heavily customized to meet business

DEV

requirements

Data cleanliness is suspect

Archiving policy does not segregate Active vs Inactive

PROD

R12.1.x

TEST

Migrate Data

history. Data in PROD instance is therefore large

Budget can be approved for functional implementation

efforts based on business benefit and the upgrade is deemed
strategic

DEV
R12.1.x
PROD

11.5.x

TEST

Process Considerations

Workshops and Questionnaires with the Business Users

R12 Features Overview for relevant modules and especially with

Financials

Questionnaires can provide visibility to the Upgrade vs ReImplement decision and will give business users a proactive role
in the decision and subsequent project

Leverage your reference resources

Oracle Corporation : Health checks, Product Roadmaps,

Benchmarks

Partner Network : Expertise with E-Business Suite and

Technology Foundation product delivery

Online Content i.e. : R12 Upgrade Center, My Support

Enable informed decisions for the Upgrade and future project roadmap

Process Considerations
Customization and the Quality of your Systems documentation

Important pre-work that can be done without external

professional services help

Report, Customization and Integration Inventories

Rationalize enhancements with the latest release

Determine the impact on an upgrade project

Improve the accuracy of the project budget estimate

Enable informed decisions for the Upgrade and future project roadmap

Process Considerations

Size Up Your Data

Is your data clean?

Is your data volume large?

What is your archive strategy?

Previous benchmarks for migrating or upgrading data?

Enable informed decisions for the Upgrade and future project roadmap

Process Considerations
Let the Discovery Drive the Plan
Upgrade
Are current business processes generally considered optimal

Yes

Are there any major configuration changes that are anticipated as part of the
upgrade such as change in the COA, use of DFFs, etc

Yes

Are there multiple instances targeted for consolidation into the R12 Post
Upgrade footprint

No

Have there been or are there plans for any major business organization or
structural changes making reconfiguration a requirement?

No

Is the current 11i environment multi org?

Yes

New modules planned in the scope of the project?

Is the upgrade considered a technology upgrade or a strategic functional
upgrade
Have there been major business organizational changes such as acquisitions or
divestures that drive the need for system change

Implement

Yes
Technical only
Yes

Technical Considerations
Upgrade
Is your system heavily customized

No

Do you have confidence in the integrity of your data

Do you have an archiving strategy which dictates reducing data size prior to
the upgrade

Implement
No

Yes

Do you have significant old history which makes your data size large

Yes

Can your business tolerate down time for migrating data

No

Do you plan on changing Master Data, DFFs, LOV values during the upgrade

No

Technology Considerations

Upgrade Testing

Preferably on a distinct test server

Comparable to production configuration to assess I/O performance

Clone of production environment

Study and tune

Post upgrade processing time can be significant even with multi-thread

processing

Data

Changes in schema and tablespace migrating from 11i to R12 result in a

net increase in space required

Note: 399362.1 on Oracle Support can provide links to some useful

metrics for planning

Technology Considerations

Connect the Fundamental Requirements

Database release level compliance for R12

OS compliance

Hardware configuration benchmarks

Implementation Activities in Any

Scenario

Training
Net change is large for Financial Suite
Many functional changes from setups to functionality
User Interface
Application Navigation has changed based on improved UI
Dont underestimate training
Testing
Major release change drives full formal system and user acceptance
testing
Applications and RICE components
Ledger Sets enable enhanced reporting capability
Security Redesign
New security model including concepts such as data access sets

Training Considerations
Invest in Training

Preparation

Build on discovery

Develop scripts which consider R12 functional improvements

Execution

Expect Business Subject Matter Expert participation as if the project is

a traditional implementation

UPK as an Enabler

R12 Content is available from Oracle

Cost Savings Considerations

Accelerators

Data

Pre Built Conversion and Integration APIs

Planning & Pre-Work

Design work done with the internal staff

Data Cleansers assist with cleaning up data

Archive

Re-design and requirements updates

Prepare AIM documentation for net change updates even if external consultants
will provide the final updates as part of the project

Offshore Delivery

Hybrid models
Conversions
Retrofitting code

Timelines

Heavily driven by several factors

Mandate of the project as a technical initiative only or an implementation of

newly available functionality
Number of E-Business Suite modules in use
Upgrade vs Re-Implement decision
Resource availability

Upgrade Type

Characteristic

Time to Deliver

Upgrade in Place

Technology project that upgrades to R12 with the intention of

maintaining the status quo. No barriers or complexity known to
prevent the scripted upgrade

Rapid Implementation

Upgrade and Implement

Scripted upgrade which delivers an R12 solution via scripted

Moderate

Re-Implement In Place

Driven by customization or the intention to change critical data

such as the chart of accounts. This upgrade approach focus on
data integrity and enabling business process that are currently
supported

Moderate

Re-Implement Full
Functional

Instance consolidation, system reconfiguration and business

process re-design require this approach. This approach may be
used for consolidating business processes and rolling out to
divisions in phase

Longest

Questions?

Thank You.