Migration R12 Overview

<Insert Picture Here>

R12 Migration Overview

© 2006 Oracle Corporation – Proprietary 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 be relied upon in making purchasing decisions.The development, release, and timing of any features or functionality described for Oracle’s products remains at the sole discretion of Oracle.


Migration Deep Dive


R12 Migration - 3 Phases:

• Get to current release level of Production and Quality

• Map Organization Structure

• Migrate Items and Organization Hierarchy

Pre-Migration Black Out Period Post-Migration

• Clean-up batches; snapshot of open batches

• Complete / close transfers• Backorder or Ship Sales

Orders• Run Preliminary Close and

Cost Processes• Post transactions to OPM

Subledger and export to GL

• OPM / Financial Data Transformation

• Re-create Open Batches from Snapshot

• Optional: • Migrate Regulatory Data• Migrate Edit Text to

Attachments


Pre-Migrations Steps Perform when the system is live11i.7 or Lower:Run the original OPM Process Execution validation

Metalink Doc: 376683.1

Map the data using Convergence Migration Setup UI; Apply patch 4563075Metalink Doc: 376683.1

Run SQL Validation Scripts; Apply patch 4699061Metalink Doc: 376683.1

11i.6 or Higher: (Optional)Migrate OPM Organizations and items;Apply patch 4582937

11i.8 or Lower:Run the original OPM QC to QMmigration and validationApply patch 5102439

11i.9 or Lower:Create new field – Forecast Set on Forecast HeaderApply patch 4268525

On to Data Migration Steps

Update Forecast Headers to have a value entered in Forecast Set


Planning Data Migration Steps All users must be logged out of the application

ASCP Users:

Review /Correct issues fromGMP_APS_Output_TBLGMP_APS_Output_DTL

OPM MRP Users:

Review /Correct issues fromMR_ACTN_TBL

To Batch Migration


Batches Data Migration Steps All users must be logged out of the application

11i.7 or Lower:

Prepare for the batch snapshotApply patch 4458028

Close all batches with astatus of Completed Batches Tab: Action >>Mass Batch Close

OracleMetalink 376683.1

Capture snapshot of Open Batches“Process Batches forMigration” Button

11i.8 or Higher:

Prepare for the batch snapshotApply patch 4458024

On to Logistics Steps


Data Migration Steps All users must be logged out of the application

OPM/OM Users:Backorder or ship salesorders that are pick confirmed or staged prior to migration

Run Preliminary Inventory Close

Complete or cancel pending transfers

Apply patch 4350832

From Pre-Migration

Note: Do not run Final Inventory Close for the period in which you are running the R12 upgrade.


Data Migration Steps All users must be logged out of the application

Run GMF Validation Scripts


On to Post - Migration Steps

OPM OF Users:Migrate to OracleOrder Management


All Costing Users: Post transactions to OPM Subledger and export to GL

Actual Cost Users: Run Actual Cost Process;

Lot Costing Users: Run Lot Cost Process;

Note: Once you upgrade you will not be able to post the transactions created prior to the upgrade.


Post Migration Steps Complete before you bring your system back up

OPM Data Transformation

Apply patch 4689881

OPM FinancialsData TransformationApply patch 4690072

Migrate OPM Regulatory data (optional)Apply patch 4688012

Recreate open batches Run Recreate Open Batches

View Migration Log and Fix Errors

Migrate OPM Edit Text to Attachments Run the GMA: Edit Text Migration

Bring up System and Celebrate a

Successful Upgrade


OPMWarehouse

WarehouseLocation

Plant or Lab

OPM Company

Organization Structure Changes

Additional restrictions for Process

Inventory Org

Set of Books

Legal Entity

Locator

Subinventory

Operating Unit

Master Org

OPM Organizations


Existing R11i Org Mapping Example

OPMCCompany

OPMEOrganization

CWEWarehouse

RMEWarehouse

FGEWarehouse

OPUOperating Unit

CWEInventory Org

RMEInventory Org

FGEInventory Org

Process Discrete

OPMUSSet Of Books

CWESubinventory

RMESubinventory

FGESubinventory

LELegal Entity


11i 12

Business Rules

Inventory Balances at a Warehouse Level

Inventory Balances at a Inventory Org or SubInventory Level

Resource Costs are defined at the OPM Organization level

OPM Resource Costs are defined at the Inventory Org level.

All documents are definedat 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


• OPM Organization migrates as a new inventory organization and warehouses remain as inventory organizations

