OPM Table Mapping

Version: 1.
12 Date Published: 16/12/2013 Page 1 of 67

ORACLE PROCESS MANUFACTURING
RELEASE 11I TO 12/12.1 MIGRATION
Migration Messages and Technical Reference

Date Published Version
December 16, 2013 1.12

Oracle Process Manufacturing (OPM) Release 11i to Release 12/12.1 - Migration Messages Overview 2
Pre-Migration Validation Messages ........................................................................................... 3
GMA: System Administration ................................................................................................ 3
GMD: Quality Management ................................................................................................... 3
GMI: Process Inventory .......................................................................................................... 4
GR: Process Regulatory .......................................................................................................... 6
GMF: Process Financials ........................................................................................................ 7
Migration Messages .................................................................................................................... 8
GMA: System Administration ................................................................................................ 8
GMI: Process Inventory ........................................................................................................ 17
GMF: Process Financials ...................................................................................................... 22
GME: Process Execution ...................................................................................................... 26
GML: Logistics ..................................................................................................................... 29
GMD: Quality Management ................................................................................................. 30
GMD: New Product Development ........................................................................................ 34
GR: Process Regulatory ........................................................................................................ 34
OPM Release 12/12.1 Migration Files..................................................................................... 37
Bucket - 1 (Run during Pre-Migration Phase): ..................................................................... 37
Bucket 2 (Run during the Inline Phase): ............................................................................. 37
Bucket 3 (Run during the Inline Phase): ............................................................................ 38
Bucket 4 (Run during the Post-Migration Phase): ............................................................. 39
Bucket 5 (Run during the Post-Migration Phase): ............................................................. 41

Version: 1.12 Date Published: 16/12/2013 Page 2 of 67
Oracle Process Manufacturing (OPM) Release 11i to
Release 12/12.1 - Migration Messages Overview

The following are log messages that can appear during the migration of data from OPM
Release 11i to Release 12/12.1. The messages are grouped by phase and then product.

It is EXTREMELY important that the log messages are checked and, where required,
addressed after each run of a given step of the migration. Failure to take the
required actions will cause a cascade of errors throughout the migration. For
example, the failure to migrate a number of inventory balances may be due to the
fact that there was a previous error while migrating a given warehouse.

To view the messages logged by logged during phases of the migration, go to the View
Migration Log function that is available from OPM System Administration Responsibility. The
messages can also be viewed by querying one of the following:

GMA_MIGRATION_LOG
The table that holds the messages with the error tokens other attributes such as message
type, tokens, values etc.

GMA_MIGRATION_LOG_V1
View based on the GMA_MIGRATION_LOG table with the translated message text (not
just the tokens).

There are three different types of messages that can appear in the log file:

1. Error - These messages are used to report database errors and data conditions that
prevent the migration from completing successfully. These messages require that
some action be taken to address these issues. These issues must be addressed
prior to progressing to the next step of the migration, and usually require that at least
the current step of the migration be re-run.

2. Warning - These messages usually appear during the running of the Pre-Migration
Validation scripts. The user has the option to ignore the message if the condition being
warned of is either expected or is not relevant. If no action has been taken, these
messages will also appear during the running of the migration.

3. Informational - These messages are used to note actions that have been taken as part
of the migration. They do not require any action on the part of the user.

NOTE: Words appearing within the "<" and ">" signs will be replaced with an actual value in
the message log.

Pre-Migration Validation Messages

GMA: System Administration

Migration Name Message Comments Action Needed
Pre-Migration
Validation
Value for template organization is
missing for organization
<ORGANIZATION>

Message Type: Error

All of the OPM organizations marked
to migrate as New on the
Convergence Migration Setup UI
must have an associated template
organization. Otherwise, an error
occurs for all organizations missing
the template organization
association.

Map template organizations for the
orgs marked to migrate as New
using the UI (OPM System
Administration >Convergence
Migration Setup)
Pre-Migration
Validation
Organization <ORGN_CODE>
cannot be defined as a child of
<ORGN_CODE2>and also be
used a master organization for
Organization <ORGN_CODE3>.

Message Type: Error

An organization cannot be defined
as a parent organization of another
organization if it has been defined as
a child of another organization. This
kind of circular reference is not
allowed.

Go to the Convergence Migration
Setup form and modify the
associations of the organizations.

GMD: Quality Management

Pre-Migration
Validation
Value for the profile "GMD: Default
Lab Organization" is missing.

Message Type: Error

An error is logged if the value for
GMD: Default Lab organization is not
set. This setting is used in the
Stability Study organization.
Set the value for this profile or set a
value on the Convergence Migration
Setup form on the Quality tab.
Pre-Migrate
Validation
There is a setup mismatch for
gmd_samples record with sample
id of <SAMPLE_ID>. Organization
Code is <ORG>and Whse Code is
<WHSE>. The organization id for
the orgn code is <ORGID>and the
organization_id for the whse is
<WHSE_ORG_ID>. They should
be the same. Check
Organization/subinventory setup.

Message Type: Error

The warehouse and OPM
organization that is referenced by
quality samples must maintain a
similar hierarchy to a subinventory
under the same inventory
organization. If the warehouse is
converted to a subinventory under a
different inventory organization, this
issue will occur.
Setup form and correct the issues
with the organization and warehouse
assocaitions.

GMI: Process Inventory

Pre-Migration
Validation

Item exists where Auto Lot
Numbering is not set up (Count =
<COUNT>).

Message Type: Informational

Logs the number of items that are
not set up for auto lot numbering.
Provide default values for the auto
lot numbering setup on the Migration
Setup UI >Items tab.

Pre-Migration
Validation
No open period for the current date
in Organization Id
<ORGN_CODE>(<ORGN_ID>)

Message Type: Warning

The inventory period is not currently
open for the specified organization.

Check to make sure that Inventory
calender is defined in Discrete. If
the Inventory Calendar does not
exist, manually create the calendar.
Open the period for the current date.
Pre-Migration
Validation
Negative balances exist for Item
<ITEM>, Lot <LOT_NO>, Sublot
<SUBLOT_NO>, Warehouse
<WHSE_CODE>, Location
<LOCT>.


Negative balances exist. This also
should have been noted during the
Pre-migration Validation so that
actions could be taken (receipts
completed, physical inventory taken,
etc) to correct this condition. The
balances are migrated.

None required.
Pre-Migration
Validation
Transaction processor error
Negative balances not allowed.


Negative balances exist and were
not addressed prior to the migration.
The organization on the discrete side
does not allow for negative
inventory.
Use the Inventory Super User
Responsibility and go to
Organizations >Parameters. Set
the Allow Negative Balances
indicator to yes. Re-run the
Inventory Balance migration.

Pre-Migration
Validation
Decimal dust balances exists for
Item <ITEM>, Lot <LOT_NO>,
Sublot <SUBLOT_NO>,
Warehouse <WHSE_CODE>,
Location <LOCT>.


A message is logged for item, lot,
sublot, warehouse and location
combinations where there is decimal
dust (<.00001) in the balance.
These residual decimal balances are
not migrated.

None required.
Pre-Migration
Validation
Mixed balances (Negative primary
and Positive secondary or vice
versa) for dual quantity exists for
Item <ITEM>, Lot <LOT>, Sublot
<SUBLOT>, Warehouse <WHSE>,
Location <LOCT>.


Mixed balances are not migrated
and should have been acted upon
during premigration validation.
These balances must be fixed using
the Process Inventory Quantity
Adjustments UI. Make sure that both
primary and secondary balances are
positive or negative. You must fix
these balances, otherwise these
balances will error out during the
migration.
Pre-Migration
Validation
Cannot migrate balances for non-
inventory item <ITEM_NO>.


inventory items because balances
should not exist for such items.
This should have also appeared as a
premigration validation message.
Customer should confirm that they
intended for the item to be set up as
non-inventory.

Pre-Migration
Validation
Both OPM and Discrete have the
descriptive flexfield context defined.
OPM=<OPM_CONTEXT>,
Discrete=<ODM_CONTEXT >
Column <
APPLICATION_COLUMN_NAME >
in OPM descriptive flexfield is also
used in Discrete. Context =
<DESCRIPT_FLEX_CONTEXT_C
ODE>, User Column Name=<
END_USER_COLUMN_NAME>

Message Type: Error

Desc flexfield column conflicts with
OPM context and ODM context.

Fix the descriptive flexfield using
Application Developer responsibility.
You can use one of the following
options to fix this issue:
1. Disable segment in OPM
descriptive flexfield. As a result,
OPM segment will not be
migrated to discrete.
2. Disable segment in Discrete
descriptive flexfield. As a result,
OPM segments will be migrated and
will override the discrete segment
values. Please use caution in
choosing this option.
3. Using SQL Plus, move the OPM
or Discrete segment values to a
different (non-conflicting) segment
and update the Descriptive flexfield
definition accordingly.

Pre-Migration
Validation
The WAREHOUSE is closed for the
date entered. The transaction is not
allowed.

Message Type: Error

An inventory period must be open
under Process Inventory for the
current date for the on hand
balances migration. An error is
logged for warehouses that have no
open period under Process
Inventory.

Open a period for the current date
(or the date when migration will be
run) using the Process Inventory
responsibility for the warehouses
that have non zero inventory
balances.
Pre-Migration
Validation
Attribute MTL_SYSTEM_ITEMS.
<ATTRIBUTE_FIELD>is controlled
at master organization level and
may result in migration issues if the
attribute values are different for
process and discrete organization.


The following attribute controls are
recommended to be set at the org
level:
ONT_PRICING_QTY_SOURCE
SECONDARY_DEFAULT_IND
SECONDARY_UOM_CODE
DUAL_UOM_DEVIATION_HIGH
DUAL_UOM_DEVIATION_LOW
ITEM_TYPE
AUTO_LOT_ALPHA_PREFIX
ENG_ITEM_FLAG
ITEM_TYPE
LOCATION_CONTROL_CODE
LOT_CONTROL_CODE
LOT_STATUS_ENABLED
START_AUTO_LOT_NUMBER
Warning messages are logged if
these are set for master org..

If the controls are not correct, then
change the attribute controls setting
using the attribute controls UI from
the Inventory Super User
responsibility.
Pre-Migration
Validation
The lot <LOT>exists with different
statuses in different locations.

Message Type: Error

This message is only applicable for
the migration to R12, not R12.1

Lots with different status existing
under different locations within the
same warehouse are logged. Lots
with different status cannot exist
under the same inventory org in
discrete in Release 12. This is
possible in Release 12.1.

Change the lot status using the
Process Inventory responsibility, or
set the lot numbers appropriately
using the Lots tab on the Migration
Setup form.


GR: Process Regulatory

Pre-Migration
Validation
Regulatory item data will not be migrated
because no Regulatory organization has
been specified.


This message can be ignored
if Regulatory Documentation
Management was not
implemented.

For Regulatory Item
Information to be migrated, at
least one organization must
be designated as a
Regulatory Org.

Setup form and set the Regulatory
Org checkbox for at least one
organization on the Organizations
tab.

Pre-Migration
Validation
Item <ITEM>has no value for CAS
number.

Message Type: Error

A Regulatory Item in R12/12.1
must have an a CAS number
associated with it, so if there
is no CAS number associated
in 11.5.10, the Regulatory
Item migration will fail.

Using the Regulatory Management
Responsibility, define CAS number
for the specified Regulatory item.
Pre-Migration
Validation
The value for profile option GR: Default
Organization is NULL.

Message Type: Error
An error is logged if the value
for GR: Default Organization
is not set. The default
organization is used as the
owner organization for the
standalone formula migration.

Use the System Administration
responsibility to set the value for this
profile at the Site level.
Pre-Migration
Validation
Item <ITEM>cannot be converted to unit
of measure for FM_YIELD_TYPE.

Message Type: Error

An error is logged if the
ingredients specified in the
item concentrations are not
convertible to the standard
uom derived from the GMD:
Yield Type UOM type.

Use the Process Inventory
responsibility to define the
conversion for the specified item.

GMF: Process Financials

Pre-Migration
Validation
<RECORD_COUNT>Unposted
Completed Inventory transaction records
exist for the Period <PERIOD>in
Company <CO_CODE>. Please run Sub-
Ledger update before proceeding.

Message Type: Error

An error is logged if there are
unposted completed
transactions existing in
IC_TRAN_CMP.
Run the Subledger Update for the
specified period and company where
the transactions are recorded.
Pre-Migration
Validation
<RECORD_COUNT>Unposted Pending
Inventory transaction records exist for the
Period <PERIOD>in Company
<CO_CODE>. Please run Sub-Ledger
update before proceeding.

Message Type: Error

unposted completed
IC_TRAN_PND.
Pre-Migration
Validation
<RECORD_COUNT>Unposted Resource
transaction records exist for the Period
<PERIOD>in Company <CO_CODE>.
Please run Sub-Ledger update before
proceeding.

Message Type: Error

unposted completed
GME_RESOURCE_TXNS.
Pre-Migration
Validation
Value <SEGMENT_VALUE>not found in
the list of values for Segment
<SEGMENT>for Structure
<STRUCTURE_NAME>. Please enter the
value in General Ledger =>Setup =>
Financials =>Flexfields =>Key =>Values
menu.

Message Type: Error

accounting segments are not
setup properly for the
company.
Setup the accounting segments
using the Process Financials
responsibility.
Pre-Migration
Validation
Account id not found for Account Code:
<ACCOUNT_CODE>Company Code:
<CO_CODE>.

Message Type: Error

The Account Code
combination used in OPM
doesnt exist in GL Account
Code Combinations.
Create the corresponding Account
Code combination in the General
Ledger module.

Migration Messages
GMA: System Administration

Migration
Name
Message Comments Action Needed
Migrate
Organizations
Failed to migrate org <ORGANIZATION>

Message Type: Error

Organization did not migrate to
discrete. The error could
originate from:
A database error
No template organization
defined for the specified
organization
No cost group defined for
the specified organization

Check the log for prior error
messages regarding the failure to
migrate specified org. Take the
necessary actions to correct the
errors, then re-run the applicable
migrations.
Migrate
Organizations
Migration Process failed due to
DB_ERROR: <DB_ERROR >

This message is followed by:

Migration Process failed to migrate table
<TABLE_NAME>

Message Type: Error

The actual database error is
included in this message.

Possible tables involved:
IC_WHSE_MST
MTL_PARAMETERS
SY_ORGN_MST
IC_LOCT_MST

Take the appropriate actions to
resolve the issue and then re-run
applicable migrations. When all of the
related issues have been resolved,
re-run the applicable migrations.
Migrate
Organizations
Cannot migrate the subinventory as the
organization <ORGANIZATION>has not
been migrated.

Message Type: Error

The token
GMD_ORG_NOT_MIGRATED
may appear instead of the text.

For a given orgn_code there is
no organization_ id located in
sy_orgn_mst.
migrate the specified organiztaion.
Take the necessary actions to correct
the errors, then re-run the applicable
migrations.
Migrate
Organizations
Value for template organization is missing
for organization <ORGANIZATION>

Message Type: Error

This message should have
appeared during the running of
the Pre-Migration Validation
and should have been
corrected at that time.

Setup for the organization
included a template
organization that either does
not exist or does not have a
fiscal policy associated to it.

Update the migration setup for the
organization in question so that it will
have the attributes of a valid
organization.
Migrate
Organizations
DB_ERROR: <DB_ERROR>

In this case, the DB_error is defined as
<ORGN_CODE>-message
and not just <DB_ERROR > and will not
be followed by Migration Process failed to
migrate table <TABLE_NAME>

Message Type: Error

This format of the DB_ERROR
indicates an issue with the cost
setup. Fetching the default cost
group for the organization
failed.
Investigate the default cost group for
the organization. Make the necessary
modifications and re-run the
applicable migrations.

Migration
Name
Migrate Action
Codes
Attachment functionality does not Exists
for form INVACODE. (Please define it with
Apps Dev Resp) (ATTACHMENT_ID=-1)
ORA-01403: no data found in Package
GMA_EDITEXT_ATTACH_MIG
Procedure Attachment Main

Message Type: Error

Attachment for this form
needs to be defined.
1. Application Developer >
Attachments >Document Entities
Create a row for Actions with the
following entries:
Table: MTL_ACTIONS_B
Entity ID: MTL_ACTIONS_B
Entity Name: Action Codes
Prompt: Action Codes
Application: Inventory

Attachments >Attachment Functions
following entries:
Type: Form
Name: INVACODE
User Name: Action Codes
Session Context Field leave
blank

3. Click Categories, and add the
following:
GMA Migration Text

4. On the main window, click Blocks,
and add the following:
Block Name:
MTL_ACTIONS_B
Method: Allow Change
Secured By: None
(Leave remaining form fields
blank.)

5. Click Entities, and add the
following:
Entity: Action Codes
Display Method: Main Entity
Include in Indicator: Checked
Privileges Tab Leave all as
Always
On Primary Key Fields Tab Key
1:
MTL_ACTIONS_B.ACTION_CODE
SQL Statement Tab Leave
blank.
6. Save
7. Re-run the applicable migrations

