6-11Understanding the OPM 11.5.10 to R12 Data Migration

5/27/2018 6-11Understanding the OPM 11.5.10 to R12 Data Migration

1/46

Understanding the OPM 11.5.10 to R12

Data Migration Process

Melanie Grosser, Oracle EBS Process Manufacturing Applications Architect


2/46 2011 Oracle CorporationProprietary and Confidential

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 berelied 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

Convergence Migration Setup UI

Organizations

Warehouses

Data

How data is migrated

Data NOT migrated

Migration Process Overview- User Interaction Perspective

Pre-Migration

In-Line (Blackout Period)

Post-Migration

Q & A


4/46

Migration Documents



OPM 11.5.10 to 12.1 Migration DocumentsSupport note 376683.1

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

This document contains an overview of the OPM Migration process and the business needs thatare met by this process.

OPM Migration Best PracticesThis document contains helpful tips to help ensure that the migration process proceeds assmoothly and as efficiently as possible.

OPM Migration Reference GuideThis document provides information on how the 11.5.10Oracle Process Manufacturing data ismapped to the converged R12.1 Oracle Inventory model, and the User Interface and optionsavailable for the mapping of that data.

OPM Migration ChecklistThis document lists all steps and patches needed to migrate data from Oracle ProcessManufacturing Release 11.5.10 to 12.1. in the order in which they must be applied.

OPM Migration Messages and Technical ReferenceThis document lists the messages that can be logged during the running of the data migrationand the actions required based upon those messages. The names of the individual migrationscripts and Data Mapping tables are also available in this document.

The Checklist and Best Practices documents are live documents and will beupdated as needed.



OPM Migration ChecklistThe Checkl is t is a l ive docum ent and wi l l be upd ated with n ewpatches/changes as needed. ALWAYS check for an updated versionpr ior to star ting a m igration run.

All steps are mandatory except where SPECIFICALLY noted. All steps must be performed inthe order in which they are presented. DO NOT PROCEED to the next step/phase until eachstep has successfully completed (No errors/all errors resolved). All patches must beinstalled in the order specifiedPatch Merge functionality CANNOT be employed acrosssteps.

The Checklist Steps are divided into four Phases:

1. Preparation:These steps are performed in preparation for migration planning. The informationcontained in the referenced documents and note help to explain the overall OPM Migrationprocess and recommendations for ensuring a smooth, successful migration.

2. Pre-Migration:These steps are performed while the system is still available for use by end-users.

3. Blackout:These steps are performed prior to Upgrade Patch Installation The following stepsare performed after end-users are no longer allowed to log into the system, but before thesystem is taken offline to apply the R12 Upgrade drivers .

4. Post-Migration:These steps are performed after the application of the R12 Upgrade andbefore bringing the system back up and allowing users to log on.



OPM Migration ChecklistI t is STRONGLY RECOMMENDED that the checkl is t be fi l led ou t appro priately as

you pro gress throug h the steps.



Migration Messages and Technical ReferenceMigrat ion Messages

This part of the document l is ts the messages that can be logged dur ing the

runn ing of the data mig rat ion and the act ions required based upo n those

messages.

GMI: Process Inventory



Migration Messages Log ViewerOPM System Adm inistrat ion > View Migrat ion Log



Migration Messages and Technical ReferenceMigrat ion Fi les

This part of the docum ent l is ts the names of the indiv idual migrat ion sc r ipts

and the ent i t ies that are migrated by each s cr ipt .



Migration Messages and Technical ReferenceTable Mapp ings

This part of the do cum ent con tains the table mappin gs from OPM 11.5.10 to

R12. The tables are l is ted by prod uct . Obsolete colum ns are denoted as such .


12/46

Migration Setup Form


13/46

2011 Oracle CorporationProprietary and Confidential

Convergence Migration Setup UI:Organization Tab

Activates On-Hand

Material Statuslevel tracking


14/46


Convergence Migration Setup UIOrganizat ion Migrate As Opt ions

NewCreates a new organization with the specified Organization Name.

Validates that an organization of the same name (not organization code)does not already exist. All inventory balances, recipes, etc are migrated tothis new organization. Requires the specification of a Template Org (anexisting org in mtl_parameters) that will be used for the setting of orgparameter values while creating this new org. The Template Org must usethe same Set of Books as the organization being migrated.