• Interorg transfer required for production

R12 Org Mapping – Default Migration

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


• OPM Organization migrates as a new inventory organization.• Warehouses moved as Subinventory under the new inventory organization.

• These warehouses must belong to the same cost warehouse.

R12 Org Mapping – Alternate 1

OPMCCompany

OPMEOrganization

CWEWarehouse

RMEWarehouse

FGEWarehouse

CWE RME FGE

R11i R12

CWE RME FGE

OPEInventory Org

CWE RME FGE

Migrate as New

Migrate as Subinventory

LELegal Entity

OPUSLedger

OPUOperating Unit

New Entities


• 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 as Subinventory

R12 Org Mapping – Alternate 2

OPMCCompany

OPMEOrganization

CWEWarehouse

RMEWarehouse

FGEWarehouse

CWEInventory Org

RME FGE

R11i

CWE RME FGERME

Migrate as Existing

R12

LELegal Entity

OPUSLedger

OPUOperating Unit


Convergence Migration Setup UI: Company Tab


Convergence Migration Setup UI: Organization Tab R12.1 New

Default On-Hand Material

Status


Convergence Migration Setup UI: Warehouses Tab


Convergence Migration Setup UI: Items Tab


Convergence Migration Setup UI: Lots/Sublots Tab – REMOVED for R-12.1


Convergence Migration Setup UI: Quality Tab


Convergence Migration Setup UI: Batches Tab


Log Viewer


Pre-Migration Items, Orgs, Warehouses, and Addresses

• Release 11.5.6 or higher run pre-migration steps• Data ensured for accuracy – run this migration• Saves time during the blackout period

• Release 11.5.5 or lower – cannot run early migration


Pre-Migration Inventory

• Run OPM Inventory validation script• Displays items without auto lot numbering set up• Verifies descriptive flexfield setup for duplicates

• OPM Inventory item master• Oracle Inventory item master• Displays lot status conflicts

• Cancel or complete pending transfers• Run Preliminary close


Pre-Migration Process Execution Batches

• Clean up erroneous data before migration• Release 11.5.8 and below

• Must run original validation script and correct errors

• All Releases prior to moving to R12• All completed batches must be closed• Pending, WIP, FPO auto-recreate in R12 • Complete Process Batches for Migration snapshot


Pre-Migration Quality

• Release 11.5.8 and below• Must run original migration validation script (QC to QM)• Correct any errors before quality transactions are processed

for migration

• Convergence Migration form – Quality Tab• Set Stability Studies default Org. code to valid value• Before Blackout run validation script verifying it is set properly


Pre-Migration Cost Management and MAC

• R 12 - OPM Companies are migrated to Legal Entities• Ability in Pre-migration to change legal entities

• Multiple OPM Companies pointing to same legal entity• Choose to migrate companies to their own legal entity• Must be done before the migration

• If Actual Cost/Lot Cost user run relevant process• Post transactions to OPM Subledger and Export to GL• Run Cost Management validation script

• Checks for unposted inv., resource, closed batch transactions• Actual costing – looks for active transaction in open period• If found – raises a warning, must be corrected


Pre-Migration Regulatory Management

• Must run validation script• Checks profile GR: Default Warehouse is not NULL• Checks profile FM: Yield Type is not NULL• Each Regulatory Item has associated CAS number• Ingredients in item conc. table can be converted to Product’s

UOM• Script returns log file displaying any failures


Pre-Migration Order Fulfillment to Order Management

• Backorder or ship sales orders that are pick confirmed or staged prior to migration

• OPM OF users migrate to OM


Pre-Migration Process Forecast to Discrete Forecast

• Below 11.5.10 must apply patch 4268525• Enter Forecast Set Name for all forecasts to migrate


Inline Migration (Blackout)


Post-Migration (Blackout)

• After Release 12 has been installed • All data must be checked to ensure accurate migration• Review log files “View Migration Log”

• Rerun migration if necessary• Data not migrated correctly• Migration did not complete


Log Viewer


Post-Migration 1st patchCommon Transformation Patch

• Run common transformation patch• Updates Org ID, Inv Item ID, Lot Number, UOM columns in

NPD, GME, GMP• Migrates specifications, samples, and stability studies• Migrates GME profiles and WIP entities• Migrates item categories and item lot conversions• Migrates move orders for Order Management• Updates PO shipment line• Updates Receiving tables


Post-Migration 2nd patchCost Management – complete data transformation

• Run Cost Management post migration patch• 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


