Delivering your Oracle EBS R12 Upgrade with 100% Confidence

Jonathan Pearson Original Software

Delivering your Oracle EBS R12 Upgrade with 100% Confidence

Delivering Quality Through Innovation

© 2013 Original Software

Oracle EBS is…

Critical & Integral – runs the business

Very complicated – a mystery to most

Often customized

Technically challenging to test


Quick Poll

What is your companies current situation?

already upgraded to R12.1

plan to upgrade to R12.1

plan on deciding when to upgrade to R12.1

are discontinuing use of EBS

getting support for 11i via 3rd party


Situation Assessment

End of life coming for 11i


The Upgrade Process


Stakeholders

DBA’s Business

Leadership

Programmers

Power

Users

Helpdesk

Training

Project

Manager

Business

Analyst


Quick Poll

How many Power Users do you expect to involve in Testing & Validation?

Less than 10

10 to 30

31 to 50

50 to 70

Over 70


Upgrade Responsibilities

IT responsibility

Database Changes

Customization redevelopment

Business responsibility

Functional & Process changes

e.g. sub ledger accounting, centralized bank

transactions, multiple ledger capability, etc.


Overlooked Impact


Biggest Challenges

Confirmed top 3 Challenges

Inadequate validation processes

Poor communication and collaboration

Limited access to needed business resources


Original Software Solutions

Provide Structure & Best Practice Processes

Unified Collaboration Platform

Bring Technologists & Business

Tie Geographically Dispersed Teams Together

Capture EBS SME’s Knowledge Effectively

Processes (for training materials)

Test Cases (for validations)

Requirements (for customizations)

Collect, Manage, Execute, Track Validations

Capture Custom Test Cases & Processes

Provide Standard Test Cases


Benefits using Original Software

Ensure Success

Greater coverage, less risk

Increase Visibility

Shared problem, shared success

Minimize Impact

Start Quickly

Easy to use

Save Time, Money

During upgrade

On-going patches

Eliminate a CRP?


11i functionality is the basis for

validation after the upgrade

Business perspective

The upgrade is “ALL about TESTING and

VALIDATION”

You need to involve business to test – in a big way

Customizations add to complexity

Current 11i functionality defines requirements of

R12 testing

Is this formalized in any way?


Are you enabled to achieve success?

Are your current scenarios well

documented?

Do you know what constitutes goodness?

Is “Create an order” good enough

Explicit vs. Implicit definition of test cases

Are your business users easily

accessible?

They know what it should do

Are they able/willing/available to

document current functionality?


Quick Poll

How well documented are your business

processes?

Poorly

Some documentation, likely out of date

Customizations documented, little else

Well documented


Once upgrade process starts…

All ongoing initiatives stop

until upgrade is done

Stable baseline in 11i required

Often a moratorium on business

driven enhancements


Typical work impact and

cost of effort


Knowledge transfer is key

Transform “Tribal” Knowledge

into Formal

A myriad of islands of expertise

Systematic approach to filling in

all gaps

Distribute load to all involved

Track & manage progress & effort

It’s all about collaboration


Collaboration – What?

Project plans

Resources

Timescales

Tasks

Progress

Coverage

Re-use

Knowledge

Data

Environments

Availability

Audit

Traceability

Customizations

Complexity

Process


Foundations for Collaboration


Collaboration – How?

How to establish a Knowledge Base?

Collect What, How, and Why things are done in EBS

Establish a central document library or Database

Workflow & Process to “herd the cats”

Dashboards

Visibility

Time saving tools


Why do you need a

knowledge base?

Sheer volume

Prioritize

» Business critical vs. low impact

» High risk vs. low risk

Categorize

» Standard vs. Customizations

Various & Numerous people

involved

Different skills & areas of expertise


Original Software Solutions

Qualify – Test Planning & Management

TestDrive – Manual & Automated Testing

Oracle EBS Validation Package

Pre-defined Application Model & Process

» Layouts and Views

» Reports

» Documentation

Accelerator Test Packs

» Pre-loaded manual test cases

For Financial modules from TruTek

Accelerated implementation


Plan, Track, Manage


Execute, Capture, Document


Execute, Capture, Document


Document


Automated Testing


Sample Implementation

Timeline

Mar

Apr

May

3/4

Mon (AM)

for 5 days

3/11

Mon (PM)

for 1.5 days

3/13

Wed (AM)

for 1.5 days

3/18

Mon (AM)

for 10 days

3/21

Thu (AM)

for 0.5 day

4/1

Mon (PM)

for 3 days

4/4

Thu (PM)

for 11 days

4/11

Thu (PM)

for 0.5 day

4/22

Mon (PM)

for 3 days

4/25

Thu (PM)

for 10 days

5/9

Thu (PM)

for 0.5 day

EBS Project Automation Checkpoint

Automated Testing Workshop

- Advanced

EBS Team Builds Advanced Automated Test

Assets

EBS Project Review

EBS Team Builds Plan and Manual Test Assets

EBS Project Manual Testing Checkpoint

Automated Testing Workshop

- Fundamentals

EBS Team Builds Automated Test Assets

Product Installation and Setup

Qualify Design Review & Implementation

Manual Testing Workshop

- Train the trainer

4 11 18 25 1 8 15 22 29 6

Implementation/Training Activity (9 days)

Remote Activity (1.5 days)

ViaSat Activity (36 days)

Legend

Customer Activity (36 Days)

Legend


Projected Savings in Labor


Enable Success

Deploy flawlessly

Guarantee that the upgraded applications continue to meet

business requirements

Execute efficiently

Ensure the entire upgrade process is managed as productively

as possible

Deliver swiftly

Meet the end-of support deadlines

Lift moratorium on business enhancements

Minimise costs

Can be reduced by 25%

Eliminate a CRP?


The difference between

success and failure…

Q & A

http://www.origsoft.com/OracleEBS

Download our business case for Oracle EBS

upgrades and patches.

In the meantime……..

Thank You

