migration checklist(1)

of 19

Checklist for Process Manufacturing Migration from Release 11.5.10 to R12.1 This document provides high level steps that describe how to migrate data from Oracle Process Manufacturing Release 11.5.10 to Release 12.1. Wherever possible, links to more detailed information have been provided. All steps are mandatory except where SPECIFICALLY noted. All patches must be installed in the order specified – Patch Merge functionality CANNOT be employed for these steps. The columns in the checklist are required to be filled out when each step has been completed, including notes on errors or notable conditions, and a note on optional steps indicating whether or not they were executed. NOTE: This document is specifically limited to the migration of data from Oracle Process Manufacturing Release 11.5.10 to 12.1. Upgrades and/or migrations pertaining to the database, operating system, other products (e.g. Order Management, Oracle Inventory), etc. are not covered in this document. Date Published Version Sep 20, 2011 3.5

of 19

1. Preparation ALL Customers: The following steps are performed in preparation for migration planning. The information contained in the referenced documents and note help to explain the overall OPM Migration process and recommendations for ensuring a smooth, successful migration. Action Action Owner Date Completed Notes

1.1. Please see Metalink note#

376683.1 for OPM Migration related

documents.

1.2. Review the Best Practices Guide

for OPM Migration from 11i to

R12.1

1.3. Review the Oracle Process

Manufacturing (OPM) Migration

Reference Guide – Release 11i to

12.1

https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=376683.1�

https://support.us.oracle.com/cgi-bin/cr/getfile.cgi?p_attid=376683.1:BESTPRAC�



https://support.us.oracle.com/cgi-bin/cr/getfile.cgi?p_attid=376683.1:MIGREF�




of 19

2. Pre-Migration If you have not already done so, you must complete the preparation steps listed above prior to continuing on to this section. The following steps are performed while the system is still available for use by end-users. The steps must be performed in the order presented and before you continue with the other tasks in subsequent sections. 2. Action Applicability Applicable

Patch and

Comments

Action Owner Date

Completed

Notes

2.1. Install the latest Datafix

patches.

ALL Customers 5750051 Above patch fixes data corruption issues with Items that would affect migrating OPM entities.

2.2. Map the data using the

Convergence Migration

Setup user interface,

which is available in the

OPM System

Administration

Responsibility.

ALL Customers Apply following patches if migrating to 12.0 • 4563075 • 7582494 Apply following patches if migrating to 12.1 • 4563075 • 6694260 • 10302784

of 19

2. Action Applicability Applicable

Patch and

Comments

Action Owner Date

Completed

Notes

2.3. Execute Actual SubLedger

Update

ALL Customers

2.4. Execute GL Export ALL Customers

2.5. Execute Journal Import ALL Customers

2.6. Set up INV and IVA

accounts at the

organizations level, as this

is required for migrating

Inventory balances.

ALL Customers The Process to Discrete Inventory Transfer functionality is leveraged for Inventory balance migartion.

2.7. Update Forecast Headers

to have a value entered in

Forecast Set.

All Customers Only those forecasts that have a value in this field will be migrated.

2.8. Run the Pre-Migration

Validation script.

ALL Customers 4699061 and follow the instructions from the README, as the application of the patch does not automatically run the validation scripts. Additonally, apply patch 6696828 if migrating to 12.1

of 19


Patch and

Comments

Action Owner Date

Completed

Notes

2.9. Check the Migration Log

User Interface or check

log table for errors and/or

applicable warning

messages.

If none are found, proceed

directly to step 2.11

ALL Customers

2.10 Take the appropriate

corrective actions to

address ALL errors and

applicable warning

messages. Refer to the

Oracle Process

Manufacturing (OPM)

Migration Release 11i to

12.1 Migration Messages

and Technical Reference

for the required actions.

When completed, repeat

step 2.9

ALL Customers

2.11 (Optional) Migrate all

organizations and items.

ALL Customers 4582937 and follow the instructions from README

https://support.us.oracle.com/cgi-bin/cr/getfile.cgi?p_attid=376683.1:messages�





