Best practices for OPM Migration from Release 11.5.10 to12.

An Oracle White Paper October 2009

OPM Migration from 11i to 12/12.1 Best Practices Guide

Page 1

INTRODUCTION............................................................................................................. 3 BEST PRACTICES .......................................................................................................... 4 TIP#1- USE THE MIGRATION CHECKLIST AS A GUIDE THROUGH THE STEPS....................... 4 TIP#2 CLEAN-UP DATA.................................................................................................. 4 TIP#3 RESEARCH, DECIDE AND DOCUMENT OPM ENTITY MIGRATION CHOICES. ........... 4 TIP#4 PLAN AND EXECUTE MULTIPLE TEST MIGRATION RUNS BEFORE GO-LIVE. ........... 5 TIP#5 ORGANIZATION AND ITEMS CAN BE MIGRATED IN PRE-MIGRATION PHASE TO REDUCE DOWNTIME FOR UPGRADE PROCESS. ................................................................... 6 TIP#6 ESTIMATE THE AMOUNT OF DATA THAT WILL BE MIGRATED. .............................. 6 TIP#7 WHEN TO LOG AN SR AND WHAT INFORMATION IS NEEDED................................ 6 CHANGE RECORD......................................................................................................... 7

OPM Migration from 11i to 12/12.1 Best Practices Guide

Page 2

Introduction
This white paper describes the best migration practices to help your enterprise become successful on OPM Release 12.1. It offers practical advice from professionals in Oracles Support, Consulting, IT, and Development organizations, on how to upgrade OPM to Release 12.1. This paper provides the things you wish you knew before embarking upon your Release 12.1 migration project. This white paper is intended to be a living document. As we gather additional Release 12.1 migration best practice advice, we will revise and re-publish this paper.

OPM Migration from 11i to 12/12.1 Best Practices Guide

Page 3

Best Practices
The following sections describe best practices for OPM migration to Release 12.1.

Tip#1- Use the migration checklist as a guide through the steps.

The migration checklist enables you to efficiently migrate from OPM 11.5.10 to 12.1. The checklist has been organized in the correct sequence of migration phases to ensure that all of the necessary actions in one phase are performed before attempting the next action or phase. The checklist also serves as a record of actions taken, which Oracle Customer Support can then refer to if they are engaged. Checklist can be used to record observations and decisions about migration issues or messages. For example, a customer might decide to ignore warning messages about mixed inventory or negative inventory balances. In this case, they might update the checklist to capture this decision. These types of updates will be beneficial in troubleshooting any issues.

Tip#2 Clean-up data.

It is absolutely essential to start the migration process with valid 11.5.10data. Invalid or corrupt data will unnecessarily consume time in troubleshooting issues or engaging Customer Support. For example, Data corruption for items table has very high impact on item migration or inventory balances migration. Datafix patches are listed in the migration checklist. Archive or purge historical data to speed up the migration. For example, run the Purge Empty Balances program, archive old transaction data, review open batches/FPOs and clean up whatever data is no longer required. The data model has changed in R12.1 for some of the OPM entities. This requires existing 11.5.10 data mapping to be remapped in R12.1. E.g. If a warehouse is migrated as a subinventory, then the organization code on Quality samples must be same as organization code of that subinventory. 11.5.10 data must be corrected for such restrictions.

Tip#3 Research, decide and document OPM Entity migration choices.

As described in OPM Migration Reference Guide, Release 12.1, the Migration User Interface offers various choices to migrate entities like companies, organizations, warehouses etc. It is important to be aware of: The different options available for the migration of each entity. The impact of these options on the migrated entities and related functionality Understand how these choices fit in the grand scheme of the anticipated usage of R12.1.

It is very important that these choices are internalized, discussed and debated before making the decision of using a specific choice. Document the choices made and the reasoning behind those choices so that the information is available for future reference.

OPM Migration from 11i to 12/12.1 Best Practices Guide

Page 4

