Professional Documents
Culture Documents
of a Successful Oracle
E-Business R12 Upgrade
Written by
WHITE PAPER
Contents
Abstract........................................................................................................................................................................... 3
Introduction ..................................................................................................................................................................... 4
The 10 Commandments of a Successful Oracle E-Business R12 Upgrade .................................................................. 5
Commandment #1: Thou Shalt Understand the Key Metrics of Change .................................................................... 5
Commandment #2: Thou Shalt Implement Planning and Process Control ................................................................. 5
Commandment #3: Thou Shalt Secure the Tides of Change ..................................................................................... 5
Commandment #4: Thou Shalt Thoughtfully Plan Process Workflow ........................................................................ 6
Commandment #5: Thou Shalt Leverage Approvals as Check-and-Balance Controls .............................................. 6
Commandment #6: Thou Shalt Maintain Project Sanity via Proper Versioning .......................................................... 6
Commandment #7: Thou Shalt Explore Potential Issues Proactively ......................................................................... 6
Commandment #8: Thou Shalt Check your Work with Auditing and Reporting ......................................................... 7
Commandment #9: Thou Shalt Seek to Automate Manual Processes ....................................................................... 7
Commandment #10: Thou Shalt Be a Great Communicator ...................................................................................... 8
Conclusion ...................................................................................................................................................................... 9
About the Authors ......................................................................................................................................................... 10
Abstract
Complex enterprise resource planning (ERP) systems like Oracle E-Business Suite are critical to many organizations,
serving diverse business needs and supporting both functional-level and business-level decision-making. Therefore,
it is essential to effectively manage change to those systems, especially change as major as upgrading to Oracle EBusiness Suite R12. This white paper provides 10 key best practices to help your organization effectively manage
change to your ERP systems, with particular attention to upgrading to R12.
Introduction
Enterprise Resource Planning (ERP) systems like Oracle E-Business Suite are large, complex applications that serve
diverse business needs. In fact, these systems typically span finance and accounting, HR, manufacturing, sales and
marketing essentially the entire business, end-to-end. This breadth of use gives rise to the value of ERP in
supporting functional- and business-level decision-making. Users share data with functional peers and users in other
departments to make business decisions every day, such as: How many pieces of our product can we produce next
week? Do we have enough of the right staff to do the work?
Because large numbers of users varying in skill, geography and job function often depend on these systems and their
data, ERP systems present a certain amount of risk as well. In particular, system change, whether from a migration or
an upgrade like Oracle R12, is inevitable and can lead to downtime, which puts the productivity of all the diverse
users who depend on ERP systems at risk.
The complexity and risk inherent to ERP systems demands a solid change management strategy. How will your
organization manage something like a major system upgrade? How will you upgrade the system comprehensively
and with minimal downtime to the business? The following commandments are critical to any successful ERP
implementation and especially so for those users upgrading to Oracle E-Business Suite R12.
especially for large patches, the risk of applying a patch blindly is typically greater. Simply identifying the modified
objects leaves a gap between what files were modified and what should be tested. Users may reference many
changed objects either directly or indirectly through the application. Good reporting will not only identify what objects
are impacted, but also how the objects affect users. For example, mapping an impacted form to the responsibility and
navigation path for a user helps guide testing of the patch.
Oracle best practices provide methods for customizing objects without fear of a patch destroying these
customizations. New custom objects are often created from objects provided by Oracle. Customizing in this fashion
prevents the customization from being destroyed by a patch, but other objects referenced by the custom object may
change and break the custom object. Although these best practices are relatively easy to adopt, they are often not
followed, and failure to adopt the best practices means each patch has the potential to destroy the customization. It is
important to know whether a changed object was customized or used to create a custom object. Patch impact
analysis executed in advance of the patch even in the development environment can bring rewards. The
development team can prepare resources to modify impacted customizations prior to the patch being applied, thus
minimizing the risk to the stability of the development environment and not delaying other development or testing
projects.
Auditing the change process is concerned with the who, what, where, when and why. For example, when a
security policy is changed, auditing tells us who changed the security policy. When a patch is applied,
auditing tells us which patch was applied, when it was applied, who applied it, who approved the patch, who
tested it, which files were modified, etc. Auditing will also tell when a customized object has been changed,
or when the original object used to create the custom object was changed.
Auditing change itself is all about issue tracking. Before a patch is ever applied, theres a reason the patch
was applied either a bug was found or a new patch set was released. The issues should be tracked from
inception to postmortem for proper auditing of change. Auditing data can be used to report the current,
future and past state of an environment; activity that has been performed affecting the state; and the
difference between two or more environments.
To that end, reporting capabilities are critical for assessing the state of each environment. Whats the difference
between production, test and development? What will a patch do to a system before it is applied? How do testers
know what to test when a patch is applied? What area of the business could be put at risk and to what extent? Proper
change reporting brings this key information to light for the stakeholders involved.
For another example, there is a balance between effective use of resources and security. Because of security
concerns, only a few people may be allowed to access the production servers. Restricting access is good practice,
but can also place those few people on the critical path of the change process. Automation can eliminate the need to
distribute passwords by allowing key contributors to be identified for tasks or phases of work and provisioned
accordingly, rather than using a common password shared by the group. By storing that password in a centralized
location, not everyone needs to know the password. Instead, users can log into a chosen change management
application and complete tasks as they have been provisioned.
Automation can also help ensure that customizations to E-Business Suite applications are not destroyed by a patch.
Even when you follow Oracles best practice for patching, its still necessary to monitor each patchs activity to identify
when the source object for a custom object is modified. When Oracle-provided objects are customized, its even more
critical to monitor what a patch is doing to avoid losing the customizations that a user has made to an Oracledelivered object.
Conclusion
ERP gives organizations tremendous support in functional- and business-level decision-making. A diverse set of
users depend on these applications to complete their day-to-day work. Complex upgrades like R12 can require a host
of cumbersome changes to these business-critical applications. Therefore, it is imperative that IT admins manage this
change in a comprehensive, proactive way. Successful Oracle E-Business R12 upgrades and other ERP
implementations will obey the commandments of change management described here.
To learn more about managing the R12 upgrade or other change in your ERP systems, visit the Quest Software
community dedicated to the topic.
10
Trademarks
Quest, Quest Software, the Quest Software logo, AccessManager, ActiveRoles, Aelita, Akonix, AppAssure,
Benchmark Factory, Big Brother, BridgeAccess, BridgeAutoEscalate, BridgeSearch, BridgeTrak, BusinessInsight,
ChangeAuditor, ChangeManager, Defender, DeployDirector, Desktop Authority, DirectoryAnalyzer,
DirectoryTroubleshooter, DS Analyzer, DS Expert, Foglight, GPOADmin, Help Desk Authority, Imceda,
IntelliProfile, InTrust, Invirtus, iToken, I/Watch, JClass, Jint, JProbe, LeccoTech, LiteSpeed, LiveReorg, LogADmin,
MessageStats, Monosphere, MultSess, NBSpool, NetBase, NetControl, Npulse, NetPro, PassGo, PerformaSure,
Point,Click,Done!, PowerGUI, Quest Central, Quest vToolkit, Quest vWorkSpace, ReportADmin, RestoreADmin,
ScriptLogic, Security Lifecycle Map, SelfServiceADmin, SharePlex, Sitraka, SmartAlarm, Spotlight, SQL Navigator,
SQL Watch, SQLab, Stat, StealthCollect, Storage Horizon, Tag and Follow, Toad, T.O.A.D., Toad World,
vAutomator, vControl, vConverter, vFoglight, vOptimizer, vRanger, Vintela, Virtual DBA, VizionCore, Vizioncore
vAutomation Suite, Vizioncore vBackup, Vizioncore vEssentials, Vizioncore vMigrator, Vizioncore vReplicator,
WebDefender, Webthority, Xaffire, and XRT are trademarks and registered trademarks of Quest Software, Inc in
the United States of America and other countries. Other trademarks and registered trademarks used in this guide
are property of their respective owners.
11
WHITE PAPER
If you are located outside North America, you can find your
sales@quest.com
World Headquarters
5 Polaris Way
USA
5 Polaris Way, Aliso Viejo, CA 92656 | PHONE 800.306.9329 | WEB www.quest.com | EMAIL sales@quest.com
If you are located outside North America, you can find local office information on our Web site.
2011 Quest Software, Inc.
ALL RIGHTS RESERVED.
Quest, Quest Software, the Quest Software logo are registered trademarks of Quest Software, Inc. in the U.S.A. and/or other countries. All other trademarks and registered trademarks are property of their respective
owners. WPA-OracleR12-10Command-US-KS