Rapid Upgrade
Transcript of Rapid Upgrade
Implementations for Oracle
1
Upgrade with
Rapid e-Suite
to
Oracle Release 12
Implementations for Oracle
2
What are your Options ?
Technical Upgrade • Preparation and testing time 5-9 months [or more]
• Lots of patches with pre and post requisite patches
• Lots of documentation to read and understand
• 200,000+ scripts to run • Not all these scripts will work in your environment
• Average of 10-30 TAR’s to resolve issues
• Dedicated user resources will be required to assist with data migration issues • TCA architecture will prevent duplicate parties that exist in 11i from being loaded
• Functional resources will be needed to e-business tax adjustments
• Many of the CEMLI’s will break, some will never work again
• During the project it will be necessary to FREEZE code and configuration changes
• Downtime on the production server will be at least 5 days for the AVG multi-national
Impacts • Business freeze for 9 months or more
• Downtime on the production server for 5 days or more
• Disruption to the business for 9+ months
• Like for like – 11i look and feel in R12 • Multi-org can be setup after the upgrade as can some other R12 functionality
• SLA will require setting up a new operating unit
Implementations for Oracle
3
What are your Options ?
Re-Implementation • A complete rebuild, reimplement and data migration project
• Leave behind the old ways and start afresh
Impacts • Lengthy process
• Significant disruption to the business
• No downtime on the production server needed
• Costly to the business
• Not a favorite option to many
Implementations for Oracle
4
What are your Options ?
Automated Re-Implementation • Extract – Transform – Load
• Configurations
• Master Data
• History Transaction Data
• Open Transactions
• Extract allows
• One operating unit
• Groups of operating units
• All operating units
• Transform allows
• Merge and split of operating units
• Change the COA
• Make any other configuration changes as needed
Impacts • No Downtime - Existing business runs on 11i while R12 instance is prepared
• Delta changes to all data types moved by the ETL process until live
• Flexible
• Faster
• Minimum impact to business
Only from
Rapid e-Suite
Implementations for Oracle
5
A standard ETL concept But for configurations, master data and history transaction data
How Does It Work ?
EBS
R11
Reverse
Extract Transform Load
Configurator
Build
EBS
R12
Implementations for Oracle
6
REVERSE CONFIGURATOR BUILD
RAPID e-Suite Intelligent Engine
Data Cartridges
Oracle
11i
Oracle
R12
Custom
Others
Application Server Cartridges
Oracle
11i
Oracle
R12
Custom
Others
Custom
Others
Client Cartridges
Oracle
11i
Oracle
R12
Rapid E-Suite – “The Tools”
Knowledge Modules
Implementations for Oracle
7
How do we do it ?
The Tools
Implementations for Oracle
8
The Service
EXTRACT [uses REVERSE] For each operating unit there are 3 extractions
• Configurations
• Master data
• Closed transactions and Open transactions
Reverse is
Fast ……..
Data is extracted in a BR100
format enabling full
documentation almost
immediately
Implementations for Oracle
9
The Service
TRANSFORM [uses CONFIGURATOR]
Configurations
• The configurations are analyzed, mapped to R12 formats, cleaned, have e-business tax
configurations added, ledger structures are confirmed,
• Transformation rules are applied if any exist
• Changes to the COA, item coding structures, instance level standards changes, etc
Review the
configurations – drill
down on the Oracle
responsibility
Follow the Oracle style menus
Displays the data in BR100 format –
real-time and changeable
Implementations for Oracle
10
The Service
TRANSFORM [uses CONFIGURATOR]
Configurations
• The configurations are analyzed, mapped to R12 formats, cleaned, have e-business tax
configurations added, ledger structures are confirmed,
• Transformation rules are applied if any exist
• Changes to the COA, item coding structures, instance level standards changes, etc
Or select a printer icon
at ANY level and get a
BR100 document
immediately of the
configurations
Implementations for Oracle
11
The Service
TRANSFORM [uses CONFIGURATOR]
Master Data
• The Master data is mapped to R12 formats
• Transformation rules are applied if any exist
• Changes to the COA, item coding structures, instance level standards changes,
etc
The same is done for
master data
Implementations for Oracle
12
The Service
TRANSFORM [uses CONFIGURATOR]
Transactions [including all history]
• The Transaction data is mapped to R12 formats
• Transformation rules are applied if any exist
• Changes to the COA, item coding structures, instance level standards changes,
etc
And transaction history
Implementations for Oracle
13
The Service
LOAD [uses BUILD] Only Oracle supplied standard products are used.
There is no custom code
There is no direct writes to the database of any kind
All data loaded is done via
• Open interfaces
• API’s
• FORMS or HTML
The package is
provided by
CONFIGURATOR- this
contains all the
dependency sequence
and the steps to
execute
Click START and the
appropriate technology
is launched as needed
Implementations for Oracle
14
Panaya simulates the upcoming Oracle EBS
Upgrade
Map Your Customizations & Usage
What will break
How to fix
What to test
Implementations for Oracle
15
SYSTEM OVERVIEW Various statistics
Implementations for Oracle
16
Sample code correction
Know how to fix, right down to
the code-line level, even before
you build your upgraded
environment
Anywhere that Panaya advises
you to adjust the code, we also
create unit test tasks for all
entry level objects that are
using the impacted code
The tool highlights the error
All the objects that use the
above code – are listed
Implementations for Oracle
17
SAMPLE UNIT TEST
Test Concurrent Report
Ready to Test • Having the testing plan
integrated into the
corrections plan means
that testing can be
coordinated.
• Knowing when a test can
be performed is
possible, since Panaya
knows if the underlying
corrections have been
performed or not.
Implementations for Oracle
18
SAMPLE UNIT TEST
Review Underlying Corrections
Fix First, Then Test •The traditional methodology would be to test,
then fix.
•With Panaya, the corrections are all identified
in the analysis, giving your team the
opportunity to fix first, then once all the
corrections are done, the tester will know that
the test is “ready to test”
Implementations for Oracle
19
UPGRADE METHODOLOGIES
Mapping
Customizations
& Usage Integration
Testing
User
Acceptance
Testing
Fix Unit
Testing -
CRP1
Patch
Research Initial
Testing Go-Live User
Acceptance
Testing - UAT Technical
Upgrade
Rapid e-
Suite
Unit
Testing
Go-Live
More Cycles
Integration
Testing - CRP2
Mnth 1 Mnth 2 Mnth 3
Mnth 4
Mnth 5
Mnth 6
Mnth 7
Mnth 8
Mnth 9
Mnth 10
Mnth 11
Mnth 12
Extract
Transfor
m
OU1
and
OU 2
Load
OU1
And
OU2
CRP1 Transfor
m
All other
OU’s
Load all
other
OU’s
User
Acceptance
Testing -
UAT
Extract
Delta’s
CEMLI’S
CEMLI’S
Implementations for Oracle
20
What you get
• A new R12 instance
• on any operating system
• on any hardware configuration
• Each
• selected operating unit,
• group of operating units
• or all operating units
• in your new R12 instance
• All your
• configurations,
• master data
• transaction data
• for the selected operating units
Implementations for Oracle
21
What you get
• Changes to
• the COA
• or any other configurations
• Split / merge operating units
• from the same instance
• from different instances
• into one or more R12 instances
• Standardize
• your instance level configurations across the company
• Create business rules to end date no longer used instance configurations
• Your business process by bringing standard configurations to all businesses
Implementations for Oracle
22
What you get
• Your CEMLI’s
• Will be converted as identified by the Panaya tool
• Some CEMLI’s may not be able to be upgraded
• Some CEMLI’s may be replaced by R12 functionality
• New R12 URL
• Switch the the new R12 instance at any time using the new URL
• The 11i URL is immediately available as a fall back position
• Your old 11i system
• Keep it for as long as you require
• Downgrade the hardware to a test type server
• Mothball the 11i system at any time
• What do you save
• No downtime on your production server
• A project that takes 50% or less of the time for a technical upgrade
• Ability to continue making business changes to the instance
• Minimal disruption to the business
Implementations for Oracle
23
• No downtime on the production server
• No need to freeze business for 9-18 months • make configurations changes
• Add new inventory organizations
• Add new operating units
• Continue your business as normal
• Upgrade • one operating unit at a time,
• groups of operating units
• Or all operating units
• do it as the business allows
• Make configuration changes • Such as changing the COA
• SLA
• Multi Org
• Takes around 50% or less time than a technical upgrade
Benefits of the Rapid e-Suite solution
Implementations for Oracle
24
Q U E S T I O N S
A N S W E R S
Video on the
next slide – click
to start