Existing-All inventory balances, recipes, etc are migrated to this existing(in mtl_parameters) organization. This organization must be ProcessEnabled.

InactiveWill 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 theviewing of historical data.

NoneWill not migrate any existing data related the org. The organizationmust be marked as Inactive in OPM in order for this option to be chosen.


15/46


Convergence Migration Setup UIWarehouses Tab


16/46


11i 12

Warehouse Mapping Considerations

Inventory Balances at a Warehouse

Level

Inventory Balances at a Inventory Org

and SubInventory Level

Resource Costs are defined

at the OPM Organization level

OPM Resource Costs are defined

at the Inventory Org level.

All documents are defined

at OPM Org (Plant) level

All OPM document are defined

at Inventory Org level

Costing and Planning:

Process is at Warehouse level

Discrete is at Inventory Org level

Costing and Planning is done at the

Inventory Org level

The following should be considered when deciding whether to migrate awarehouse as an inventory organization or a subinventory.

O i ti d W h M i


17/46


OPM Organization migrates as a new inventory organization andwarehouses remain as inventory organizations

Interorg transfers required for production

Organization and Warehouse MappingDefault Migrat ion

OPMCCompany

OPMEOrganization

CWEWarehouse

RMEWarehouse

FGEWarehouse

LELegal Entity

CWEInventory Org

RMEInventory Org

FGEInventory Org

R11iR12

CWESubinventory

RMESubinventory

FGESubinventory

OPMInventory Org

OPMSubinventory

OPUSLedger

OPUOperating Unit

New Entities

O i ti d W h M i


18/46


OPM Organization migrates as a new inventory organization.

Warehouses moved as Subinventory under the new inventoryorganization.

These warehouses must belong to the same cost warehouse.

Organization and Warehouse MappingAlternate Example 1

OPMCCompany

OPME

Organization

CWEWarehouse

RMEWarehouse

FGEWarehouse

CWE RME FGE

R11i R12

CWE RME FGE

OPEInventory Org

CWE RME FGE

Migrate asNew

Migrate asSubinventory

LELegal Entity

OPUS

Ledger

OPUOperating Unit

New Entities

O i ti d W h M i


19/46


OPM Organization migrate to one of its warehouse inventory

organization Warehouses with the same cost warehouse can be selectively

moved as Subinventory to the org mapped above.

Migrate asSubinventory

Organization and Warehouse MappingAlternate Example 2

OPMCCompany

OPMEOrganization

CWEWarehouse

RMEWarehouse

FGEWarehouse

CWEInventory Org

RME FGE

R11i

CWE RME FGERME

Migrate asExist ing

R12

LELegal Entity

OPUSLedger

OPUOperating Unit


20/46

Data - What is and isnt migrated?


21/46


OPM Data MigrationOrder of Migrat ion Dependenc ies

Inventory Types

OPM Category Sets

Actions

Grades

Organizations/

Warehouse/

Locations

Transaction Types

Reason Codes

Lot Status

Update Existing OPM Items

in DiscreteCommon Upgrade Scripts

Item Creation/ Migration

Lot Create Migration

Lot Conversions

Inventory Balances

New Product Development

Migration

Process Execution

MigrationProcess Quality Migration

Costing Migration Regulatory MigrationPlanning Migration

Logistics Migration


22/46


Open Batch and FPO Migration Process

Pre-Migration Completed batches are closed.

Batches and FPOs in Pending or WIP status are snapshotted copied tomigration tables with the current state (material transactions, resourcetransactions, steps, etc) reflected.

WIP batches are unreleased (set back to Pending) and all open batches andFPOs 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

Only documents in a Pending or WIP status can be included in thesnapshot. Batches that are not included in the snapshot (re-

created) cannot be transacted in R12.


23/46


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 withAccounting 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 TABTest Accounting

Methods Builder.

Subledger code will be retained to use as extract program in

SLA.


24/46


Other Product Migrations Common Transformation

Updates columns in NPD, GME and GMP tables with the appropriate values for Org ID, InvItem ID, Lot Number, and units of measure