Migration
Name
Migrate Items Attachment functionality does not Exists
for form INVIDITM. (Please define it with

Message Type: Error

Attachment for this form needs
to be defined.
following entries:
Table: MTL_SYSTEM_ITEMS
Entity ID: MTL_SYSTEM_ITEMS
Entity Name: Item Text Codes
Prompt:
Item Text Codes

following entries:
Type: Form
Name: INVIDITM
User Name: Item Text Codes
blank

following:
GMA Migration Text

4. On the main window click Blocks
Block Name:
MTL_SYSTEM_ITEMS
Secured By: None
blank.)

following:
Entity: Item Text Codes
Always
1:
MTL_SYSTEM_ITEMS.ORGANIZATI
ON_ID
Key2:
MTL_SYSTEM_ITEMS.INVENTORY
_ITEM_ID
blank
6. Save

Migration
Name
Migrate Lots Attachment functionality does not Exists
for form INVIDILT. (Please define it with

Message Type: Error

to be defined.
following entries:
Table: MTL_LOT_NUMBERS
Entity ID: MTL_LOT_NUMBERS
Entity Name: Lot Text Codes
Prompt:
Lot Text Codes

following entries:
Type: Form
Name: INVTDILT
User Name: Lot Text Codes
blank

following:
GMA Migration Text

4. On the main window click Blocks,
Block Name:
MTL_LOT_NUMBERS
Secured By: None
blank.)

following:
Entity: Lot Text Codes
Always
1:
MTL_LOT_NUMBERS.ORGANIZATI
ON_ID
Key2:
MTL_LOT_NUMBERS.INVENTORY_
ITEM_ID
Key3:
MTL_LOT_NUMBERS.LOT_NUMBE
R
blank
6. Save

Migration
Name
Migrade Grades Attachment functionality does not Exists
for form INVGRADE. (Please define it
with Apps Dev Resp)
(ATTACHMENT_ID=-1)

Message Type: Error

to be defined.
following entries:
Table: MTL_GRADES_B
Entity ID: MTL_GRADES_B Entity
Name: GradeText Codes
Prompt:
Grade Text Codes

following entries:
Type: Form
Name: INVGRADE
User Name: GradeText Codes
blank

following:
GMA Migration Text

Block Name:
MTL_GRADES_B
Secured By: None
blank.)

following:
Entity: Grade Text Codes
Always
1: MTL_GRADES_B.GRADE_CODE
blank
6. Save

Migration
Name
Migrate
Reason Codes
for form INVTDTRS. (Please define it
with Apps Dev Resp)
(ATTACHMENT_ID=-1)

Message Type: Error

to be defined.
following entries:
Table:
MTL_TRANSACTION_REASONS
Entity ID:
MTL_TRANSACTION_REASONS
Entity Name: Reason Codes
Prompt: Reason Codes

following entries:
Type: Form
Name: INVTDTRS
User Name: Reason Codes
blank

following:
GMA Migration Text

Block Name:
TRANS_REASONS
Secured By: None
blank.)

following:
Entity: Reason Codes
Always
1:
MTL_TRANSACTION_REASONS.R
EASON_ID
blank
6. Save

Migration
Name
Migrate
Organizations
for form PERWSDOR. (Please define it
with Apps Dev Resp)
(ATTACHMENT_ID=-1)

Message Type: Error

to be defined.
following entries:
Table: MTL_PARAMETERS
Entity ID: MTL_PARAMETERS
Entity Name: Organization Codes
Prompt:
Organization Codes

following entries:
Type: Form
Name: PERWSDOR
User Name: Organization Codes
blank

following:
GMA Migration Text

Block Name:
MTL_PARAMETERS
Secured By: None
blank.)

following:
Entity: Organization Codes
Always
1:
MTL_PARAMETERS.ORGANIZATIO
N_ID
blank
6. Save

Migrate
Organizations
GMA_WHSE_INSERT_ERROR
displays as a token because the message
is not defined.

Message Type: Error

Migration of the subinventory
has failed.
Determine that the organization
migrated, and check for the following
database error message:
Migration of location has failed. When
all of the related issues have been
resolved, re-run the applicable
migrations.

Migration
Name
Migrate
Organizations
Organization <ORGN_CODE>cannot be
defined as a child of <ORGN_CODE2>
and also be used a master organization
for Organization <ORGN_CODE3>.

Message Type: Error

An organization cannot be
defined as a parent
organization of another
organization if it has been
defined as a child of another
organization. This kind of
circular reference is not
allowed.

Setup form and modify the
associations of the organizations.
Re-run the applicable migrations.
Migrate Items <ERROR>

Message Type: Error

Unexpected error pertaining to
an Invalid Regulatory Item.
migrate Items and Regulatory related
data. Take the necessary actions and
then re-run the applicable migrations.

Migrate Items Invalid OPM Item id <ITEM_ID>

Message Type: Error

Item_id has no record in
ic_item_mst table. This is due
to some kind of data
corruption.
migrate Items . Take the necessary
actions and then re-run the applicable
migrations.

Migrate Items Cannot migrate item to discrete
organization. Organization
Id=<ORGANIZATION_ID>, Item
Id=<ITEM_ID>

Message Type: Error

Cannot migrate discrete
organization. It is possible that
the remapping of the existing
warehouse to the subinventory
for the discrete organization
did not occur.
Map the existing warehouse to the
subinventory for the discrete inventory
organization.
Migrate Items Unable to get <NAME>for value
<VALUE>

Message Type: Error

Data not found for respective
combination:
Orgn Accts/Orgn_ Id
UOM Code/Item_UM
Def Status Id/Lot Status
Use SQL*Plus to validate and correct
the corrupt data combinations. Re-
run the applicable migrations.

Migrate Items Migration Process failed due to

Message Type: Error

The actual database error is
included in this message.

Table involved:
IC_ITEM_MST_B
The actual database error is included
in this message. Take the appropriate
actions to resolve the issue and then
re-run applicable migrations. When
migrations.

Validate Item
Controls
Attribute <ATTRIBUTE_NAME>is
controlled at master organization level and
may result in migration issues if the
attribute values are different for process
and discrete organization.


This is a check to determine
whether certain item attributes
are set to be controlled at
master level. This does not
prevent the migration from
continuing..
Validate that the existing setup is OK.
Attributes are different in process as
compared to discrete in that the
organizations are now at organization
level only.

Migration
Name
Validate
Flexfield
Definitions
Both OPM and Discrete have the
descriptive flexfield context defined.
OPM=<OPM_context>,
Discrete=<ODM_context

Column <
APPLICATION_COLUMN_NAME >in
OPM descriptive flexfield is also used in
Discrete. Context =
<DESCRIPT_FLEX_CONTEXT_CODE>,
User Column Name=<
END_USER_COLUMN_NAME>

Message Type: Error

appeared during premigration.

Desc flexfield column conflicts
with OPM context and ODM
context.
Fix the descriptive flexfield using
Application Developer responsibility.
You can use one of the following
options to fix this issue: 1. Disable
segment in OPM descriptive flexfield.
As a result, OPM segment will not be
migrated to discrete. 2. Disable
segment in Discrete descriptive
flexfield. As a result, OPM segments
will be migrated and override the
discrete segment values. Please use
caution in choosing this option. 3.
Using SQL Plus move the OPM or
Discrete segment values to a different
(non-conflicting) segment and update
the Description flexfield definition
accordingly.

Migrate Items Invalid or NULL parameters passed to the
migration process.

Message Type: Error

This is most likely due to a
previous error, related to the
organization or the item.
Review why the parameters were not
passed, because the failure may be
due to an earlier listed error.
Migrate Items Migration Process failed due to

Message Type: Error

Table involved:
IC_ITEM_MST_B
resolve the database issue and then
re-run applicable migrations. When
migrations.
Migrate
Obsolete
Columns
Invalid or NULL parameters passed to the
migration process.

Message Type: Error

Invalid parameters for
obsolete column migration
Review why the parameters were not
passed, because the failure may be
Migrate
Obsolete
Columns
Invalid obsolete column
<OBSOLETE_COLUMN_NAME>
specified

Message Type: Error

Invalid value for the obsolete
column

6 columns are not used in
Release 12.
Make sure that these were the valid
values used:
ALT_ITEMA
ALT_ITEMB
MATCH_TYPE
UPC_CODE
QCITEM_ID
QCHOLD_RES_CODE

Migrate
Obsolete
Columns
Obsolete column already migrated to
different flexfield column
<COLUMN_NAME>


Obsolete column already
migrated to different flexfield
column
None required.
Migrate
Obsolete
Columns
Invalid flexfield column
<COLUMN_NAME>specified

Message Type: Error

Invalid value for the flexfield
column
Check flexfields and their associated
column names.
Migrate
Obsolete
Columns
Flexfield <COLUMN <FLEX FIELD
COLUMN>is already in use

Message Type: Error

Flexfield column is already in
use. Descriptive flexfield
column is used for another
column.
There is contention for the flexfield.
Try requerying to determine whether
you have access.



Inventory Balance No open period for the current date in
Organization Id

This will be followed by:
Opening Inventory period for
Organization Id


The inventory period was not
open for the organization on
the date when the migration
was run. The system reopens
the period on the discrete side
if required.

Although the message display
indicates that this is an error, it
is not.
None required.
Inventory Balance No open period for the current date in
Organization Id

This is NOT followed by a message that
the period was automatically opened.

Message Type: Error

The inventory calendar does
not exist in Discrete, or the
periods are not correctly
defined.
Check to make sure that Inventory
calender is defined in Discrete and
that all of the periods have been
defined. If the Inventory Calendar
does not exist, manually create the
calendar. Open the period for the
current date.
Inventory Balance Negative balances exist for Item
<WHSE_CODE>, Location <LOCT>.


Negative balances exist. This
also should have been noted
during the Pre-migration
Validation so that actions could
be taken (receipts completed,
physical inventory taken, etc)
to correct this condition. The
balances are migrated.

None required.
Migrate Inventory
Balances
Transaction processor error Negative
balances not allowed.


Negative balances exist and
were not addressed prior to the
migration. The organization on
the discrete side does not
allow for negative inventory.
Use the Inventory Super User
Responsibility and go to
Organizations >Parameters. Set
the Allow Negative Balances
indicator to yes. Re-run the

Migrate Inventory
Balances
Decimal dust balances exists for Item
<WHSE_CODE>, Location <LOCT>.



Residual decimal balances are
not migrated. These should
have been managed during the
premigration validation.

None required.

Migrate Inventory
Balances
Mixed balances (Negative primary and
Positive secondary or vice versa) for
dual quantity exists for Item <ITEM>,
Lot <LOT>, Sublot <SUBLOT>,
Warehouse <WHSE>, Location
<LOCT>.

Message Type: Error

Mixed balances are not
migrated and should have
been acted upon during
If the balances are meant to be
migrated, they will need to be
corrected through the use of SQL.
Then re-run the Inventory Balance
migration.
Migrate Inventory
Balances
Unexpected ORA-20001: APP-FND-
01934: ORA-00001: unique constraint
(ENI.ENI_OLTP_ITEM_STAR_U3)
violated in Package
ENI_ITEMS_STAR_PKG Procedure
UPDATE_ITEMS_IN_STAR occurred.

Message Type: Error

A required patch is missing or
patches were applied for the
wrong release.
Check for the latest migration
patches associated to the release
that is being migrated to (there are
different patches for R12 and
R12.1). Apply all of the latest
patches and then re-run the
Migrate Inventory
Balances
Warehouse <WHSE_CODE>not
migrated to discrete.

Message Type: Error

The warehouse was not
successfully migrated.
migrate the specified warehouse.
Take the necessary actions to
correct the errors, then re-run the

Migrate Inventory
Balances

Account -2 for Company <COMPANY>
is invalid.

Message Type: Error

The Process to Discrete
Transfer functionality makes
use of the IVA and INV
accounts defined at the
company level. The
accounting setup at the
company level cannot be
found.

Set up the INV and IVA accounts at
the company level for the specified
company using the Process
Financials responsibility.
Migrate Inventory
Balances
An error occurred while retrieving the
open period ID.

Message Type: Error

Inventory period is not open in
the discrete inventory
application for specified
organization.
All warehouses under this
organization will be skipped.

Error retrieving open period for the
organization. Review the discrete
period definition using SQL*Plus to
determine why the period cannot be
found.
Migrate Inventory
Balances
Cannot open period. Previous cost
period is not opened yet.

Message Type: Error

Prior period is not open. The
code skips all rows for the
warehouse.
open the inventory period. Take
the necessary actions to correct the
migrations.

Migrate Inventory
Balances
Failed to get the next period ID.

Message Type: Error

Cannot get next period. The
code skips all rows for the
warehouse.
open the inventory period. Take
migrations.

Migrate Inventory
Balances
INV_DUPLICATE_OPEN_PERIOD
Message is not setup for this token.

Message Type: Error

Period opened by another
user.
The code skips all rows for the
warehouse. This is a timing issue.
Determine whether the period was
opened by another user.

Migrate Inventory
Balances
No changes to commit.

Message Type: Error

No change was made for
period opening.
The code skips all rows for the
warehouse.
Migrate Inventory
Balances
Failed to migrate item. Organization Id
<ORG_ID>, Item No <ITEM_ID>

Message Type: Error

Failed to migrate item
organization.
Review why item migration failed.
This may have been due to an
earlier error.
Migrate Inventory
Balances
inventory item <ITEM_NO>.

Message Type: Error

Cannot migrate balances for
non-inventory items since
balances should not exist for
such items.
Warning message. - This should
have also appeared as a
premigration validation message.
Customer should confirm that they
intended for the item to be setup as
non-inventory.
Migrate Inventory
Balances
Failed to migrate lot. Item
Id=<ITEM_ID>, Lot Id=<LOT_ID>,
Warehouse=<WHSE_CODE>,
Location=<LOCATION>

Message Type: Error

The lot was not successfully
migrated.
Review why lot migration failed as it
may have been due to an earlier
listed error.
Migrate Inventory
Balances
OPM location not migrated. Warehouse
<WHSE_CODE>, Location
<LOCATION>

Message Type: Error

Warehouse location not
migrated.
Review why location migration
failed because it may have been
Migrate Inventory
Balances
GMI_LOC_CREATION_FAILED
No text setup for this token

Message Type: Error

Warehouse location creation
failed.
Review why location creation failed
because it may have been due to
an earlier listed error.
Migrate Inventory
Balances
Balance migration failed for item
<ITEM_ID>, warehouse
<WHSE_CODE>, Lot Number
<LOT_ID>, Location <LOCATION>

Message Type: Error

This will most likely be due to a
previous error.
migrate the specified item,
warehouse, lot or location. Take
migrations.

Migrate Inventory
Balances
<ERROR>

Message Type: Error

The actual error message will
be displayed.
Review the error message and take
migrations.

Migrate Inventory
Balances
Unable to get <DEFAULT LOCATION>
for value <NULL>

Message Type: Error

Default Location Profile No data found, balance migration
will rollback. Use SQL to be sure a
loc_id exists for the location in
question.
Migrate Inventory
Balances

Message Type: Error

Table involved:
IC_LOCT_INV
Review SQL Error message and
take appropriate action.
Migrate Inventory
Balances
The WAREHOUSE is closed for the
date entered. The transaction is not
allowed.

Message Type: Error

Warehouse is closed or not
open for period in question.
This should have appeared during

Migrate Inventory
Balances
Item's secondary unit of measure should
be same in Process and Discrete
Inventory.
(FND_ERROR_LOCATION_FIELD=)
(FND_MESSAGE_TYPE=E)

Message Type: Error

GMI_DXFR_DIFF_SEC_UOM
item.secondary_uom_code is
not the same as the
opm_item_secondary_uom_co
de
Process to discrete transfer issue.
Secondary unit of measure should
be same in Process and Discrete.
Migrate Inventory
Balances
Fiscal policy not defined for company
owning inventory organization.
<ORGANIZATION>

Message Type: Error

GMI_DXFR_ODM_NO_FISCA
L_POLICY

Process to discrete transfer
issue.

ODM set of books does not
exist.
Check if warehouse was migrated
as an inactive organization because
it may need to be active or check
the HR form to see if it has been
populated with an end date that is
earlier than the current date. May
need to rerun
$INV_TOP/patch/115/sql/GMIG3MI
B.sql

Migrate Inventory
Balances
Invalid locator <LOCATOR>

Message Type: Error

This error is related to the table
IC_LOCT_INV.
migrate locations. Take the
migrations.

Migrate Inventory
Balances
Lot id cannot be zero for lot controlled
item <ITEM_NO>for line no.
<LINE_NO>.

Message Type: Error

Data Corruption might be a
cause, or the lot controlled
indicator was modified through
the use of SQL after
transactions were entered.
If the balance is meant to be
migrated, either the lot_id in the
ic_loct_inv table must be updated
or the lot_cntrl column in
ic_item_mst must be set to 0
through the use of SQL. Re-run the
inventory balance migration to
migrate the material.

Migrate Inventory
Balances
Fiscal policy not defined for
company owning inventory
organization.

Message Type: Error

There is a problem with the
fiscal property setup.
migrate the specified company.
Migrate Inventory
Balances
Transactable attribute is not set for
this item. (ITEM =<ITEM>)

Message Type: Error

The most likely cause is that
the migration/upgrade of the
specified item was not
successful.
migrate specified item. If no such
error is found, use the Inventory
Super User responsibility to set the
transactable flag for the item at the
organization level. If errors are
found, take the necessary actions
to correct the errors, then re-run the

