There is a lot of talk about R12 upgrade, especially from a DBA point of view and the technology stack. But, what does it mean functionally? Read along for tips to minimize upgrade downtime, proven tools of a successful R12 upgrade and other considerations.
Minimizing Upgrade Downtime:
Downtime is very crucial for an upgrade. It could make or break the success of upgrade depending on if the upgrade can be completed in available downtime. Here are a few tips to manage the downtime. Apart from standard pre-upgrade tasks like completing payment batches, processing depreciation/ posting mass additions in fixed assets and create accounting/transfer to GL, using following options as part of pre-upgrade steps can reduce downtime significantly.
GL Journal Entries Pre-upgrade program: It is an optional program which upgrades posted General Ledger journal entries before the planned downtime, leaving only un-posted journals and newly posted journals to upgrade during downtime.
Upgrade by request: Due to this, minimal data can be included in initial upgrade. A minimum of 6 months of data is mandatory and can be updated to specific requirements of the client. Any historical data can be processed after upgrade is complete thus enabling reduced upgrade downtime
Splitting the Upgrade: One more way to manage downtime is by splitting the database upgrade from application upgrade. By separating these two upgrades, downtime can be broken down into two smaller segments. This path also enables identification of issues with database upgrade separately from applications upgrade.
Upgrade Toolkit:
Following documents can help in tracking the upgrade steps and downtime over multiple iterations and note identified issue fixes.
Upgrade Cookbook – It is a document similar to upgrade assistant available for 11i. It was prepared from information on R12 upgrade user guide and further customized to the specific client requirements. It provides the step by step process followed for Release 12 upgrade and helps in tracking the time taken for the steps in various iterations, summary of patches applied, issues fixed etc and also includes the steps from installation to final user acceptance.
Data Verification Tracker – Apart from new functionality testing, verification of historical data accuracy is a very important part of upgrade testing and data verification tracker is an organized way to ensure it. This document contains pre-listed reports, queries and record counts which can be verified to ensure data validity. It also facilitates the tracking of data validation tasks
R12 Manuals and RCDs – The scope of this document is to highlight the new features of R12 and compare the existing functionality and features with EBS 11i. This is very helpful for training and change management
Issue Tracker – All the issues encountered during the upgrade (all iterations) are tracked. This document captures issue resolutions so the same can be incorporated in further iterations.
Conclusion
Apart from above mentioned tips and tools, change management is another aspect which is especially important for R12 upgrade. This is because of changes to UI and new functionalities introduced especially for financials. Enabling a few functionalities in R12 may also result in reducing the customizations. Talking about customization, migration of existing customizations may need additional attention especially related to payables due to change in architecture, table names etc
Are you planning an upgrade to R12? Please feel free to post a question.
References: Upgrade Guide: Release 11i to Release 12