OPM Quality Migrates specifications, samples, and stability studies to the appropriate organizations andsubinventories

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 costadjustments, 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.


25/46


Data NOT migratedData is st i l l viewable in R12 from read-only versions

of the old forms

Historic Transactions - data in ic_tran_pnd and ic_tran_cmp

Planning Setups OPM Warehouse, Production, & Transfer Rules not migrated as they do

not directly map to ASCP Sourcing Rules

Item Lead-times from MRP

Old lots that no longer have inventory nor are they associated toany documents (batches, quality samples, etc.)

Lot genealogy

Inactive items that are not associated to a document such as abatch or formula.A new patch has been created to allow customersto migrate/update items and attributes that were not

migrated/updated as part of the inline migration for a givenorganization (Patch 10405668).

Discrete organization/item data is not touched during migration
http://bugpriority.oraclecorp.com/pls/bugpriority/BUGPRI.ECMS_ADHOC.SHOW_BUG?P_BUG_NUMBER=10405668&P_URL_FROM=Ohttp://bugpriority.oraclecorp.com/pls/bugpriority/BUGPRI.ECMS_ADHOC.SHOW_BUG?P_BUG_NUMBER=10405668&P_URL_FROM=O


26/46

Migration Process- User Interaction Perspective


27/46


Migration Process- User Interaction

PerspectivePre-Migration

Map the Company, Organization, Warehouse, Items,

and Quality data using the Convergence Migration

Setup user interface.

Prepare Costing Data for migration Run Actual SubLedger Update

Execute GL Export

Execute Journal Import

Run the Pre-Migration Validation script for all products

and correct all errors

Optionally migrate all organizations and items.

Associate Forecast Sets to Forecasts


28/46



PerspectiveIn-l ine (B lacko ut Period )

Review, act upon, and dispose of information inOracle ASCP interface tables

Review, act upon, and dispose of information in theOPM MRP interface

Process Batches for migration Complete or cancel all pending transfers and Internal

Sales Orders

Backorder or ship OPM Order Fulfillment sales orders

that are pick confirmed or staged prior to migration Run Preliminary Inventory Close Process

RUN GMF Data validationCorrect all errors


29/46



PerspectivePost -Migrat ion Steps

Run OPM Data Transformation

Run OPM Financials Data Transformation

Migrate OPM Regulatory data

Recreate Open Batches Migrate OPM Edit Text to attachments

Update items attributes for MRP/MPS and Lead times

for migrated items for ASCP planning

Run Planning Manager Run script to update additional existing org/item

definitions (Optional)


30/46


Q U E S T I O N SA N S W E R S


31/46


Appendix


32/46


OPM Inventory Data MigrationPre-Migration Phase

OPM Inventory Discrete InventoryOrganizations (Optional) Organizations

Warehouses (Optional) Organizations and/or Subinventories

Locations (Optional) Stock Locators

Items (Optional) Master Items and Organization Items

.

OPM I D Mi i


33/46


OPM Inventory Data MigrationIn-Line Phase

OPM Inventory Discrete InventoryReason Codes Transaction Reasons

Organizations Organizations

Warehouses Organizations and/or Subinventories

Locations Stock Locators

Items Master Items and Organization Items

Action Codes Action Codes

Grades Grades

Lot Statuses Material StatusesInventory Types Item Types

Lots/Sublots (lot_id) Organization specific Parent Lots/Lots (no idreference key element is lot_number)

Lot Specific Conversions Lot Specific ConversionsInventory Balances Inventory Balances

.

OPM R l t D t Mi ti


34/46


OPM Regulatory Data MigrationPost-Migrat ion Phase

OPM Regulatory Discrete InventoryRegulatory Items Master Items and Organization Items

Standalone Regulatory Formulas Formulas and Recipes

Master Item Associations Item Relationships

Hazard Classifications PO Hazard ClassesUN Numbers PO UN Numbers

Item Version Item RevisionsPrimary CAS Number CAS Number

.

OPM Pl i D t Mi ti


35/46


OPM Planning Data MigrationIn -L ine Phase

OPM Planning ASCPForecasts Forecasts

.

OPM C T f ti


36/46


OPM Common TransformationsIn-Line Phase

Updates columns in GMD-New Product Development