Migrate Inventory
Balances
Item not found. Invalid item. Please
re-enter. (ITEM =<ITEM>)

Message Type: Error

The item that the lot is
associated to cannot be found.
migrate specified item. Take the
migrations.

Migrate Inventory
Balances
Item is not Grade controlled. (ITEM
=<ITEM>)

Message Type: Error

The lot has a grade associated
to it but the item is not grade
controlled.
migrate specified item. Take the
migrations.

Migrate Inventory
Balances
Unexpected ORA-06508: PL/SQL:
could not find program unit being
called occurred.

Message Type: Error

A required patch is missing or
patches were applied for the
wrong release.
Check for the latest migration
patches associated to the release
that is being migrated to (there are
different patches for R12 and
R12.1). Apply all of the latest
patches and then re-run the

Migrate Items Attribute MTL_SYSTEM_ITEMS.
<ATTRIBUTE_FIELD>is controlled at
master organization level and may
result in migration issues if the attribute
values are different for process and
discrete organization.


The controls for these
attributes are set at master
level and may be different
between the orgs. If that is
acceptable to the customer
than ignore the message.

If the controls are not correct, then
use the Inventory Super User
responsibility to set the attribute
controls for this field to be
controlled at the organization level.
Migrate Inventory
Types

Message Type: Error

Table involved :
IC_INVN_TYP
Review the SQL Error message
and take appropriate action. When
migrations.

Migrate Default
Categories

Message Type: Error

Table involved :
GMI_CATEGORY_SETS
migrations.

Migrate Default
Categories

Message Type: Error

Table involved:
GMI_ITEM_CATEGORIES
migrations.

Migrate Lot
Statuses

Message Type: Error

Table involved:
IC_LOTS_STS
migrations.

Migrate Actions Migration Process failed due to

Message Type: Error

Table involved:
GMD_ACTIONS
migrations.

Migrate Grades Migration Process failed due to

Message Type: Error

Table involved:
GMD_GRADES
migrations.

Migrate Grades Migration Process failed due to

Message Type: Error

Table involved:
MTL_LOT_NUMBERS
migrations.

Lot Conversion GMI_LOC_CREATION_FAILED no
message setup for this token

Message Type: Error

Unable to create the locator
for dynamic OPM location
Rerun lot conversion migration.
Lot Conversion Unable to get <locator_id>for value
<warehouse/location>

Message Type: Error

This is most likely due to the
fact that the location and or/the
warehouse was not
migrate the specified location
and/or warehouse. Take the
necessary actions and then re-run
the applicable migrations.

Lot Conversion Migration Process failed due to

Message Type: Error

Table involved: IC_ITEM_CNV Review the SQL Error message
migrations.

GMF: Process Financials

Migrate Account
Mappings
Error : Account id not found for Account
Code: <ACCOUNT_CODE>Company
Code: <CO_CODE>.

Message Type: Error

The account was not migrated
successfully.
migrate the specified account code.
Take the necessary actions and
then re-run the applicable
migrations.

Migrate Fiscal
Policies

GMA_MIGRATION_ERROR_ABSTRA
CT (TABLE_NAME=<TABLE_NAME>)
(COLUMN_NAME=<COLUMN_NAME>
) (RECORD_COUNT=<COUNT>)


This is a summary message.

TABLE_NAME
XLA_RULES_T
CM_WHSE_SRC
GL_SUBR_STA
COLUMN_NAME
Not Null Constraint
Legal Entities
None Required.
Migrate Fiscal
Policies

GMA_MIG_FISCAL_DUP_LE_ERROR
(CO_CODE=<CO_CODE>)


This message may be received
if the financials migration has
been re-run and the Legal
Entity has already been
migrated.
None Required.

Financials
Migration
Completed Inventory transaction
records exist for the Period <PERIOD>
in Company <CO_CODE>. Please run
Sub-Ledger update before proceeding.

Message Type: Error


Inventory Transaction records
exist which are not yet posted
to Sub-Ledger

Make sure that all the transactions
for the company for the period
denoted in Completed transactions
table IC_TRAN_CMP has been
posted.
Financials
Migration
Pending Inventory transaction records
exist for the Period <PERIOD>in
Company <CO_CODE>. Please run
Sub-Ledger update before proceeding.

Message Type: Error


Inventory Transaction records
to Sub-Ledger

denoted in Pending transactions
table IC_TRAN_PND have been
posted.
Financials
Migration
Resource transaction records exist for
the Period <PERIOD>in Company
<CO_CODE>. Please run Sub-Ledger
update before proceeding.

Message Type: Error


Resource Transaction records
to Sub-Ledger

denoted in Resource transactions
table GME_RESOURCE_TXNS
have been posted.
Financials
Migration
Value <SEGMENT_VALUE>not found
in the list of values for Segment
<SEGMENT>for Structure
<STRUCTURE_NAME>. Please enter
the value in General Ledger =>Setup
=> Financials =>Flexfields =>Key =>
Values menu.

Message Type: Error


Segment values used in the
account codes are missing in
Flex field values setup.
Setup the accounting segments
using the Process Financials
responsibility.
Financials
Migration
OPM Item Id: <ITEM_ID>not found /
migrated.

Message Type: Error

OPM Item has not been
migrated by the Common Item
Migration script
Run the Common Item Migration
Script and rerun this GMF migration
script.
Financials
Migration
Legal Entity Details not found for
Company: <CO_CODE>.

Message Type: Error

Fiscal Policies for the Legal
Entity has not been migrated
for this Company Code
Run the Fiscal Policy migration
script and rerun this GMF Migration
Script.
Financials
Migration
Organization: <ORGANIZATION_ID>.

Message Type: Error

Legal Entity Information is not
available for the organization
ID.
Check whether the Legal entity
information for this organization has
been mentioned in the organization
parameters.
Financials
Migration
Warehouse: <WHSE_CODE>.

Message Type: Error

Legal Entity Information is not
available for the organization
ID for the warehouse code
mentioned.
Check whether the Legal entity
information for the organization /
warehouse code has been
mentioned in the organization
parameters.

Financials
Migration
Item Number not fetched for Inventory
Item Id: <INVENTORY_ITEM_ID>.

Message Type: Error

Not able to fetch the Item
Number flex field value for the
Inventory Item ID passed
Compile the Item Flex field. And
retry this script again.
Financials
Migration
Customer Details not found for
Customer Id: <CUST_ID>.

Message Type: Error

Customer Details are not
available for the customer ID.
Check the Synchronization
between the Customer Master and
OPM customer tables.
Financials
Migration
Vendor Details not found for Vendor Id:
<VENDOR_ID>.

Message Type: Error

Vendor Details are not
available for the customer ID.
Check the Synchronization
between the Vendor Master and
OPM Vendor tables.
Financials
Migration
Routing Details not found for Routing Id:
<ROUTING_ID>.

Message Type: Error

Routing Details are corrupted Routing Id referred in the Account
Mapping doesnt seem to exist in
the Routing tables. Check the
Routing table for the availability of
the Routing details.

Financials
Migration
Acquisition Code Details not found for
Acquisition Id: <AQUI_COST_ID>.

Message Type: Error

Acquisition Codes not yet
Migrated.
Run Acquisition Codes migration
again before running the Account
Mapping Migration.
Financials
Migration
Cost Component Class Code Details
not found for Cost Component Class Id:
<COST_CMPNTCLS_ID>.

Message Type: Error

cause, since the cost
component classes can be
used in account mapping only
if they exist in the master cost
component class table.
Cost Component Class Id referred
in the Account Mappings not
existing in Cost Component class
tables. Data might be corrupted,
Check the Cost Component Class
table for the availability of related
record.

Financials
Migration
Order Type Details not found for Order
Type Id: <ORDER_TYPE>.

Message Type: Error

cause, since the Order types
can be used in account
mapping only if they exist in
the master table.

Order Type Details not available in
op_ordr_typ or
oe_transaction_types tables.
Financials
Migration
Line Type Details not found for Line
Type Id: <LINE_TYPE>.

Message Type: Error

cause, since the Line types
can be used in account
the master table.
Line Type details referred in
Account Mapping does not exist in
the lookup table.
Financials
Migration
AR Transaction Type Details not found
for AR Transaction Type Id:
<AR_TRX_TYPE_ID>.

Message Type: Error

cause, since the AR
transaction types can be used
in account mapping only if they
exist in the master table.
AR Transaction Type details
referred in Account Mappings not
available in ra_cust_trx_types table.
Financials
Migration
GL Business Class Details not found for
GL Business Class Id:
<GL_BUSINESS_CLASS_CAT_ID>.

Message Type: Error

cause, since the GL Business
Class can be used in account
the master table.
GL Business Class Details referred
in account mappings does not exist
in the Flex field values. Data might
be corrupted.
Financials
Migration
GL Product Line Details not found for
GL Product Line Id:
<GL_PRODUCT_LINE_CAT_ID>.

Message Type: Error

cause, since the GL product
lines can be used in account
the master table.
GL Product line Details referred in
account mappings does not exist in
the Flex field values. Data might be
corrupted.

Financials
Migration
UOM Code: <UM_CODE>not found /
Migrated.

Message Type: Error

OPM UOMS has not been
migrated by the Common Item
Migration script
Run the Common UOM Migration
Script and rerun this GMF migration
script.
Financials
Migration
Account id not found for Account Code:
<ACCOUNT_CODE>Company Code:
<CO_CODE>.

Message Type: Error

Code Combination referred in
OPM doesnt exist in the
original GL code combinations
table.
Account Code combination used in
OPM doesnt exist in GL Account
Code Combinations. Create the
Corresponding Account code
combination in General Ledger
module before running Account
Mapping Migration script again.

Financials
Migration
Company Code Details not found for
Warehouse: <WHSE_CODE>.

Message Type: Error

Warehouse OPM
Organization mapping or OPM
organization Company
mapping might be corrupted.
Check the Warehouse OPM
Organization mapping or OPM
organization Company mapping.
Make the appropriate changes to
the mappings and then re-run the

Financials
Migration
Fiscal Policy of Company Code:
<CO_CODE>being migrated as Legal
Entity already exists. Skipping migration
of Fiscal Policy record.


Two Company Codes are
migrated to the sane Legal
Entity and the fiscal policy
record for the Legal entity has
already been created.
None required.
Financials
Migration
Migration of <COLUMN_NAME>in
<TABLE_NAME>failed for
<RECORD_COUNT>rows.

Message Type: Error

High Level error message for
failed migrations.
migrate data from the specified
table. Take the necessary actions
to correct the errors and then re-run

Financials
Migration
Migration of <COLUMN_NAME>in
<TABLE_NAME>failed for
<RECORD_COUNT>rows for
<PARAMETERS>.

Message Type: Error

Low Level error message for
failed migrations.
migrate data from the specified
table. Take the necessary actions
to correct the errors and then re-run

GME: Process Execution

Re-Create
Batches

Batch <BATCH_NO>could not be
migrated. <MSG>

Message Type: Error

The actual error is included in
this message.
Take the appropriate actions and
then re-run applicable migrations.
When all of the related issues have
been resolved, re-run the Migration
ReCreate Open Batches
concurrent program.

Re-Create
Batches

Unexpected ORA-20001: occurred.

Message Type: Error

Table Involved :
IC_ITEM_MST_B

resolved, re-run the Migration
concurrent program.

Re-Create
Batches

You cannot reopen this batch. It has
migrated from a release that does not
have reopen functionality.


The Batch Re-Open
functionality was not available
prior to 11.5.9
None required.
Re-Create
Batches

Batch <BATCH_NO>transaction with
Trans ID =<TRANS_ID>and details
<TXN_DATA>could not be migrated
because batch status does not allow
completed transactions.

Message Type: Error

previous error that prevented
the releasing of the batch.
Check the log file for prior
messages related to the specified
batch. When all of the related
issues have been resolved, either
re-run the Migration ReCreate
Open Batches concurrent program
or manually release the batch an
re-create the transactions.

Re-Create
Batches

<TXN_DETAILS>- a miscellaneous
issue transaction is being created from
<ORG>and a miscellaneous receipt
transaction is being created in the batch
organization so that the transaction or
reservation can be created in the batch
organization.


Material was moved to the
batch organization so that the
material can be reserved for
the specified batch.
None required.
Re-Create
Batches

Batch <BATCH_NO> transaction with
because miscellaneous issue or receipt
failed. <MSG>

Message Type: Error

The movement of material from
or to the batch organization
has failed.
The actual error is included in this
message. Take the appropriate
actions and then re-run applicable
migrations. When all of the related
issues have been resolved, re-run
the Migration ReCreate Open
Batches concurrent program.
Re-Create
Batches

because create pending product lot
failed. <MSG>New pending product lot
details were <NEW_DATA>.

The batch was created without
the pending product lots. The
actual error message is
included.
Correct the error. Manually create
the Pending Product Lot.

Re-Create
Batches

because create transaction failed.
<MSG>New transaction details were
<NEW_DATA.>

Message Type: Error

The reason actual message
from the transaction manager
will be included in the
message. Some possible
issues could be related to
material status, transactability
of the item, etc.
Check for prior error messages
related to the reason for transaction
failure. Take the appropriate
actions and then re-run the
applicable migrations. When all of
the related issues have been
resolved, re-run the Migration
concurrent program.

Re-Create
Batches

because item is lot controlled and the
original transaction has no lot details.

Message Type: Error

Either the transaction record is
missing lot information and is
corrupt, or the item has been
changed to be lot controlled in
the batch organization whereas
it had not been defined that
way prior to R12/12.1
Adjust the inventory accordingly
and manually re-create the
transaction.

Re-Create
Batches

because item is not lot controlled and
the original transaction has lot details or
pending product lots can only be
created for lot controlled products and
byproducts.

Message Type: Error

failure to migrate/upgrade the
specified item.
Check for priior error messages
related to the specified item. Take
the appropriate actions and then re-
concurrent program.
Re-Create
Batches

because item is not reservable.

Message Type: Error

specified item.
concurrent program.
Re-Create
Batches

because item is not transaction enabled.

Message Type: Error
specified item.
concurrent program.

Re-Create
Batches

because locator could not be
determined.

Message Type: Error

This is due to the failure to
migrate the specified location.
related to the specified location.
Take the appropriate actions and
migrations. When all of the related
issues have been resolved, re-run
the Migration ReCreate Open
Batches concurrent program.

Re-Create
Batches

because lot number could not be
determined.

Message Type: Error

migrate the specified lot.
related to the specified lot. Take
concurrent program.

Re-Create
Batches

<TXN_DATA> - the reason ID could not
be determined for reason code
&REASON_CODE. Transaction will be
created without reason ID.


migrate the specified reason
code.
migrate the specified reason code.
correct the errors. Update the
reason code to the transaction
manually.
Re-Create
Batches

because item is revision controlled and
no revisions exist.

Message Type: Error

This item may have existed in
the organization prior to
migration with the revision
control attribute set, or the
revision control attribute was
set after the item was
migrated.
Manually create the appropriate
revision for the specified item.
Re-Create
Batches

because subinventory could not be
determined.

Message Type: Error

either a database error or the
failure to migrate the
corresponding warehouse
migrate the warehouse noted in the
transaction data. Take the
migrations.
Re-Create
Batches

because uom conversion from
<FROM_UM>to <TO_UOM>does not
exist.

Message Type: Error

This is most like due to either
the failure to migrate the
specified item or the specified
item conversion record.
messages regarding the specified
item or uom conversion for the
specified item. Take the necessary
actions to correct the errors, then

Re-Create
Batches

Batch &BATCH_NO transaction
migration failed. <MSG>

Message Type: Error

The actual error is included in
this message.
correct the issue and then re-run
Re-Create
Batches

Phantoms could not be linked for Batch
<BATCH_NO>. Phantom batch was not
found.

Message Type: Error

The batch itself has been re-
created but the re-creation of
the phantom batch failed.
messages regarding create the
phantom batch. Take the
migrations.

Re-Create
Batches

Unexpected error occurred while linking
phantoms for Batch <BATCH_NO>.
<MSG>

Message Type: Error

The batch itself has been re-
created but the re-creation of
the phantom batch failed.
messages regarding create the
phantom batch. Take the
migrations.

Re-Create
Batches

Item/Organization combination not
found for item <ITEM>and Organization
<ORG>.

Message Type: Error

Either the organization or the
item failed to migrate
successfully.
messages regarding the specified
organization or the specified item.

Re-Create
Batches

No open periods found while releasing
Batch <BATCH_NO>.

Message Type: Error

This is most likely due to old
data that is outside of the
current open financial and
inventory periods.
Check the batch information to
determine why this batch had not
been prevously closed or cancelled.
Re-Create
Batches

Trans ID =<TRANS_ID>with details
because there were no open periods.

Message Type: Error

current opne financial and
inventory periods.
Re-Create
Batches

No open periods found while releasing
or completing Batch <BATCH_NO>
Step <STEP_NO>.

Message Type: Error

current opne financial and
inventory periods.
Re-Create
Batches

Batch <BATCH_NO>Step <STEP_NO>
could not be completed. <MSG>

Message Type: Error

The actual error is included in this
message. Take the appropriate
actions and then re-run applicable
migrations.

GML: Logistics

Migrate Open
Orders
Quantity on hand fails to satisfy
reservation

