Delivering your Oracle EBS R12 Upgrade with 100% Confidence

Jonathan Pearson
Original Software

Delivering Quality Through Innovation

 Oracle EBS is…

Critical & Integral – runs the business

Very complicated – a mystery to most
Often customized
Technically challenging to test

© 2013 Original Software

 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

© 2013 Original Software

 Situation Assessment

End of life coming for 11i

© 2013 Original Software

The Upgrade Process

© 2013 Original Software

 Stakeholders

Power Training
Users
Business
Analyst
Helpdesk

Programmers

Business Project DBA’s

Leadership Manager

© 2013 Original Software

 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

© 2013 Original Software

 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.

© 2013 Original Software

Overlooked Impact

© 2013 Original Software

 Biggest Challenges

Confirmed top 3 Challenges

Inadequate
validation processes

Poor communication
and collaboration

Limited access to needed

business resources

© 2013 Original Software

 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

© 2013 Original Software

 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?

© 2013 Original Software

 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?

© 2013 Original Software

 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?

© 2013 Original Software

 Quick Poll

How well documented are your business

processes?

 Poorly
 Some documentation, likely out of date
 Customizations documented, little else
 Well documented

© 2013 Original Software

 Once upgrade process starts…

All ongoing initiatives stop

until upgrade is done
 Stable baseline in 11i required
 Often a moratorium on business
driven enhancements

© 2013 Original Software

Typical work impact and
cost of effort

© 2013 Original Software

 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

© 2013 Original Software

 Collaboration – What?

Project plans Data

Resources Environments
Timescales Availability
Tasks Audit
Progress Traceability
Coverage Customizations
Re-use Complexity
Knowledge Process

© 2013 Original Software

Foundations for Collaboration

© 2013 Original Software

 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

© 2013 Original Software

 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

© 2013 Original Software

 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

© 2013 Original Software

Plan, Track, Manage

© 2013 Original Software

Execute, Capture, Document

© 2013 Original Software

Execute, Capture, Document

© 2013 Original Software

Document

© 2013 Original Software

Automated Testing

© 2013 Original Software

 Sample Implementation
Timeline

y
r

r
Ma

Ma
Ap
4 11 18 25 1 8 15 22 29 6
3/4
Product Installation and Setup Mon (AM)
for 5 days
3/11
Qualify Design Review & Implementation Mon (PM)
for 1.5 days Legend
Legend
3/13
Manual Testing Workshop
Wed (AM)
- Train the trainer
for 1.5 days
ViaSat Activity
Customer (36 days)
Activity (36 Days)
3/18
EBS Team Builds Plan and Manual Test Assets Mon (AM) Implementation/Training Activity (9 days)
for 10 days

EBS Project Manual Testing Checkpoint

3/21
Thu (AM)
Remote Activity (1.5 days)
for 0.5 day
4/1
Automated Testing Workshop
Mon (PM)
- Fundamentals
for 3 days
4/4
EBS Team Builds Automated Test Assets Thu (PM)
for 11 days
4/11
EBS Project Automation Checkpoint Thu (PM)
for 0.5 day
4/22
Automated Testing Workshop
Mon (PM)
- Advanced
for 3 days
4/25
EBS Team Builds Advanced Automated Test
Thu (PM)
Assets
for 10 days
5/9
EBS Project Review Thu (PM)
for 0.5 day

© 2013 Original Software

Projected Savings in Labor

© 2013 Original Software

 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?

© 2013 Original Software

The difference between
success and failure…

© 2013 Original Software

 Q&A
In the meantime……..

Download our business case for Oracle EBS

upgrades and patches.
http://www.origsoft.com/OracleEBS

Thank You