You are on page 1of 6

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

Any migration messages that are logged by this validation must be reviewed. a warning appears stating that after transactions are migrated to Release 12. All active transactions must be posted prior to migration. and where required. then all OPM Companies are migrated to the legal entities to which they are currently assigned. 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. Cost Management and Manufacturing Accounting Controller (MAC) Validation For Release 12. addressed before progressing to the inline phase of the migration. You must then verify and post the transactions by running the subledger update process. If multiple OPM Companies in Release 11i all point to the same Legal Entity you can. Though running the subledger is a mandatory step.0 Page 2 of 6 . 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. items. OPM Companies are migrated to Legal Entities. To correct this issue. as part of the pre-migration configuration.1. If the Legal Entity asscociation is not changed on the Convergence Migration Setup form before the migration. addressed before progressing to the inline phase of the migration. and where required. This validation script does the following: • Determines whether there are any unposted inventory transactions. the script cannot automatically post the unposted transactions. batches and quality related data.1. However. There is also a Cost Management validation script that must be run to ensure the accuracy of your data. then a warning is raised. Inventory Validation There is an OPM Inventory validation script that must be run to ensure accuracy in your data. If active transactions are identified. organizations. and where required. Any migration messages that are logged by this validation must be reviewed. warehouses. • If the Actual Costing method is used for inventory valuation. the Actual Cost process must be run at month end for the current open period. or unposted closed batches. Version 1. addressed before progressing to migrating inventory balances.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. this script validates that it was completed. actual costs might not be accurate for the current period. choose to migrate these companies to their own legal entities. then the validation script looks for active transactions in the current open period in which you are migrating. unposted resource transactions. If any are found.

it is necessary to complete a series of pre-migration steps to prepare the data for migration. This saves time during the blackout period. This script validates that: • A valid value is specified for the profile option GR: Default Warehouse. WIP.1. where the final data transformation takes place. Version 1. and FPO batches to be automatically recreated in Release 12.1. • Each Regulatory Item has an associated CAS number.1: • All completed batches must be closed. Any migration messages that are logged by this validation must be reviewed. • Users must execute the Process Batches for Migration snapshot procedure from the Batches tab for pending. • A valid value is specified for the profile option FM: Yield Type is not NULL.5. but the data is not completely.0 Page 3 of 6 . Early Migration of Items.5. Process Execution Batches The following actions are required prior to moving Oracle Process Execution batches to Release 12.1. addressed before progressing to the inline phase of the migration. The Forecast Set Name field was added in 11. and addresses prior to the blackout period. Orgs. This ensures that all transactions related to closed batches have been properly booked. These steps can be found in the Oracle Process Manufacturing Order Fulfillment to Order Management Migration documentation available on OracleMetalink. Warehouses. batches can no longer be manipulated until after the migration to Release 12. GL Export. Order Fulfillment to Order Management While the Release 12.1.10. and Addresses Users can migrate items.1 • All ingredients in the item concentrations table can be converted to the product’s unit of measure.10. organizations.1 install includes the migration of Order Fulfillment to Order Management. • The Subledger Update. This value is used as the owner organization for migrated standalone Regulatory formulas. as that value is required for a Regulatory Item in Release 12. This value is used as the unit of measure code for migrated standalone Regulatory formulas.Regulatory Management Validation If OPM Regulatory Management has been implemented in 11. and where required. and Journal Import scripts must be run prior to migration. warehouses. Process Forecast to Discrete Forecast In R12. Migration to this table will occur only if the OPM forecasts have a forecast set name. After this procedure has been run. Forecasts will be defined in a common forecast table.updated with all of the required process related values until the installation of Release 12. the Regulatory Management validation script must be run.

Lot_Number. The script performs the following actions: • Updates Organization_Id. Post Migration Phase Common Transformation The Common Transformation must be run after the successful migration of all data during the inline phase. Any migration messages that are logged during this phase of the migration must be reviewed. This script manipulates the migrated data so that it works properly in the new Oracle Inventory organization and structure. • Updates PO shipment lines • Updates Receiving tables Any migration messages logged by this script and must be reviewed. Version 1.1.Inline Migration Phase The migration is phased so that data is processed in a logical order. In the event that a script does not migrate or transform the data properly. addressed before progressing to the inline phase of the migration. the previous scripts must be run again. Inventory_Item_Id. • Migrates move orders for Order Management. addressed prior to commencing business in Release 12. The migration scripts support this phased approach. and where required. and stability studies • Migrates Process Execution profiles and WIP entities • Migrates item categories and item lot conversions. and where required. and Unit of Measure columns in the Product Development. samples. and Process Planning tables • Migrates specifications.0 Page 4 of 6 . Process Execution.

This script performs the following data migration and transformation: • Migrates resource details.1. lot costs. Any migration messages logged by the concurrent program must be reviewed. lot cost adjustments. lot costing item setup. Any migration messages logged by this script and must be reviewed. item costs. • Migration of account mappings and various data intensive GMF entities to SLA.1. cost component details. Version 1. lot costing material transactions. 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. When a sublot is migrated to Oracle Inventory. Sublots are modeled as Parent/Child lots in the converged model. 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. and where required. addressed prior to commencing business in Release 12. Receiving lot and lot supply transactions are updated for the lot number field representing the parent/child lot combination in the common inventory model.Cost Management Post-Migration The Cost Management post-migration script completes the data transformation for the Cost Management module.1. Batch Recreation The Batch Recreation concurrent program must be run to recreate the WIP. addressed prior to commencing business in Release 12.1. Pending. addressed prior to commencing business in Release 12. and where required. and FPO Batches that were unreleased and canceled during the snapshot taken during pre-migration. burden details. 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. • If multiple companies are migrated to the same Legal Entity. Regulatory Management Post-Migration The Regulatory Post-Migration script must be run to migrate Regulatory Items and their associated data. the Parent lot field is left blank and the lot field contains the lot number. standard cost ledgers. This script renames the old version of the batch appended with a -M and creates the new batches with the same batch number. and where required. 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. addressed prior to commencing business in Release 12. Any migration messages logged by this script and must be reviewed. For a sublot-controlled item with a blank or NULL sublot field. actual cost ledgers.0 Page 5 of 6 . adjustment details. the script copies the existing costs appropriately. lot costing burdens. and where required.

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