Message Type: Error

For create reservation -
Usually means that there is not
enough quantity available to
reserve. This could be due to
a failure to migrate inventory
balances.

messages regarding inventory
balance migration failures. If found,
take the necessary actions to
applicable migrations If not, create
sufficient quantities e.g Misc
Receipts.

Migrate Open
Orders
Create Reservation failed due to locator

Message Type: Error

For create reservation -
Could be that locator has
expired.
Check the locator expiration date.

Migrate Open
Orders
Invalid Reservation Qty

Message Type: Error

For create reservation. Usually
means that there is not enough
ATR to reserve against. This
could be due to a failure to
migrate inventory balances.

messages regarding inventory
balance migration failures. If found,
take the necessary actions to
applicable migrations If not, create
sufficient quantities e.g Misc
Receipts.

Migrate Open
Orders
Invalid locator

Message Type: Error

This is in reference to
reservation creation. Either the
location migration failed, or the
locator has expired.
Check locator migration
could have expired.
Migrate Open
Orders
The lot number has expired

Message Type: Error

reservation creation.
Check lot the lot expiration date.
Migrate Open
Orders
Suppy/Demand document does not
have enough quantity to be reserved
against


reservation creation. This is
usually seen when the material
has already been reserved
when re-running this migration.
None required.
Migrate Open
Orders
Transactable attribute is not set for
this item

Message Type: Error

This is in reference to move
order creation. The most likely
cause is that the migration/
upgrade of the specified item
was not successful.
migrate specified item. If no such
error is found, use the Inventory
Super User responsibility to set the
transactable flag for the item at the
organization level. If errors are
found, take the necessary actions
to correct the errors, then re-run the

GMD: Quality Management

Migrate Quality
Parameters
Value for the profile "GMD: Default
Lab Organization" is missing.

Message Type: Error

appeared during the running of the
Pre-Migration Validation and should
have been corrected at that time.

Set the value of profile "GMD:
Default Lab Organization" to a valid
organization.
Migrate Quality
Parameters
Quality Default Lab Profile Value
does not exist.

Message Type: Error

appeared during the running of the
Pre-Migration Validation and should
have been corrected at that time.

Set the value of profile "GMD:
Default Lab Organization" to a valid
organization.
Migrate Samples

Unexpected ORA-01403: no data
found occurred. Error from call to
inv_opm_lot_migration.
get_odm_lot.

Message Type: Error

This is mostly likely due to the
failure to migrate the item or lot.
migrate items and lots. Take the
applicable errors and then re-run

Migrate Samples Error retrieving data from
ic_loct_mst. Passed whse code is
<WHSE_CODE>and location is
<LOCATION>.

Message Type: Error

The warehouse or the location
failed to migrate successfully.
migrate the specified warehouse
and location. Take the necessary
actions to correct the applicable
errors and then re-run the

Update Quality
Tables with Batch
Data
Batch Id migration for GMD
Sum mary.gmd_sampling_events
records updated - <SAMPLE_EVT>
sample records updated -<SMPL>
spec validity rule records updated -
records updated - <MATDET>.


WIP sample and WIP specification
related data have been updated
with the new batch id.
None required.
Migrate
Specifications
A record with null organization code
has been deleted from <TABLE>. It
was not attached to any Samples.


This pertains to a specification
validity rule.
None required.
Migrate Quality
Parameters
Updates to gmd_quality_config
have not been successful.
Processing of the null organization
row will not take
place until all existing
gmd_quality_config rows are
migrated successfully.

Message Type: Error

Error were encountered while
updating the gmd_quality_config
table.
messages regarding
gmd_quality_config. Take the
the applicable migrations
Migrate Quality
Parameters
Updates to gmd_quality_config
have not been completed. Correct
all logged errors on this table
before proceeding.

Message Type: Error

Errors were encountered while
updating the gmd_quality_config
table.
messages regarding
the applicable migrations
Migrate Stability
Studies
Default Stability Study organization
code for migration is not set up
properly. Check to see if it exists in
table GMD_MIGRATE_PARMS. If
so, verify that an organization id
has been assigned to this default
organization code specified in that
table.

Message Type: Error

Either the value for the Default
Stability Study Organization had not
not been corrected in the Pre-
Migration Validation phase, or the
Quality Parameters migration failed.
messages regarding the Default
Stability Study Organization and

Migrate
Specifications
gmd_inventory_spec_vrs record
with spec_vrid of <VRID>.
Organization Code is <ORG>and
Whse Code is <WHSE>. The
organization id for the orgn code is
<ORGID>and the organization_id
for the whse is <WHSEID>. They
should be the same. Check the

Message Type: Error

converted to a subinventory under
a different inventory organization,
this issue will occur.
The only way to fix this issue post
migration is to resolve the
association of the subinevtory and
organization and then use SQL to
update the ids properly in the
gmd_inventory_spec_vrs table.
Migrate
Specifications
gmd_monitoring_spec_vrs record
with spec_vrid of <VRID>.
Organization Code is <ORG>and
Whse Code is <WHSE>.
The organization id for the orgn
code is <ORGID>and the
<WHSEID>. They should be the
same. Check

Message Type: Error

gmd_monitoring_spec_vrs table.
Migrate
Specifications
Failure in call to Create Non-
validated location.
GMA_MIGRATE _ORG.
CREATE_LOCATION

Message Type: Error

This is most likely due to a either a
database error or the failure to
migrate the corresponding
warehouse.
messages regarding
mtl_item_locations or the failure to
migrate the corresponding
warehouse. Take the necessary

Migrate
Specifications
Organization Code was not
migrated. Organization Code is
<ORG>.

Message Type: Error

The organization migration failed. Check the log for prior error
migrate the specified organization.
migrations.

Migrate
Specifications
Organization Id not found on
sy_orgn_mst for Organization Code
=<ORG>.

Message Type: Error

This is due to the failure of the
organization to successfully
migrate.
migrations.

Migrate
Specifications
Error retrieving orgn_code from
mtl_parameters for organization_id
=<ORGID>.

Message Type: Error

This is due to the failure of the
organization to successfully
migrate.
migrations.

Migrate
Specifications
Unit of Measure <UOM>not
migrated.

Message Type: Error

The unit of measure code did not
migrate successfully.
migrate the specified unit of
measure. Take the necessary

Migrate Stability
Studies
Organization Id not found on
Sy_orgn_mst for Default Lab
Organization Code =<ORG>.

Message Type: Error

Either the Default Lab Organization
parameter is NULL or invalid, or the
organization migration failed.
migrations.

Migrate Stability
Studies
Error converting Reason Code to
Reason ID. Reason Code is
<REASON>.

Message Type: Error

The reason code was not
migrate the specified reason code.
migrations.

Migrate Stability
Studies
gmd_storage_history record with
storage history id of
<STORAGE_ID>.
Warehouse/Subinventory Code is
<WHSE>. Location is
<LOCATION>and its associated
locator id is <LOC_ID>. The
subinventory associated with the
locator is <LOC_SUBINV>. It
should match the Warehouse
Code. Check

Message Type: Error

gmd_storage_history table.
Migrate Samples Error converting Status Code to
Status id. Status Code is
<STATUS>.

Message Type: Error

The migration of the status code
failed.
migrate the specified status code.
migrations.

Migrate Samples Error retrieving data from
mtl_item_locations using locator id
=<LOCATOR>.

Message Type: Error

The migration of the location failed. Check the log for prior error
migrate the specified location.
migrations.

Migrate Samples There is a setup mismatch for
gmd_samples record with sample
id of <SAMPLE_ID>. Organization
Code is <ORG>and Whse Code is
<WHSE>. The organization id for
the orgn code is <ORGID>and the
<WHSE_ORG_ID>. They should
be the same. Check

Message Type: Error

gmd_samples table.


GMD: New Product Development

Data
Transformation
Unexpected ORA-20001: APP-INV-
05247: You have entered a
duplicate item. Please clear your
changes occurred.

Message Type: Error

This error usually occurs when the
transformation is running for the
same item and organization
combination simultaneously. This
is usually in reference to either the
FM_MATL_DTL table or the
GMD_RECIPE_VALIDITY_RULES
table.
Rerun the data transformation
patch for GMD,GME and GMP.

GR: Process Regulatory

Migrate
Regulatory Items

Message Type: Error

The actual db error appears in
the message.
correct the database errors, then
Migrate
Regulatory Items
Regulatory item data will not be
migrated because no Regulatory
organization has been specified.



In order for Regulatory Item
Information to be migrated, at
least one organization must be
designated as a Regulatory
Org.

Setup form and set the Regulatory
Org checkbox for at least one
organization on the Organizations
tab. The column regulatory_ind
may need to be set to through the
use of SQL if the Organization
migration has been completed
successfully and the form is in a
frozen state. Run GRG6PST.sql and
then re-run this migration.

Migrate
Regulatory Items
Organization <ORGANIZATION>has
not been migrated.

Message Type: Error

The specified organization was
not migrated.
migrations.

Migrate
Regulatory Items
There are no Regulatory items to
migrate.


There are no Regulatory items
that need to be migrated. This
could be due to the fact that all
items had been previously
migrated, or that no
Regulatory Items had been
defined or that no
organizations
were specified as Regulatory
Organizations.
None required.
Migrate
Regulatory Items
The value for profile option <PROFILE>
is NULL.

Message Type: Error


The value for the specified
profile option is required for
data migration.

Go to the Profiles form and set the
value for the specified profile
option. Re-run this migration.

Migrate
Regulatory Items
Item <ITEM>has no value for CAS
number.

Message Type: Error


A Regulatory Item in R12/12.1
must have a CAS number
associated to it, so if there is
no CAS number associated in
11.5.10, the Regulatory Item
migration will fail.

A CAS number will need to be
updated directly to the column in
the table through the use of SQL.

Migrate
Regulatory Items
Item <ITEM>does not exist in
Organization <ORG>.

Message Type: Error

The migration of the specified
item to the specified
organization must have
previously failed.
migrate the specified item to the
specified organization. Take the

Migrate
Standalone
Formulas
Item <REGITEM>is an invalid
Regulatory Item.

Message Type: Error

The referenced Regulatory
item no longer appears in the
Regulatory Items table. The
item may not have been
successfully migrated, or the
Hazardous material flag may
not be set.
Check the ODM Inventory Item to
see that the Hazardous material
flag is set. Go to the Regulatory
Item Information form and then re-
define the item. Re-run this
migration.
Migrate
Standalone
Formulas

Message Type: Error

The actual databse error
appears in the message.
correct the database errors, then

Migrate
Standalone
Formulas
The value for profile option GR: Default
Organization is NULL.

Message Type: Error

for GR: Default Organization is
not set. This is used as the
owner organization for the
standalone formula migration.

Set the value for this profile at the
site level using the System
Administration responsibility. Re-
run this migration.

Migrate
Standalone
Formulas
The value for profile option GMD: Yield
Type is NULL.

Message Type: Error


for GMD: Yield Type is not set.
This is used as the base uom
type for checking conversions
for the ingredient
concentrations.

Set the value for this profile at the
site level using the System
Administration responsibility. Re-
run this migration.

Migrate
Standalone
Formulas
Item <ITEM>cannot be converted to
unit of measure for FM_YIELD_TYPE.

Message Type: Error


ingredients specified in the
item concentrations are not
convertible to the standard
uom derived from the GMD:
Yield Type UOM type.

Use the Invetory Super User
responsibility and go to the Item
Conversions form and set up a
conversion between the specified
item's primary unit of measure base
type uom to the base unit of
measure for the the GMD: Yield
Type UOM type class. Re-run this
migration.

OPM Release 12/12.1 Migration Files

The following are the PL/SQL files that execute the individual pieces of the OPM migration. These files are
organized into different buckets based on their order of execution and dependencies. These files can be re-run to
migrate any data that was not previously migrated. Before running any of the listed files, the files listed in
theDependent On column must be run, and the errors reported by the dependent files must be fixed.

Bucket - 1 (Run during Pre-Migration Phase):

Migration Name SQL Script Migrating/Upgrading Entity Dependent On Comments
Pre-Migration
Validation
GMAR12VAL.sql N/A

None The script can be run with
the following parameter
value:
ALL - Runs all of the
validations
GMA - Runs the GMA
validation
GMI - Runs the GMI
validation
GMD - Runs the GMD
validation
GMF - Runs the GMF
validation
GR - Runs the
Regulatory validation

Organization
Migration (optional)

GMAORGMG.sql SY_ORGN_MST
IC_WHSE_MST
None Migrates Organizations and
Warehouses
Item Migration
Setup (optional)
GMAITSTP.sql IC_ITEM_MST_B_MIG GMAORGMG.sql Populates the item migration
table with the appropriate
organization and item
combinations. This table
drives the item migration.
Item Migration
(optional)
gmiitmin.sql

IC_ITEM_MST GMAORGMG.sql
GMAITSTP.sql
Migrates Items and updates
existing discrete items

Bucket 2 (Run during the Inline Phase):

Update Process
Organizations
GMAG1UOR.sql MTL_PARAMETERS
MTL_SECONDARY_INVENTORIES
None Updates process
organizations with valid
attribute controls
Migrate Reason
Codes
GMAG1MRS.sql SY_REAS_CDS None Migrates Reason Codes
Migrate
Organizations
GMAG2MOR.sql SY_ORGN_MST
IC_WHSE_MST
None Migrates Organizations and
Warehouses

Migrate Action
Codes
GMIG1MAC.sql GMD_ACTIONS_B/TL None Migrates Action Codes
Migrate Grade GMIG1MGD.sql GMD_GRADES_B/TL None Migrates Grade Codes
Migrate Lot Status GMIG1MLS.sql IC_LOTS_STS None Migrates Lot Status Codes
Migrate Inventory
Types
GMIG1MIT.sql IC_INVN_TYP None Migrates Inventory Types
Migrates Default
Categories
GMIG1MDC.sql GMI_CATEGORY_SETS None Migrates default category
sets migration
Migrate GMD
Profiles
GMDG1MPR.sql FND_PROFILE_OPTION_VALUES None Migrates Product
Development Profiles
Migrate Acquisition
Codes
GMFG1MAC.sql PO_COST_MST None Migrates Acquisition Codes
Migrate Cost Types GMFG1MCM.sql CM_MTHD_MST None Migrates Cost Types
Migrate Fiscal
Policies LE
GMFG1MFP.sql GMF_FISCAL_POLICIES
GL_PLCY_MST
None Migrates Fiscal Policies LE
Migrate Lot Cost
Types
GMFG2MLM.sql CM_MTHD_MST None Migrates Lot Cost Types
Migrate Vendors GMFG3MVI.sql GL_ACCT_MAP None Migrates Vendor IDs
Update Purchasing
Lines
GMLG5UPS.sql PO_LINE_LOCATIONS_ALL None Updates secondary
quantities and shipment
quantities for the purchasing
table.

Bucket 3 (Run during the Inline Phase):

Migrate Inventory
Balances
GMIG3MIB.sql IC_LOCT_INV GMAG2MOR.sql Updates process
organizations with valid
attribute controls and
migrates inventory balances
Migrate Lot
Conversions
GMIG3MLC.sql IC_ITEM_CNV
GMI_ITEM_CONV_AUDIT
GMI_ITEM_CONV_AUDIT_DETAILS
GMIG3MIB.sql Migrates Item Lot
Conversions and Audit data.
Migrate Product
Development
Parameters
GMDG3MPL.sql SY_ORGN_MST GMAG2MOR.sql Migrates Plant and Lab
Indicator to Product
Development Parameters
Migrate Quality
Setup
GMDG3MST.sql GMD_QUALITY_CONFIG GMAG2MOR.sql Migrates OPM Quality Setup
Data
Transformation
GMAMIGT.sql Tables listed in
GMA_UPGRADE_SETUP for GMD,
GME, GMP
GMAG2MOR.sql Transforms data for
organization_id,
inventory_item_id,
lot_number and UOM for the
tables listed.

The script will need to be run
individually for each of the 3
products with the following
parameters:
P_num_workers =1,
P_table_owner =
<PROD_CODE>
e.g. GMD
P_batch_size ='3000'
P_worker_id =1

Data
Transformation
GMAFMIGT.sql Tables listed in
GMA_UPGRADE_SETUP for GMF
GMAG2MOR.sql Transforms data for
organization_id,
inventory_item_id,
lot_number and UOM for the
tables listed

The script will need to be run
with the following
parameters:
P_num_workers =1,
P_table_owner = GMF
P_batch_size ='3000'
P_worker_id =1