of 19


Patch and

Comments

Action Owner Date

Completed

Notes

2.12 If step 2.11 was executed,

check the Migration Log

User Interface, or check


applicable warning

messages. If step 2.11

was NOT executed or no

errors are found, the OPM

Pre-Migration steps section

is complete.

ALL Customers

2.13 Take the appropriate

corrective actions to

address ALL errors and

applicable warning

messages. Refer to the

Oracle Process

Manufacturing (OPM)

Migration Release 11i to

12.1 Migration Messages

and Technical Reference

for the required actions.

When completed, go to

step 2.12 and repeat.

ALL Customers






of 19

3. Blackout phase – Prior To Upgrade Patch Installation The pre-migration steps listed above MUST be completed prior to beginning this section. There should be no unresolved errors from the pre-migration phase. If errors exist from pre-migration, take the necessary actions to correct them before proceeding. The following steps are performed after end-users are no longer allowed to log into the system, but before the system is taken offline to apply the 12.1 Upgrade. The steps must be performed in the order presented and before continuing with the other tasks in subsequent sections. 3. Action Applicability Applicable patch and

Comments

Action Owner Date

Completed

Notes

3.1. Disable any and all

custom code and or

triggers before

migration.

ALL Customers

3.2. Turn off Formula

Security.

ALL Customers

3.3. For ALL existing Discrete

Inventory Organizations,

ensure that Lot

uniqueness is set to ‘NO’.

ALL Customers

of 19

3. Action Applicability Applicable patch and

Comments

Action Owner Date

Completed

Notes

3.4. Review, act upon, and

dispose of information in

Oracle ASCP interface

tables

Customers using ASCP

Review, act upon, and dispose of information provided in the Oracle Advanced Supply Chain Planning application interface tables: GMP_APS_OUTPUT_ TBL GMP_APS_OUTPUT_DTL

3.5. Review, act upon, and

dispose of information in

the OPM MRP interface

table

ALL Customers using OPM MRP

Review, act upon, and dispose of the information provided in the OPM interface table MR_ACTN_TBL. This is important as user will be moving from using MRP to ASCP Unconstrained.

3.6. If there are no open

batches then go to 3.9

Prepare for the batch

snapshot

ALL Customers Apply patch 12790235. A snapshot must be taken to recreate all the open batches after the upgrade.

3.7. Navigate to the Migration

Setup User Interface

Batches tab. Choose

Mass Batch Close from

the Action menu to close

all batches with a status

of Completed.

ALL Customers

of 19


Comments

Action Owner Date

Completed

Notes

3.8. If there are no open

batches then go to 3.9

Click the Process Batches

for Migration button on

the Convergence

Migration Setup user

interface to capture a

snapshot of the open

batches that will be used

during the post migration

process to recreate the

batches

ALL Customers

3.9. Complete or cancel all

pending transfers

ALL Customers Refer to the OPM Inventory Management User’s Guide for details on how to complete a pending transfer or, apply patch 4350832 to cancel pending transfers

3.10 Backorder or ship OPM

Order Fulfillment sales

orders that are pick

confirmed or staged prior

to migration

Applicable to customers migrating from OPM Order Fulfillment to Oracle Order Management

If these order lines are not shipped prior to migration, then only backordering prior to migration will make these order lines visible for updates to Oracle Inventory.

of 19


Comments

Action Owner Date

Completed

Notes

3.11 Run Preliminary

Inventory Close Process

for all warehouses under

all the OPM Companies.

ALL Customers Do not run Final Inventory Close for the period in which you are running the R12 upgrade.

3.12 Post inventory &

resource transactions to

OPM Subledger and

export to GL.

Customers using Standard Costing

Run the OPM Subledger Update, OPM GL Export, and General Ledger Journal Import. Refer to the OPM Manufacturing Accounting Controller User’s Guide & Oracle General Ledger User's Guide for further details. Once you upgrade you will not be able to post the transactions created prior to the upgrade.

3.13 Run Actual Cost Process

to calculate the cost and

then post inventory &


OPM Subledger and

