Beruflich Dokumente
Kultur Dokumente
The following is intended to outline our general product direction. It is intended for information purposes only, and may not be incorporated into any contract. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described for Oracles products remains at the sole discretion of Oracle.
Agenda
Migration Documents
Support Note Migration Checklist OPM Migration Messages and Technical Reference
Data
How data is migrated Data NOT migrated
Q&A
Migration Documents
These documents are available to help customers understand the migration process and to help guide them through the process.
OPM Migration Overview and Business Needs Guide OPM Migration Best Practices
This document contains an overview of the OPM Migration process and the business needs that are met by this process.
This document contains helpful tips to help ensure that the migration process proceeds as smoothly and as efficiently as possible. This document provides information on how the 11.5.10 Oracle Process Manufacturing data is mapped to the converged R12.1 Oracle Inventory model, and the User Interface and options available for the mapping of that data. This document lists all steps and patches needed to migrate data from Oracle Process Manufacturing Release 11.5.10 to 12.1. in the order in which they must be applied. This document lists the messages that can be logged during the running of the data migration and the actions required based upon those messages. The names of the individual migration scripts and Data Mapping tables are also available in this document.
The Checklist and Best Practices documents are live documents and will be updated as needed.
2011 Oracle Corporation Proprietary and Confidential
Preparation: These 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.
2. Pre-Migration: These steps are performed while the system is still available for use by endusers. 3. Blackout: These steps are performed prior to Upgrade Patch Installation 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 R12 Upgrade drivers . 4. Post-Migration: These steps are performed after the application of the R12 Upgrade and before bringing the system back up and allowing users to log on.
Existing - All inventory balances, recipes, etc are migrated to this existing
(in mtl_parameters) organization. This organization must be Process Enabled.
Inactive Will migrate all of the related data (inventory balances, recipes,
etc) and will end date the organization on the R12 side. This will prevent the organization from being transacted against in R12 but will allow for the viewing of historical data.
None Will not migrate any existing data related the org. The organization
must be marked as Inactive in OPM in order for this option to be chosen.
2011 Oracle Corporation Proprietary and Confidential
11i
12
OPM Resource Costs are defined at the Inventory Org level. All OPM document are defined at Inventory Org level Inventory Balances at a Inventory Org and SubInventory Level
OPM
Inventory Org
CWE
Inventory Org
RME
Inventory Org
FGE
Inventory Org
CWE
Warehouse
RME
Warehouse
FGE
Warehouse
OPM
Subinventory
CWE
Subinventory
RME
Subinventory
FGE
Subinventory
New Entities
OPUS Ledger
LE Legal Entity
OPME Organization
OPE
Inventory Org
CWE
RME
FGE
Migrate as Subinventory
CWE
Warehouse
RME
Warehouse
FGE
Warehouse
CWE
RME
FGE
CWE
RME
FGE
New Entities
OPME Organization
CWE
Inventory Org
RME
FGE
CWE
Warehouse
RME
Warehouse
FGE
Warehouse
CWE
RME RME
FGE
Lot Conversions
Inventory Balances
Logistics Migration
Planning Migration
Costing Migration
Regulatory Migration
Pre-Migration
Completed batches are closed. Batches and FPOs in Pending or WIP status are snapshotted copied to migration tables with the current state (material transactions, resource transactions, steps, etc) reflected. WIP batches are unreleased (set back to Pending) and all open batches and FPOs are cancelled.
Post-Migration
Renames old version of the batch, appends M Creates new batches (with the same batch number) from the snapshot data. Pending transactions are re-created as reservations If the batch had been in WIP status prior to migration, the batch is released. Completed transactions are re-created as allocations
OPM Financials
Moving from MAC to SLA
OPM MAC module will be obsoleted. OPM Event model will be mapped to SLA event model. Account Titles will be replaced with Journal Line Types in SLA. Account Mapping functionality will be replaced with Accounting Definition Rules (ADRs) in SLA. (NOTE: If your company maintains a large number of accounting mapping rules, it may be advantageous to manually define ADRs as opposed to using the default migration.) Test Subledger will be replaced with TAB Test Accounting Methods Builder. Subledger code will be retained to use as extract program in SLA.
OPM Quality
Migrates specifications, samples, and stability studies to the appropriate organizations and subinventories
Process Execution
Migrates GME profiles and WIP entities Open Batch/FPO Migration
OPM Logistics
Migrates move orders for Order Management Updates PO shipment line with uoms and secondary quantities Updates Receiving tables with uoms and secondary quantities
OPM Costing
Migration of resource details, cost component details, standard ledgers, actual cost ledgers, adjustment details, burden details, item costs, lot costs, lot cost item setups, lot cost adjustments, lot costing material transactions, lot costing burdens If multiple companies are migrated to the same Legal Entity then the scripts copy existing costs appropriately Migration of account mappings and GMF entities to SLA
Regulatory Management
Migration of Regulatory Items to INV Migration of Regulatory Standalone Formulas to GMD with a validity rule for Regulatory Use Update of Dispatch History records with the appropriate org id and item id.
Old lots that no longer have inventory nor are they associated to any documents (batches, quality samples, etc.) Lot genealogy Inactive items that are not associated to a document such as a batch or formula. A new patch has been created to allow customers to migrate/update items and attributes that were not migrated/updated as part of the inline migration for a given organization (Patch 10405668). Discrete organization/item data is not touched during migration
Run the Pre-Migration Validation script for all products and correct all errors Optionally migrate all organizations and items. Associate Forecast Sets to Forecasts
Q U E S T I O N S A N S W E R S
Appendix
2011 Oracle Corporation Proprietary and Confidential
Discrete Inventory
Organizations Organizations and/or Subinventories Stock Locators Master Items and Organization Items
Discrete Inventory
Transaction Reasons Organizations Organizations and/or Subinventories Stock Locators Master Items and Organization Items Action Codes Grades Material Statuses Item Types Organization specific Parent Lots/Lots (no id reference key element is lot_number) Lot Specific Conversions Inventory Balances
Discrete Inventory
Master Items and Organization Items Formulas and Recipes Item Relationships PO Hazard Classes PO UN Numbers Item Revisions CAS Number
ASCP
Forecasts
Discrete Inventory
Org ID Inventory Item ID Lot Number UOM Code (3 Character)
Sources
Account Titles Sub-Event Account Title Templates Account Unit Mappings & Account Mappings (per account title) Account Selection Priorities
Test Mapping
Inventory Migration
Action Codes Grades Category Sets Inventory Types Lot Status
Item Categories Lot Conversions Process to Discrete Transfer Calls Inventory Balance Calls Item & Lot Migration