Migrate Expense
Allocation Basis
GMFG2MAB.sql GL_ALOC_BAS GMAG2MOR.sql Migrates expense allocation
basis
Migrate Expense
Allocation Codes
GMFG2MAC.sql GL_ALOC_MST GMFG1MFP.sql Migrates expense allocation
codes
Migrates Expense
Allocation
Expenses
GMFG2MAE.sql GL_ALOC_EXP GMFG1MFP.sql Migrates expense allocation
expenses
Migrates Expense
Allocation Inputs
GMFG2MAI.sql GL_ALOC_INP GMFG1MFP.sql Migrates expense allocation
inputs
Migrates Burden
Priorities
GMFG2MBP.sql GMF_BURDEN_PRIORITIES GMAG2MOR.sql Migrates burden priorities
Migrates Cost
Calendar
Assignments
GMFG2MCC.sql GMF_CALENDAR_ASSIGNMENTS GMFG1MFP.sql Migrates cost calendar
assignments
Migrates Material
Cost Components
GMFG2MCM.sql CM_CMPT_MTL GMAG2MOR.sql Migrates material cost
components
Migrates Event
Fiscal Policies
GMFG2MEP.sql GL_EVENT_PLC GMFG1MFP.sql Migrates event fiscal policies
Migrates Fiscal
Policies
GMFG2MFP.sql GMF_FISCAL_POLICIES
GMF_LEDGER_VALUATION_METH
ODS
GMFG1MFP.sql Migrates Fiscal Policies -
Others
Migrate Item Cost
Component Details
GMFG5MCP.sql CM_CMPT_DTL GMFG1MFP.sql Copies Item Cost
Component Details
Migrate Cost
Warehouses
GMFG5CWA.sql CM_WHSE_ASC GMAG2MOR.sql Migrates Cost Warehouses
Migrates Costing
Items
GMFG5ITM.sql GMF_ITEMS_MIGRATION GMAG2MOR.sql Migrates Process Costing
Items
Populate
Regulatory
Migration table
GRG6PST.sql GR_ITEM_GENERAL_MIG GMAG2MOR.sql Populate the table that is
used to migrate Regulatory
Items
Updates receiving
transaction tables
for lot number
GMLG5RCV.sql RCV_LOT_TRANSACTIONS
GML_RCV_LOTS_MIGRATION
GMAG2MOR.sql Updates receiving
transaction tables for lot
number
Updates the
receiving supply
table for secondary
quantities
GMLG6RCV.sql RCV_SUPPLY GMAG2MOR.sql Updates the receiving supply
table for secondary
quantities
Updates Receiving
Lot Supplies
GMLG7RCV.sql RCV_LOTS_SUPPLY GMAG2MOR.sql Updates receiving lot supply
table for lot number and
transaction reason

Bucket 4 (Run during the Post-Migration Phase):

SQL Script Migrating/Upgrading Entity Dependent On Comments

Update Recipe
Types
GMDG3MRT.sql GMD_RECIPES_B GMAMIGT.sql Updates Recipe Type with
the default value
Migrate Samples GMDG5MSM.sql GMD_SAMPLES GMAMIGT.sql Migrates OPM Quality
sample data
Migrate
Specifications.
GMDG5MSP.sql GMD_SPECIFICATIONS_B GMAMIGT.sql Migrates OPM Qaulity
specifications.
Migrate Stability
Studies
GMDG5MST.sql GMD_STABILITY_STUDIES_B GMAMIGT.sql Migrates stability studies.
Migrate GME
Profiles
GMEG6MIG.sql FND_PROFILE_OPTION_VALUES
GME_BATCH_HEADER
GME_RESOURCE_TXNS
GMAMIGT.sql Migrates Process Execution
Profiles.
Updates batch header for
laboratory Ind
Creation of Wip_Entities row
for batch_no.
Reason_Id upgrade for
resource transactions.
Migrates Burden
Percentages
GMFG3MBP.sql GMF_BURDEN_PERCENTAGES GMAFMIGT.sql Migrates Burden
Percentages
Migrate Item Cost
Component Details
GMFG5MCP.sql CM_CMPT_DTL
GL_ITEM_CST
GL_ITEM_DTL
GMFG5ITM.sql Copies Item Cost
Component Details
Migrate Resource
Details
GMFG6P01.sql CM_RSRC_DTL GMAFMIGT.sql Migrates Resource Details
Migrate Actual Cost
Adjustments
GMFG6P02.sql CM_ADJ S_DTL GMAFMIGT.sql Migrates Actual Cost
Adjustments
Migrate Item Cost
Component Details
GMFG6P03.sql CM_CMPT_DTL GMFG5MCP.sql Migrates Item Cost
Component Details
Migrate Burden
Details
GMFG6P04.sql CM_BRDN_DTL GMAFMIGT.sql Migrates Burden Details
Migrate Item Costs GMFG6P05.sql GL_ITEM_CST GMAFMIGT.sql Migrates Item Costs
Migrate Lot Costs GMFG6P06.sql GMF_LOT_COSTS GMAFMIGT.sql Migrates Lot Costs
Migrate Lot Costed
Items
GMFG6P07.sql GMF_LOT_COSTED_ITEMS GMAFMIGT.sql Migrates Lot Costed Items
Migrate Lot Cost
Burdens
GMFG6P08.sql GMF_LOT_COST_BURDENS GMAFMIGT.sql Migrates Lot Cost Burdens
Migrate Lot Cost
Adjustments
GMFG6P09.sql GMF_LOT_COST_ADJ USTMENTS GMAFMIGT.sql Migrates Lot Cost
Adjustments
Migrate Material Lot
Cost Transactions
GMFG6P10.sql GMF_MATERIAL_LOT_COST_TXNS GMAFMIGT.sql Migrates Material Lot Cost
Transactions
Migrate Standard
Cost Ledgers
GMFG6P11.sql CM_SCST_LED GMAFMIGT.sql Migrates Standard Cost
Ledgers
Migrate Actual Cost
Ledgers
GMFG6P12.sql CM_ACST_LED GMAFMIGT.sql Migrates Actual Cost
Ledgers
Migrate Account
Mappings
GMFG6P13.sql SLA_ADR_MIGRATION GMAFMIGT.sql Migrates Account Mappings
Migrate Period
Balances
GMFG6P14.sql GMF_PERIOD_BALANCES GMAFMIGT.sql Migrates Period Balances
Migrate Source
Warehouses
GMFG6P15.sql CM_WHSE_SRC GMAFMIGT.sql Migrates Source
Warehouses
Migrate Actual Cost
control data
GMFG6P16.sql CM_ACPR_CTL GMAFMIGT.sql Migrates Actual Cost control
data
Migrate Rollup
Control Records
GMFG6P17.sql CM_RLUP_CTL GMAFMIGT.sql Migrates Rollup Control
Records
Migrates Cost
Update control data
GMFG6P18.sql CM_CUPD_CTL GMAFMIGT.sql Migrates Cost Update
control data
Migrates Subledger
control data
GMFG6P19.sql GL_SUBR_STA GMAFMIGT.sql Migrates Subledger control
data
Migrate Forecasts GMPG7FCM.sql MRP_FORECAST_DESIGNATORS GMAMIGT.sql Migrates Forecasts
Migrate Regulatory
Items
GRG7PST.sql GR_ITEM_GENERAL GRG6PST.sql Migrates Regulatory Item
data

Migrate Standalone
Formulas
GRG8PST.sql GR_ITEM_CONCENTRATIONS
GR_DISPATCH_HISTORY
GMAG2MOR.sql Migrates standalone
Regulatory formula
(composition) data
Migrate Open
Orders
GMLG5MMO.sql IC_TRAN_PND
MTL_RESERVATIONS
GMAG2MOR.sql
GMIG3MIB.sql
Migrates Open Order lines

Bucket 5 (Run during the Post-Migration Phase):

Update Quality
Tables with Batch
Data
GMDG6UMD.sql GMD_SAMPLES_B
GMD_SAMPLING_EVENTS
GMD_WIP_SPEC_VRS
GMAMIGT.sql
GMDG5MSM.sql
GMDG5MSP.sql
Updates Material Detail IDs

Table Mappings
This section contains the table mapping from OPM to Oracle Inventory. In addition, obsolete columns are
denoted as such.

IC_ITEM_MST_B
The following table contains data mapping from OPM Item Master to Oracle Inventory Item Master table. Because the
current Item Synchronization already creates the items in Oracle Inventory, the columns that need migration are highlighted
in gray. However, the update script updates all process attributes to ensure the correct value for the process enabled
organizations.

Source Column (in
IC_ITEM_MST_B)
Data Type
(*=Not Null)
Destination
Column (in
MTL_SYSTEM_ITEMS_B)
Date Type Comments
ITEM_ID *NUMBER(10) INVENTORY_ITEM_ID NUMBER System generated id. Note that the id has
the same value, if the item is assigned to
multiple organizations.
ORGANIZATION_ID NUMBER Only the process enabled organizations is
affected by this migration (with the
exception of a new discrete master
organization).
ITEM_NO *VARCHAR2(32) SEGMENT1 VARCHAR2(40) OPM items are migrated to segment1
only.
ITEM_DESC1 VARCHAR2(70) DESCRIPTION VARCHAR2
(240)

RECIPE_ENABLED_FLAG
PROCESS_EXECUTION_ENABL
ED_FLAG
PROCESS_COSTING_ENABLED
_FLAG
PROCESS_QUALITY_ENABLED_
FLAG
VARCHAR2(1)

These columns do not exist in OPM. For
the process-enabled organizations, they
are updated to Y during migration.
ITEM_DESC2 VARCHAR2(70) LONG_DESCRIPTION VARCHAR2
(4000)
We currently dont synchronize this
column. Note that this migration occurs if
the LONG_DESCRIPTION column is null
in discrete.
ALT_ITEMA VARCHAR2(32) Obsolete.
ALT_ITEMB VARCHAR2(32) Obsolete.
ITEM_UM *VARCHAR2(4) PRIMARY_UNIT_OF_MEASURE
PRIMARY_UOM_CODE
UNIT_OF_ISSUE
VARCHAR2(25)
VARCHAR2(3)
VARCHAR2(25)
Note that the migrated values are derived
from the sy_uoms_mst view.
DUALUM_IND *NUMBER(5) TRACKING_QUANTITY_IND
SECONDARY_DEFAULT_IND
VARCHAR2(30)
VARCHAR2(30)
Dualum_
ind
Tracking_
quantity_
ind
Secondary_
default_
ind
0
1
2
3
P
PS
PS
PS
NULL
F
D
N
ITEM_UM2 VARCHAR2(4) SECONDARY_UOM_CODE VARCHAR2(3) Note that the migrated values are derived
from the sy_uoms_mst view.
DEVIATION_LO *NUMBER DUAL_UOM_DEVIATION_LOW NUMBER =DEVIATION_LO * 100
DEVIATION_HI *NUMBER DUAL_UOM_DEVIATION_HIGH NUMBER =DEVIATION_HI * 100
ONT_PRICING_QTY_SO
URCE
NUMBER(5) ONT_PRICING_QTY_SOURCE VARCHAR2(30) =P, if ONT_PRICING_QTY_SOURCE =0
=S, if ONT_PRICING_QTY_SOURCE =1
LEVEL_CODE NUMBER(5) Obsolete, not supported in OPM.
LOT_CTL *NUMBER(5) LOT_CONTROL_CODE NUMBER =LOT_CTL +1
LOT_INDIVISIBLE *NUMBER(5) LOT_DIVISIBLE_FLAG VARCHAR2(1) =Y if LOT_INDIVISIBLE =0

=N if LOT_INDIVISIBLE =1
AUTOLOT_ACTIVE_INDI
CATOR
NUMBER(1) In Oracle Inventory, the auto lot
numbering is always enabled for a lot or
lot/child lot controlled items.
LOT_PREFIX VARCHAR2(32) AUTO_LOT_ALPHA_PREFIX VARCHAR2(30) LOT_PREFIX can be null in OPM. In case
the value is NULL in IC_ITEM_MST_B,
use the default value from column
AUTO_LOT_ALPHA_PREFIX in
GMI_MIGRATION_PARMS table.
LOT_SUFFIX NUMBER(32) START_AUTO_LOT_NUMBER VARCHAR2(30) LOT_SUFFIX can be null in OPM. In case
the value is NULL in IC_ITEM_MST_B,
use the default value from column
START_AUTO_LOT_NUMBER in
SUBLOT_CTL *NUMBER(5) CHILD_LOT_FLAG
CHILD_LOT_VALIDATION_FLAG
COPY_LOT_ATTRIBUTE_FLAG
PARENT_CHILD_GENERATION_
FLAG
VARCHAR2(1)
VARCHAR2(1)
VARCHAR2(1)
If SUBLOT_CTL =1 THEN
CHILD_LOT_FLAG =Y
CHILD_LOT_VALIDATION_FLAG =Y
COPY_LOT_ATTRIBUTE_FLAG =N
PARENT_CHILD_GENERATION_
FLAG=C
SUBLOT_PREFIX VARCHAR2(32) CHILD_LOT_PREFIX VARCHAR2(30) SUBLOT_PREFIX can be null in OPM. In
case the value is NULL in
IC_ITEM_MST_B, use the default value
from column CHILD_LOT_PREFIX in
SUBLOT_SUFFIX NUMBER(32) CHILD_LOT_STARTING_NUMBE
R
NUMBER SUBLOT_SUFFIX can be null in OPM. In
case the value is NULL in
IC_ITEM_MSTn_B, use the default value
from column
CHILD_LOT_STARTING_NUMBER in
LOCT_CTL *NUMBER(5) LOCATION_CONTROL_CODE NUMBER =LOCT_CTL +1
NONINV_IND *NUMBER(5) INVENTORY_ITEM_FLAG
INVENTORY_ASSET_FLAG
COSTING_ENABLED_FLAG
STOCK_ENABLED_FLAG
BUILD_IN_WIP_FLAG
MTL_TRANSACTIONS_ENABLE
D_FLAG
VARCHAR2(1)
VARCHAR2(1)
VARCHAR2(1)
VARCHAR2(1)
IF NONINV_IND =1
Set all of these flags to N.
ELSE
No Change
MATCH_TYPE *NUMBER(5) Obsolete.
INACTIVE_IND *NUMBER(5) BUILD_IN_WIP_FLAG
PURCHASING_ENABLED_FLAG
MTL_TRANSACTIONS_ENABLE
D_FLAG
STOCK_ENABLED_FLAG
CUSTOMER_ORDER_ENABLED
_FLAG
INTERNAL_ORDER_ENABLED_F
LAG
INVOICE_ENABLED_FLAG
RECIPE_ENABLED_FLAG
PROCESS_EXECUTION_ENABL
ED_FLAG
PROCESS_COSTING_ENABLED
_FLAG
PROCESS_QUALITY_ENABLED
_FLAG
VARCHAR2(1) IF INACTIVE_FLAG =1 THEN
Set all these flags to N.
ELSE
No Change.

INV_TYPE VARCHAR2(4) ITEM_TYPE VARCHAR2(30) OPM Inventory types are migrated to Item
Types in discrete. The Item Types are
defined as Lookup Codes.
SHELF_LIFE *NUMBER SHELF_LIFE_CODE
SHELF_LIFE_DAYS
NUMBER
NUMBER
If(LOT_CTL =0 or
(LOT_CTL =1 and SHELF_LIFE =
NULL))
SHELF_LIFE_CODE =1 (No Control)
ELSE
SHELF_LIFE_CODE =2 (Shelf Life
Days)

SHELF_LIFE_DAYS =SHELF_LIFE

RETEST_INTERVAL *NUMBER RETEST_INTERVAL NUMBER
GL_CLASS VARCHAR2(8) All Item Classes are converged to Item
categories. For example, GL_CLASS is

assigned as a category in the
MTL_ITEM_CATEGORIES table.
INV_CLASS VARCHAR2(8) All Item Classes are converged to Item
categories. For example, INV_CLASS is
SALES_CLASS VARCHAR2(8) All Item Classes are converged to Item
categories. For example, SALES_CLASS
is assigned as a category in the
SHIP_CLASS VARCHAR2(8) All Item Classes are converged to Item
categories. For example, SHIP_CLASS is
FRT_CLASS VARCHAR2(8) All Item Classes are converged to Item
categories. For example, FRT_CLASS is
PRICE_CLASS VARCHAR2(8) All Item Classes are converged to Item
categories. For example, PRICE_CLASS
STORAGE_CLASS VARCHAR2(8) All Item Classes are converged to Item
categories. For example,
STORAGE_CLASS is assigned as a
category in the MTL_ITEM_CATEGORIES
table.
PURCH_CLASS VARCHAR2(8) All Item Classes are converged to Item
categories. For example, PURCH_CLASS
TAX_CLASS VARCHAR2(8) All Item Classes are converged to Item
categories. For example, GL_CLASS is
CUSTOMS_CLASS VARCHAR2(8) All Item Classes are converged to Item
CUSTOMS_CLASS is assigned as a
table.
ALLOC_CLASS VARCHAR2(8) All Item Classes are converged to Item
categories. For example, ALLOC_CLASS
PLANNING_CLASS VARCHAR2(8) All Item Classes are converged to Item
PLANNING_CLASS is assigned as a
table.
ITEMCOST_CLASS VARCHAR2(8) All Item Classes are converged to Item
ITEMCOST_CLASS is assigned as a
table.
SEQ_DPND_CLASS VARCHAR2(8) All Item Classes are converged to Item
SEQ_DPND_CLASS is assigned as a
table.
COST_MTHD_CODE VARCHAR2(4) Obsolete. Not on OPM form.
UPC_CODE VARCHAR2(16) There is no matching column in Oracle
Inventory for this field. This column
migrates as an obsolete column to the
flexfield.
GRADE_CTL *NUMBER(5) GRADE_CONTROL_FLAG VARCHAR2(1) =Y if GRADE_CTL =1
=N if GRADE_CTL =0
STATUS_CTL *NUMBER(5) LOT_STATUS_ENABLED VARCHAR2(1) =Y if STATUS_CTL =1
=N if STATUS_CTL =0
QC_GRADE VARCHAR2(4) DEFAULT_GRADE VARCHAR2
(150)