(Formulas, Recipes, Validity Rules, etc), GME Process

Execution (Batches, Batch Resources, etc) and GMD-Quality

(Specifications, Validity Rules, Samples, etc.) tables.

OPM Inventory Discrete InventoryOrganization ID Org ID

Item ID Inventory Item ID

Lot ID Lot Number

UM Code (4 Character) UOM Code (3 Character)

.

OPM GMD NPD D t Mi ti


37/46


OPM GMD-NPD Data MigrationIn-Line Phase

OPM GMD-NPD 11i OPM GMD-NPD 12.1

New Product Development Profiles Options New Product Development Parameters

Recipe Owner/Master Org Recipe Types (General/Site/Master)

.

OPM GMD Q lit D t Mi ti


38/46


OPM GMD-Quality Data MigrationIn-Line Phase

OPM GMD-Quality 11i Discrete Inventory/OPM GMD-Quality 12.1

OPM GMD-Quality Profiles Options OPM GMD-Quality Parameters

Stability Studies Organization Specific Stability Studies

Quality Actions Action Codes

Grades Grades

.

OPM P E ti D t Mi ti


39/46


OPM Process Execution Data MigrationIn-Line Phase


OPM Process Profiles Options OPM Process Parameters

.

OPM Process Execution Data Migration


40/46


OPM Process Execution Data MigrationPre-Migration Phase


Open Batches Batch Snapshot

.

OPM Process Execution Data Migration


41/46


OPM Process Execution Data MigrationPost-Migrat ion Phase

OPM Process Execution 11i Discrete Inventory/OPM ProcessExecution

Snapshot of Open Batches Renames Old Batches, Recreates OpenBatches

Specifications, Samples, Results againstbatches

Specifications, Samples, Results updatedbased upon new batches/ids.

Quality Actions Action Codes

Grades Grades

.


42/46


OPM Financials Data Migration

In-Line Phase

Data is m igrated to the appropriate LE/Organizat ion

Cost Types

Fiscal Policies

Lot Cost Type

GMF Data Transformation (update of ids, uoms etc) Expense Allocation Basis

Expense Allocation Codes Expense Allocation Expenses Expense Allocation Inputs Burden Priorities Cost Calendar Assignments Material Cost Components Event Fiscal Policies Fiscal Policies Item Cost Component Details Cost Warehouses Costing Items


43/46


OPM Financials Data MigrationPost-Migrat ion Phase

Data is m igrated to th e app rop r iate LE/Organizat ion

Burden Percentages Item Cost Component Details Resource Details Actual Cost Adjustments Item Cost Component Details Burden Details Item Costs Lot Costs Lot Costed Items Lot Cost Burdens Lot Cost Adjustments Material Lot Cost Transactions Standard Cost Ledgers Actual Cost Ledgers Account Mappings to SLA Account Derivation Rules (May wish to manually create

ADRs) Period Balances

Source Warehouses Actual Cost control data Rollup Control Records Cost Update control data Subledger control data


44/46


OPM Financials MAC to SLA

MAC Seed Data SLA Seed DataEvents, Sub-Events SLA Event Entities, SLA Event Entity Classes,

SLA Event TypesSources SLA Process CategoriesAccount Titles Journal Line Types (JLT) as well as TAB

definitions.Sub-Event Account Title Templates Application Accounting Definitions (AAD)Account Unit Mappings & Account Mappings

(per account title) Account Derivation Rules (ADR) (per JLT)Account Selection Priorities Will be used to derive the sequencing of ADR

conditions for migration.New ADR definitions will have to explicitly

set up the sequencing of the conditions tomimic the priority

Test Mapping Test Transaction Account Builder (TAB)function

The following seed data entities in OPM MAC will be migrated to SLA seed data as shown.


45/46


OPM Costing Data MigrationOrder of Migrat ion Dependencies


46/46

Inventory Migration

Action CodesCategory

Sets

Inventory

TypesLot Status

Inventory

Balance

Item Categories

Lot

Conversions

Org/Whse/

Locations

Item & Lot

Migration

Calls

Grades

Item Upgrade

Process to Discrete

Transfer

Calls

Date post:	18-Oct-2015
Category:	Documents
Upload:	ggangad
View:	87 times
Download:	2 times