export to GL. Also see

note below.

Customers using Actual Costing

Run the OPM Actual Cost Process, OPM Cost Update Process, OPM Subledger Update, OPM GL Export, and General Ledger Journal Import. Refer to the OPM Manufacturing Accounting Controller User’s Guide & Oracle General Ledger User's Guide for further details. After you upgrade you will not be able to post the transactions created prior to the upgrade.

of 19


Comments

Action Owner Date

Completed

Notes

3.14 Review Note at the end

of this document about

actual costing

Customers using Actual Costing

3.15 Run Lot Cost Process to

calculate the cost and

then post inventory &


OPM Subledger and

export to GL.

Customers using Lot Costing

Run the OPM Lot Cost Process, OPM Cost Update Process, OPM Subledger Update, OPM GL Export, and General Ledger Journal Import. Refer to the OPM Manufacturing Accounting Controller User’s Guide & Oracle General Ledger User's Guide for further details. Once you upgrade you will not be able to post the transactions created prior to the upgrade.

3.16 Review Note at the end

of this document about

Lot costing.

Customers using Lot Costing

3.17 Run the GMF validation

scripts

ALL Customers Run the script GMAR12VAL.sql with the parameter value set to ‘GMF’ Refer to document Oracle Process Manufacturing (OPM) Migration Release 11i to 12.1 Migration Messages and Technical Reference for details.

3.18 OPM Order Fulfillment to Customers using OPM Order

Refer to document OPM Migration Reference









of 19


Comments

Action Owner Date

Completed

Notes

Oracle Order

Management migration

Fulfillment Guide, Release 12.1 for further details

3.19 Check the Migration Log


log table for errors

and/or applicable

warning messages. If

none are found, go to

step 3.21.

ALL Customers .

3.20 Refer to the Oracle

Process Manufacturing

(OPM) Migration Release

11i to 12.1 Migration

Messages and Technical

Reference for the

required actions. After

taking corrective actions,

go to step 3.19

ALL Customers

3.21 Apply the latest ALL Customers Apply following patches if migrating to 12.0







of 19


Comments

Action Owner Date

Completed

Notes

additional OPM In-Line

Migration patches in pre-

install mode just before

applying the upgrade

driver.

• 7513308:R12.INV.A • 8363586:R12.INV.A • 9143261:R12.INV.A • 9403348:R12.INV.A • 8359386:R12.GMI.A • 10332854:R12.GME.A Apply following patches if migrating to 12.1 • 8359386:R12.GMI.B • 9004088:R12.INV.B • 9143261:R12.INV. • 9403348:R12:INV.B • 9476958:R12:INV.B • 9560244:R12.ITM.C • 9893621:R12:INV.B • 9893621:R12.INV.B • 10279332:R12:INV.B • 10413599:R12:INV.B • 11887554:R12.INV.B • 12387835:R12.INV.B • 11767692:R12.GMD.B • 12422840:R12.GMD.B • 10332854:R12.GME.B • 12591257:R12.INV.B • 12591131:R12.PO.B • 12879278:R12.GMD.B

of 19

4. Post-Migration

Perform the following steps after the application of the 12.1 Upgrade and before bringing the system back up and allowing users to log on. The steps must be performed in the order presented. 4. Action Applicability Applicable patch and

comments

Action Owner Date

Completed

Notes

4.1. If adworker failed for any

OPM script, go to My

Oracle Support to check

for any new patches or

workarounds that exist

for a failure in the in-line

phase. If none are found,

log a service request.

ALL Customers Refer to the Oracle Process Manufacturing (OPM) Migration Release 11i to 12.1 Migration Messages and Technical Reference for details on running failed scripts.

4.2. Check the Migration Log



applicable warning

messages. If none are

found, go to step 4.4

ALL Customers







of 19


comments

Action Owner Date

Completed

Notes

4.3. Refer to the Oracle





Reference for the



go to step 4.2

ALL Customers

4.4. Run OPM Data

Transformation