LOT_STATUS VARCHAR2(4) DEFAULT_LOT_STATUS_ID NUMBER Note that the STATUS_ID is obtained from
the IC_LOTS_STS.STATUS_ID . This
column is populated in OPM by material

status migration.
BULK_ID NUMBER(10) Obsolete. Not on OPM form.
PKG_ID NUMBER(10) Obsolete. Not on OPM form.
QCITEM_ID NUMBER(10) Obsolete.
QCHOLD_RES_CODE VARCHAR2(4) Obsolete.
EXPACTION_CODE VARCHAR2(4) EXPIRATION_ACTION_CODE VARCHAR2(32)
FILL_QTY *NUMBER Obsolete. Not on OPM form.
FILL_UM VARCHAR2(4) Obsolete. Not on OPM form.
EXPACTION_INTERVAL *NUMBER EXPIRATION_ACTION_INTERVA
L
NUMBER
PHANTOM_TYPE *NUMBER(5) Obsolete. Not on OPM form.
WHSE_ITEM_ID *NUMBER(10) Warehouse items were used in OPM
Production for plant/warehouse rules.
Going forward, these rules are not used by
the OPM production in the convergence
model.

Warehouse items were also used in the
OPM MRP module. This module is
obsolete in the Converged model.

EXPERIMENTAL_IND *NUMBER(5) ENG_ITEM_FLAG VARCHAR2(1) =Y, if EXPERIMENTAL_IND =1
=N, if EXPERIMENTAL_IND =0
EXPORTED_DATE *DATE Obsolete. Not on OPM form.
TRANS_CNT NUMBER(10) Obsolete. Not on OPM form.
DELETE_MARK *NUMBER(5) See INACTIVE_IND See INACTIVE_IND. Delete mark is
migrated like inactive indicator.
TEXT_CODE NUMBER(10) Migrated as edit text.
COMMODITY_CODE VARCHAR2(9) Obsolete. A separate migration script
existing in OPM from release 11.5.9
onwards which migrates the commodity
code as Item Categories and assigns
them to Items. No separate migration is
needed for this column.
ITEM_ABCCODE VARCHAR2(4) The assignment of ABC code in OPM item
master is not functional. OPM Physical
Inventory uses ABC code from the
warehouse rules.
<>Since the Physical Inventory will be
replaced with the Oracle Discrete Physical
Inventory, this column doesnt need to be
converged.
However, the actual ABC Rank (Classes
in discrete) can be converged to the ABC
Class master table in discrete. The
assignment of the ABC class to item is
more complex in discrete and cannot be
automatically determined using the OPM
setup.
ALLOC_CATEGORY_ID NUMBER This category assignment already exists in
Item Categories in discrete. If not, then it
migrates as an item category in discrete.
CUSTOMS_CATEGORY_I
D
NUMBER This category assignment already exists in
FRT_CATEGORY_ID NUMBER This category assignment already exists in
GL_CATEGORY_ID NUMBER This category assignment already exists in
INV_CATEGORY_ID NUMBER This category assignment already exists in
COST_CATEGORY_ID NUMBER This category assignment already exists in
PLANNING_CATEGORY_I
D

PRICE_CATEGORY_ID NUMBER This category assignment already exists in
PURCH_CATEGORY_ID NUMBER This category assignment already exists in
SALES_CATEGORY_ID NUMBER This category assignment already exists in
SEQ_CATEGORY_ID NUMBER This category assignment already exists in
SHIP_CATEGORY_ID NUMBER This category assignment already exists in
STORAGE_CATEGORY_I
D
TAX_CATEGORY_ID NUMBER This category assignment already exists in
Who Columns *DATE Standard Who columns
ATTRIBUTE1-30 VARCHAR2
(240)
(240)
The flexfield columns are migrated if the
flexfields are not defined in Discrete Item
Master or they are defined but do not
conflict with the OPM Item Master flexfield
definition.
Otherwise, an error is reported in the
validation script.
ATTRIBUTE_CATEGORY VARCHAR2(30) ATTRIBUTE_CATEGORY VARCHAR2(30) This column is migrated only if the
attribute category is blank in the discrete
item master.
validation script.

IC_PLNT_INV

Source Column
(in IC_PLNT_INV)
Data Type
(*=Not Null)
Destination Column
(in MTL_SYSTEM_ITEMS)
Date Type Comments
ORGN_CODE VARCHAR2(4) ORGANIZATION_ID NUMBER Note that the lead time is migrated only if
1.There is record for the item and
organization of the OPM
warehouse (corresponding to
discrete organization) or
2.There is a record for the item and a
NULL organization.
FIXED_LEADTIME *NUMBER FIXED_LEAD_TIME NUMBER
VARIABLE_LEADTIME *NUMBER VARIABLE_LEAD_TIME NUMBER =VARIABLE_LEADTIME / STD_QTY

IC_ITEM_CPG

Source Column
(in IC_ITEM_CPG)
Data Type
(*=Not Null)
Destination Column
(in MTL_SYSTEM_ITEMS)
Date Type Comments
ORGANIZATION_ID NUMBER Only the process enabled organizations
will be affected by this migration.
IC_MATR_DAYS NUMBER(5) MATURITY_DAYS NUMBER
IC_HOLD_DAYS NUMBER(5) HOLD_DAYS NUMBER
Who Columns Who columns

IC_ITEM_MST_TL

Source Column (in
IC_ITEM_MST_tl)
Data Type
(*=Not Null)
Destination
Column (in
MTL_SYSTEM_ITEMS_tl)
Date Type Comments
ORGANIZATION_ID NUMBER Only the process enabled organizations
will be affected by this migration.
LANGUAGE *VARCHAR2(4) LANGUAGE VARCHAR2(4)
SOURCE_LANG *VARCHAR2(4) SOURCE_LANG VARCHAR2(4)
ITEM_DESC1 *VARCHAR2
(70)
DESCRIPTION VARCHAR2
(240)

ITEM_DESC2 VARCHAR2(70) LONG_DESCRIPTION VARCHAR2
(4000)
We currently dont synchronize this
column. Note that this migration will only
happen if the LONG_DESCRIPTION
column is null in discrete.

GMI_ITEM_CATEGORIES

Source Column (in
GMI_ITEM_CATEGORI
ES)
Data Type
(*=Not Null)
Destination Column (in
MTL_ITEM_CATEGORIES)
Date Type Comments
ITEM_ID *NUMBER INVENTORY_ITEM_ID NUMBER
ORGANIZATION_ID NUMBER
CATEGORY_SET_ID *NUMBER CATEGORY_SET_ID NUMBER
CATEGORY_ID *NUMBER CATEGORY_ID NUMBER

GMI_CATEGORY_SETS
Source Column
(in
gmi_category_sets)
Data Type
(*=Not Null)
Destination Column
(in MTL_DEFAULT_
CATEGORY_SETS )
Date Type Comments
OPM_CLASS *VARCHAR2(40) FUNCTIONAL_AREA_ID NUMBER
CATEGORY_SET_ID NUMBER CATEGORY_SET_ID NUMBER
USER_OPM_CLASS *VARCHAR2(40)
RESTRICTED VARCHAR2(1)

IC_INVN_TYP

Source Column
(in IC_INVN_TYP)
Data Type
(*=Not Null)
Destination Column
(in FND_LOOKUP_VALUES)
Date Type Comments
LOOKUP_TYPE *VARCHAR2(30) =ITEM TYPE
LANGUAGE *VARCHAR2(30) MLS setup
SOURCE_LANG *VARCHAR2(4) MLS setup
SECURITY_GROUP_ID *NUMBER(15) 0
VIEW_APPLICATION_ID *NUMBER(15) 3 (AU)
TERRITORY_CODE VARCHAR2(2) NULL
TAG VARCHAR2(30) NULL
INV_TYPE *VARCHAR2(4) LOOKUP_CODE *VARCHAR2(30)
INV_TYPE *VARCHAR2(4) MEANING *VARCHAR2(80)
INV_TYPE_DESC *VARCHAR2(40) DESCRIPTION VARCHAR2(240)
DELETE_MARK *NUMBER(5) ENABLED_FLAG *VARCHAR2(1) =Y, if Delete Mark =0
=N, if Delete Mark =1
START_DATE_ACTIVE DATE NULL
END_DATE_ACTIVE DATE NULL
Who Columns Who Columns
ATTRIBUTE_CATEGORY VARCHAR2(30) ATTRIBUTE_CATEGORY VARCHAR2(30)
ATTRIBUTE1-30 VARCHAR2(240) ATTRIBUTE1-15 VARCHAR2(150)
TAG VARCHAR2(30)

IC_LOTS_MST
Source Column
(in IC_LOTS_MST)
Data Type
(*=Not Null)
Destination Column
(in MTL_LOT_NUMBERS)
Date Type Comments
ITEM_ID *NUMBER(10) INVENTORY_ITEM_ID NUMBER
ORGANIZATION_ID NUMBER
LOT_ID *NUMBER(10) No migration needed because discrete
uses lot_number as part of the key.
LOT_NO *VARCHAR2(32) PARENT_LOT_NUMBER
LOT_NUMBER
VARCHAR2(80) The following table shows the logic to
derive the lot number. Note that additional
logic to create new lots for lot status may
be needed as discussed in the overview
section of this migration. Also, the lot
number can already exist in
ic_lots_mst_mig table from the pre-
migration form.
Sublot
Control
Sublot
No
Parent
Lot
Lot
(Child)
Yes NULL NULL LOT_NO
Yes Not
NULL
LOT_
NO
LOT_NO
||
SUBLOT
_NO
No - NULL LOT_NO
SUBLOT_NO VARCHAR2(32) PARENT_LOT_NUMBER
LOT_NUMBER
VARCHAR2(80) Same as above

LOT_DESC VARCHAR2(40) DESCRIPTION VARCHAR2
(256)
Description column in discrete inventory
is non-functional. However, we will
migrate the OPM Lot description to this
column.
QC_GRADE VARCHAR2(4) GRADE_CODE VARCHAR2
(150)
Foreign Key reference to the
MTL_GRADES table.
STATUS_ID NUMBER The LOT_STATUS from IC_LOCT_INV
for this lot will be used to derive this value.
See above for the example and discussion
on case where a lot exists in multiple
location
AVAILABILITY_TYPE NUMBER This value will be derived from the
MTL_MATERIAL_STATUSES for the
STATUS_ID of the lot.
INVENTORY_ATP_CODE NUMBER This value will be derived from the
RESERVABLE_TYPE NUMBER This value will be derived from the
EXPACTION_CODE VARCHAR2(4) EXPIRATION_ACTION_CODE VARCHAR2(32) Foreign Key reference to the
MTL_ACTIONS table.
EXPACTION_DATE DATE EXPIRATION_ACTION_DATE DATE
LOT_CREATED DATE ORIGINATION_DATE DATE
EXPIRE_DATE DATE EXPIRATION_DATE DATE
RETEST_DATE DATE RETEST_DATE DATE
STRENGTH *NUMBER Obsolete Column, not used in OPM.
INACTIVE_IND *NUMBER(5) DISABLE_FLAG NUMBER =1, if INACTIVE_IND =1
=NULL, otherwise
ORIGINATION_TYPE *NUMBER(5) ORIGINATION_TYPE NUMBER(2)
SHIPVEND_ID NUMBER(10) VENDOR_ID

VENDOR_NAME
NUMBER

VARCHAR2
(240)
Use this to get the discrete vendor_id
select of_vendor_id
from po_vend_mst
where vendor_id = <SHIPVEND_ID>
VENDOR_LOT_NO VARCHAR2(32) SUPPLIER_LOT_NUMBER VARCHAR2
(150)

DELETE_MARK *NUMBER(5) DISABLE_FLAG NUMBER =1, if DELETE_MARK =1
=NULL, otherwise
(240)
The flexfield columns are migrated if the
flexfields are not defined in Discrete Lot
Master or they are defined but do not
conflict with the OPM Lot Master flexfield
definition.
validation script.
ATTRIBUTE_CATEGORY VARCHAR2(30) This column is migrated only if the
attribute category is blank in the discrete
item master.
validation script.
ODM_LOT_NUMBER VARCHAR2(30) Obsolete in convergence.

GMD_GRADES_B

Source Column
(in GMD_GRADES_B)
Data Type
(*=Not Null)
Destination Column
(in MTL_GRADES_B)
Date Type Comments
QC_GRADE *VARCHAR2(4) GRADE_CODE VARCHAR2
(150)

QC_GRADE_DESC VARCHAR2(40) Description is migrated to the TL table
only.
DELETE_MARK *NUMBER(5) DISABLE_FLAG VARCHAR2(1) =Y if delete_mark =1
=N otherwise
(240)
(240)


GMD_GRADES_TL

Source Column
(in GMD_GRADES_TL)
Data Type
(*=Not Null)
Destination Column
(in MTL_GRADES_TL)
Date Type Comments
QC_GRADE *VARCHAR2(4) GRADE_CODE VARCHAR2(150)
QC_GRADE_DESC *VARCHAR2(40) DESCRIPTION VARCHAR2(240)

GMD_ACTIONS_B

Source Column
(in GMD_ACTIONS_B)
Data Type
(*=Not Null)
Destination Column
(in MTL_ACTIONS_B)
Date Type Comments
ACTION_CODE *VARCHAR2(32) ACTION_CODE VARCHAR2(32)
ACTION_INTERVAL *NUMBER Currently Non-functional in OPM.
Obsolete in the converged model.
DELETE_MARK *NUMBER(5) DISABLE_FLAG VARCHAR2(1) =Y if delete_mark =1
=N otherwise
(240)
(240)


GMD_ACTIONS_TL

Source Column
(in GMD_ACTIONS_TL)
Data Type
(*=Not Null)
Destination Column
(in MTL_ACTIONS_TL)
Date Type Comments
ACTION_CODE *VARCHAR2(32) ACTION_CODE VARCHAR2(32)
DESCRIPTION *VARCHAR2(80) DESCRIPTION VARCHAR2(80)


IC_LOTS_STS to MTL_MATERIAL_STATUSES_B

Source Column
(in IC_LOTS_STS)
Data Type
(*=Not Null)
MTL_MATERIAL_STATUSES_
B)
Date Type Comments
LOT_STATUS *VARCHAR2(4) Will be migrated to
mtl_material_statuses_tl table.
STATUS_ID System generated surrogate for the
status.
STATUS_DESC *VARCHAR2(40) Will be migrated to
QCHOLD_RES_CODE VARCHAR2(4) Obsolete
ZONE_CONTROL NUMBER =2 (Means No)
Zone refers to the Subinventory Status
control
LOCATOR_CONTROL NUMBER =2 ( No )
LOT_CONTROL NUMBER =1 ( Yes )
SERIAL_CONTROL NUMBER =2 ( No )
NETTABLE_IND *NUMBER(5) AVAILABILITY_TYPE NUMBER =1, if NETTABLE_IND=1 &
REJ ECTED_IND=0
=2, otherwise
ORDER_PROC_IND *NUMBER(5) NUMBER T=It will mapped to the allowed/disallowed
transaction types in
mtl_status_transaction_control as show
below in the data mapping.
PROD_IND *NUMBER(5) NUMBER Same as above
SHIPPING_IND *NUMBER(5) NUMBER Same as above
REJ ECTED_IND *NUMBER(5) RESERVABLE_TYPE
INVENTORY_ATP_CODE
NUMBER
NUMBER
=1, if NETTABLE_IND =1
=2, otherwise
DELETE_MARK *NUMBER(5) ENABLED_FLAG NUMBER =1, if DELETE_MARK =0
=2 otherwise
Who Column Who Column

IC_LOTS_STS to MTL_MATERIAL_STATUSES_TL

Source Column
(in IC_LOTS_STS)
Data Type
(*=Not Null)
Destination Column (in MTL_
MATERIAL_STATUSES_TL)
Date Type Comments
LOT_STATUS *VARCHAR2(4) STATUS_CODE VARCHAR2(80) Will be migrated to
STATUS_ID NUMBER System generated surrogate for the
status.
STATUS_DESC *VARCHAR2(40) DESCRIPTION VARCHAR2(240) Will be migrated to
LANGUAGE VARCHAR2(4) Determine by MLS package when called
to insert a row.
SOURCE_LANG VARCHAR2(4) Determine by MLS package when called
to insert a row.
Who Column Who Column

IC_LOTS_STS to MTL_STATUS_TRANSACTION_CONTROL

Source Column
(in IC_LOTS_STS)
Data Type
(*=Not Null)
MTL_STATUS_TRANSACTION_
CONTROL)
Date Type Comments
LOT_STATUS *VARCHAR2(4)
STATUS_ID NUMBER System generated surrogate for the
status.
IS_ALLOWED NUMBER =1, (Yes) if OPM indicators are 1
=2, (No) otherwise.
NETTABLE_IND *NUMBER(5)
ORDER_PROC_IND *NUMBER(5) TRANSACTION_TYPE_ID NUMBER This indicator allows or disallows
transaction type based on the Lot Status.
PROD_IND *NUMBER(5) TRANSACTION_TYPE_ID NUMBER This indicator allows or disallows
SHIPPING_IND *NUMBER(5) TRANSACTION_TYPE_ID NUMBER This indicator allows or disallows
REJ ECTED_IND *NUMBER(5) TRANSACTION_TYPE_ID NUMBER This indicator allows or disallows
transaction type based on the Lot Status..
Who Column

