Click here to load reader
Upload
doandieu
View
212
Download
0
Embed Size (px)
Citation preview
© Hexaware Technologies. All rights reserved. www.hexaware.com
Best Upgrade Practices for AdoptingOracle E-Business suite - R12.1.3
Whitepaper
Published on: January 2014 | Author: Ravindra Kulkarni | Email Address: [email protected]
WhitepaperBest upgrade practices for adopting Oracle E-Business suite to R12.1.3
Table of Contents
1. Introduction
2. Why Upgrade?
3. The Upgrade Phases
4. Oracle Upgrade Best Practices
4.1. Pre Upgrade Best Practices
4.2. Post Upgrade Best Practices
5. Conclusion
2© Hexaware Technologies. All rights reserved. www.hexaware.com
03
03
03
04
04
05
05
Introduction
This white paper describes major upgrade areas to consider in determining whether an upgrade is appropriate for your Organization. It also
offers practical advice from Oracle support, consulting and development Organization on how doing an R12 upgrade. This white paper tells
you “things you need to do” before and after R12 upgrade project.
Why Upgrade?
Business owners have realized that their key enterprise applications must be upgraded regularly to benefit from many compelling reasons
such as:
● Unlocking new mature functionalities to keep your organization well positioned to meet business objectives.
● Staying current with the highest and latest levels of the product support. The extended support to R11.5.10.2 is ending on December,
2014.
● Enables you with best performance and usage of enhanced features like functional capabilities, technical infrastructure etc. which
enables you to increase application’s efficiency for your business.
[Refer Oracle Applications Documentation Resources Release 12 Note 394692.1] For more detailed information of finance and procurement
upgrade impacts, see Oracle Financials and Oracle Procurement Functional Upgrade Guide: Release 11i to Release 12.
An upgrade is similar to implementation; however upgrade can be more efficient than implementation as it leverages earlier implementation
efforts and business processes. Also, the upgrade can be executed within the existing change management system by your organization.
Below graphic presents the standard upgrade phases at a high level:
3
Whitepaper
© Hexaware Technologies. All rights reserved. www.hexaware.com
Best upgrade practices for adopting Oracle E-Business suite to R12.1.3
The Upgrade Phases
Ap
plicati
on
Vers
ion
11.5
.10.2
Curr
ent E
nvironm
ent
Stu
dy
Syste
m R
evie
w
Data
base U
pgra
de
Applic
ation U
pgra
de
Applic
ation P
atc
hin
g
Function T
esting
User
Tra
inin
g
UA
T
Pro
duction M
igra
tion
and G
o L
ive
Post P
roduction S
upport
Pla
nnin
g
Planning &
InitiationAnalysis Upgrade UAT Go Live
PostProduction
Support
4
Whitepaper
© Hexaware Technologies. All rights reserved. www.hexaware.com
Best upgrade practices for adopting Oracle E-Business suite to R12.1.3
This section describes R12 best practices for pre and post upgrade and testing activities.
Pre Upgrade Best Practices
Oracle Upgrade Best Practices
● Evaluation: Before initiating upgrade, it is important to thoroughly evaluate the new release to confirm the capabilities and enhance-
ments which will provide expected benefits and justified returns from the upgrade to the business. Information on release notes can
help in determining what exactly will change in the newly upgraded system along with the new features. [Refer Oracle note 461705.1
which provide a consolidated view of information you may need for an upgrade project]
● Planning: A successful upgrade begins with a crystal clear definition of project scope and detailed project plan. Though R12 has new
significant changes in data model and functionality specifically in financial modules, defining realistic schedule for upgrade project
considering implemented modules in R11, integration with other third party systems and respective development, expected new
modules to be introduced in R12, end user training and their confidence to go with R12, any change in terms of hardware or operating
system or merging multiple instances into one single global instance should be considered while planning the project scope and
timelines. You may separate such activities as a separate project than upgrade to minimize the risk. Though standard upgrade moves
you from R11 to R12 with same setups and functionality with additional and default functionality about tax, sub-ledger accounting, still
you have option to implement new functionality at desired time.
● Data validation approach: A minimal upgrade requires some functional setups which come by default like Trading Community
Architecture (TCA) for customer/ supplier data, payments and E-business tax. If you have inconsistencies within R11 setups, then you
should resolve them before R12 upgrade. You can run “Accounting Setup Manager Pre-upgrade Diagnostics” report to view R11 setup
for financial modules, through you can identify setups that are potentially problematic. Also, results of standard reports from each
module would also help to know successful upgrade – the reports have to run before and after upgrade as well.
● Technical Iterations: Executing technical upgrade is critical initial phase. A best approach would suggest at least three iterations. The
first iteration may be taken up to identify hurdles/ issues throughout upgrade (including functional/ technical configurations and testing
activities). The second would be taken up to minimize issues which are identified within first iteration and further UAT activities. The
third iteration would be taken up to identify exact down time (including all end to end activities) and help for Production upgrade.
Capturing regular backups throughout the upgrade process would be enabling you to restore the environment to a specific point rather
than re-initiating the entire process.
● Fall-back planning: Approaching towards the production stage upgrade, fallback planning is most essential and important. You can
have multiple modes of backup which are capable enough to restore immediately and enable end users to work on. One round of
resting on restoring the environment is recommended.
● Pre-requisites: You can start the upgrade post completing month end activities, clearing all interfaces and posting all journals to
General Ledger, closing all sub-ledger/ ledger periods. All such activities (including DBA, functional and technical) have to be sequen-
tially listed down with priority, navigation, activity owner, specific notes (if any) and respective estimated time against the activity. Many
of such activities can be done in parallel mode to minimize upgrade time. Closure of major service requests prior to upgrade is highly
required. Allocation to appropriate owners to activities and involvement of respective business users to their activities is most important
for this project. Running of key reports before and after upgrade is one of the important activities in terms of data verification and recon-
ciliation.
● Cook-Book concept: Cook-Book includes end to end activities along with various phases which are sequentially listed down. Each
activity should have respective owner, activity duration, activity sequence, activity mode (parallel/ standalone). Building and maintain-
ing ‘Cook-Book’ is a proven concept which requires experience to minimize cutover time, avoid last minute surprises and a very
successful upgrade project.
5
Whitepaper
© Hexaware Technologies. All rights reserved. www.hexaware.com
Best upgrade practices for adopting Oracle E-Business suite to R12.1.3
A detailed, well planned and coordinated production upgrade is important in successful upgrade and minimizing risk factors.
Below is high level pictorial view of Cook-Book:
Post Upgrade Best Practices
Conclusion
● End User Training: Organize key user training and make them familiar to R12 environment, new features and functionalities. Prepare
training documentation and update user guide to reflect changes in both functionality and business processes.
At cutover, the final “Production” upgrade pass is completed.
● Smoke Testing: Formulate robust testing strategy with required testing rounds, team involvement with overall performing to see an
end to end testing of all business scenarios. In addition to CRP testing to validate setups, ensure that you do full functional testing with
business users. Testing should be guided by detailed test scripts in advance along with enough time to complete end to end scenarios.
● Data Reconciliation: Running Oracle’s standard reporting from each module (based on each and every operating unit implemented)
and mapping the outputs with R11 instance reports is the standard approach of data reconciliation. The majority of reports are from
financial modules which need to run and validate.
● Hand Hold Period: Keep your key project members in place at least for successful closure of the first financial period within the new
R12 environment to increase end user confidence level. Consider doing a mock period closing at least 5 days before the actual close.
The team can monitor the R12 environment, logging the service requests (if required). Re-examine user roles and responsibilities due
to change in business processes introduced in R12. For example, global process owners reviewed R12 process changes with
business users and redefined roles and responsibilities accordingly.
Oracle R12 has been adopted by many enterprises across the globe and is well accepted as the most reliable, stable from the family of
Oracle EBS suite. Thus, it is crucial for existing 11i users or may be older versions to consider future business process alignment, scalabil-
ity and lowest TCO while mapping to Oracle R12 and eventually Fusion Application.
Oracle is committed to supporting customer investments in technology platforms for applications as well as certified infrastructure
products (hardware, operating systems, databases and middleware). Details can be accessed at the following location:
http://www.oracle.com/us/support/lifetime-support/index.html
6
Whitepaper
© Hexaware Technologies. All rights reserved. www.hexaware.com
Best upgrade practices for adopting Oracle E-Business suite to R12.1.3
Hexaware is an Oracle Platinum Partner, offering comprehensive services across the entire value chain of Oracle E-Business suite. With our
right blend of industry domain expertise, Oracle Solution Experts, Tools & Accelerators and best practices, we enable you with the right
solution required for maximizing returns from your Oracle investments. Our right-fit approach delivers key solution milestones that help
organizations to stay ahead of the business curve. As a premier Oracle Service Provider, our services range right from Consulting, Imple-
mentations & Rollouts, Integration's, Upgrades & Migration, Application Management & Support, Custom Developments &
Enhancements, Database Support and Testing.
About Hexaware and Oracle Practice
Address
1095 Cranbury South River Road, Suite 10, Jamesburg, NJ 08831. Main: 609-409-6950 | Fax: 609-409-6910
Safe HarborCertain statements on this whitepaper concerning our future growth prospects are forward-looking statements, which involve a number of risks, and uncertainties that could cause actual results to differ materially from those in such forward-looking statements. The risks and uncertainties relating to these statements include, but are not limited to, risks and uncertainties regarding fluctuations in earnings, our ability to manage growth, intense competition in IT services including those factors which may affect our cost advantage, wage increases in India, our ability to attract and retain highly skilled professionals, time and cost overruns on fixed price, fixed-time frame contracts, client concentration, restrictions on immigration, our ability to manage our international operations, reduced demand for technology in our key focus areas, disruptions in telecommunication networks, our ability to successfully complete and integrate potential acquisitions, liability for damages on our service contracts, the success of the companies in which Hexaware has made strategic investments, withdrawal of governmental fiscal incentives, political instability, legal restrictions on raising capital or acquiring companies outside India, and unauthorized use of our intellectual property and general economic conditions affecting our industry.
To learn more, visit http://www.hexaware.com/oracle.htm