Tip#4 Plan and execute multiple test migration runs before go-live.
Customers should plan to run multiple tests to confirm data accuracy and downtime expectations. Customers should start test runs at least 4 months before the actual migration date. There are many benefits of performing test migration runs. These runs enable users to: Become familiar and comfortable with the Migration User Interface. Examine whether the final result of the migration is as expected. Confirm that the entity has been migrated as anticipated and that the result reflects what you plan to implement. It is important to note that at this stage, you can still make changes to your migration strategy, rerun the migration, see the effect, finalize choices for final go-live, and then document the changes. Make certain that the entity has been migrated as anticipated and is indeed what they want to go forward with. It is important to note that at this stage users can still make changes to their migration strategy, rerun the migration, see the effect, finalize choices for final go-live, and document the changes. Estimate the total time required for each of the migration phases. This will help you plan the go-live/blackout activities in an effective manner. This may also validate hardware requirements/adjustments. Estimating the total time required for each migration phase can also influence your choice to pre-migrate specific OPM entities (such as, item and organizations) ahead of the in-line migration (see Tip#5 for more information on premigration). Identify areas for user training. R12.1 has a new data model for some OPM functionality. E.g. OPM Inventory has been converged with Oracle Inventory from R12 onwards. As a result, user must use Oracle Inventory forms and functionality to review OPM related data. These forms have different UI and functionality than 11i OPM forms. Therefore it may require usertraining to validate migrated data. For example, User the Material Workbench form is used to change material status, as opposed to using the Status Immediate form in 11i. Validate OPM business flows for the migrated data. Identify any data issues during the migration runs and the phase in which they occurred. Uncover unexpected code or data issues that might warrant interaction with Oracle Support. You should note any exception activity and include the actions performed to resolve the exception. After the exception has been resolved, update the checklist for future reference.

OPM Migration from 11i to 12/12.1 Best Practices Guide

Page 5

Tip#5 Organization and items can be migrated in pre-migration phase to reduce downtime for upgrade process.
It is highly recommended that organizations and items to be migrated in pre-migration phase. This will significantly reduce the amount of time that is taken during the In-Line/Blackout period, thus reducing the amount of time that the system is unavailable for transaction. Items will be migrated for a warehouse where they are used in OPM. Note that only items that have inventory balances or items that are used in Formulas, Batches, Quality, etc are migrated.

Tip#6 Estimate the amount of data that will be migrated.

It is generally a good idea to reconcile migrated data with the original data in 11.5.10. To perform this reconciliation, estimate the amount of data that will be migrated, such as the number of items, organizations, warehouses, and inventory balances in a given organization, etc. You can then use this information to verify the migration of the data. Estimating the amount of migrated data will also be helpful in determining the amount of time required in the In-Line/Blackout period. This information can also be used to pass along to Customer Support if they become involved with a related issue. Example: Relevant inventory reports can be run for items before migration to ensure that all the closing balances are correctly carried forward or migrated as opening balances.

Tip#7 When to Log an SR and what information is needed.

The System validates data in all migration phases. Almost all data errors include ready-made solution plans. Review Oracle Process Manufacturing (OPM) Migration Release 11i to 12.1 Migration Messages and Technical Reference documentation, which includes information on how to resolve error conditions. Log a service request only when you are unable to locate information on a specific error condition, or when the corrective actions taken do not prevent the error message from appearing after re-running the applicable migrations.

Please provide following information when service request is logged. Output of the view GMA_MIGRATION_LOG_V1 in neat xls format. Output of the table GMA_MIGRATION_LOG in neat xls format. Provide screen shot of the UI for any issues related to migrated data. Check if UI works for brand new data. Trace files (raw and tkproffed) for any performance related issue.

OPM Migration from 11i to 12/12.1 Best Practices Guide

Page 6

Change Record

Date October 7, 2009

Version 1.0

OPM Migration from 11i to 12/12.1 Best Practices Guide

Page 7