Migration Business Needs

The primary focus of the migration from Release 11.5.10 to Release 12.1 is to minimize system downtime,
while streamlining the implementation of Oracle Inventory for process manufacturers. To this extent, the
migration:
Enables you retain or change your organization structure. Inventory convergence enables you fully

embrace the Oracle Inventory organization structure. Prior to Release 12.1, Process Manufacturing did
not support the concept of subinventories. Although a subinventory is created as part of Oracle
Warehouse setup, inventory transactions are recorded at the warehouse level only. Subinventories are
integral to the Oracle Inventory organization structure. All transactions are performed at this level. The
migration process allows you to optionally map your warehouses as subinventories. You can keep the
original warehouse as an active inventory organization, or make it inactive. Alternatively you can keep
warehouses as inventory organizations and define new subinventories associated with them.
Updates references to the new item master and organization master. In Release 12.1, items exist

within the context of an organization. Internal IDs are used to reference the item number and inventory
organization for a record. These new IDs are added to existing objects (formulas, batches, quality
samples, etc.) to allow the user to continue to query and update existing data.
Transfers inventory balances. All onhand inventory balances are transferred to existing or new

Inventory organizations, based upon the pre-migration setup. Users can review the balances in Oracle
Inventory and review historical transactional data in OPM Inventory. Period end balances for the most
recent inventory period are also migrated.
Transfers lot and sublot information. Lot and sublot information is transferred from Process

Manufacturing to Oracle Inventory lot tables.

Transfers other master data for lot status, quality grades, costing and Oracle Regulatory. Key

process manufacturing attributes have been added to Oracle Inventory. The supporting data required
to make use of the functionality is transferred to the converged Inventory model.
Transfers open production batches. Batches that were open in 11.5.10 are re-created in Release 12.1.

Detail level reservations are automatically created against the material that was allocated to the open
batches in Process Manufacturing in 11.5.10. High level reservations are created for the unallocated
material.

Migration Process Overview

The migration of data from Release 11.5.10 to Release 12.1 occurs in three phases pre-migration, inline
migration (during the Release 12.1 installation), and post-migration. The pre-migration activities involve the
use of a Convergence Migration Setup form to prepare the data for the actual migration, the running of
validation scripts, and the correction of any erroneous or missing data. The inline migration is run
automatically when Release 12.1.is installed. During this period, transactions in 11.5.10 are halted and the
actual migration of the data is completed. The post-migration phase is where the data is transformed into the
new data model, and final scripts are run to complete the movement of all data. Migration messages are logged
during each phase and must be reviewed in the log viewer, and where required, acted upon before progressing
to the next phase of the migration. The migrations scripts are designed to be re-runnable, migrating only the
data which was not previously migrated.

Version 1.0

Page 1 of 6

Pre-Migration Phase
Convergence Migration form

The new Convergence Migration form consists of multiple tabs where users can view their data and
perform the setup required to successfully migrate companies, organizations, warehouses, items,
batches and quality related data.
Inventory Validation

There is an OPM Inventory validation script that must be run to ensure accuracy in your data. This
validation script performs the following actions:
Displays all items in OPM that do not have the auto lot numbering set up in the validation report
Checks the descriptive flexfield setup in both OPM Inventory and Oracle Inventory item master

for conflicting use of attributes

Any migration messages that are logged by this validation must be reviewed, and where required,
addressed before progressing to migrating inventory balances.
Quality Validation

The OPM Quality validation script verifies that the Stability Studies Default Organization code located
on the Quality tab of the Convergence Migration form has been set to a valid value. Any migration
messages that are logged by this validation must be reviewed, and where required, addressed before
progressing to the inline phase of the migration.
Cost Management and Manufacturing Accounting Controller (MAC) Validation

For Release 12.1, OPM Companies are migrated to Legal Entities. If multiple OPM Companies in
Release 11i all point to the same Legal Entity you can, as part of the pre-migration configuration,
choose to migrate these companies to their own legal entities. If the Legal Entity asscociation is not
changed on the Convergence Migration Setup form before the migration, then all OPM Companies are
migrated to the legal entities to which they are currently assigned. There is also a Cost Management
validation script that must be run to ensure the accuracy of your data. This validation script does the
following:
Determines whether there are any unposted inventory transactions, unposted resource

transactions, or unposted closed batches. If any are found, then a warning is raised. You must
then verify and post the transactions by running the subledger update process. Though running
the subledger is a mandatory step, this script validates that it was completed. However, the
script cannot automatically post the unposted transactions.
If the Actual Costing method is used for inventory valuation, then the validation script looks for

active transactions in the current open period in which you are migrating. If active transactions
are identified, a warning appears stating that after transactions are migrated to Release 12.1,
actual costs might not be accurate for the current period. To correct this issue, the Actual Cost
process must be run at month end for the current open period. All active transactions must be
posted prior to migration.
Any migration messages that are logged by this validation must be reviewed, and where required,
addressed before progressing to the inline phase of the migration.

Version 1.0

Page 2 of 6

Regulatory Management Validation

If OPM Regulatory Management has been implemented in 11.5.10, the Regulatory Management
validation script must be run. This script validates that:
A valid value is specified for the profile option GR: Default Warehouse. This value is used as the

owner organization for migrated standalone Regulatory formulas.

A valid value is specified for the profile option FM: Yield Type is not NULL. This value is used

