Finish migration preparations for OPM (conditional)

Applies to 11i release level: All

TUMS step key: GMA_PREP_MIGRATE_FINISH

Make sure you have completed all the steps in the previous task prior before you begin this task. Perform the steps in the order listed. Users must be logged off the system.

1. Disable any and all custom code and or triggers before migration.

2. Turn off Formula Security.

3. For ALL existing Discrete Inventory Organizations, ensure that Lot uniqueness is set to 'NO'.

4. Review, act on, and dispose of information in Oracle ASCP tables. (required for all releases that use ASCP)

Review, act on, and dispose of information provided in the Oracle Advanced Supply Chain Planning application tables: GMP_APS_OUTPUT_TBL and GMP_APS_OUTPUT_DTL.

5. Review, act on, and dispose of information in OPM MRP table. (all releases that use OPM MRP)

Review, act on, and dispose of the information in the OPM table:

MR_ACTN_TBL.

6. Prepare for the batch snapshot (if there are open batches)

Apply patch 12790235. A snapshot must be taken to recreate all the open batches after the upgrade as described in the Migration Checklist that is attached to Oracle Process Manufacturing (OPM) Release 12.1 Migration document (Doc ID: 376683.1).

7. Close all batches with a status of Completed (all releases)

Navigate to the Migration Setup User Interface Batches tab. Choose Mass Batch Close from the Action menu. See the OPM Migration Reference Guide (Doc ID:

376683.1) for details.

8. Capture snapshot (all releases)

Click the Process Batches for Migration button on the Convergence Migration Setup user interface to capture a snapshot of the open batches to be used during the post-migration process (that recreates the batches). See the OPM Migration Reference Guide (Doc ID: 376683.1) for details.

9. Complete or cancel pending transfer (all releases).

See the OPM Inventory Management User's Guide for details about how to

complete a pending transfer. Or, apply patch 4350832 to your Release 11i APPL_TOP to cancel pending transfers.

10. Back order or ship OPM Order Management Fulfillment sales orders that are pick-confirmed or staged prior to migration (all releases)

If these order lines are not shipped prior to the migration, then the only way to make them visible for updates to Oracle Inventory is to back order them prior to the migration.

11. Run Preliminary Inventory Close Process for all warehouses under all the OPM Companies (all releases). Do not run Final Inventory Close for the period in which you are running the upgrade.

Refer to the following table for instructions:

If you are a... Follow these instructions...

Standard Costing user Post inventory and resource transactions to OPM Subledger and export to GL:

Run the OPM Subledger Update, OPM GL Export, and General Ledger Journal Import. See the OPM Manufacturing Accounting Controller User's Guide and the Oracle General Ledger User's Guide for details.

Note: Once you upgrade, you cannot post the transactions created prior to the upgrade.

If you are a... Follow these instructions...

Actual Costing user Run Actual Cost Process to calculate the cost and then post inventory and resource transactions to OPM Subledger and export to GL:

Run the OPM Actual Cost Process, OPM Cost Update Process, OPM Subledger Update, OPM GL Export, and General Ledger Journal Import. See the OPM Manufacturing Accounting Controller User's Guide and the Oracle General Ledger User's Guide for details.

Note: Once you upgrade to Release 12.2, the Actual Cost program looks at transactions under process

organizations recorded only in Oracle Inventory — the average cost

calculations after the upgrade do not consider the transactions created in the Release 11i OPM Inventory system. As a result, the average cost calculated may not be accurate if the upgrade is done during the middle of a costing period and there are transactions in OPM Inventory for the same costing period.

If possible, consider doing the upgrade at the beginning of a costing period. By doing so, you can ensure that a majority of transactions in that costing period are recorded In this release, thereby arriving at a more accurate average cost when you run the OPM Actual Cost Process.

Once you upgrade, you cannot post the transactions created prior to the upgrade.

If you are a... Follow these instructions...

Lot Costing user Run Lot Cost Process to calculate the cost, and then post inventory and resource transactions to OPM Subledger and export to GL:

Run the OPM Lot Cost Process, OPM Cost Update Process, OPM Subledger Update, OPM GL Export, and General Ledger Journal Import. See the OPM Manufacturing Accounting Controller User's Guide and the Oracle General Ledger User's Guide for details.

Note: Once you upgrade, you cannot post the transactions created prior to the upgrade.

Note: For Lot Cost Simulation Users:

If you are using Lot Costs as

additional cost method for simulation purposes, run the lot cost process in final mode before migration.

Otherwise, the costs created in test mode may be wiped out when you run the process again in the upgraded system.

12. Run the GMF validation scripts (all releases)

Refer to OPM Release 12.2 Migration (Doc ID: 376683.1) for details.

13. Migrate OPM Order Fulfillment to Order Management (all releases that use OPM Order Fulfillment)

Refer to the OPM Migration Reference Guide (Doc ID: 376683.1) for details.

Note: The migration process varies depending on your version.

Service Contracts:

Perform these tasks only if you are using Oracle Service Contracts.

1. Update Currency Code setup in Global Contracts defaults (conditional)