ALL Customers If migrating to 12.0 apply following patches in the order mentioned 1. 6677022 If migrating to 12.1 apply following patches in the order mentioned 1. 11670689:R12.PO.B 2. 6677049 3. 12879251:R12.GMA.B 4. 12692010:R12.GME.B These patches will transform the organization_id, inventory_item_id, lot_number, and uom columns in GMD,GME, GME OM WSH, PO, and RCV.







of 19


comments

Action Owner Date

Completed

Notes

4.5. Run OPM Financials Data

Transformation

ALL Customers Apply following patch if migrating to 12.0 5. 4690072 Apply following patch if migrating to 12.1 6. 12372491:R12.GMF.B Above patches will perform following migrations: • Transformation of organization_id, inventory_item_id, uom, lot_number, and uom columns in the OPM Financials tables • Migration of OPM financials data

4.6. Migrate OPM Regulatory

data

Customers using OPM Regulatory Management

Apply patch 4688012

4.7. Apply patches required

for reopening batches.

ALL Customers Apply the following patches if migrating to 12.0 • 9090024:R12.GME.A • 9170460:R12.GME.A Apply the following patches if migrating to 12.1 • 9090024:R12.GME.B • 9170460:R12.GME.B

of 19


comments

Action Owner Date

Completed

Notes

• 12966683:R12.GME.B

4.8. Recreate open batches ALL Customers Run the Process Execution Migration Recreate Open Batches concurrent program based on the snapshot captured during pre-migration.

4.9. Migrate OPM Edit Text to

attachments

ALL Customers Run the GMA: Edit Text Migration concurrent program to migrate the OPM Edit Text to attachments for the organizations, items, lots, grades, and reason codes. Refer to the OPM System Administration User’s Guide for details

4.10 Check the Migration Log


log table for errors and

or/applicable warning

messages. If none are

found, proceed directly to

step 4.12

ALL Customers

4.11 Refer to the Oracle




ALL Customers





of 19


comments

Action Owner Date

Completed

Notes


Reference for the



repeat step 4.10

4.12 Update items attributes

for MRP/MPS and Lead

times for migrated items

for ASCP planning.

Customers using ASCP Planning

New ASCP users: Refer to the Oracle Process Manufacturing Process Planning User's Guide and the Oracle Advanced Supply Chain Planning Implementation and Users Guides for details. Current ASCP users: If changes were made to your organization structure, review Sourcing Rules to ensure the proper planning will take place for this new organization structure.

4.13 Apply additional post migration patches

ALL Customers Apply following patch if migrating to 12.0 • 8968112:R12.GML.A Apply following patch if migrating to 12.1 • 8968112:R12.GML.B

4.14 Validate various business flows to ensure that the OPM data transformation process completed successfully.

ALL Customers

of 19


comments

Action Owner Date

Completed

Notes

4.15. (Optional) Migrate Un-Migrated Items

Optional Follow the instructions in the README for patch 10405668:R12.INV.B. There is no need to apply the patch, as the required code has already been applied. Migration process does not migrate items that are not in use (e.g. no on-hand balance, not used in formula etc.) This step will provide the ability to update these organization items if required.

Note for Actual Costing Users only: After you upgrade to Release 12.1, the Actual Cost program in Release 12.1 will only recognize transactions under process organizations that are recorded in Oracle Inventory. In other words, the average cost calculations after the upgrade will not recognize the transactions created in the 11i OPM Inventory system. As a result, the average cost calculated may not be accurate if the upgrade is performed during the middle of a costing period--and there are transactions in OPM Inventory for the same costing period. If possible, consider upgrading to R12.1 at the beginning of a costing period. By doing so, you can ensure that the majority of the transactions in that period are recorded in Release 12.1. Upgrading at the beginning of the costing period will therefore result in a more accurate average cost when you run the Release 12.1 OPM Actual Cost Process. Note for Lot Cost Simulation Users: If you are using Lot Costs as an additional costing method for simulation purposes, you must run the Lot Cost process in final mode before migration. Otherwise, the costs created in test mode may be overwritten when you run the process again in Release 12.1

migration checklist(1)

Documents