IC_ITEM_CNV

Source Column
(in IC_ITEM_CNV)
Data Type
(*=Not Null)
MTL_LOT_UOM_CLASS
_CONVERSIONS)
Date Type Comments
ORGANIZATION_ID *NUMBER Call the get_ODM_lot routine to get (or
create) the discrete item/ lot for the OPM
item/ lot.
LOT_ID *NUMBER(10) LOT_NUMBER *VARCHAR2(80) Call the get_ODM_lot routine to get (or
item/ lot.
ITEM_ID *NUMBER(10) INVENTORY_ITEM_ID *NUMBER Call the get_ODM_lot routine to get (or
item/ lot.
FROM_UNIT_OF_MEASURE *VARCHAR2(25) Select the value for the base UOM of
the UOM Class of the Items primary
UOM.

Select b.UNIT_OF_MEASURE,
b.UOM_CODE,
b.UOM_CLASS
from mtl_system_items_b I,
mtl_units_of_measure iu,
mtl_units_of_measuer bu
where
i.organication_id = <organization_id>
and i.inventory_item_id =
<inventory_item_id>
and i.PRIMARY_UOM_CODE =
iu.uom_Code
and iu.uom_class = bu.uom_class
and bu.base_uom_flag = Y
FROM_UOM_CODE *VARCHAR2(3) Derive the value using the above logic
FROM_UOM_CLASS *VARCHAR2(10) UOM Class of the items primary UOM.
TO_UNIT_OF_MEASURE *VARCHAR2(25) Select the base unit of measure for the
um_type.
select unit_of_measure, uom_code
from mtl_units_of_measure
where
uom_class = <um_type> and
base_uom_flag = y
TO_UOM_CODE *VARCHAR2(3) Call the get_ODM_lot routine to get (or

item/ lot.
UM_TYPE *VARCHAR2(10) TO_UOM_CLASS *VARCHAR2(10)
TYPE_FACTOR *NUMBER CONVERSION_RATE *NUMBER
TYPE_FACTORREV *NUMBER Discrete tables do not store the reverse
factors
CONVERSION_ID *NUMBER System generated surrogate using the
MTL_CONVERSION_ID_S sequence.
EVENT_SPEC_DISP_ID NUMBER EVENT_SPEC_DISP_ID NUMBER
DELETE_MARK *NUMBER(5) DISABLE_DATE DATE =LAST_UPDATE_DATE, if
DELETE_MARK =1
=NULL, otherwise.

GMI_ITEM_CONV_AUDIT

Source Column (in
GMI_ITEM_CONV_AUDIT
)
Data Type
(*=Not Null)
MTL_LOT_CONV_AUDIT)
Date Type Comments
CONV_AUDIT_ID *NUMBER CONV_AUDIT_ID *NUMBER System generated surrogate using the
MTL_CONV_AUDIT_ID_S sequence.
CONVERSION_ID *NUMBER CONVERSION_ID *NUMBER Use the CONVERSION_ID from the
MTL_LOT_UOM_CLASS_CONMVERSIO
NS table.
CONVERSION_DATE *DATE CONVERSION_DATE *DATE
REASON_CODE VARCHAR2(4) REASON_ID NUMBER REASON_ID from the
MTL_TRANSACTION_REASONS table
for the REASON_CODE
OLD_TYPE_FACTOR NUMBER OLD_CONVERSION_RATE NUMBER
NEW_TYPE_FACTOR *NUMBER NEW_CONVERSION_RATE *NUMBER
EVENT_SPEC_DISP_ID NUMBER EVENT_SPEC_DISP_ID NUMBER
BATCH_ID NUMBER(10) BATCH_ID NUMBER
UPDATE_BATCH_INDICATO
R
NUMBER(10) UPDATE_TYPE_INDICATOR *NUMBER

GMI_ITEM_CONV_AUDIT_DETAILS

Source Column
(in GMI_ITEM_CONV_
AUDIT_DETAILS)
Data Type
(*=Not Null)
MTL_LOT_CONV_AUDIT
_DETAILS)
Date Type Comments
CONV_AUDIT_DETAIL_ID *NUMBER CONV_AUDIT_DETAIL_ID *NUMBER System generated surrogate using the
MTL_CONV_AUDIT_DETAIL_ID_S
sequence
CONV_AUDIT_ID *NUMBER CONV_AUDIT_ID *NUMBER CONV_AUDIT_ID from the
MTL_LOT_CONV_AUDIT table.
REVISION VARCHAR2(3) =NULL
WHSE_CODE *VARCHAR2(4) ORGANIZATION_ID *NUMBER =ORGANIZATION_ID from
IC_WHSE_MST for the WHSE_CODE.
SUBINVENTORY_CODE VARCHAR2(10) =WHSE_CODE
LPN_ID NUMBER NULL
LOCATION *VARCHAR2(16) LOCATOR_ID NUMBER =INVENTORY_LOCATION_ID from
IC_LOCT_MST for the WHSE_CODE,
LOCATION.
OLD_ONHAND_QTY *NUMBER OLD_PRIMARY_QTY *NUMBER
OLD_ONHAND_QTY2 NUMBER OLD_SECONDARY_QTY NUMBER
NEW_ONHAND_QTY NUMBER NEW_PRIMARY_QTY NUMBER
NEW_ONHAND_QTY2 NUMBER NEW_SECONDARY_QTY NUMBER

TRANS_QTY NUMBER TRANSACTION_PRIMARY_QTY NUMBER
TRANS_QTY2 NUMBER TRANSACTION_SECONDARY_QTY NUMBER
TRANS_UPDATE_FLAG *VARCHAR2(1) TRANSACTION_UPDATE_FLAG *VARCHAR2(2)

CREATE_TRANSFER_PUB
This table is mapping to the API call that is used to transfer inventory balances from OPM to Oracle Inventory
Destination Column
(in Create_transfer_pub)
In/ Out Data Type Comments
P_api_version IN NUMBER
P_init_msg_list IN VARCHAR2 DEFAULT FND_API.G_FALSE
P_commit IN VARCHAR2 DEFAULT FND_API.G_FALSE
P_validation_level IN NUMBER DEFAULT FND_API.G_VALID_LEVEL_FULL
X_return_status OUT NOCOPY VARCHAR2
X_msg_count OUT NOCOPY NUMBER
X_msg_data OUT NOCOPY VARCHAR2
P_hdr_rec IN GMIVDX.hdr_type
P_line_rec_tbl IN GMIVDX.line_type_tbl
P_lot_rec_tbl IN GMIVDX.lot_type_tbl
x_hdr_row OUT NOCOPY gmi_discrete_transfers%ROWTYPE
x_line_row_tbl OUT NOCOPY GMIVDX.line_row_tbl
x_lot_row_tbl OUT NOCOPY GMIVDX.lot_row_tbl

IC_LOT_INV to Header Type
This table is mapping to the API call.
Source Column
(in IC_LOCT_INV)
Data Type
(*=Not Null)
Destination (in
HDR_TYPE record)
Comments
ORGN_CODE =orgn_code of the inventory balance warehouse.
CO_CODE API will internally determine the values when determining the
charge account.
TRANSFER_NUMBER Automatically generated number
TRANSFER_TYPE =0 ( Process to Discrete)
=1 ( Discrete to Process) used for transferring negative
balances.
TRANS_DATE =sysdate
COMMENTS OPM Convergence Migration
ATTRIBUTE_CATEGORY NULL
ATTRIBUTE1-30 NULL
ASSIGNMENT_TYPE NULL
TRANSACTION_HEADER_ID NULL

IC_LOCT_INV to Line Type
Source Column
(in IC_LOCT_INV)
Data Type
(*=Not Null)
Destination (in
LINE_TYPE record)
Comments
LINE_NO Automatically generated line number for each transfer. For a
single transfer multiple lines can be specified and they start
with 1 for each transfer.
ITEM_ID NUMBER(10) OPM_ITEM_ID
WHSE_CODE VARCHAR2(4) OPM_WHSE_CODE
LOCATION VARCHAR2(16) OPM_LOCATION
LOT_ID NUMBER(10) OPM_LOT_ID =0 for non-lot controlled items.
=NULL for lot controlled items. For lot controlled items, the
LOT_TYPE record will be used to specify multiple lots.
OPM_LOT_EXPIRATION_DATE API internally determines the values.
LOT_STATUS VARCHAR2(4) OPM_LOT_STATUS API internally determines the values.
OPM_GRADE API internally determines the values.
OPM_CHARGE_ACCT_ID API internally determines the values.
OPM_CHARGE_AU_ID API internally determines the values.
OPM_REASON_CODE NULL
ODM_INV_ORGANIZATION_ID MTL_ORGANIZATION_ID from the IC_WHSE_MST for the
OPM warehouse.
ODM_ITEM_ID Call the get_ODM_item to get Discrete Item from discrete
inventory for the OPM Item and the warehouse.
ODM_ITEM_REVISION NULL. No OPM items are revision controlled.
WHSE_CODE VARCHAR2(4) ODM_SUBINVENTORY Determine the subinventory associated to the stock locator
linked to the OPM location. If the item is not location
controlled, then whse_code will be used as the subinventory.
IN most cases this should be the (the default subinventory
created by OPM trigger during the warehouse/inventory
organization creation in discrete.)
ODM_LOCATOR_ID INVENTORY_LOCATION_ID from the IC_LOCT_MST for the
OPM Warehouse and Location.
ODM_LOT_NUMBER LOT_NUMBER from the IC_LOTS_MST_MIG table for the
Inventory organization_id and OPM LOT_ID.
ODM_LOT_EXPIRATION_DATE API internally determines the values.
ODM_CHARGE_ACCOUNT_ID API internally determines the values.
ODM_PERIOD_ID API internally determines the values.
ODM_UNIT_COST NULL
ODM_REASON_ID NULL
LOCT_ONHAND NUMBER QUANTITY Only for non-lot controlled items. For lot controlled items,
multiple lots can be specified in the lot_type record and this
quantity should be the sum of the lot quantity.
QUANTITY_UM =ITEM_UM from ic_item_mst_b for the item_id.
LOCT_ONHAND2 NUMBER QUANTITY2 Only for non-lot controlled items. For lot controlled items,
multiple lots can be specified in the lot_type record and this
quantity should be the sum of the lot quantity.
OPM_PRIMARY_QUANTITY API internally determines the values.
ODM_PRIMARY_QUANTITY API internally determines the values.
LOT_LEVEL API internally determines the values.
ATTRIBUTE1-30 NULL
OPM_ITEM_NO API internally determines the values.
LOT_CONTROL API internally determines the values.
ODM_QUANTITY_UOM_CODE API internally determines the values.
OPM_LOT_NO API internally determines the values.
OPM_SUBLOT_NO API internally determines the values.

IC_LOCT_INV to Lot Type
This table is mapping to the API call:
Source Column
(in IC_LOCT_INV)
Data Type
(*=Not Null)
Destination (in
LOT_TYPE record)
Comments
LINE_NO The line_no in the LINE_TYPE record for which the lot data is
being specified.
LOT_ID NUMBER(10) OPM_LOT_ID Call the get_ODM_lot to get Discrete Item/ Lot from the
discrete inventory for the OPM Items and the warehouse.
OPM_LOT_EXPIRATION_DATE API internally determines the values.
OPM_LOT_STATUS API internally determines the values.
OPM_GRADE API internally determines the values.
ODM_LOT_NUMBER LOT_NUMBER from the IC_LOTS_MST_MIG table for the
Inventory organization_id and OPM LOT_ID.
ODM_LOT_EXPIRATION_DATE API internally determines the values.
LOCT_ONHAND NUMBER QUANTITY
LOCT_ONHAND2 NUMBER QUANTITY2
LOCT_ONHAND NUMBER OPM_PRIMARY_QUANTITY
LOCT_ONHAND NUMBER ODM_PRIMARY_QUANTITY
OPM_LOT_NO API internally determines the values.
OPM_SUBLOT_NO API internally determines the values.

Material Reservation Record Mapping
The following is the mapping of Record ic_tran_pnd to mtl_reservations:
IC_TRAN_PND to Create_Reservations
Source Column
(in IC_TRAN_PND)
Data Type
(*=Not Null)
Destination (in
MTL_RESERVATIONS
record)
Comments
ORGN_CODE =orgn_code of the inventory balance warehouse.
CO_CODE API will internally determine the values when determining the
charge account.
TRANSFER_NUMBER Automatically generated number
TRANSFER_TYPE =0 ( Process to Discrete)
=1 ( Discrete to Process) used for transferring negative
balances.
TRANS_DATE =sysdate
COMMENTS OPM Convergence Migration
ATTRIBUTE1-30 NULL
ASSIGNMENT_TYPE NULL
TRANSACTION_HEADER_ID NULL

RESERVATION_ID NULL
REQUIREMENT_DATE OE_ORDER_LINES_ALL.REQUEST_DATE
ORGANIZATION_ID OE_ORDER_LINES_ALL.SHIP_FROM_ORG_ID
INVENTORY_ITEM_ID OE_ORDER_LINES_ALL.INVENTORY_ITEM_ID
DEMAND_SOURCE_TYPE_ID OE_ORDER_LINES_ALL.DEMAND_SOURCE_TYPE_ID
DEMAND_SOURCE_NAME NULL

DEMAND_SOURCE_LINE_ID OE_ORDER_LINES_ALL.LINE_ID
DEMAND_SOURCE_DELIVERY NULL
PRIMARY_UOM_CODE OE_ORDER_LINES_ALL.ORDER_QUANTITY_UOM
PRIMARY_UOM_ID NULL
PRIMARY_RESERVATION_QUANTITY OE_ORDER_LINES_ALL..ORDERED_QUANTITY
RESERVATION_UOM_CODE OE_ORDER_LINES_ALL.ORDER_QUANTITY_UOM
RESERVATION_UOM_ID NULL
RESERVATION_QUANTITY OE_ORDER_LINES_ALL.ORDERED_QUANTITY
LOT_NUMBER LOT_NO || SUBLOT_NO FROM IC_TRAN_PND

Organization Column Mapping

HR_LOCATIONS_ALL
The address associated with the organization is created in this table.
Column Value
LOCATION_CODE Orgn_Code
ADDRESS_LINE_1 Addr1
BILL_TO_SITE_FLAG NULL
COUNTRY Country_Code
DESCRIPTION Orgn_Name
DESIGNATED_RECEIVER_ID NULL
IN_ORGANIZATION_FLAG NULL
INACTIVE_DATE NULL
INVENTORY_ORGANIZATION_ID Migrated Organization_Id from Hr_Organization_Units this is updated after migrating the organization.
OFFICE_SITE_FLAG NULL
POSTAL_CODE Postal_Code
RECEIVING_SITE_FLAG NULL
REGION_1 Province
REGION_2 County
REGION_3 State_Code
SHIP_TO_LOCATION_ID NULL
SHIP_TO_SITE_FLAG NULL
DERIVED_LOCALE NULL
STYLE OPM
TAX_NAME NULL
TELEPHONE_NUMBER_1 NULL
TOWN_OR_CITY Addr4
HR_ORGANIZATION_UNITS
The HR organization is created in this table.
Column Value

Column Value
ORGANIZATION_ID hr_organization_units_s.nextval
BUSINESS_GROUP_ID Hr_operating_unts.business_group_id based on the fiscal policy operating unit.
COST_ALLOCATION_KEYFLEX_ID NULL
LOCATION_ID Location_Id generated from the above insert.
SOFT_CODING_KEYFLEX_ID NULL
DATE_FROM Creation_Date
NAME Orgn_Name
COMMENTS NULL
DATE_TO Set to SYSDATE if the org is being migrated as Inactive.
INTERNAL_EXTERNAL_FLAG INT
INTERNAL_ADDRESS_LINE NULL
TYPE NULL

HR_ORGANIZATION_INFORMATION
The HR organization classification for inventory organizations is created in this table if the Inventory_Org indicator is 1.
Column Value
ORG_INFORMATION_ID hr_organization_information_s.nextval
ORG_INFORMATION_CONTEXT CLASS
ORGANIZATION_ID Organization_Id generated above
ORG_INFORMATION1 INV
ORG_INFORMATION2 Y
ORG_INFORMATION3 NULL

After classifying the accounting information, it is created in this table.
Column Value
ORG_INFORMATION_ID hr_organization_information_s.nextval
ORG_INFORMATION_CONTEXT Accounting Information
ORG_INFORMATION1 Set_Of_Books ID from the template organization
ORG_INFORMATION2 Legal Entity ID from the template organization
ORG_INFORMATION3 Operation Unit from the template organization

MTL_PARAMETERS
The inventory organization is created in this table.
Column Value
ORGANIZATION_CODE Organization_Code from the Setup
MASTER_ORGANIZATION_ID Master Organization Id from the setup
PRIMARY_COST_METHOD Inherited from the template organization
COST_ORGANIZATION_ID Inherited from the template organization
DEFAULT_MATERIAL_COST_ID Inherited from the template organization
CALENDAR_EXCEPTION_SET_ID Inherited from the template organization
CALENDAR_CODE Inherited from the template organization
GENERAL_LEDGER_UPDATE_CODE Inherited from the template organization
DEFAULT_ATP_RULE_ID Inherited from the template organization
DEFAULT_PICKING_RULE_ID Inherited from the template organization
DEFAULT_LOCATOR_ORDER_VALUE Inherited from the template organization
DEFAULT_SUBINV_ORDER_VALUE Inherited from the template organization
NEGATIVE_INV_RECEIPT_CODE Inherited from the template organization
STOCK_LOCATOR_CONTROL_CODE Inherited from the template organization
MATERIAL_ACCOUNT Inherited from the template organization
MATERIAL_OVERHEAD_ACCOUNT Inherited from the template organization
MATL_OVHD_ABSORPTION_ACCT Inherited from the template organization
RESOURCE_ACCOUNT Inherited from the template organization

Column Value
PURCHASE_PRICE_VAR_ACCOUNT Inherited from the template organization
AP_ACCRUAL_ACCOUNT Inherited from the template organization
OVERHEAD_ACCOUNT Inherited from the template organization
OUTSIDE_PROCESSING_ACCOUNT Inherited from the template organization
INTRANSIT_INV_ACCOUNT Inherited from the template organization
INTERORG_RECEIVABLES_ACCOUNT Inherited from the template organization
INTERORG_PRICE_VAR_ACCOUNT Inherited from the template organization
INTERORG_PAYABLES_ACCOUNT Inherited from the template organization
COST_OF_SALES_ACCOUNT Inherited from the template organization
ENCUMBRANCE_ACCOUNT Inherited from the template organization
INTERORG_TRANSFER_CR_ACCOUNT Inherited from the template organization
MATL_INTERORG_TRANSFER_CODE Inherited from the template organization
INTERORG_TRNSFR_CHARGE_PERCENT Inherited from the template organization
SOURCE_ORGANIZATION_ID Inherited from the template organization
SOURCE_SUBINVENTORY Inherited from the template organization
SOURCE_TYPE Inherited from the template organization
SERIAL_NUMBER_TYPE Inherited from the template organization
AUTO_SERIAL_ALPHA_PREFIX Inherited from the template organization
START_AUTO_SERIAL_NUMBER Inherited from the template organization
AUTO_LOT_ALPHA_PREFIX Inherited from the template organization
LOT_NUMBER_UNIQUENESS 2 (None)
LOT_NUMBER_GENERATION Inherited from the template organization
LOT_NUMBER_ZERO_PADDING Inherited from the template organization
LOT_NUMBER_LENGTH Inherited from the template organization
STARTING_REVISION Inherited from the template organization
DEFAULT_DEMAND_CLASS Inherited from the template organization
ENCUMBRANCE_REVERSAL_FLAG Inherited from the template organization
MAINTAIN_FIFO_QTY_STACK_TYPE Inherited from the template organization
PROCESS_ENABLED_FLAG Y

Warehouse Subinventory Column Mapping

MTL_SECONDARY_INVENTORIES
The data from ic_whse_mst is migrated to this table for the rows where subinventory_ind =Y.
Column Value
SECONDARY_INVENTORY_NAME Whse_Code
ORGANIZATION_ID L_orgn_id
DESCRIPTION Whse_Name
DISABLE_DATE NULL
INVENTORY_ATP_CODE 1
AVAILABILITY_TYPE 1
RESERVABLE_TYPE 1
LOCATOR_TYPE If Org Locator Control Code =4 Then Assign 5 (Determined at item)
Else Assign 1
PICKING_ORDER NULL
DROPPING_ORDER NULL
MATERIAL_ACCOUNT Material_Account from Mtl_Parameters for :Organization_Id
MATERIAL_OVERHEAD_ACCOUNT Material_Overhead_Account from Mtl_Parameters for :Organization_Id
RESOURCE_ACCOUNT Resource_Account from Mtl_Parameters for :Organization_Id
OVERHEAD_ACCOUNT Overhead_Account from Mtl_Parameters for :Organization_Id
OUTSIDE_PROCESSING_ACCOUT Outside_Processing_Account from Mtl_Parameters for :Organization_Id
QUANTITY_TRACKED 1
ASSET_INVENTORY 1
SOURCE_TYPE NULL
SOURCE_SUBINVENTORY NULL
SOURCE_ORGANIZATION_ID NULL

Column Value
REQUISITION_APPROVAL_TYPE NULL
EXPENSE_ACCOUNT Expense_Account from Mtl_Parameters for :Organization_Id
ENCUMBRANCE_ACCOUNT Encumbrance_Account from Mtl_Parameters for :Organization_Id
ATTRIBUTE1..15 NULL
PREPROCESSING_LEAD_TIME NULL
PROCESSING_LEAD_TIME NULL
POSTPROCESSING_LEAD_TIME NULL
DEMAND_CLASS NULL
PROJ ECT_ID NULL
TASK_ID NULL
SUBINVENTORY_USAGE NULL
NOTIFY_LIST_ID NULL
DEPRECIABLE_FLAG 2
LOCATION_ID NULL
STATUS_ID 1
DEFAULT_LOC_STATUS_ID 1
LPN_CONTROLLED_FLAG 0
DEFAULT_COST_GROUP_ID Default_Cost_Group_Id from Mtl_Parameters for :Organization_Id
PICK_UOM_CODE NULL
CARTONIZATION_FLAG 0
PLANNING_LEVEL 2
DEFAULT_COUNT_TYPE_CODE 2 (Order Quantity)
SUBINVENTORY_TYPE 1 (Storage)
ENABLE_BULK_PICK N

MTL_ITEM_LOCATIONS
The data from ic_loct_mst is migrated to this table.
Column Value
INVENTORY_LOCATION_ID Mtl_item_locations_s.nextval
ORGANIZATION_ID L_orgn_id
DESCRIPTION Loct_Name
DESCRIPTIVE_TEXT NULL
DISABLE_DATE NULL
PICKING_ORDER
LOCATION_MAXIMUM_UNITS NULL
SUBINVENTORY_CODE :Whse_Code
LOCATION_WEIGHT_UOM_CODE NULL
MAX_WEIGHT NULL
VOLUME_UOM_CODE NULL
MAX_CUBIC_AREA NULL
SEGMENT1 :Location
SEGMENT2..20 NULL
SUMMARY_FLAG N
ENABLED_FLAG Y
START_DATE_ACTIVE :Creation_Date
END_DATE_ACTIVE NULL
ATTRIBUTE1..15 NULL
PROJ ECT_ID NULL
TASK_ID NULL
PHYSICAL_LOCATION_ID NULL
PICK_UOM_CODE NULL
DIMENSION_UOM_CODE NULL
LENGTH NULL
WIDTH NULL
HEIGHT NULL
LOCATOR_STATUS 1
STATUS_ID NULL
CURRENT_CUBIC_AREA NULL

Column Value
AVAILABLE_CUBIC_AREA NULL
CURRENT_WEIGHT NULL
AVAILABLE_WEIGHT NULL
LOCATION_CURRENT_UNITS NULL
LOCATION_AVAILABLE_UNITS NULL
SUGGESTED_CUBIC_AREA NULL
EMPTY_FLAG NULL
MIXED_ITEMS_FLAG NULL
DROPPING_ORDER NULL
LOCATION_SUGGESTED_UNITS NULL
AVAILABILITY_TYPE NULL
INVENTORY_ATP_CODE 1
RESERVABLE_TYPE 1
INVENTORY_ITEM_ID NULL

Cost Management Table Mapping
Global Column Changes
The following shows data model changes necessary for Co_Code, Item_id, Whse_code, Lot_id, UOM columns.
In each case, the new column is added to the table. However, the old columns are not dropped and continue to
hold the existing data for historical rows.

Co_code is transformed in each table to the Legal Entity. If the suggested option is chosen, the company can be migrated
to the Legal Entity.
Column Name Datatype Maximum Length Description
LEGAL_ENTITY_ID NUMBER 15 Legal Entity Identifier
Item_Id, Whse_Code are transformed to inventory_item_id and organization_id.
INVENTORY_ITEM_ID NUMBER Inventory Item Identifier
ORGANIZATION_ID NUMBER Inventory Organization
Cost_mthd_code is transformed to cost_type_id.
COST_TYPE_ID NUMBER (15) Cost Type Identifier
Calendar_code, period_code are transformed to period_id.
PERIOD_ID NUMBER (15) Cost Period Identifier
Lot_ID is transformed to lot_number.
LOT_NUMBER VARCHAR2 (80) Lot Number
UOM is transformed to the 3 character UOM Code in Discrete.

XXX_um or um_YYY or
um_code
VARCHAR2 (3) UOM.
Note: Unit of Measure is a separate column that
is not added. It contains the full 25 character unit
of measure name.
Wherever we store the complete code combination in the form of account_key, it is transformed to account_id.
ACCOUNT_ID NUMBER (15) Code Combination Id

Cost Management Table Column Additions
CM_ACPR_CTL

Column Name Data Type Size Column Description
INTORDERS_PROCESSED NUMBER 15
INVOICES_PROCESSED NUMBER 15
MISCRCPT_PROCESSED NUMBER 15

CM_ADJS_DTL

ORGANIZATION_ID NUMBER 15 Organization Id
INVENTORY_ITEM_ID NUMBER Inventory Item Id
COST_TYPE_ID NUMBER Cost Type Id
PERIOD_ID NUMBER 15 Cost Period Id
ADJ UST_QTY_UOM VARCHAR2 3 3 Char UOM Code

CM_BRDN_DTL

BURDEN_UOM VARCHAR2 3 3 Char UOM Code
ITEM_UOM VARCHAR2 3 3 Char UOM Code

CM_CLDR_HDR_B
In the calendar header table, the existing references to company and cost method are not valid in Release 12 and are
dropped from the calendar setup window.The calendars are shared across multiple Legal Entitys and cost types.
LEGAL_ENTITY_ID NUMBER 15 Legal Entity Id

CM_RLUP_CTL

FROM_ORGANIZATION_ID NUMBER From Organization
TO_ORGANIZATION_ID NUMBER To Organization

CM_RSRC_DTL

USAGE_UOM VARCHAR2 3 3 Char UOM Code

CM_SCST_LED

FORM_PROD_UOM VARCHAR2 3 3 Char UOM Code
ITEM_FMQTY_UOM VARCHAR2 3 3 Char UOM Code
USAGE_UOM VARCHAR2 3 3 Char UOM Code

CM_WHSE_SRC

SOURCE_ORGANIZATION_ID NUMBER 15 Source Organization Id

GL_ALOC_EXP

FROM_ACCOUNT_ID NUMBER From GL Account Id
TO_ACCOUNT_ID NUMBER To GL Account Id

GL_ALOC_INP

ACCOUNT_ID NUMBER 15 Account
GL_EVNT_PLC

ENTITY_CODE VARCHAR2 30 Event Entity
ENTITY_CLASS_CODE VARCHAR2 30 Event Class

GL_ITEM_DTL


GMF_BURDEN_PRIORITIES

ORGANIZATION_PRI NUMBER 5 Organization Priority

GMF_LOT_COST_ADJUSTMENTS

LOT_NUMBER VARCHAR2 80 Lot Number

GMF_LOT_COST_BURDENS

LOT_NUMBER VARCHAR2 80 Lot Number
RESOURCE_UOM VARCHAR2 3 3 Char UOM Code
ITEM_UOM VARCHAR2 3 3 Char UOM Code

GMF_MATERIAL_LOT_COST_TXNS

COST_TRANS_UM VARCHAR2 3 3 Char UOM Code
TRANSACTION_ID NUMBER Transaction_Id from MMT
MIGRATION_IND NUMBER 3 Migration or Old row indicator. 1 =old row; null =
new row in R12

COST_LEVEL NUMBER 5 Cost Level Indicator

New Cost Management Tables for Release 12

GMF_FISCAL_POLICIES
A new table, GMF_FISCAL_POLICIES, has been introduced to migrate the fiscal policy records to the new Release 12 data
model. Following is the GL_PLCY_MST to GMF_FISCAL_POLICIES data mapping.
Source Column in
GL_PLCY_MST
Purpose Destination Column in
GMF_FISCAL_POLICIES
CO_CODE OPM Company LEGAL_ENTITY_ID, LEGAL_ENTITY_NAME
NUMBER_OF_OPEN_PERIODS Obsolete in 11i
AUTO_LINK_FLAG Obsolete in 11i
BASE_CURRENCY_CODE Display Only.
Derived from the Set of Books associated to the
Operating Unit.
BASE_CURRENCY_CODE
In R12, this column will be derived from the legal
entitys primary ledgers currency.
FRONT_CURR_IND Obsolete in 11i
VOUCHER_REVERSAL_DAY Obsolete in 11i
PRIMARY_LEDGER_CODE Obsolete in 11i
UPD_OPEN_BAL Obsolete in 11i
SEGMENT_DELIMITER Will be obsolete in R12.
TRANS_CNT Will be obsolete in R12.
TEXT_CODE Edit Text TEXT_CODE
DELETE_MARK Mark for purge indicator DELETE_MARK
DFLTS_IND Obsolete in 11i
SET_OF_BOOKS_NAME Set of Books name LEDGER_NAME
Name of the primary ledger in R12.
MTL_CMPNTCLS_ID Company wide default for Actual Cost material
component class for raw materials.
MTL_CMPNTCLS_ID

MTL_ANALYSIS_CODE Company wide default for Actual Cost material
analysis code for raw materials.
MTL_ANALYSIS_CODE

GL_COST_MTHD Stores the cost method used for inventory
valuation to GL.
COST_TYPE

CREV_CURR_MTHD Cost Revaluation current cost type Obsolete
CREV_CURR_CALENDAR Cost Revaluation current cost calendar Obsolete
CREV_CURR_PERIOD Cost Revaluation current cost period Obsolete
CREV_PRIOR_MTHD Cost Revaluation previous cost type Obsolete
CREV_PRIOR_CALENDAR Cost Revaluation previous cost calendar Obsolete
CREV_PRIOR_PERIOD Cost Revaluation previous cost period Obsolete
GL_TRANS_DATE Cost Revaluation GL date for journals Obsolete
COST_BASIS Indicates if the cost to be used should come from
current period or previous period. No indication
that customers are using this at this time.
Obsolete
SOB_ID Set of Books identifier LEDGER_ID
Id of the primary ledger in R12
OPERATING_UNIT Obsolete
ORG_ID Obsolete
CREATED_BY WHO column CREATED_BY
CREATION_DATE WHO column CREATION_DATE
LAST_UPDATE_LOGIN WHO column LAST_UPDATE_LOGIN
LAST_UPDATE_DATE WHO column LAST_UPDATE_DATE
LAST_UPDATED_BY WHO column LAST_UPDATED_BY
ATTRIBUTE1 thru ATTRIBUTE30 Descriptive Flexfield ATTRIBUTE1 thru ATTRIBUTE30
ATTRIBUTE_CATEGORY Descriptive Flexfield ATTRIBUTE_CATEGORY

GMF_CALENDAR_ASSIGNMENTS
This is a new table that stores the association between a calendar and the Legal Entity/cost type combination. A calendar
can be associated to any number of Legal Entity/cost type combination as long as for the same combinations no two
calendar periods are defined for the same time period.
ASSIGNMENT_ID NUMBER 15 Assignmnt Id
CALENDAR_CODE VARCHAR2 4 Calendar Code
CREATION_DATE DATE Standard Columns
CREATED_BY NUMBER 15 Standard Columns
LAST_UPDATE_DATE DATE Standard Columns
LAST_UPDATED_BY NUMBER 15 Standard Columns
LAST_UPDATE_LOGIN NUMBER 15 Standard Columns
TEXT_CODE NUMBER 10 Text Code
DELETE_MARK NUMBER 1 Delete Mark Indicator
ATTRIBUTE1 VARCHAR2 240 Standard Attribute Column

GMF_PERIOD_STATUSES
This table stores the period statuses for the Legal Entity/cost type combination. For the calendars associated or assigned to
the Legal Entity/cost type this table stores the statuses of the various periods. The table is de-normalized to store the
calendar code, period code, and start/end dates so that all code can refer to this table to derive the necessary information.
PERIOD_ID NUMBER 15 Period Id
CALENDAR_CODE VARCHAR2 4 Calendar Code
PERIOD_CODE VARCHAR2 4 Period Code
PERIOD_ID NUMBER 15 Period Unique Identifier
PERIOD_STATUS VARCHAR2 1 Period Status
START_DATE DATE Period Start Date
END_DATE DATE Period End Date
CREATION_DATE DATE Standard Columns
CREATED_BY NUMBER 15 Standard Columns
LAST_UPDATE_DATE DATE Standard Columns
LAST_UPDATED_BY NUMBER 15 Standard Columns
LAST_UPDATE_LOGIN NUMBER 15 Standard Columns
TEXT_CODE NUMBER 10 Text Code
DELETE_MARK NUMBER 1 Delete Mark Indicator

OPM Table Mapping

Încărcat de

Informații document

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

OPM Table Mapping

Încărcat de

Drepturi de autor:

Formate disponibile

Version: 1.

12 Date Published: 16/12/2013 Page 1 of 67

S-ar putea să vă placă și