Upgrades to the Oracle E-Business Suite (EBS) are a regular and painful occurrence. The impact of these upgrades varies between the patch releases, which can normally be absorbed by the existing IT and user teams, to the totally disruptive major releases such as release 12, which have a major impact across the business. For most organisations these upgrades have too frequent and too great an impact on the business. Business analysts and end users must be reassigned for extended periods from their valuable and regular roles to plan, test and implement these upgrades. View this presentation from our Webinar session where Jonathan Pearson, Solution Consultant, explores the difference between success and failure during your Oracle upgrade. You can also learn more about these “Top 5 Benefits of Original Software’s Oracle EBS Accelerator Pack”: 1. Eliminate risk - your application supports your critical business processes 2. Reduce critical defects found after go-live to zero 3. Get back to business sooner – hit your project deadline 4. Reduce dependence on Oracle EBS users 5. Effortlessly create a detailed audit trail for compliance purposes See more at: http://www.origsoft.com/solutions/oracle-testing/

1. Jonathan Pearson
Original Software
Delivering your Oracle EBS R12 Upgrade with 100% Confidence
Delivering Quality Through Innovation

2. © 2013 Original Software
Oracle EBS is…
Critical & Integral – runs the business
Very complicated – a mystery to most
Often customized
Technically challenging to test

3. © 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

4. © 2013 Original Software
Situation Assessment
End of life coming for 11i

5. © 2013 Original Software
The Upgrade Process

6. © 2013 Original Software
Stakeholders
DBA’sBusiness
Leadership
Programmers
Power
Users
Helpdesk
Training
Project
Manager
Business
Analyst

7. © 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

8. © 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.

9. © 2013 Original Software
Overlooked Impact

10. © 2013 Original Software
Biggest Challenges
Confirmed top 3 Challenges
Inadequate
validation processes
Poor communication
and collaboration
Limited access to needed
business resources

11. © 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

12. © 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?

13. © 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?

14. © 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?

15. © 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

16. © 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

17. © 2013 Original Software
Typical work impact and
cost of effort

18. © 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

19. © 2013 Original Software
Collaboration – What?
Project plans
Resources
Timescales
Tasks
Progress
Coverage
Re-use
Knowledge
Data
Environments
Availability
Audit
Traceability
Customizations
Complexity
Process

20. © 2013 Original Software
Foundations for Collaboration

21. © 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

22. © 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

23. © 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

24. © 2013 Original Software
Plan, Track, Manage

25. © 2013 Original Software
Execute, Capture, Document

26. © 2013 Original Software
Execute, Capture, Document

27. © 2013 Original Software
Document

28. © 2013 Original Software
Automated Testing

29. © 2013 Original Software
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 (9days)
Remote Activity (1.5days)
ViaSatActivity (36days)
Legend
Customer Activity (36 Days)
Legend

30. © 2013 Original Software
Projected Savings in Labor

31. © 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?

32. © 2013 Original Software
The difference between
success and failure…

33. Q & A
http://www.origsoft.com/OracleEBS
Download our business case for Oracle EBS
upgrades and patches.
In the meantime……..
Thank You