as the unit of measure code for migrated standalone Regulatory formulas.

Each Regulatory Item has an associated CAS number, as that value is required for a Regulatory

Item in Release 12.1

All ingredients in the item concentrations table can be converted to the products unit of measure.

Any migration messages that are logged by this validation must be reviewed, and where required,
addressed before progressing to the inline phase of the migration.
Order Fulfillment to Order Management

While the Release 12.1 install includes the migration of Order Fulfillment to Order Management, it is
necessary to complete a series of pre-migration steps to prepare the data for migration. These steps can
be found in the Oracle Process Manufacturing Order Fulfillment to Order Management Migration
documentation available on OracleMetalink.
Process Forecast to Discrete Forecast

In R12.1, Forecasts will be defined in a common forecast table. Migration to this table will occur only
if the OPM forecasts have a forecast set name. The Forecast Set Name field was added in 11.5.10.
Early Migration of Items, Orgs, Warehouses, and Addresses

Users can migrate items, organizations, warehouses, and addresses prior to the blackout period. This
saves time during the blackout period, but the data is not completely.updated with all of the required
process related values until the installation of Release 12.1, where the final data transformation takes
place.
Process Execution Batches

The following actions are required prior to moving Oracle Process Execution batches to Release 12.1:
All completed batches must be closed.
Users must execute the Process Batches for Migration snapshot procedure from the Batches tab

for pending, WIP, and FPO batches to be automatically recreated in Release 12.1. After this
procedure has been run, batches can no longer be manipulated until after the migration to
Release 12.1.
The Subledger Update, GL Export, and Journal Import scripts must be run prior to migration.

This ensures that all transactions related to closed batches have been properly booked.

Version 1.0

Page 3 of 6

Inline Migration Phase

The migration is phased so that data is processed in a logical order. The migration scripts support this phased
approach.

Any migration messages that are logged during this phase of the migration must be reviewed, and
where required, addressed before progressing to the inline phase of the migration. In the event that a
script does not migrate or transform the data properly, the previous scripts must be run again.

Post Migration Phase

Common Transformation
The Common Transformation must be run after the successful migration of all data during the inline
phase. This script manipulates the migrated data so that it works properly in the new Oracle Inventory
organization and structure. The script performs the following actions:
Updates Organization_Id, Inventory_Item_Id, Lot_Number, and Unit of Measure columns in the

Product Development, Process Execution, and Process Planning tables

Migrates specifications, samples, and stability studies
Migrates Process Execution profiles and WIP entities
Migrates item categories and item lot conversions.
Migrates move orders for Order Management.
Updates PO shipment lines
Updates Receiving tables

Any migration messages logged by this script and must be reviewed, and where required,
addressed prior to commencing business in Release 12.1.

Version 1.0

Page 4 of 6

Cost Management Post-Migration

The Cost Management post-migration script completes the data transformation for the Cost
Management module. This script performs the following data migration and transformation:
Migrates resource details, cost component details, standard cost ledgers, actual cost ledgers,

adjustment details, burden details, item costs, lot costs, lot costing item setup, lot cost
adjustments, lot costing material transactions, lot costing burdens.
If multiple companies are migrated to the same Legal Entity, the script copies the existing costs

appropriately.
Migration of account mappings and various data intensive GMF entities to SLA.

Any migration messages logged by this script and must be reviewed, and where required, addressed
prior to commencing business in Release 12.1.
Regulatory Management Post-Migration
The Regulatory Post-Migration script must be run to migrate Regulatory Items and their associated
data, update dispatch history records for organization and item combinations, and migrate Regulatory
standalone formulas to Product Development. Any migration messages logged by this script and must
be reviewed, and where required, addressed prior to commencing business in Release 12.1.
Batch Recreation
The Batch Recreation concurrent program must be run to recreate the WIP, Pending, and FPO Batches
that were unreleased and canceled during the snapshot taken during pre-migration. This script renames
the old version of the batch appended with a -M and creates the new batches with the same batch
number. Any migration messages logged by the concurrent program must be reviewed, and where
required, addressed prior to commencing business in Release 12.1.
Planning Post-Migration
Attributes for ASCP planning must be manually defined on the MRP/MPS Planning Tab and Leadtimes Tab of for the migrated Organizational Items.
Purchasing Post-Migration
The Purchasing Post-migration script updates the secondary ship quantity and secondary cancelled
quantity for PO shipments based on the respective primary transactions quantities. Sublots are
modeled as Parent/Child lots in the converged model. When a sublot is migrated to Oracle Inventory,
one record is created with the Parent Lot field representing the lot number and the lot field containing a
concatenation of the lot and sublot fields.
For a sublot-controlled item with a blank or NULL sublot field, the Parent lot field is left blank and the
lot field contains the lot number. Receiving lot and lot supply transactions are updated for the lot
number field representing the parent/child lot combination in the common inventory model. Any
migration messages logged by this script and must be reviewed, and where required, addressed prior to
commencing business in Release 12.1.

Version 1.0

Page 5 of 6

Edit Text Migration

Users can submit the concurrent program "GMA: Edit Text Migration to migrate the text associated
with items, lots, organizations, grades and reason codes as attachments. Any migration messages
logged by this script and must be reviewed, and where required, addressed prior to commencing
business in Release 12.1.

Version 1.0

Page 6 of 6