Post-Migration 3rd patchRegulatory Management script

• Run Regulatory Management post-migration script• Creates records for regulatory item migration• Updates dispatch history records for organization and item• Migrates regulatory items to discrete• Migrates regulatory standalone formulas to Product Dev.


Post-Migration Batch Recreation

• Run concurrent program • Recreates WIP, Pending, and FPO’s• Renames old version of the batch appended with a –M• Creates new batches with the same batch number


Post-Migration Planning – Manual Setup Attributes

• Define Item attributes for ASCP• Inventory – MRP/MPP Tab, Lead-times Tab

• Create Souring Rules• OPM Warehouse, Production, & Transfer Rules not migrated


R-12.1 New Migration Information

• Organization – Default On Hand Material Status• Lot – On Hand Material Status, removes Lot Tab• Error Messages• Check List• Pre-Migration Patches• In-Line Migration Patches• Oracle Migration Team – proposed calls


Lot Status Migration Default Lot Migration behavior

If a lot / sublot exists in multiple locations with a different status, the system will migrate the largest quantity balance with the original Lot number as the Parent Lot and the Lot updates with the lot /sublot number concatenated.


Lot Status Migration Case 1A single Lot Status is associated with Lot Number, all locations have the same statusIn this case, there is a single lot status within a warehouse and the lot can be stored in multiple locations that are all “active”. The system will migrate the largest quantity balance with the original Lot number as the Parent Lot and the Lot updates with the lot /sublot number concatenated. The Locators will all have a status of active. As a result, the material status will be determined by the Lot level status.


Lot Status Migration Case 2Lot Status varies by location


Lot Status Migration Case 2 - ContinuedLot Status varies by location


Lot Status Migration Case 3Lots can be stored in multiple locators and have different statuses. The locator can contain lots with different statuses.

In this case, the lots you have may have a different status based on the location they are stored in and a given location co-mingles items with different statuses. As in Case 2, first run validation report which will identify the items with the same lot / sublot in locations with different statuses (highlighted below in Bold Italics). Next manually change the conflicting status to a status of your choose (such as “migrate”). The system will migrate the Lots and Sublots as previously described in case 1. The Status will be migrated to the Lot Status and all locators will have an “active” status as displayed in the table below:


Lot Status Migration Case 3 - ContinuedLots can be stored in multiple locators and have different statuses. The locator can contain lots with different statuses.


Lot Status Migration Case 3 - ContinuedLots can be stored in multiple locators and have different statuses. The locator can contain lots with different statuses.

Manually change all Lot Statuses to Active and move the inventory to the appropriate locators:This would result in the following transaction and data:


R-12.1 Error Messages


R-12.1 Check List


Pre-Migration R-12.1 New Patches

Phase Existing Patches Additional Patches

Patches Description

Pre-Migration 4582937 8340090 GMAUPGST.SQL NEEDS UPDATING

FOR DATA PROBLEM

8487779 R12MIG:LOCATOR_ID IN IC_LOCT_MST IS NOT UPDATED WHEN ORG IS MIGRATED IN

PRE-MIG

8584508 DUPLICATE INVENTORY ORG. CREATED BY SYSTEM AFTER R12

UPGRADE.


Pre-Migration R-12.1 New Patches –Continued

Phase Existing Patches Additional Patches

Patches Description

Pre-Migration 4699061 8466443 R12MIG:OL:NEED VALIDATION TO CHECK FOR SINGLE MASTER

ORGANIZATION

8466438 R12MIG:OL:NEED VALIDATION TO CHECK ORGANIZATION LINKED ON QUALITY

SAMPLES


In Line-Migration R-12.1 New Patches

Phase Patches Patches Description

In Line 8359386 R12MIG:VALIDATE_TRANSFER API TO VALIDATE THE LOCATION

EXISTANCE IN IC_LOCT_INV.

8363586 R12MIG: OPM INVENTORY BALANCE MIGRATION SHOULD

IGNORE DELETE_MARKED ROWS.

7513308 API INV_LOT_API_PUB.CREATE_INV_LOT DOES NOT INITIALIZE

MESSAGE STACK


Oracle Migration Team

• Proposed Calls• Oracle Development group• Support group• Strategy Product Management• Customer

• Before you begin the Migration Process• Arrange for your call• Contact

[email protected]

914-524-1606

mailto:[email protected]

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

<Insert Picture Here>

Thank You

Migration R12 Overview

Documents

Transcript of Migration R12 Overview