Oracle OPM 11i to 12 Migration Guide and Reference

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

Date Published January 5, 2010 Version 1.10
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.10
Date Published: 01/05/2010
Page 1 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.
Version: 1.10
Page 2 of 67
Pre-Migration Validation Messages

GMA: System Administration
Migration Name Pre-Migration Validation Message Value for template organization is missing for organization <ORGANIZATION> Message Type: Error Comments 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. 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. Action Needed 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
Go to the Convergence Migration Setup form and modify the associations of the organizations.
GMD: Quality Management

Migration Name Pre-Migration Validation Message Value for the profile "GMD: Default Lab Organization" is missing. Message Type: Error 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 Comments An error is logged if the value for GMD: Default Lab organization is not set. This setting is used in the Stability Study organization. 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. Action Needed Set the value for this profile or set a value on the Convergence Migration Setup form on the Quality tab.
Go to the Convergence Migration Setup form and correct the issues with the organization and warehouse assocaitions.
Version: 1.10
Page 3 of 67
GMI: Process Inventory

Migration Name Pre-Migration Validation Message Item exists where Auto Lot Numbering is not set up (Count = <COUNT>). Message Type: Informational 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. Comments Logs the number of items that are not set up for auto lot numbering. Action Needed Provide default values for the auto lot numbering setup on the Migration Setup UI > Items tab.
Negative balances exist for Item <ITEM>, Lot <LOT_NO>, Sublot <SUBLOT_NO>, Warehouse <WHSE_CODE>, Location <LOCT>. Message Type: Warning
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. Negative balances exist and were not addressed prior to the migration. The organization on the discrete side does not allow for negative inventory.
None required.
Transaction processor error Negative balances not allowed. Message Type: Warning
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. None required.
Decimal dust balances exists for Item <ITEM>, Lot <LOT_NO>, Sublot <SUBLOT_NO>, Warehouse <WHSE_CODE>, Location <LOCT>. Message Type: Informational
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.
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: Warning
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. 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.
Cannot migrate balances for noninventory item <ITEM_NO>. Message Type: Warning
Cannot migrate balances for noninventory items because balances should not exist for such items.
Version: 1.10
Page 4 of 67
Migration Name Pre-Migration Validation
Message 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
Comments Desc flexfield column conflicts with OPM context and ODM context.
Action Needed 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. 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.
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. 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.. 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.
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. Message Type: Warning
If the controls are not correct, then change the attribute controls setting using the attribute controls UI from the Inventory Super User responsibility.
The lot <LOT> exists with different statuses in different locations. Message Type: Error
Change the lot status using the Process Inventory responsibility, or set the lot numbers appropriately using the Lots tab on the Migration Setup form.
Version: 1.10
Page 5 of 67
GR: Process Regulatory

Migration Name Pre-Migration Validation Message Regulatory item data will not be migrated because no Regulatory organization has been specified. Message Type: Warning For Regulatory Item Information to be migrated, at least one organization must be designated as a Regulatory Org. 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. 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. 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. Using the Regulatory Management Responsibility, define CAS number for the specified Regulatory item. Comments This message can be ignored if Regulatory Documentation Management was not implemented. Action Needed Go to the Convergence Migration Setup form and set the Regulatory Org checkbox for at least one organization on the Organizations tab.
The value for profile option GR: Default Organization is NULL. Message Type: Error
Use the System Administration responsibility to set the value for this profile at the Site level.
Item <ITEM> cannot be converted to unit of measure for FM_YIELD_TYPE. Message Type: Error
Use the Process Inventory responsibility to define the conversion for the specified item.
Version: 1.10
Page 6 of 67
GMF: Process Financials

Migration Name Pre-Migration Validation Message <RECORD_COUNT> Unposted Completed Inventory transaction records exist for the Period <PERIOD> in Company <CO_CODE>. Please run SubLedger update before proceeding. Message Type: Error 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 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 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 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. An error is logged if the accounting segments are not setup properly for the company. Setup the accounting segments using the Process Financials responsibility. An error is logged if there are unposted completed transactions existing in GME_RESOURCE_TXNS. Run the Subledger Update for the specified period and company where the transactions are recorded. An error is logged if there are unposted completed transactions existing in IC_TRAN_PND. Run the Subledger Update for the specified period and company where the transactions are recorded. Comments An error is logged if there are unposted completed transactions existing in IC_TRAN_CMP. Action Needed Run the Subledger Update for the specified period and company where the transactions are recorded.
Version: 1.10
Page 7 of 67
Migration Messages
GMA: System Administration
Migration Name Migrate Organizations Message Failed to migrate org <ORGANIZATION> Message Type: Error Comments 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 The actual database error is included in this message. Possible tables involved: IC_WHSE_MST MTL_PARAMETERS SY_ORGN_MST IC_LOCT_MST The token
GMD_ORG_NOT_MIGRATED
Action Needed 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
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.
Cannot migrate the subinventory as the organization <ORGANIZATION> has not been migrated. Message Type: Error
may appear instead of the text. For a given orgn_code there is no organization_ id located in sy_orgn_mst. 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.
Check the log for prior error messages regarding the failure to migrate the specified organiztaion. Take the necessary actions to correct the errors, then re-run the applicable migrations. Update the migration setup for the organization in question so that it will have the attributes of a valid organization.
Value for template organization is missing for organization <ORGANIZATION> Message Type: Error
Migration Process failed due to 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.
Version: 1.10
Page 8 of 67
Migration Name Migrate Action Codes
Message 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
Comments
Action Needed 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 2. Application Developer > Attachments > Attachment Functions Create a row for Actions with the 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.)
Attachment for this form needs to be defined.
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
Version: 1.10
Page 9 of 67
Migration Name Migrate Items
Message Attachment functionality does not Exists for form INVIDITM. (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
Comments Attachment for this form needs to be defined.
Action Needed 1. Application Developer > Attachments > Document Entities Create a row for Actions with the following entries: Table: MTL_SYSTEM_ITEMS Entity ID: MTL_SYSTEM_ITEMS Entity Name: Item Text Codes Prompt: Item Text Codes Application: Inventory 2. Application Developer > Attachments > Attachment Functions Create a row for Actions with the following entries: Type: Form Name: INVIDITM User Name: Item Text 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_SYSTEM_ITEMS
Method: Allow Change Secured By: None (Leave remaining form fields blank.)

Entity: Item Text Codes Display Method: Main Entity Include in Indicator: Checked Privileges Tab Leave all as Always On Primary Key Fields Tab Key 1:
MTL_SYSTEM_ITEMS.ORGANIZATI ON_ID Key2: MTL_SYSTEM_ITEMS.INVENTORY _ITEM_ID
SQL Statement Tab Leave blank 6. Save 7. Re-run the applicable migrations
Version: 1.10
Page 10 of 67
Migration Name Migrate Lots
Message Attachment functionality does not Exists for form INVIDILT. (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
Action Needed 1. Application Developer > Attachments > Document Entities Create a row for Actions with the following entries: Table: MTL_LOT_NUMBERS Entity ID:
MTL_SYSTEM_LOT_NUMBERS
Entity Name: Lot Text Codes Prompt: Lot Text Codes Application: Inventory
2. Application Developer > Attachments > Attachment Functions Create a row for Actions with the following entries: Type: Form Name: INVIDILT User Name: Lot Text 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_LOT_NUMBERS

Entity: Lot Text Codes Display Method: Main Entity Include in Indicator: Checked Privileges Tab Leave all as Always On Primary Key Fields Tab Key 1:
MTL_LOT_NUMBERS.ORGANIZATI ON_ID Key2: MTL_LOT_NUMBERS.INVENTORY_ ITEM_ID Key3: MTL_LOT_NUMBERS.MTL_LOT_N UMBERS.LOT_NUMBER
Version: 1.10
Page 11 of 67
Migration Name Migrade Grades
Message Attachment functionality does not Exists for form INVGRADE. (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
Action Needed 1. Application Developer > Attachments > Document Entities Create a row for Actions with the following entries: Table: MTL_GRADES_B Entity ID: MTL_GRADES_B Entity Name: GradeText Codes Prompt: Grade Text Codes Application: Inventory 2. Application Developer > Attachments > Attachment Functions Create a row for Actions with the following entries: Type: Form Name: INVGRADE User Name: GradeText 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_GRADES_B

Entity: Grade Text Codes Display Method: Main Entity Include in Indicator: Checked Privileges Tab Leave all as Always On Primary Key Fields Tab Key 1: MTL_GRADES_B.GRADE_CODE SQL Statement Tab Leave blank 6. Save 7. Re-run the applicable migrations
Version: 1.10
Page 12 of 67
Migration Name Migrate
Message Attachment functionality does not Exists for form INVTDTRS. (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
Action Needed 1. Application Developer > Attachments > Document Entities Create a row for Actions with the following entries: Table:
MTL_TRANSACTION_REASONS
Reason Codes
Entity ID:
MTL_TRANSACTION_REASONS
Entity Name: Reason Codes Prompt: Reason Codes Application: Inventory
2. Application Developer > Attachments > Attachment Functions Create a row for Actions with the following entries: Type: Form Name: INVTDTRS User Name: Reason 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:
TRANS_REASONS

Entity: Reason Codes Display Method: Main Entity Include in Indicator: Checked Privileges Tab Leave all as Always On Primary Key Fields Tab Key 1:
MTL_TRANSACTION_REASONS.R EASON_ID
Version: 1.10
Page 13 of 67
Migration Name Migrate
Message Attachment functionality does not Exists for form PERWSDOR. (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
Action Needed 1. Application Developer > Attachments > Document Entities Create a row for Actions with the following entries: Table: MTL_PARAMETERS Entity ID: MTL_PARAMETERS Entity Name: Organization Codes Prompt: Organization Codes Application: Inventory 2. Application Developer > Attachments > Attachment Functions Create a row for Actions with the following entries: Type: Form Name: PERWSDOR User Name: Organization 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_PARAMETERS
Organizations

Entity: Organization Codes Display Method: Main Entity Include in Indicator: Checked Privileges Tab Leave all as Always On Primary Key Fields Tab Key 1:
MTL_PARAMETERS.ORGANIZATIO N_ID
SQL Statement Tab Leave blank 6. Save 7. Re-run the applicable migrations 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.
Version: 1.10
Page 14 of 67
Migration Name Migrate Organizations
Message 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
Comments 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. Unexpected error pertaining to an Invalid Regulatory Item.
Action Needed Go to the Convergence Migration Setup form and modify the associations of the organizations. Re-run the applicable migrations.
Migrate Items
<ERROR> Message Type: Error
Check the log for prior error messages regarding the failure to migrate Items and Regulatory related data. Take the necessary actions and then re-run the applicable migrations. Check the log for prior error messages regarding the failure to migrate Items . Take the necessary actions and then re-run the applicable migrations. Map the existing warehouse to the subinventory for the discrete inventory organization.
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
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. Data not found for respective combination: Orgn Accts/Orgn_ Id UOM Code/Item_UM Def Status Id/Lot Status The actual database error is included in this message.
Migrate Items
Unable to get <NAME> for value <VALUE> Message Type: Error
Use SQL*Plus to validate and correct the corrupt data combinations. Rerun the applicable migrations.
Migrate Items
Migration Process failed due to DB_ERROR: <DB_ERROR> Message Type: Error
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 all of the related issues have been resolved, re-run the applicable migrations. 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.
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. Message Type: Warning
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..
Version: 1.10
Page 15 of 67
Migration Name Validate Flexfield Definitions
Message 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
Comments This message should have appeared during the running of the Pre-Migration Validation and should have been corrected at that time. appeared during premigration. Desc flexfield column conflicts with OPM context and ODM context.
Action Needed 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. Review why the parameters were not passed, because the failure may be due to an earlier listed error.
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.
Migrate Items
Table involved:
IC_ITEM_MST_B
Migrate Obsolete Columns
Invalid or NULL parameters passed to the migration process. Message Type: Error
Invalid parameters for obsolete column migration
Take the appropriate actions to resolve the database issue and then re-run applicable migrations. When all of the related issues have been resolved, re-run the applicable migrations. Review why the parameters were not passed, because the failure may be due to an earlier listed error.
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 None required.
Obsolete column already migrated to different flexfield column <COLUMN_NAME> Message Type: Informational
Obsolete column already migrated to different flexfield column
Invalid flexfield column <COLUMN_NAME> specified Message Type: Error
Invalid value for the flexfield column
Check flexfields and their associated column names.
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.
Version: 1.10
Page 16 of 67

Migration Name Inventory Balance Message No open period for the current date in Organization Id <ORGN_CODE>(<ORGN_ID>) This will be followed by: Comments 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. Action Needed None required.
Opening Inventory period for Organization Id

<ORGN_CODE>(<ORGN_ID>) Message Type: Informational
Inventory Balance
No open period for the current date in Organization Id <ORGN_CODE>(<ORGN_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 <ITEM>, Lot <LOT_NO>, Sublot <SUBLOT_NO>, Warehouse <WHSE_CODE>, Location <LOCT>. Message Type: Warning
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. Negative balances exist and were not addressed prior to the migration. The organization on the discrete side does not allow for negative inventory.
None required.
Migrate Inventory Balances
Transaction processor error Negative balances not allowed. Message Type: Warning
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. None required.
Decimal dust balances exists for Item <ITEM>, Lot <LOT_NO>, Sublot <SUBLOT_NO>, Warehouse <WHSE_CODE>, Location <LOCT>. Message Type: Warning
This message should have appeared during the running of the Pre-Migration Validation and should have been corrected at that time. Residual decimal balances are not migrated. These should have been managed during the premigration validation.
Version: 1.10
Page 17 of 67
Migration Name Migrate Inventory Balances
Message 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
Comments Mixed balances are not migrated and should have been acted upon during premigration validation.
Action Needed 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.
Unexpected ORA-20001: APP-FND01934: 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 Inventory Balance migration.
Warehouse <WHSE_CODE> not migrated to discrete. Message Type: Error
The warehouse was not successfully migrated.
Check the log for prior error messages regarding the failure to migrate the specified warehouse. Take the necessary actions to correct the errors, then re-run the applicable migrations. Set up the INV and IVA accounts at the company level for the specified company using the Process Financials responsibility.
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. Inventory period is not open in the discrete inventory application for specified organization. All warehouses under this organization will be skipped. Prior period is not open. The code skips all rows for the warehouse.
An error occurred while retrieving the open period ID. Message Type: Error
Error retrieving open period for the organization. Review the discrete period definition using SQL*Plus to determine why the period cannot be found.
Cannot open period. Previous cost period is not opened yet. Message Type: Error
Check the log for prior error messages regarding the failure to open the inventory period. Take the necessary actions to correct the errors, then re-run the applicable migrations. Check the log for prior error messages regarding the failure to open the inventory period. Take the necessary actions to correct the errors, then re-run the applicable migrations. The code skips all rows for the warehouse. This is a timing issue. Determine whether the period was opened by another user.
Failed to get the next period ID. Message Type: Error
Cannot get next period. The code skips all rows for the warehouse.
INV_DUPLICATE_OPEN_PERIOD Message is not setup for this token. Message Type: Error
Period opened by another user.
Version: 1.10
Page 18 of 67
Message No changes to commit. Message Type: Error
Comments No change was made for period opening.
Action Needed The code skips all rows for the warehouse.
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.
Cannot migrate balances for noninventory item <ITEM_NO>. Message Type: Error
Cannot migrate balances for non-inventory items since balances should not exist for such items.
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.
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. Review why lot migration failed as it may have been due to an earlier listed error.
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 due to an earlier listed error.
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.
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.
Check the log for prior error messages regarding the failure to migrate the specified item, warehouse, lot or location. Take the necessary actions to correct the errors, then re-run the applicable migrations. Review the error message and take the necessary actions to correct the errors, then re-run the applicable migrations. No data found, balance migration will rollback. Use SQL to be sure a loc_id exists for the location in question. Review SQL Error message and take appropriate action.
<ERROR> Message Type: Error
The actual error message will be displayed.
Unable to get <DEFAULT LOCATION> for value <NULL> Message Type: Error
Default Location Profile
Table involved:
IC_LOCT_INV
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 premigration validation.
Version: 1.10
Page 19 of 67
Message 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
Comments
GMI_DXFR_DIFF_SEC_UOM
Action Needed Process to discrete transfer issue. Secondary unit of measure should be same in Process and Discrete.
item.secondary_uom_code is not the same as the opm_item_secondary_uom_co de
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 Check the log for prior error messages regarding the failure to migrate locations. Take the necessary actions to correct the errors, then re-run the applicable migrations. 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. Check the log for prior error messages regarding the failure to migrate the specified company. Take the necessary actions to correct the errors, then re-run the applicable migrations. Check the log for prior error messages regarding the failure to 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 applicable migrations. Check the log for prior error messages regarding the failure to migrate specified item. Take the necessary actions to correct the errors, then re-run the applicable migrations.
Invalid locator <LOCATOR>

Message Type: Error
This error is related to the table IC_LOCT_INV.
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.
Fiscal policy not defined for company owning inventory organization.

Message Type: Error
There is a problem with the fiscal property setup.
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.
Item not found. Invalid item. Please re-enter. (ITEM = <ITEM>)

Message Type: Error
The item that the lot is associated to cannot be found.
Version: 1.10
Page 20 of 67
Message
Comments The lot has a grade associated to it but the item is not grade controlled.
Action Needed Check the log for prior error messages regarding the failure to migrate specified item. Take the necessary actions to correct the errors, then re-run the applicable migrations. 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 applicable migrations. 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.
Item is not Grade controlled. (ITEM = <ITEM>)

Message Type: Error
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.
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. Message Type: Warning
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.
Migrate Inventory Types
Table involved :
IC_INVN_TYP
Review the SQL Error message and take appropriate action. When all of the related issues have been resolved, re-run the applicable migrations. Review the SQL Error message and take appropriate action. When all of the related issues have been resolved, re-run the applicable migrations. Review the SQL Error message and take appropriate action. When all of the related issues have been resolved, re-run the applicable migrations. Review the SQL Error message and take appropriate action. When all of the related issues have been resolved, re-run the applicable migrations. Review the SQL Error message and take appropriate action. When all of the related issues have been resolved, re-run the applicable migrations. Review the SQL Error message and take appropriate action. When all of the related issues have been resolved, re-run the applicable migrations.
Migrate Default Categories
Table involved :
GMI_CATEGORY_SETS
Migrate Default Categories
Table involved:
GMI_ITEM_CATEGORIES
Migrate Lot Statuses
Table involved:
IC_LOTS_STS
Migrate Actions
Table involved:
GMD_ACTIONS
Migrate Grades
Table involved:
GMD_GRADES
Version: 1.10
Page 21 of 67
Migration Name Migrate Grades
Message Migration Process failed due to DB_ERROR: <DB_ERROR> Message Type: Error
Comments
Action Needed Review the SQL Error message and take appropriate action. When all of the related issues have been resolved, re-run the applicable migrations. Rerun lot conversion migration.
Table involved:
MTL_LOT_NUMBERS
Lot Conversion
GMI_LOC_CREATION_FAILED no message setup for this token Message Type: Error
Unable to create the locator for dynamic OPM location
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 successfully migrated.
Check the log for prior error messages regarding the failure to migrate the specified location and/or warehouse. Take the necessary actions and then re-run the applicable migrations. Review the SQL Error message and take appropriate action. When all of the related issues have been resolved, re-run the applicable migrations.
Lot Conversion
Table involved: IC_ITEM_CNV
GMF: Process Financials

Migration Name Migrate Account Mappings Message Error : Account id not found for Account Code: <ACCOUNT_CODE> Company Code: <CO_CODE>. Message Type: Error Comments The account was not migrated successfully. Action Needed Check the log for prior error messages regarding the failure to migrate the specified account code. Take the necessary actions and then re-run the applicable migrations. None Required.
Migrate Fiscal Policies
GMA_MIGRATION_ERROR_ABSTRA CT (TABLE_NAME=<TABLE_NAME>) (COLUMN_NAME=<COLUMN_NAME> ) (RECORD_COUNT=<COUNT>) Message Type: Informational
This is a summary message. TABLE_NAME XLA_RULES_T CM_WHSE_SRC GL_SUBR_STA COLUMN_NAME Not Null Constraint Legal Entities This message may be received if the financials migration has been re-run and the Legal Entity has already been migrated.
Migrate Fiscal Policies
GMA_MIG_FISCAL_DUP_LE_ERROR (CO_CODE=<CO_CODE>) Message Type: Warning
None Required.
Version: 1.10
Page 22 of 67
Migration Name Financials Migration
Message <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
Comments This message should have appeared during the running of the Pre-Migration Validation and should have been corrected at that time. Inventory Transaction records exist which are not yet posted to Sub-Ledger This message should have appeared during the running of the Pre-Migration Validation and should have been corrected at that time. Inventory Transaction records exist which are not yet posted to Sub-Ledger This message should have appeared during the running of the Pre-Migration Validation and should have been corrected at that time. Resource Transaction records exist which are not yet posted to Sub-Ledger This message should have appeared during the running of the Pre-Migration Validation and should have been corrected at that time. Segment values used in the account codes are missing in Flex field values setup. OPM Item has not been migrated by the Common Item Migration script
Action Needed 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
<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
Make sure that all the transactions for the company for the period denoted in Pending transactions table IC_TRAN_PND have been posted.
<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
Make sure that all the transactions for the company for the period denoted in Resource transactions table GME_RESOURCE_TXNS have been posted.
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
Setup the accounting segments using the Process Financials responsibility.
OPM Item Id: <ITEM_ID> not found / migrated. Message Type: Error
Run the Common Item Migration Script and rerun this GMF migration script.
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.
Legal Entity Details not found for 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. Check whether the Legal entity information for the organization / warehouse code has been mentioned in the organization parameters.
Legal Entity Details not found for Warehouse: <WHSE_CODE>. Message Type: Error
Legal Entity Information is not available for the organization ID for the warehouse code mentioned.
Version: 1.10
Page 23 of 67
Message Item Number not fetched for Inventory Item Id: <INVENTORY_ITEM_ID>. Message Type: Error
Comments Not able to fetch the Item Number flex field value for the Inventory Item ID passed
Action Needed Compile the Item Flex field. And retry this script again.
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.
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.
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. Run Acquisition Codes migration again before running the Account Mapping Migration.
Acquisition Code Details not found for Acquisition Id: <AQUI_COST_ID>. Message Type: Error
Acquisition Codes not yet Migrated.
Cost Component Class Code Details not found for Cost Component Class Id: <COST_CMPNTCLS_ID>. Message Type: Error
Data Corruption might be a 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. Order Type Details not available in op_ordr_typ or oe_transaction_types tables.
Order Type Details not found for Order Type Id: <ORDER_TYPE>. Message Type: Error
Data Corruption might be a cause, since the Order types can be used in account mapping only if they exist in the master table. Data Corruption might be a cause, since the Line types can be used in account mapping only if they exist in the master table. Data Corruption might be a cause, since the AR transaction types can be used in account mapping only if they exist in the master table. Data Corruption might be a cause, since the GL Business Class can be used in account mapping only if they exist in the master table. Data Corruption might be a cause, since the GL product lines can be used in account mapping only if they exist in the master table.
Line Type Details not found for Line Type Id: <LINE_TYPE>. Message Type: Error
Line Type details referred in Account Mapping does not exist in the lookup table.
AR Transaction Type Details not found for AR Transaction Type Id: <AR_TRX_TYPE_ID>. Message Type: Error
AR Transaction Type details referred in Account Mappings not available in ra_cust_trx_types table.
GL Business Class Details not found for GL Business Class Id: <GL_BUSINESS_CLASS_CAT_ID>. Message Type: Error
GL Business Class Details referred in account mappings does not exist in the Flex field values. Data might be corrupted.
GL Product Line Details not found for GL Product Line Id: <GL_PRODUCT_LINE_CAT_ID>. Message Type: Error
GL Product line Details referred in account mappings does not exist in the Flex field values. Data might be corrupted.
Version: 1.10
Page 24 of 67
Message UOM Code: <UM_CODE> not found / Migrated. Message Type: Error
Comments OPM UOMS has not been migrated by the Common Item Migration script
Action Needed Run the Common UOM Migration Script and rerun this GMF migration script.
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. Check the Warehouse OPM Organization mapping or OPM organization Company mapping. Make the appropriate changes to the mappings and then re-run the applicable migrations. None required.
Company Code Details not found for Warehouse: <WHSE_CODE>. Message Type: Error
Warehouse OPM Organization mapping or OPM organization Company mapping might be corrupted.
Fiscal Policy of Company Code: <CO_CODE> being migrated as Legal Entity already exists. Skipping migration of Fiscal Policy record. Message Type: Informational
Two Company Codes are migrated to the sane Legal Entity and the fiscal policy record for the Legal entity has already been created.
Migration of <COLUMN_NAME> in <TABLE_NAME> failed for <RECORD_COUNT> rows. Message Type: Error
High Level error message for failed migrations.
Check the log for prior error messages regarding the failure to migrate data from the specified table. Take the necessary actions to correct the errors and then re-run the applicable migrations. Check the log for prior error messages regarding the failure to migrate data from the specified table. Take the necessary actions to correct the errors and then re-run the applicable migrations.
Migration of <COLUMN_NAME> in <TABLE_NAME> failed for <RECORD_COUNT> rows for <PARAMETERS>. Message Type: Error
Low Level error message for failed migrations.
Version: 1.10
Page 25 of 67
GME: Process Execution

Migration Name Re-Create Batches Message Batch <BATCH_NO> could not be migrated. <MSG> Message Type: Error Comments The actual error is included in this message. Action Needed 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. Review the SQL Error message and take appropriate action. When all of the related issues have been resolved, re-run the Migration ReCreate Open Batches concurrent program. None required.
Re-Create Batches
Unexpected ORA-20001: occurred. Message Type: Error
Table Involved : IC_ITEM_MST_B
Re-Create Batches
You cannot reopen this batch. It has migrated from a release that does not have reopen functionality. Message Type: Informational
The Batch Re-Open functionality was not available prior to 11.5.9
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
This is most likely due to a 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. None required.
Re-Create Batches
Batch <BATCH_NO> transaction with Trans ID = <TRANS_ID> and details <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. Message Type: Informational
Material was moved to the batch organization so that the material can be reserved for the specified batch.
Re-Create Batches
Batch <BATCH_NO> transaction with Trans ID = <TRANS_ID> and details <TXN_DATA> could not be migrated 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. Correct the error. Manually create the Pending Product Lot.
Re-Create Batches
Batch <BATCH_NO> transaction with Trans ID = <TRANS_ID> and details <TXN_DATA> could not be migrated 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.
Version: 1.10
Page 26 of 67
Migration Name Re-Create Batches
Message Batch <BATCH_NO> transaction with Trans ID = <TRANS_ID> and details <TXN_DATA> could not be migrated because create transaction failed. <MSG> New transaction details were <NEW_DATA.> Message Type: Error
Comments 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.
Action Needed 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 ReCreate Open Batches concurrent program. Adjust the inventory accordingly and manually re-create the transaction.
Re-Create Batches
Batch <BATCH_NO> transaction with Trans ID = <TRANS_ID> and details <TXN_DATA> could not be migrated 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 This is most likely due to the failure to migrate/upgrade the specified item.
Re-Create Batches
Batch <BATCH_NO> transaction with Trans ID = <TRANS_ID> and details <TXN_DATA> could not be migrated 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
Check for priior error messages related to the specified item. Take the appropriate actions and then rerun the applicable migrations. When all of the related issues have been resolved, re-run the Migration ReCreate Open Batches concurrent program.
Re-Create Batches
Batch <BATCH_NO> transaction with Trans ID = <TRANS_ID> and details <TXN_DATA> could not be migrated <TXN_DATA> could not be migrated because item is not reservable. Message Type: Error
This is most likely due to the failure to migrate/upgrade the specified item.
Check for prior error messages related to the specified item. Take the appropriate actions and then rerun the applicable migrations. When all of the related issues have been resolved, re-run the Migration ReCreate Open Batches concurrent program. Check for prior error messages related to the specified item. Take the appropriate actions and then rerun the applicable migrations. When all of the related issues have been resolved, re-run the Migration ReCreate Open Batches concurrent program. Check for prior error messages related to the specified location. Take the appropriate actions and then re-run the applicable migrations. When all of the related issues have been resolved, re-run the Migration ReCreate Open Batches concurrent program.
Re-Create Batches
Batch <BATCH_NO> transaction with Trans ID = <TRANS_ID> and details <TXN_DATA> could not be migrated because item is not transaction enabled. Message Type: Error
This is most likely due to the failure to migrate/upgrade the specified item.
Re-Create Batches
Batch <BATCH_NO> transaction with Trans ID = <TRANS_ID> and details <TXN_DATA> could not be migrated because locator could not be determined. Message Type: Error
This is due to the failure to migrate the specified location.
Version: 1.10
Page 27 of 67
Message Batch <BATCH_NO> transaction with Trans ID = <TRANS_ID> and details <TXN_DATA> could not be migrated because lot number could not be determined. Message Type: Error
Comments This is due to the failure to migrate the specified lot.
Action Needed Check for prior error messages related to the specified lot. Take the appropriate actions and then rerun the applicable migrations. When all of the related issues have been resolved, re-run the Migration ReCreate Open Batches concurrent program. Check the log for prior error messages regarding the failure to migrate the specified reason code. Take the necessary actions to correct the errors. Update the reason code to the transaction manually.
Re-Create Batches
Batch <BATCH_NO> transaction with Trans ID = <TRANS_ID> and details <TXN_DATA> - the reason ID could not be determined for reason code &REASON_CODE. Transaction will be created without reason ID. Message Type: Warning
This is due to the failure to migrate the specified reason code.
Re-Create Batches
Batch <BATCH_NO> transaction with Trans ID = <TRANS_ID> and details <TXN_DATA> could not be migrated 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. This is most likely due to a either a database error or the failure to migrate the corresponding warehouse
Manually create the appropriate revision for the specified item.
Re-Create Batches
Batch <BATCH_NO> transaction with Trans ID = <TRANS_ID> and details <TXN_DATA> could not be migrated because subinventory could not be determined. Message Type: Error
Check the log for prior error messages regarding the failure to migrate the warehouse noted in the transaction data. Take the necessary actions to correct the errors, then re-run the applicable migrations. Check the log for prior error messages regarding the specified item or uom conversion for the specified item. Take the necessary actions to correct the errors, then re-run the applicable migrations.
Re-Create Batches
Batch <BATCH_NO> transaction with Trans ID = <TRANS_ID> and details <TXN_DATA> could not be migrated 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.
Re-Create Batches
Batch &BATCH_NO transaction migration failed. <MSG> Message Type: Error
The actual error is included in this message.
Take the appropriate actions to correct the issue and then re-run applicable migrations.
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 recreated but the re-creation of the phantom batch failed.
Check the log for prior error messages regarding create the phantom batch. Take the necessary actions to correct the errors, then re-run the applicable migrations. Check the log for prior error messages regarding create the phantom batch. Take the necessary actions to correct the errors, then re-run the applicable migrations.
Re-Create Batches
Unexpected error occurred while linking phantoms for Batch <BATCH_NO> . <MSG> Message Type: Error
The batch itself has been recreated but the re-creation of the phantom batch failed.
Version: 1.10
Page 28 of 67
Message Item/Organization combination not found for item <ITEM> and Organization <ORG>. Message Type: Error
Comments Either the organization or the item failed to migrate successfully.
Action Needed Check the log for prior error messages regarding the specified organization or the specified item. Take the necessary actions to correct the errors, then re-run the applicable migrations. Check the batch information to determine why this batch had not been prevously closed or cancelled.
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. This is most likely due to old data that is outside of the current opne financial and inventory periods.
Re-Create Batches
Batch <BATCH_NO> transaction with Trans ID = <TRANS_ID> with details <TXN_DATA> could not be migrated because there were no open periods. Message Type: Error
Check the batch information to determine why this batch had not been prevously closed or cancelled.
Re-Create Batches
No open periods found while releasing or completing Batch <BATCH_NO> Step <STEP_NO>. Message Type: Error
This is most likely due to old data that is outside of the current opne financial and inventory periods.
Check the batch information to determine why this batch had not been prevously closed or cancelled.
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
Migration Name Message Quantity on hand fails to satisfy reservation Message Type: Error Comments 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. Action Needed Check the log for prior error messages regarding inventory balance migration failures. If found, take the necessary actions to correct the errors, then re-run the applicable migrations If not, create sufficient quantities e.g Misc Receipts. Check the locator expiration date.
Migrate Open Orders
Migrate Open Orders
Create Reservation failed due to locator Message Type: Error
For create reservation Could be that locator has expired.
Version: 1.10
Page 29 of 67
Migration Name Migrate Open Orders
Message Invalid Reservation Qty Message Type: Error
Comments 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.
Action Needed Check the log for prior error messages regarding inventory balance migration failures. If found, take the necessary actions to correct the errors, then re-run the applicable migrations If not, create sufficient quantities e.g Misc Receipts. Check locator migration could have expired.
Migrate Open Orders
Invalid locator Message Type: Error
Migrate Open Orders
The lot number has expired Message Type: Error
This is in reference to reservation creation. Either the location migration failed, or the locator has expired. This is in reference to reservation creation.
Check lot the lot expiration date.
Migrate Open Orders
Suppy/Demand document does not have enough quantity to be reserved against Message Type: Warning
This is in reference to reservation creation. This is usually seen when the material has already been reserved when re-running this migration. This is in reference to move order creation. The most likely cause is that the migration/ upgrade of the specified item was not successful.
None required.
Migrate Open Orders
Transactable attribute is not set for this item

Message Type: Error
Check the log for prior error messages regarding the failure to 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 applicable migrations.
GMD: Quality Management

Migration Name Migrate Quality Parameters Message Value for the profile "GMD: Default Lab Organization" is missing. Message Type: Error Migrate Quality Parameters Quality Default Lab Profile Value does not exist. Message Type: Error Migrate Samples Unexpected ORA-01403: no data found occurred. Error from call to inv_opm_lot_migration. get_odm_lot. Message Type: Error Comments This message should have appeared during the running of the Pre-Migration Validation and should have been corrected at that time. This message should have appeared during the running of the Pre-Migration Validation and should have been corrected at that time. This is mostly likely due to the failure to migrate the item or lot. Action Needed Set the value of profile "GMD: Default Lab Organization" to a valid organization.
Set the value of profile "GMD: Default Lab Organization" to a valid organization.
Check the log for prior error messages regarding the failure to migrate items and lots. Take the necessary actions to correct the applicable errors and then re-run the applicable migrations.
Version: 1.10
Page 30 of 67
Migration Name Migrate Samples
Message Error retrieving data from ic_loct_mst. Passed whse code is <WHSE_CODE> and location is <LOCATION>. Message Type: Error
Comments The warehouse or the location failed to migrate successfully.
Action Needed Check the log for prior error messages regarding the failure to migrate the specified warehouse and location. Take the necessary actions to correct the applicable errors and then re-run the applicable migrations. None required.
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>. Message Type: Informational
WIP sample and WIP specification related data have been updated with the new batch id.
Migrate Specifications
A record with null organization code has been deleted from <TABLE>. It was not attached to any Samples. Message Type: Informational
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.
Check the log for prior error messages regarding gmd_quality_config. Take the necessary actions and then re-run 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.
Check the log for prior error messages regarding gmd_quality_config. Take the necessary actions and then re-run 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 PreMigration Validation phase, or the Quality Parameters migration failed.
Check the log for prior error messages regarding the Default Stability Study Organization and gmd_quality_config. Take the necessary actions and then re-run the applicable migrations.
Version: 1.10
Page 31 of 67
Migration Name Migrate Specifications
Message There is a setup mismatch for 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 Organization/subinventory setup. Message Type: Error
Comments 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.
Action Needed 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.
There is a setup mismatch for 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 organization_id for the whse is <WHSEID>. 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.
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_monitoring_spec_vrs table.
Failure in call to Create Nonvalidated 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.
Check the log for prior error messages regarding mtl_item_locations or the failure to migrate the corresponding warehouse. Take the necessary actions and then re-run the applicable migrations. Check the log for prior error messages regarding the failure to migrate the specified organization. Take the necessary actions and then re-run the applicable migrations. Check the log for prior error messages regarding the failure to migrate the specified organization. Take the necessary actions and then re-run the applicable migrations. Check the log for prior error messages regarding the failure to migrate the specified organization. Take the necessary actions and then re-run the applicable migrations. Check the log for prior error messages regarding the failure to migrate the specified unit of measure. Take the necessary actions and then re-run the applicable migrations.
Organization Code was not migrated. Organization Code is <ORG>. Message Type: Error
The organization migration failed.
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.
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.
Unit of Measure <UOM> not migrated. Message Type: Error
The unit of measure code did not migrate successfully.
Version: 1.10
Page 32 of 67
Migration Name Migrate Stability Studies
Message Organization Id not found on Sy_orgn_mst for Default Lab Organization Code = <ORG>. Message Type: Error
Comments Either the Default Lab Organization parameter is NULL or invalid, or the organization migration failed.
Action Needed Check the log for prior error messages regarding the failure to migrate the specified organization. Take the necessary actions and then re-run the applicable migrations. Check the log for prior error messages regarding the failure to migrate the specified reason code. Take the necessary actions and then re-run the applicable migrations. 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_storage_history table.
Error converting Reason Code to Reason ID. Reason Code is <REASON>. Message Type: Error
The reason code was not successfully migrated.
There is a setup mismatch for 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 Organization/subinventory setup. Message Type: Error
Migrate Samples
Error converting Status Code to Status id. Status Code is <STATUS>. Message Type: Error
The migration of the status code failed.
Check the log for prior error messages regarding the failure to migrate the specified status code. Take the necessary actions and then re-run the applicable migrations. Check the log for prior error messages regarding the failure to migrate the specified location. Take the necessary actions and then re-run the applicable migrations. 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_samples table.
Migrate Samples
Error retrieving data from mtl_item_locations using locator id = <LOCATOR>. Message Type: Error
The migration of the location failed.
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 organization_id for the whse is <WHSE_ORG_ID>. They should be the same. Check Organization/subinventory setup. Message Type: Error
Version: 1.10
Page 33 of 67
GMD: New Product Development

Migration Name Data Transformation Message Unexpected ORA-20001: APP-INV05247: You have entered a duplicate item. Please clear your changes occurred. Message Type: Error Comments 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. Action Needed Rerun the data transformation patch for GMD,GME and GMP.
GR: Process Regulatory

Migration Name Migrate Regulatory Items Message Migration Process failed due to DB_ERROR: <DB_ERROR> Message Type: Error Migrate Regulatory Items Regulatory item data will not be migrated because no Regulatory organization has been specified. Message Type: Warning This message should have appeared during the running of the Pre-Migration Validation and should have been corrected at that time. In order for Regulatory Item Information to be migrated, at least one organization must be designated as a Regulatory Org. Migrate Regulatory Items Organization <ORGANIZATION> has not been migrated. Message Type: Error The specified organization was not migrated. Go to the Convergence Migration 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. Check the log for prior error messages regarding the failure to migrate the specified organization. Take the necessary actions and then re-run the applicable migrations. Comments The actual db error appears in the message. Action Needed Take the necessary actions to correct the database errors, then re-run the applicable migrations.
Version: 1.10
Page 34 of 67
Migration Name Migrate Regulatory Items
Message There are no Regulatory items to migrate. Message Type: Informational
Comments 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. This message should have appeared during the running of the Pre-Migration Validation and should have been corrected at that time. The value for the specified profile option is required for data migration.
Action Needed None required.
Migrate Regulatory Items
The value for profile option <PROFILE> is NULL. Message Type: Error
Go to the Profiles form and set the value for the specified profile option. Re-run this migration.
Item <ITEM> has no value for CAS number. Message Type: Error
This message should have appeared during the running of the Pre-Migration Validation and should have been corrected at that time. 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.
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.
Check the log for prior error messages regarding the failure to migrate the specified item to the specified organization. Take the necessary actions and then re-run the applicable migrations. Check the ODM Inventory Item to see that the Hazardous material flag is set. Go to the Regulatory Item Information form and then redefine the item. Re-run this migration. Take the necessary actions to correct the database errors, then re-run the applicable migrations.
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. The actual databse error appears in the message.
Version: 1.10
Page 35 of 67
Migration Name Migrate Standalone Formulas
Message The value for profile option GR: Default Organization is NULL. Message Type: Error
Comments This message should have appeared during the running of the Pre-Migration Validation and should have been corrected at that time. An error is logged if the value for GR: Default Organization is not set. This is used as the owner organization for the standalone formula migration.
Action Needed Set the value for this profile at the site level using the System Administration responsibility. Rerun this migration.
The value for profile option GMD: Yield Type is NULL. Message Type: Error
This message should have appeared during the running of the Pre-Migration Validation and should have been corrected at that time. An error is logged if the value 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. Rerun this migration.
Item <ITEM> cannot be converted to unit of measure for FM_YIELD_TYPE. Message Type: Error
This message should have appeared during the running of the Pre-Migration Validation and should have been corrected at that time. 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 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.
Version: 1.10
Page 36 of 67
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 Pre-Migration Validation SQL Script GMAR12VAL.sql Migrating/Upgrading Entity N/A Dependent On None Comments 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 Migrates Organizations and Warehouses Populates the item migration table with the appropriate organization and item combinations. This table drives the item migration. Migrates Items and updates existing discrete items
Organization Migration (optional) Item Migration Setup (optional)
GMAORGMG.sql
SY_ORGN_MST IC_WHSE_MST IC_ITEM_MST_B_MIG
None
GMAITSTP.sql
GMAORGMG.sql
Item Migration (optional)
gmiitmin.sql
IC_ITEM_MST
GMAORGMG.sql GMAITSTP.sql
Bucket 2 (Run during the Inline Phase):

Migration Name Update Process Organizations Migrate Reason Codes Migrate Organizations SQL Script GMAG1UOR.sql Migrating/Upgrading Entity MTL_PARAMETERS MTL_SECONDARY_INVENTORIES SY_REAS_CDS SY_ORGN_MST IC_WHSE_MST Dependent On None Comments Updates process organizations with valid attribute controls Migrates Reason Codes Migrates Organizations and Warehouses
GMAG1MRS.sql GMAG2MOR.sql
None None
Version: 1.10
Page 37 of 67
Migration Name Migrate Action Codes Migrate Grade Migrate Lot Status Migrate Inventory Types Migrates Default Categories Migrate GMD Profiles Migrate Acquisition Codes Migrate Cost Types Migrate Fiscal Policies LE Migrate Lot Cost Types Migrate Vendors Update Purchasing Lines
SQL Script GMIG1MAC.sql GMIG1MGD.sql GMIG1MLS.sql GMIG1MIT.sql GMIG1MDC.sql GMDG1MPR.sql GMFG1MAC.sql GMFG1MCM.sql GMFG1MFP.sql GMFG2MLM.sql GMFG3MVI.sql GMLG5UPS.sql
Migrating/Upgrading Entity GMD_ACTIONS_B/TL GMD_GRADES_B/TL IC_LOTS_STS IC_INVN_TYP GMI_CATEGORY_SETS FND_PROFILE_OPTION_VALUES PO_COST_MST CM_MTHD_MST GMF_FISCAL_POLICIES GL_PLCY_MST CM_MTHD_MST GL_ACCT_MAP PO_LINE_LOCATIONS_ALL
Dependent On None None None None None None None None None None None None
Comments Migrates Action Codes Migrates Grade Codes Migrates Lot Status Codes Migrates Inventory Types Migrates default category sets migration Migrates Product Development Profiles Migrates Acquisition Codes Migrates Cost Types Migrates Fiscal Policies LE Migrates Lot Cost Types Migrates Vendor IDs Updates secondary quantities and shipment quantities for the purchasing table.
Bucket 3 (Run during the Inline Phase):

Migration Name Migrate Inventory Balances SQL Script GMIG3MIB.sql Migrating/Upgrading Entity IC_LOCT_INV Dependent On GMAG2MOR.sql Comments Updates process organizations with valid attribute controls and migrates inventory balances Migrates Item Lot Conversions and Audit data. Migrates Plant and Lab Indicator to Product Development Parameters Migrates OPM Quality Setup 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
Migrate Lot Conversions Migrate Product Development Parameters Migrate Quality Setup Data Transformation
GMIG3MLC.sql
GMDG3MPL.sql
IC_ITEM_CNV GMI_ITEM_CONV_AUDIT GMI_ITEM_CONV_AUDIT_DETAILS SY_ORGN_MST
GMIG3MIB.sql
GMAG2MOR.sql
GMDG3MST.sql GMAMIGT.sql
GMD_QUALITY_CONFIG Tables listed in GMA_UPGRADE_SETUP for GMD, GME, GMP
GMAG2MOR.sql GMAG2MOR.sql
Version: 1.10
Page 38 of 67
Migration Name Data Transformation
SQL Script GMAFMIGT.sql
Migrating/Upgrading Entity Tables listed in GMA_UPGRADE_SETUP for GMF
Dependent On GMAG2MOR.sql
Comments 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 Migrate Expense Allocation Codes Migrates Expense Allocation Expenses Migrates Expense Allocation Inputs Migrates Burden Priorities Migrates Cost Calendar Assignments Migrates Material Cost Components Migrates Event Fiscal Policies Migrates Fiscal Policies Migrate Item Cost Component Details Migrate Cost Warehouses Migrates Costing Items Populate Regulatory Migration table Updates receiving transaction tables for lot number Updates the receiving supply table for secondary quantities Updates Receiving Lot Supplies
GMFG2MAB.sql GMFG2MAC.sql GMFG2MAE.sql
GL_ALOC_BAS GL_ALOC_MST GL_ALOC_EXP
GMAG2MOR.sql GMFG1MFP.sql GMFG1MFP.sql
Migrates expense allocation basis Migrates expense allocation codes Migrates expense allocation expenses Migrates expense allocation inputs Migrates burden priorities Migrates cost calendar assignments Migrates material cost components Migrates event fiscal policies Migrates Fiscal Policies Others Copies Item Cost Component Details Migrates Cost Warehouses Migrates Process Costing Items Populate the table that is used to migrate Regulatory Items Updates receiving transaction tables for lot number Updates the receiving supply table for secondary quantities Updates receiving lot supply table for lot number and transaction reason
GMFG2MAI.sql GMFG2MBP.sql GMFG2MCC.sql
GL_ALOC_INP GMF_BURDEN_PRIORITIES GMF_CALENDAR_ASSIGNMENTS
GMFG1MFP.sql GMAG2MOR.sql GMFG1MFP.sql
GMFG2MCM.sql GMFG2MEP.sql GMFG2MFP.sql
CM_CMPT_MTL GL_EVENT_PLC GMF_FISCAL_POLICIES GMF_LEDGER_VALUATION_METH ODS CM_CMPT_DTL CM_WHSE_ASC GMF_ITEMS_MIGRATION GR_ITEM_GENERAL_MIG
GMAG2MOR.sql GMFG1MFP.sql GMFG1MFP.sql
GMFG3MCP.sql GMFG5CWA.sql GMFG5ITM.sql GRG6PST.sql
GMFG1MFP.sql GMAG2MOR.sql GMAG2MOR.sql GMAG2MOR.sql
GMLG5RCV.sql
RCV_LOT_TRANSACTIONS GML_RCV_LOTS_MIGRATION RCV_SUPPLY
GMAG2MOR.sql
GMLG6RCV.sql
GMAG2MOR.sql
GMLG7RCV.sql
RCV_LOTS_SUPPLY
GMAG2MOR.sql
Bucket 4 (Run during the Post-Migration Phase):

SQL Script Migrating/Upgrading Entity Dependent On Comments
Version: 1.10
Page 39 of 67
SQL Script Update Recipe Types Migrate Samples Migrate Specifications. Migrate Stability Studies Migrate GME Profiles GMDG3MRT.sql GMDG5MSM.sql GMDG5MSP.sql GMDG5MST.sql GMEG6MIG.sql
Migrating/Upgrading Entity GMD_RECIPES_B GMD_SAMPLES GMD_SPECIFICATIONS_B GMD_STABILITY_STUDIES_B FND_PROFILE_OPTION_VALUES GME_BATCH_HEADER GME_RESOURCE_TXNS
Dependent On GMAMIGT.sql GMAMIGT.sql GMAMIGT.sql GMAMIGT.sql GMAMIGT.sql
Comments Updates Recipe Type with the default value Migrates OPM Quality sample data Migrates OPM Qaulity specifications. Migrates stability studies. 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 Copies Item Cost Component Details Migrates Resource Details Migrates Actual Cost Adjustments Migrates Item Cost Component Details Migrates Burden Details Migrates Item Costs Migrates Lot Costs Migrates Lot Costed Items Migrates Lot Cost Burdens Migrates Lot Cost Adjustments Migrates Material Lot Cost Transactions Migrates Standard Cost Ledgers Migrates Actual Cost Ledgers Migrates Account Mappings Migrates Period Balances Migrates Source Warehouses Migrates Actual Cost control data Migrates Rollup Control Records Migrates Cost Update control data Migrates Subledger control data Migrates Forecasts Migrates Regulatory Item data
Migrates Burden Percentages Migrate Item Cost Component Details Migrate Resource Details Migrate Actual Cost Adjustments Migrate Item Cost Component Details Migrate Burden Details Migrate Item Costs Migrate Lot Costs Migrate Lot Costed Items Migrate Lot Cost Burdens Migrate Lot Cost Adjustments Migrate Material Lot Cost Transactions Migrate Standard Cost Ledgers Migrate Actual Cost Ledgers Migrate Account Mappings Migrate Period Balances Migrate Source Warehouses Migrate Actual Cost control data Migrate Rollup Control Records Migrates Cost Update control data Migrates Subledger control data Migrate Forecasts Migrate Regulatory Items
GMFG3MBP.sql GMFG5MCP.sql
GMF_BURDEN_PERCENTAGES CM_CMPT_DTL GL_ITEM_CST GL_ITEM_DTL CM_RSRC_DTL CM_ADJS_DTL CM_CMPT_DTL CM_BRDN_DTL GL_ITEM_CST GMF_LOT_COSTS GMF_LOT_COSTED_ITEMS GMF_LOT_COST_BURDENS GMF_LOT_COST_ADJUSTMENTS GMF_MATERIAL_LOT_COST_TXNS CM_SCST_LED CM_ACST_LED SLA_ADR_MIGRATION GMF_PERIOD_BALANCES CM_WHSE_SRC CM_ACPR_CTL CM_RLUP_CTL CM_CUPD_CTL GL_SUBR_STA MRP_FORECAST_DESIGNATORS GR_ITEM_GENERAL
GMAFMIGT.sql GMFG5ITM.sql
GMFG6P01.sql GMFG6P02.sql GMFG6P03.sql GMFG6P04.sql GMFG6P05.sql GMFG6P06.sql GMFG6P07.sql GMFG6P08.sql GMFG6P09.sql GMFG6P10.sql GMFG6P11.sql GMFG6P12.sql GMFG6P13.sql GMFG6P14.sql GMFG6P15.sql GMFG6P16.sql GMFG6P17.sql GMFG6P18.sql GMFG6P19.sql GMPG7FCM.sql GRG7PST.sql
GMAFMIGT.sql GMAFMIGT.sql GMFG5MCP.sql GMAFMIGT.sql GMAFMIGT.sql GMAFMIGT.sql GMAFMIGT.sql GMAFMIGT.sql GMAFMIGT.sql GMAFMIGT.sql GMAFMIGT.sql GMAFMIGT.sql GMAFMIGT.sql GMAFMIGT.sql GMAFMIGT.sql GMAFMIGT.sql GMAFMIGT.sql GMAFMIGT.sql GMAFMIGT.sql GMAMIGT.sql GRG6PST.sql
Version: 1.10
Page 40 of 67
SQL Script Migrate Standalone Formulas Migrate Open Orders GRG8PST.sql
Migrating/Upgrading Entity GR_ITEM_CONCENTRATIONS GR_DISPATCH_HISTORY IC_TRAN_PND MTL_RESERVATIONS
Dependent On GMAG2MOR.sql
Comments Migrates standalone Regulatory formula (composition) data Migrates Open Order lines
GMLG5MMO.sql
GMAG2MOR.sql GMIG3MIB.sql
Bucket 5 (Run during the Post-Migration Phase):

SQL Script Update Quality Tables with Batch Data GMDG6UMD.sql Migrating/Upgrading Entity GMD_SAMPLES_B GMD_SAMPLING_EVENTS GMD_WIP_SPEC_VRS Dependent On GMAMIGT.sql GMDG5MSM.sql GMDG5MSP.sql Comments Updates Material Detail IDs
Version: 1.10
Page 41 of 67
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)

ITEM_ID
Data Type (*=Not Null)

*NUMBER(10)
Destination Column (in MTL_SYSTEM_ITEMS_B)

INVENTORY_ITEM_ID
Date Type
Comments
NUMBER
ORGANIZATION_ID
NUMBER
ITEM_NO ITEM_DESC1
*VARCHAR2(32) VARCHAR2(70)
SEGMENT1 DESCRIPTION RECIPE_ENABLED_FLAG PROCESS_EXECUTION_ENABL ED_FLAG PROCESS_COSTING_ENABLED _FLAG PROCESS_QUALITY_ENABLED_ FLAG LONG_DESCRIPTION
VARCHAR2(40) VARCHAR2 (240) VARCHAR2(1)
System generated id. Note that the id has the same value, if the item is assigned to multiple organizations. Only the process enabled organizations is affected by this migration (with the exception of a new discrete master organization). OPM items are migrated to segment1 only.
These columns do not exist in OPM. For the process-enabled organizations, they are updated to Y during migration.
ITEM_DESC2
VARCHAR2(70)
VARCHAR2 (4000)
ALT_ITEMA ALT_ITEMB ITEM_UM
VARCHAR2(32) VARCHAR2(32) *VARCHAR2(4)
DUALUM_IND
*NUMBER(5)
PRIMARY_UNIT_OF_MEASURE PRIMARY_UOM_CODE UNIT_OF_ISSUE TRACKING_QUANTITY_IND SECONDARY_DEFAULT_IND
VARCHAR2(25) VARCHAR2(3) VARCHAR2(25) VARCHAR2(30) VARCHAR2(30)
We currently dont synchronize this column. Note that this migration occurs if the LONG_DESCRIPTION column is null in discrete. Obsolete. Obsolete. Note that the migrated values are derived from the sy_uoms_mst view. Dualum_ ind Tracking_ Secondary_ quantity_ default_ ind ind 0 P NULL 1 PS F 2 PS D 3 PS N Note that the migrated values are derived from the sy_uoms_mst view. = DEVIATION_LO * 100 = DEVIATION_HI * 100 = P, if ONT_PRICING_QTY_SOURCE = 0 = S, if ONT_PRICING_QTY_SOURCE = 1 Obsolete, not supported in OPM. = LOT_CTL + 1 = Y if LOT_INDIVISIBLE = 0
ITEM_UM2 DEVIATION_LO DEVIATION_HI ONT_PRICING_QTY_SO URCE LEVEL_CODE LOT_CTL LOT_INDIVISIBLE
VARCHAR2(4) *NUMBER *NUMBER NUMBER(5) NUMBER(5) *NUMBER(5) *NUMBER(5)
SECONDARY_UOM_CODE DUAL_UOM_DEVIATION_LOW DUAL_UOM_DEVIATION_HIGH ONT_PRICING_QTY_SOURCE
VARCHAR2(3) NUMBER NUMBER VARCHAR2(30)
LOT_CONTROL_CODE LOT_DIVISIBLE_FLAG
NUMBER VARCHAR2(1)
Version: 1.10
Page 42 of 67
AUTOLOT_ACTIVE_INDI CATOR LOT_PREFIX
NUMBER(1)
VARCHAR2(32)
AUTO_LOT_ALPHA_PREFIX
VARCHAR2(30)
LOT_SUFFIX
NUMBER(32)
START_AUTO_LOT_NUMBER
VARCHAR2(30)
SUBLOT_CTL
*NUMBER(5)
CHILD_LOT_FLAG CHILD_LOT_VALIDATION_FLAG COPY_LOT_ATTRIBUTE_FLAG PARENT_CHILD_GENERATION_ FLAG CHILD_LOT_PREFIX
VARCHAR2(1) VARCHAR2(1) VARCHAR2(1)
SUBLOT_PREFIX
VARCHAR2(32)
VARCHAR2(30)
SUBLOT_SUFFIX
NUMBER(32)
CHILD_LOT_STARTING_NUMBE R
NUMBER
LOCT_CTL NONINV_IND
*NUMBER(5) *NUMBER(5)
LOCATION_CONTROL_CODE INVENTORY_ITEM_FLAG INVENTORY_ASSET_FLAG COSTING_ENABLED_FLAG STOCK_ENABLED_FLAG BUILD_IN_WIP_FLAG MTL_TRANSACTIONS_ENABLE D_FLAG 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 ITEM_TYPE
NUMBER VARCHAR2(1) VARCHAR2(1) VARCHAR2(1) VARCHAR2(1)
= N if LOT_INDIVISIBLE = 1 In Oracle Inventory, the auto lot numbering is always enabled for a lot or lot/child lot controlled items. 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 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 GMI_MIGRATION_PARMS table. 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 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 GMI_MIGRATION_PARMS table. 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 GMI_MIGRATION_PARMS table. = LOCT_CTL + 1 IF NONINV_IND = 1 Set all of these flags to N. ELSE No Change
MATCH_TYPE INACTIVE_IND
*NUMBER(5) *NUMBER(5)
VARCHAR2(1)
Obsolete. IF INACTIVE_FLAG = 1 THEN Set all these flags to N. ELSE No Change.
INV_TYPE
VARCHAR2(4)
VARCHAR2(30)
SHELF_LIFE
*NUMBER
SHELF_LIFE_CODE SHELF_LIFE_DAYS
NUMBER NUMBER
OPM Inventory types are migrated to Item Types in discrete. The Item Types are defined as Lookup Codes. 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 GL_CLASS
*NUMBER VARCHAR2(8)
RETEST_INTERVAL
NUMBER All Item Classes are converged to Item categories. For example, GL_CLASS is
Version: 1.10
Page 43 of 67
INV_CLASS
VARCHAR2(8)
SALES_CLASS
VARCHAR2(8)
SHIP_CLASS
VARCHAR2(8)
FRT_CLASS
VARCHAR2(8)
PRICE_CLASS
VARCHAR2(8)
STORAGE_CLASS
VARCHAR2(8)
PURCH_CLASS
VARCHAR2(8)
TAX_CLASS
VARCHAR2(8)
CUSTOMS_CLASS
VARCHAR2(8)
ALLOC_CLASS
VARCHAR2(8)
PLANNING_CLASS
VARCHAR2(8)
ITEMCOST_CLASS
VARCHAR2(8)
SEQ_DPND_CLASS
VARCHAR2(8)
COST_MTHD_CODE UPC_CODE
VARCHAR2(4) VARCHAR2(16)
GRADE_CTL STATUS_CTL QC_GRADE LOT_STATUS
*NUMBER(5) *NUMBER(5) VARCHAR2(4) VARCHAR2(4)
GRADE_CONTROL_FLAG LOT_STATUS_ENABLED DEFAULT_GRADE DEFAULT_LOT_STATUS_ID
VARCHAR2(1) VARCHAR2(1) VARCHAR2 (150) NUMBER
assigned as a category in the MTL_ITEM_CATEGORIES table. All Item Classes are converged to Item categories. For example, INV_CLASS is assigned as a category in the MTL_ITEM_CATEGORIES table. All Item Classes are converged to Item categories. For example, SALES_CLASS is assigned as a category in the MTL_ITEM_CATEGORIES table. All Item Classes are converged to Item categories. For example, SHIP_CLASS is assigned as a category in the MTL_ITEM_CATEGORIES table. All Item Classes are converged to Item categories. For example, FRT_CLASS is assigned as a category in the MTL_ITEM_CATEGORIES table. All Item Classes are converged to Item categories. For example, PRICE_CLASS is assigned as a category in the MTL_ITEM_CATEGORIES table. All Item Classes are converged to Item categories. For example, STORAGE_CLASS is assigned as a category in the MTL_ITEM_CATEGORIES table. All Item Classes are converged to Item categories. For example, PURCH_CLASS is assigned as a category in the MTL_ITEM_CATEGORIES table. All Item Classes are converged to Item categories. For example, GL_CLASS is assigned as a category in the MTL_ITEM_CATEGORIES table. All Item Classes are converged to Item categories. For example, CUSTOMS_CLASS is assigned as a category in the MTL_ITEM_CATEGORIES table. All Item Classes are converged to Item categories. For example, ALLOC_CLASS is assigned as a category in the MTL_ITEM_CATEGORIES table. All Item Classes are converged to Item categories. For example, PLANNING_CLASS is assigned as a category in the MTL_ITEM_CATEGORIES table. All Item Classes are converged to Item categories. For example, ITEMCOST_CLASS is assigned as a category in the MTL_ITEM_CATEGORIES table. All Item Classes are converged to Item categories. For example, SEQ_DPND_CLASS is assigned as a category in the MTL_ITEM_CATEGORIES table. Obsolete. Not on OPM form. There is no matching column in Oracle Inventory for this field. This column migrates as an obsolete column to the flexfield. = Y if GRADE_CTL = 1 = N if GRADE_CTL = 0 = Y if STATUS_CTL = 1 = N if STATUS_CTL = 0
Note that the STATUS_ID is obtained from the IC_LOTS_STS.STATUS_ID . This column is populated in OPM by material
Version: 1.10
Page 44 of 67
BULK_ID PKG_ID QCITEM_ID QCHOLD_RES_CODE EXPACTION_CODE FILL_QTY FILL_UM EXPACTION_INTERVAL PHANTOM_TYPE WHSE_ITEM_ID
NUMBER(10) NUMBER(10) NUMBER(10) VARCHAR2(4) VARCHAR2(4) *NUMBER VARCHAR2(4) *NUMBER *NUMBER(5) *NUMBER(10)
status migration. Obsolete. Not on OPM form. Obsolete. Not on OPM form. Obsolete. Obsolete. EXPIRATION_ACTION_CODE VARCHAR2(32) Obsolete. Not on OPM form. Obsolete. Not on OPM form. EXPIRATION_ACTION_INTERVA L NUMBER Obsolete. Not on OPM form. 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 EXPORTED_DATE TRANS_CNT DELETE_MARK TEXT_CODE COMMODITY_CODE
*NUMBER(5) *DATE NUMBER(10) *NUMBER(5) NUMBER(10) VARCHAR2(9)
ENG_ITEM_FLAG
VARCHAR2(1)
See INACTIVE_IND
ITEM_ABCCODE
VARCHAR2(4)
= Y, if EXPERIMENTAL_IND = 1 = N, if EXPERIMENTAL_IND = 0 Obsolete. Not on OPM form. Obsolete. Not on OPM form. See INACTIVE_IND. Delete mark is migrated like inactive indicator. Migrated as edit text. 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. 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. This category assignment already exists in Item Categories in discrete. If not, then it migrates as an item category in discrete. This category assignment already exists in Item Categories in discrete. If not, then it migrates as an item category in discrete. This category assignment already exists in Item Categories in discrete. If not, then it migrates as an item category in discrete. This category assignment already exists in Item Categories in discrete. If not, then it migrates as an item category in discrete. This category assignment already exists in Item Categories in discrete. If not, then it migrates as an item category in discrete. This category assignment already exists in Item Categories in discrete. If not, then it migrates as an item category in discrete. This category assignment already exists in Item Categories in discrete. If not, then it migrates as an item category in discrete.
ALLOC_CATEGORY_ID
NUMBER
CUSTOMS_CATEGORY_I D FRT_CATEGORY_ID
NUMBER
NUMBER
GL_CATEGORY_ID
NUMBER
INV_CATEGORY_ID
NUMBER
COST_CATEGORY_ID
NUMBER
PLANNING_CATEGORY_I D
NUMBER
Version: 1.10
Page 45 of 67
PRICE_CATEGORY_ID
NUMBER
PURCH_CATEGORY_ID
NUMBER
SALES_CATEGORY_ID
NUMBER
SEQ_CATEGORY_ID
NUMBER
SHIP_CATEGORY_ID
NUMBER
STORAGE_CATEGORY_I D TAX_CATEGORY_ID
NUMBER
NUMBER
Who Columns ATTRIBUTE1-30
*DATE VARCHAR2 (240)
ATTRIBUTE1-30
VARCHAR2 (240)
ATTRIBUTE_CATEGORY
VARCHAR2(30)
ATTRIBUTE_CATEGORY
VARCHAR2(30)
This category assignment already exists in Item Categories in discrete. If not, then it migrates as an item category in discrete. This category assignment already exists in Item Categories in discrete. If not, then it migrates as an item category in discrete. This category assignment already exists in Item Categories in discrete. If not, then it migrates as an item category in discrete. This category assignment already exists in Item Categories in discrete. If not, then it migrates as an item category in discrete. This category assignment already exists in Item Categories in discrete. If not, then it migrates as an item category in discrete. This category assignment already exists in Item Categories in discrete. If not, then it migrates as an item category in discrete. This category assignment already exists in Item Categories in discrete. If not, then it migrates as an item category in discrete. Standard Who columns 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. This column is migrated only if the attribute category is blank in the discrete item master. Otherwise, an error is reported in the validation script.
IC_PLNT_INV
Source Column (in IC_PLNT_INV)
ITEM_ID

*NUMBER(10)
Destination Column (in MTL_SYSTEM_ITEMS)

INVENTORY_ITEM_ID
Date Type
NUMBER
Comments
System generated id. Note that the id has the same value, if the item is assigned to multiple organizations. 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. = VARIABLE_LEADTIME / STD_QTY
ORGN_CODE
VARCHAR2(4)
ORGANIZATION_ID
NUMBER
FIXED_LEADTIME VARIABLE_LEADTIME
*NUMBER *NUMBER
FIXED_LEAD_TIME VARIABLE_LEAD_TIME
NUMBER NUMBER
Version: 1.10
Page 46 of 67
IC_ITEM_CPG
Source Column (in IC_ITEM_CPG)

ITEM_ID

*NUMBER(10)
Destination Column (in MTL_SYSTEM_ITEMS)

INVENTORY_ITEM_ID
Date Type
NUMBER
Comments
System generated id. Note that the id has the same value, if the item is assigned to multiple organizations. Only the process enabled organizations will be affected by this migration.
ORGANIZATION_ID IC_MATR_DAYS IC_HOLD_DAYS Who Columns NUMBER(5) NUMBER(5) MATURITY_DAYS HOLD_DAYS Who columns
NUMBER NUMBER NUMBER
IC_ITEM_MST_TL
Source Column (in IC_ITEM_MST_tl)
ITEM_ID

*NUMBER(10)
Destination Column (in MTL_SYSTEM_ITEMS_tl)

INVENTORY_ITEM_ID
Date Type
Comments
NUMBER
ORGANIZATION_ID LANGUAGE SOURCE_LANG ITEM_DESC1 ITEM_DESC2 *VARCHAR2(4) *VARCHAR2(4) *VARCHAR2 (70) VARCHAR2(70) LANGUAGE SOURCE_LANG DESCRIPTION LONG_DESCRIPTION
NUMBER VARCHAR2(4) VARCHAR2(4) VARCHAR2 (240) VARCHAR2 (4000)
System generated id. Note that the id has the same value, if the item is assigned to multiple organizations. Only the process enabled organizations will be affected by this migration.
We currently dont synchronize this column. Note that this migration will only happen if the LONG_DESCRIPTION column is null in discrete.
Who Columns
Who columns
GMI_ITEM_CATEGORIES
Source Column (in GMI_ITEM_CATEGORI ES)
ITEM_ID CATEGORY_SET_ID CATEGORY_ID Who Columns

*NUMBER *NUMBER *NUMBER
Destination Column (in MTL_ITEM_CATEGORIES)

INVENTORY_ITEM_ID ORGANIZATION_ID CATEGORY_SET_ID CATEGORY_ID Who columns
Date Type
Comments
NUMBER NUMBER NUMBER NUMBER
Version: 1.10
Page 47 of 67
GMI_CATEGORY_SETS
Source Column (in gmi_category_sets)
OPM_CLASS CATEGORY_SET_ID USER_OPM_CLASS RESTRICTED Who Columns

*VARCHAR2(40) NUMBER *VARCHAR2(40) VARCHAR2(1)
Destination Column (in MTL_DEFAULT_ CATEGORY_SETS )

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

*NUMBER(10) *NUMBER(10) *VARCHAR2(32)
Destination Column (in MTL_LOT_NUMBERS)

INVENTORY_ITEM_ID ORGANIZATION_ID
Date Type
NUMBER NUMBER
Comments
PARENT_LOT_NUMBER LOT_NUMBER
VARCHAR2(80)
SUBLOT_NO
VARCHAR2(32)
PARENT_LOT_NUMBER LOT_NUMBER
VARCHAR2(80)
No migration needed because discrete uses lot_number as part of the key. 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 premigration form. Sublot Sublot Parent Lot Control No Lot (Child) Yes NULL NULL LOT_NO Yes Not LOT_ LOT_NO NULL NO || SUBLOT _NO No NULL LOT_NO Same as above
Version: 1.10
Page 48 of 67
LOT_DESC
VARCHAR2(40)
DESCRIPTION
VARCHAR2 (256)
QC_GRADE
VARCHAR2(4)
GRADE_CODE STATUS_ID
VARCHAR2 (150) NUMBER
AVAILABILITY_TYPE
NUMBER
INVENTORY_ATP_CODE
NUMBER
RESERVABLE_TYPE
NUMBER
EXPACTION_CODE EXPACTION_DATE LOT_CREATED EXPIRE_DATE RETEST_DATE STRENGTH INACTIVE_IND ORIGINATION_TYPE SHIPVEND_ID
VARCHAR2(4) DATE DATE DATE DATE *NUMBER *NUMBER(5) *NUMBER(5) NUMBER(10)
EXPIRATION_ACTION_CODE EXPIRATION_ACTION_DATE ORIGINATION_DATE EXPIRATION_DATE RETEST_DATE DISABLE_FLAG ORIGINATION_TYPE VENDOR_ID VENDOR_NAME
VARCHAR2(32) DATE DATE DATE DATE NUMBER NUMBER(2) NUMBER VARCHAR2 (240) VARCHAR2 (150) NUMBER
Description column in discrete inventory is non-functional. However, we will migrate the OPM Lot description to this column. Foreign Key reference to the MTL_GRADES table. 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 This value will be derived from the MTL_MATERIAL_STATUSES for the STATUS_ID of the lot. This value will be derived from the MTL_MATERIAL_STATUSES for the STATUS_ID of the lot. This value will be derived from the MTL_MATERIAL_STATUSES for the STATUS_ID of the lot. Foreign Key reference to the MTL_ACTIONS table.
Obsolete Column, not used in OPM. = 1, if INACTIVE_IND = 1 = NULL, otherwise Use this to get the discrete vendor_id select of_vendor_id from po_vend_mst where vendor_id = <SHIPVEND_ID>
VENDOR_LOT_NO Who Columns DELETE_MARK TEXT_CODE ATTRIBUTE1-30
VARCHAR2(32)
SUPPLIER_LOT_NUMBER Who Columns DISABLE_FLAG
*NUMBER(5) NUMBER(10) VARCHAR2 (240)
ATTRIBUTE_CATEGORY
VARCHAR2(30)
ODM_LOT_NUMBER
VARCHAR2(30)
= 1, if DELETE_MARK = 1 = NULL, otherwise Migrated as edit text. 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. Otherwise, an error is reported in the validation script. This column is migrated only if the attribute category is blank in the discrete item master. Otherwise, an error is reported in the validation script. Obsolete in convergence.
Version: 1.10
Page 49 of 67
GMD_GRADES_B
Source Column (in GMD_GRADES_B)
QC_GRADE QC_GRADE_DESC DELETE_MARK TEXT_CODE ATTRIBUTE1-30 ATTRIBUTE_CATEGORY Who Columns

*VARCHAR2(4) VARCHAR2(40) *NUMBER(5) NUMBER(10) VARCHAR2 (240) VARCHAR2(30)
Destination Column (in MTL_GRADES_B)

GRADE_CODE
Date Type
VARCHAR2 (150)
Comments
DISABLE_FLAG
VARCHAR2(1)
Description is migrated to the TL table only. = Y if delete_mark = 1 = N otherwise Migrated as edit text.
ATTRIBUTE1-30 ATTRIBUTE_CATEGORY Who Columns
VARCHAR2 (240) VARCHAR2(30)
GMD_GRADES_TL
Source Column (in GMD_GRADES_TL)
QC_GRADE QC_GRADE_DESC SOURCE_LANG LANGUAGE Who Columns

*VARCHAR2(4) *VARCHAR2(40) *VARCHAR2(4) *VARCHAR2(4)
Destination Column (in MTL_GRADES_TL)

GRADE_CODE DESCRIPTION SOURCE_LANG LANGUAGE Who Columns
Date Type
VARCHAR2(150) VARCHAR2(240) VARCHAR2(4) VARCHAR2(4)
Comments
GMD_ACTIONS_B
Source Column (in GMD_ACTIONS_B)
ACTION_CODE ACTION_INTERVAL DELETE_MARK TEXT_CODE ATTRIBUTE1-30 ATTRIBUTE_CATEGORY Who Columns

*VARCHAR2(32) *NUMBER *NUMBER(5) NUMBER(10) VARCHAR2 (240) VARCHAR2(30)
Destination Column (in MTL_ACTIONS_B)

ACTION_CODE
Date Type
VARCHAR2(32)
Comments
DISABLE_FLAG
VARCHAR2(1)
Currently Non-functional in OPM. Obsolete in the converged model. = Y if delete_mark = 1 = N otherwise Migrated as edit text.
ATTRIBUTE1-30 ATTRIBUTE_CATEGORY Who Columns
VARCHAR2 (240) VARCHAR2(30)
GMD_ACTIONS_TL
Source Column Data Type (in GMD_ACTIONS_TL) (*=Not Null)
ACTION_CODE DESCRIPTION SOURCE_LANG LANGUAGE Who Columns *VARCHAR2(32) *VARCHAR2(80) *VARCHAR2(4) *VARCHAR2(4)
Destination Column (in MTL_ACTIONS_TL)

ACTION_CODE DESCRIPTION SOURCE_LANG LANGUAGE Who Columns
Date Type
VARCHAR2(32) VARCHAR2(80) VARCHAR2(4) VARCHAR2(4)
Comments
Version: 1.10
Page 50 of 67
IC_LOTS_STS to MTL_MATERIAL_STATUSES_B
Source Column (in IC_LOTS_STS)
LOT_STATUS

*VARCHAR2(4)
Destination Column (in MTL_MATERIAL_STATUSES_ B)

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

*VARCHAR2(4)
Destination Column (in MTL_ MATERIAL_STATUSES_TL)

STATUS_CODE STATUS_ID
Date Type
VARCHAR2(80) NUMBER VARCHAR2(240) VARCHAR2(4) VARCHAR2(4)
Comments
Will be migrated to mtl_material_statuses_tl table. System generated surrogate for the status. Will be migrated to mtl_material_statuses_tl table. Determine by MLS package when called to insert a row. Determine by MLS package when called to insert a row.
STATUS_DESC
*VARCHAR2(40)
DESCRIPTION LANGUAGE SOURCE_LANG
Who Column
Who Column
Version: 1.10
Page 51 of 67
IC_LOTS_STS to MTL_STATUS_TRANSACTION_CONTROL
LOT_STATUS

*VARCHAR2(4)
Destination Column (in Date Type MTL_STATUS_TRANSACTION_ CONTROL)

STATUS_ID IS_ALLOWED NUMBER NUMBER
Comments
System generated surrogate for the status. = 1, (Yes) if OPM indicators are 1 = 2, (No) otherwise. This indicator allows or disallows transaction type based on the Lot Status. This indicator allows or disallows transaction type based on the Lot Status. This indicator allows or disallows transaction type based on the Lot Status. This indicator allows or disallows transaction type based on the Lot Status..
NETTABLE_IND ORDER_PROC_IND PROD_IND SHIPPING_IND REJECTED_IND Who Column
*NUMBER(5) *NUMBER(5) *NUMBER(5) *NUMBER(5) *NUMBER(5)
TRANSACTION_TYPE_ID TRANSACTION_TYPE_ID TRANSACTION_TYPE_ID TRANSACTION_TYPE_ID
IC_ITEM_CNV
Source Column (in IC_ITEM_CNV) Data Type (*=Not Null) Destination Column (in MTL_LOT_UOM_CLASS _CONVERSIONS)
ORGANIZATION_ID
Date Type
Comments
*NUMBER
LOT_ID
*NUMBER(10)
LOT_NUMBER
*VARCHAR2(80)
ITEM_ID
*NUMBER(10)
INVENTORY_ITEM_ID
*NUMBER
FROM_UNIT_OF_MEASURE
*VARCHAR2(25)
Call the get_ODM_lot routine to get (or create) the discrete item/ lot for the OPM item/ lot. Call the get_ODM_lot routine to get (or create) the discrete item/ lot for the OPM item/ lot. Call the get_ODM_lot routine to get (or create) the discrete item/ lot for the OPM item/ lot. 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 Derive the value using the above logic UOM Class of the items primary UOM. 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 Call the get_ODM_lot routine to get (or create) the discrete item/ lot for the OPM
FROM_UOM_CODE FROM_UOM_CLASS TO_UNIT_OF_MEASURE
*VARCHAR2(3) *VARCHAR2(10) *VARCHAR2(25)
TO_UOM_CODE
*VARCHAR2(3)
Version: 1.10
Page 52 of 67
item/ lot. UM_TYPE TYPE_FACTOR TYPE_FACTORREV CONVERSION_ID EVENT_SPEC_DISP_ID DELETE_MARK *VARCHAR2(10) *NUMBER *NUMBER *NUMBER NUMBER *NUMBER(5) EVENT_SPEC_DISP_ID DISABLE_DATE NUMBER DATE TO_UOM_CLASS CONVERSION_RATE *VARCHAR2(10) *NUMBER Discrete tables do not store the reverse factors System generated surrogate using the MTL_CONVERSION_ID_S sequence. = LAST_UPDATE_DATE, if DELETE_MARK = 1 = NULL, otherwise. Migrated as edit text.
TEXT_CODE Who Columns
NUMBER(10) Who Columns
GMI_ITEM_CONV_AUDIT
Source Column (in Data Type GMI_ITEM_CONV_AUDIT (*=Not Null) )
CONV_AUDIT_ID CONVERSION_ID *NUMBER *NUMBER
Destination Column (in MTL_LOT_CONV_AUDIT)

CONV_AUDIT_ID CONVERSION_ID
Date Type
Comments
*NUMBER *NUMBER
System generated surrogate using the MTL_CONV_AUDIT_ID_S sequence. Use the CONVERSION_ID from the MTL_LOT_UOM_CLASS_CONMVERSIO NS table. REASON_ID from the MTL_TRANSACTION_REASONS table for the REASON_CODE
CONVERSION_DATE REASON_CODE
*DATE VARCHAR2(4)
CONVERSION_DATE REASON_ID
*DATE NUMBER
OLD_TYPE_FACTOR NUMBER NEW_TYPE_FACTOR *NUMBER EVENT_SPEC_DISP_ID NUMBER BATCH_ID NUMBER(10) UPDATE_BATCH_INDICATO NUMBER(10) R Who Columns
OLD_CONVERSION_RATE NEW_CONVERSION_RATE EVENT_SPEC_DISP_ID BATCH_ID UPDATE_TYPE_INDICATOR Who Columns
NUMBER *NUMBER NUMBER NUMBER *NUMBER
GMI_ITEM_CONV_AUDIT_DETAILS
Source Column (in GMI_ITEM_CONV_ AUDIT_DETAILS)
CONV_AUDIT_DETAIL_ID

*NUMBER
Destination Column (in MTL_LOT_CONV_AUDIT _DETAILS)

CONV_AUDIT_DETAIL_ID
Date Type
Comments
*NUMBER
CONV_AUDIT_ID
*NUMBER
CONV_AUDIT_ID REVISION ORGANIZATION_ID SUBINVENTORY_CODE LPN_ID LOCATOR_ID
*NUMBER VARCHAR2(3) *NUMBER VARCHAR2(10) NUMBER NUMBER
WHSE_CODE
*VARCHAR2(4)
LOCATION
*VARCHAR2(16)
System generated surrogate using the MTL_CONV_AUDIT_DETAIL_ID_S sequence CONV_AUDIT_ID from the MTL_LOT_CONV_AUDIT table. = NULL = ORGANIZATION_ID from IC_WHSE_MST for the WHSE_CODE. = WHSE_CODE NULL = INVENTORY_LOCATION_ID from IC_LOCT_MST for the WHSE_CODE, LOCATION.
OLD_ONHAND_QTY OLD_ONHAND_QTY2 NEW_ONHAND_QTY NEW_ONHAND_QTY2
*NUMBER NUMBER NUMBER NUMBER
OLD_PRIMARY_QTY OLD_SECONDARY_QTY NEW_PRIMARY_QTY NEW_SECONDARY_QTY
*NUMBER NUMBER NUMBER NUMBER
Version: 1.10
Page 53 of 67
TRANS_QTY TRANS_QTY2 TRANS_UPDATE_FLAG Who Columns
NUMBER NUMBER *VARCHAR2(1)
TRANSACTION_PRIMARY_QTY NUMBER TRANSACTION_SECONDARY_QTY NUMBER TRANSACTION_UPDATE_FLAG *VARCHAR2(2) Who Columns
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/ Out (in Create_transfer_pub)
P_api_version P_init_msg_list P_commit P_validation_level X_return_status X_msg_count X_msg_data P_hdr_rec P_line_rec_tbl P_lot_rec_tbl x_hdr_row x_line_row_tbl x_lot_row_tbl IN IN IN IN OUT NOCOPY OUT NOCOPY OUT NOCOPY IN IN IN OUT NOCOPY OUT NOCOPY OUT NOCOPY
Data Type
Comments
NUMBER VARCHAR2 DEFAULT FND_API.G_FALSE VARCHAR2 DEFAULT FND_API.G_FALSE NUMBER DEFAULT FND_API.G_VALID_LEVEL_FULL VARCHAR2 NUMBER VARCHAR2 GMIVDX.hdr_type GMIVDX.line_type_tbl GMIVDX.lot_type_tbl gmi_discrete_transfers%ROWTYPE GMIVDX.line_row_tbl 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)
ORGN_CODE CO_CODE TRANSFER_NUMBER TRANSFER_TYPE
Comments
= orgn_code of the inventory balance warehouse. API will internally determine the values when determining the charge account. Automatically generated number = 0 ( Process to Discrete) = 1 ( Discrete to Process) used for transferring negative balances. = sysdate OPM Convergence Migration NULL NULL NULL NULL
TRANS_DATE COMMENTS ATTRIBUTE_CATEGORY ATTRIBUTE1-30 ASSIGNMENT_TYPE TRANSACTION_HEADER_ID
Version: 1.10
Page 54 of 67
IC_LOCT_INV to Line Type

Source Column (in IC_LOCT_INV) Data Type (*=Not Null) Destination (in LINE_TYPE record)
LINE_NO
Comments
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 WHSE_CODE LOCATION LOT_ID
NUMBER(10) VARCHAR2(4) VARCHAR2(16) NUMBER(10)
OPM_ITEM_ID OPM_WHSE_CODE OPM_LOCATION OPM_LOT_ID
LOT_STATUS
VARCHAR2(4)
OPM_LOT_EXPIRATION_DATE OPM_LOT_STATUS OPM_GRADE OPM_CHARGE_ACCT_ID OPM_CHARGE_AU_ID OPM_REASON_CODE ODM_INV_ORGANIZATION_ID ODM_ITEM_ID ODM_ITEM_REVISION ODM_SUBINVENTORY
WHSE_CODE
VARCHAR2(4)
ODM_LOCATOR_ID ODM_LOT_NUMBER ODM_LOT_EXPIRATION_DATE ODM_CHARGE_ACCOUNT_ID ODM_PERIOD_ID ODM_UNIT_COST ODM_REASON_ID QUANTITY
LOCT_ONHAND
NUMBER
LOCT_ONHAND2
NUMBER
QUANTITY_UM QUANTITY2
OPM_PRIMARY_QUANTITY ODM_PRIMARY_QUANTITY LOT_LEVEL ATTRIBUTE_CATEGORY ATTRIBUTE1-30 OPM_ITEM_NO LOT_CONTROL ODM_QUANTITY_UOM_CODE OPM_LOT_NO OPM_SUBLOT_NO
= 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. API internally determines the values. API internally determines the values. API internally determines the values. API internally determines the values. API internally determines the values. NULL MTL_ORGANIZATION_ID from the IC_WHSE_MST for the OPM warehouse. Call the get_ODM_item to get Discrete Item from discrete inventory for the OPM Item and the warehouse. NULL. No OPM items are revision controlled. 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.) INVENTORY_LOCATION_ID from the IC_LOCT_MST for the OPM Warehouse and Location. LOT_NUMBER from the IC_LOTS_MST_MIG table for the Inventory organization_id and OPM LOT_ID. API internally determines the values. API internally determines the values. API internally determines the values. NULL NULL 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. = ITEM_UM from ic_item_mst_b for the item_id. 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. API internally determines the values. API internally determines the values. API internally determines the values. NULL NULL API internally determines the values. API internally determines the values. API internally determines the values. API internally determines the values. API internally determines the values.
Version: 1.10
Page 55 of 67
IC_LOCT_INV to Lot Type

This table is mapping to the API call:
Source Column (in IC_LOCT_INV)
LOT_ID

NUMBER(10)
Destination (in LOT_TYPE record)

LINE_NO OPM_LOT_ID OPM_LOT_EXPIRATION_DATE OPM_LOT_STATUS OPM_GRADE ODM_LOT_NUMBER ODM_LOT_EXPIRATION_DATE QUANTITY QUANTITY2 OPM_PRIMARY_QUANTITY ODM_PRIMARY_QUANTITY OPM_LOT_NO OPM_SUBLOT_NO
Comments
The line_no in the LINE_TYPE record for which the lot data is being specified. Call the get_ODM_lot to get Discrete Item/ Lot from the discrete inventory for the OPM Items and the warehouse. API internally determines the values. API internally determines the values. API internally determines the values. LOT_NUMBER from the IC_LOTS_MST_MIG table for the Inventory organization_id and OPM LOT_ID. API internally determines the values.
LOCT_ONHAND LOCT_ONHAND2 LOCT_ONHAND LOCT_ONHAND
API internally determines the values. 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)
ORGN_CODE CO_CODE TRANSFER_NUMBER TRANSFER_TYPE
Comments
TRANS_DATE COMMENTS ATTRIBUTE_CATEGORY ATTRIBUTE1-30 ASSIGNMENT_TYPE TRANSACTION_HEADER_ID
= orgn_code of the inventory balance warehouse. API will internally determine the values when determining the charge account. Automatically generated number = 0 ( Process to Discrete) = 1 ( Discrete to Process) used for transferring negative balances. = sysdate OPM Convergence Migration NULL NULL NULL NULL
RESERVATION_ID REQUIREMENT_DATE ORGANIZATION_ID INVENTORY_ITEM_ID DEMAND_SOURCE_TYPE_ID DEMAND_SOURCE_NAME
NULL OE_ORDER_LINES_ALL.REQUEST_DATE OE_ORDER_LINES_ALL.SHIP_FROM_ORG_ID OE_ORDER_LINES_ALL.INVENTORY_ITEM_ID OE_ORDER_LINES_ALL.DEMAND_SOURCE_TYPE_ID NULL
Version: 1.10
Page 56 of 67
DEMAND_SOURCE_LINE_ID DEMAND_SOURCE_DELIVERY PRIMARY_UOM_CODE PRIMARY_UOM_ID PRIMARY_RESERVATION_QUANTITY RESERVATION_UOM_CODE RESERVATION_UOM_ID RESERVATION_QUANTITY LOT_NUMBER
OE_ORDER_LINES_ALL.LINE_ID NULL OE_ORDER_LINES_ALL.ORDER_QUANTITY_UOM NULL OE_ORDER_LINES_ALL..ORDERED_QUANTITY OE_ORDER_LINES_ALL.ORDER_QUANTITY_UOM NULL OE_ORDER_LINES_ALL.ORDERED_QUANTITY 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
LOCATION_CODE ADDRESS_LINE_1 ADDRESS_LINE_2 ADDRESS_LINE_3 BILL_TO_SITE_FLAG COUNTRY DESCRIPTION DESIGNATED_RECEIVER_ID IN_ORGANIZATION_FLAG INACTIVE_DATE INVENTORY_ORGANIZATION_ID OFFICE_SITE_FLAG POSTAL_CODE RECEIVING_SITE_FLAG REGION_1 REGION_2 REGION_3 SHIP_TO_LOCATION_ID SHIP_TO_SITE_FLAG DERIVED_LOCALE STYLE TAX_NAME TELEPHONE_NUMBER_1 TELEPHONE_NUMBER_2 TELEPHONE_NUMBER_3 TOWN_OR_CITY
Value
Orgn_Code Addr1 Addr2 Addr3 NULL Country_Code Orgn_Name NULL NULL NULL Migrated Organization_Id from Hr_Organization_Units this is updated after migrating the organization. NULL Postal_Code NULL Province County State_Code NULL NULL NULL OPM NULL NULL NULL NULL Addr4
HR_ORGANIZATION_UNITS
The HR organization is created in this table.
Column Value
Version: 1.10
Page 57 of 67
Column
ORGANIZATION_ID BUSINESS_GROUP_ID COST_ALLOCATION_KEYFLEX_ID LOCATION_ID SOFT_CODING_KEYFLEX_ID DATE_FROM NAME COMMENTS DATE_TO INTERNAL_EXTERNAL_FLAG INTERNAL_ADDRESS_LINE TYPE
Value
hr_organization_units_s.nextval Hr_operating_unts.business_group_id based on the fiscal policy operating unit. NULL Location_Id generated from the above insert. NULL Creation_Date Orgn_Name NULL Set to SYSDATE if the org is being migrated as Inactive. INT NULL NULL
HR_ORGANIZATION_INFORMATION
The HR organization classification for inventory organizations is created in this table if the Inventory_Org indicator is 1.
Column
ORG_INFORMATION_ID ORG_INFORMATION_CONTEXT ORGANIZATION_ID ORG_INFORMATION1 ORG_INFORMATION2 ORG_INFORMATION3
Value
hr_organization_information_s.nextval CLASS Organization_Id generated above INV Y NULL
After classifying the accounting information, it is created in this table.

Column
ORG_INFORMATION_ID ORG_INFORMATION_CONTEXT ORGANIZATION_ID ORG_INFORMATION1 ORG_INFORMATION2 ORG_INFORMATION3
Value
hr_organization_information_s.nextval Accounting Information Organization_Id generated above Set_Of_Books ID from the template organization Legal Entity ID from the template organization Operation Unit from the template organization
MTL_PARAMETERS
The inventory organization is created in this table.
Column
ORGANIZATION_ID ORGANIZATION_CODE MASTER_ORGANIZATION_ID PRIMARY_COST_METHOD COST_ORGANIZATION_ID DEFAULT_MATERIAL_COST_ID CALENDAR_EXCEPTION_SET_ID CALENDAR_CODE GENERAL_LEDGER_UPDATE_CODE DEFAULT_ATP_RULE_ID DEFAULT_PICKING_RULE_ID DEFAULT_LOCATOR_ORDER_VALUE DEFAULT_SUBINV_ORDER_VALUE NEGATIVE_INV_RECEIPT_CODE STOCK_LOCATOR_CONTROL_CODE MATERIAL_ACCOUNT MATERIAL_OVERHEAD_ACCOUNT MATL_OVHD_ABSORPTION_ACCT RESOURCE_ACCOUNT
Value
Organization_Id generated above Organization_Code from the Setup Master Organization Id from the setup Inherited from the template organization Inherited from the template organization Inherited from the template organization Inherited from the template organization Inherited from the template organization Inherited from the template organization Inherited from the template organization Inherited from the template organization Inherited from the template organization Inherited from the template organization Inherited from the template organization Inherited from the template organization Inherited from the template organization Inherited from the template organization Inherited from the template organization Inherited from the template organization
Version: 1.10
Page 58 of 67
Column
PURCHASE_PRICE_VAR_ACCOUNT AP_ACCRUAL_ACCOUNT OVERHEAD_ACCOUNT OUTSIDE_PROCESSING_ACCOUNT INTRANSIT_INV_ACCOUNT INTERORG_RECEIVABLES_ACCOUNT INTERORG_PRICE_VAR_ACCOUNT INTERORG_PAYABLES_ACCOUNT COST_OF_SALES_ACCOUNT ENCUMBRANCE_ACCOUNT INTERORG_TRANSFER_CR_ACCOUNT MATL_INTERORG_TRANSFER_CODE INTERORG_TRNSFR_CHARGE_PERCENT SOURCE_ORGANIZATION_ID SOURCE_SUBINVENTORY SOURCE_TYPE SERIAL_NUMBER_TYPE AUTO_SERIAL_ALPHA_PREFIX START_AUTO_SERIAL_NUMBER AUTO_LOT_ALPHA_PREFIX LOT_NUMBER_UNIQUENESS LOT_NUMBER_GENERATION LOT_NUMBER_ZERO_PADDING LOT_NUMBER_LENGTH STARTING_REVISION DEFAULT_DEMAND_CLASS ENCUMBRANCE_REVERSAL_FLAG MAINTAIN_FIFO_QTY_STACK_TYPE PROCESS_ENABLED_FLAG
Value
Inherited from the template organization Inherited from the template organization Inherited from the template organization Inherited from the template organization Inherited from the template organization Inherited from the template organization Inherited from the template organization Inherited from the template organization Inherited from the template organization Inherited from the template organization Inherited from the template organization Inherited from the template organization Inherited from the template organization Inherited from the template organization Inherited from the template organization Inherited from the template organization Inherited from the template organization Inherited from the template organization Inherited from the template organization Inherited from the template organization 2 (None) Inherited from the template organization Inherited from the template organization Inherited from the template organization Inherited from the template organization Inherited from the template organization Inherited from the template organization Inherited from the template organization 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
SECONDARY_INVENTORY_NAME ORGANIZATION_ID DESCRIPTION DISABLE_DATE INVENTORY_ATP_CODE AVAILABILITY_TYPE RESERVABLE_TYPE LOCATOR_TYPE PICKING_ORDER DROPPING_ORDER MATERIAL_ACCOUNT MATERIAL_OVERHEAD_ACCOUNT RESOURCE_ACCOUNT OVERHEAD_ACCOUNT OUTSIDE_PROCESSING_ACCOUT QUANTITY_TRACKED ASSET_INVENTORY SOURCE_TYPE SOURCE_SUBINVENTORY SOURCE_ORGANIZATION_ID
Value
Whse_Code L_orgn_id Whse_Name NULL 1 1 1 If Org Locator Control Code = 4 Then Assign 5 (Determined at item) Else Assign 1 NULL NULL Material_Account from Mtl_Parameters for :Organization_Id Material_Overhead_Account from Mtl_Parameters for :Organization_Id Resource_Account from Mtl_Parameters for :Organization_Id Overhead_Account from Mtl_Parameters for :Organization_Id Outside_Processing_Account from Mtl_Parameters for :Organization_Id 1 1 NULL NULL NULL
Version: 1.10
Page 59 of 67
Column
REQUISITION_APPROVAL_TYPE EXPENSE_ACCOUNT ENCUMBRANCE_ACCOUNT ATTRIBUTE_CATEGORY ATTRIBUTE1..15 PREPROCESSING_LEAD_TIME PROCESSING_LEAD_TIME POSTPROCESSING_LEAD_TIME DEMAND_CLASS PROJECT_ID TASK_ID SUBINVENTORY_USAGE NOTIFY_LIST_ID DEPRECIABLE_FLAG LOCATION_ID STATUS_ID DEFAULT_LOC_STATUS_ID LPN_CONTROLLED_FLAG DEFAULT_COST_GROUP_ID PICK_UOM_CODE CARTONIZATION_FLAG PLANNING_LEVEL DEFAULT_COUNT_TYPE_CODE SUBINVENTORY_TYPE ENABLE_BULK_PICK
Value
NULL Expense_Account from Mtl_Parameters for :Organization_Id Encumbrance_Account from Mtl_Parameters for :Organization_Id NULL NULL NULL NULL NULL NULL NULL NULL NULL NULL 2 NULL 1 1 0 Default_Cost_Group_Id from Mtl_Parameters for :Organization_Id NULL 0 2 2 (Order Quantity) 1 (Storage) N
MTL_ITEM_LOCATIONS
The data from ic_loct_mst is migrated to this table.
Column
INVENTORY_LOCATION_ID ORGANIZATION_ID DESCRIPTION DESCRIPTIVE_TEXT DISABLE_DATE PICKING_ORDER LOCATION_MAXIMUM_UNITS SUBINVENTORY_CODE LOCATION_WEIGHT_UOM_CODE MAX_WEIGHT VOLUME_UOM_CODE MAX_CUBIC_AREA SEGMENT1 SEGMENT2..20 SUMMARY_FLAG ENABLED_FLAG START_DATE_ACTIVE END_DATE_ACTIVE ATTRIBUTE_CATEGORY ATTRIBUTE1..15 PROJECT_ID TASK_ID PHYSICAL_LOCATION_ID PICK_UOM_CODE DIMENSION_UOM_CODE LENGTH WIDTH HEIGHT LOCATOR_STATUS STATUS_ID CURRENT_CUBIC_AREA
Value
Mtl_item_locations_s.nextval L_orgn_id Loct_Name NULL NULL NULL :Whse_Code NULL NULL NULL NULL :Location NULL N Y :Creation_Date NULL NULL NULL NULL NULL NULL NULL NULL NULL NULL NULL 1 NULL NULL
Version: 1.10
Page 60 of 67
Column
AVAILABLE_CUBIC_AREA CURRENT_WEIGHT AVAILABLE_WEIGHT LOCATION_CURRENT_UNITS LOCATION_AVAILABLE_UNITS SUGGESTED_CUBIC_AREA EMPTY_FLAG MIXED_ITEMS_FLAG DROPPING_ORDER LOCATION_SUGGESTED_UNITS AVAILABILITY_TYPE INVENTORY_ATP_CODE RESERVABLE_TYPE INVENTORY_ITEM_ID
Value
NULL NULL NULL NULL NULL NULL NULL NULL NULL NULL NULL 1 1 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
LEGAL_ENTITY_ID
Datatype
NUMBER
Maximum Length
15
Description
Legal Entity Identifier
Item_Id, Whse_Code are transformed to inventory_item_id and organization_id.

Column Name
INVENTORY_ITEM_ID ORGANIZATION_ID
Datatype
NUMBER NUMBER
Maximum Length
Description
Inventory Item Identifier Inventory Organization
Cost_mthd_code is transformed to cost_type_id.

Column Name
COST_TYPE_ID
Datatype
NUMBER
Maximum Length
(15)
Description
Cost Type Identifier
Calendar_code, period_code are transformed to period_id.

Column Name
PERIOD_ID
Datatype
NUMBER
Maximum Length
(15)
Description
Cost Period Identifier
Lot_ID is transformed to lot_number.

Column Name
LOT_NUMBER
Datatype
VARCHAR2
Maximum Length
(80)
Description
Lot Number
UOM is transformed to the 3 character UOM Code in Discrete.
Version: 1.10
Page 61 of 67
Column Name
XXX_um or um_YYY or um_code
Datatype
VARCHAR2
Maximum Length
(3)
Description
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.
Column Name
ACCOUNT_ID
Datatype
NUMBER
Maximum Length
(15)
Description
Code Combination Id
Cost Management Table Column Additions

CM_ACPR_CTL
Column Name
INTORDERS_PROCESSED INVOICES_PROCESSED MISCRCPT_PROCESSED
Data Type
NUMBER NUMBER NUMBER
Size
15 15 15
Column Description
CM_ADJS_DTL
Column Name
ORGANIZATION_ID INVENTORY_ITEM_ID COST_TYPE_ID PERIOD_ID ADJUST_QTY_UOM
Data Type
NUMBER NUMBER NUMBER NUMBER VARCHAR2
Size
15
Column Description
Organization Id Inventory Item Id Cost Type Id Cost Period Id 3 Char UOM Code
15 3
CM_BRDN_DTL
Column Name
BURDEN_UOM ITEM_UOM
Data Type
VARCHAR2 VARCHAR2
Size
3 3
Column Description
3 Char UOM Code 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.
Column Name
LEGAL_ENTITY_ID
Data Type
NUMBER
Size
15
Column Description
Legal Entity Id
Version: 1.10
Page 62 of 67
CM_RLUP_CTL
Column Name
FROM_ORGANIZATION_ID TO_ORGANIZATION_ID
Data Type
NUMBER NUMBER
Size
Column Description
From Organization To Organization
CM_RSRC_DTL
Column Name
USAGE_UOM
Data Type
VARCHAR2
Size
3
Column Description
3 Char UOM Code
CM_SCST_LED
Column Name
FORM_PROD_UOM ITEM_FMQTY_UOM USAGE_UOM
Data Type
VARCHAR2 VARCHAR2 VARCHAR2
Size
3 3 3
Column Description
3 Char UOM Code 3 Char UOM Code 3 Char UOM Code
CM_WHSE_SRC
Column Name
SOURCE_ORGANIZATION_ID
Data Type
NUMBER
Size
15
Column Description
Source Organization Id
GL_ALOC_EXP
Column Name
FROM_ACCOUNT_ID TO_ACCOUNT_ID
Data Type
NUMBER NUMBER
Size
Column Description
From GL Account Id To GL Account Id
GL_ALOC_INP
Column Name
ACCOUNT_ID
Data Type
NUMBER
Size
15
Column Description
Account
GL_EVNT_PLC
Column Name
ENTITY_CODE ENTITY_CLASS_CODE
Data Type
VARCHAR2 VARCHAR2
Size
30 30
Column Description
Event Entity Event Class
GL_ITEM_DTL
Version: 1.10
Page 63 of 67
Column Name
COST_LEVEL
Data Type
NUMBER
Size
5
Column Description
Cost Level Indicator
GMF_BURDEN_PRIORITIES
Column Name
ORGANIZATION_PRI
Data Type
NUMBER
Size
5
Column Description
Organization Priority
GMF_LOT_COST_ADJUSTMENTS
Column Name
LOT_NUMBER
Data Type
VARCHAR2
Size
80
Column Description
Lot Number
GMF_LOT_COST_BURDENS
Column Name
LOT_NUMBER RESOURCE_UOM ITEM_UOM
Data Type
VARCHAR2 VARCHAR2 VARCHAR2
Size
80 3 3
Column Description
Lot Number 3 Char UOM Code 3 Char UOM Code
GMF_MATERIAL_LOT_COST_TXNS
Column Name
COST_TRANS_UM TRANSACTION_ID MIGRATION_IND
Data Type
VARCHAR2 NUMBER NUMBER
Size
3 3
Column Description
3 Char UOM Code Transaction_Id from MMT Migration or Old row indicator. 1 = old row; null = new row in R12
Version: 1.10
Page 64 of 67
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
CO_CODE NUMBER_OF_OPEN_PERIODS AUTO_LINK_FLAG BASE_CURRENCY_CODE
Purpose
OPM Company Obsolete in 11i Obsolete in 11i Display Only. Derived from the Set of Books associated to the Operating Unit. Obsolete in 11i Obsolete in 11i Obsolete in 11i Obsolete in 11i Will be obsolete in R12. Will be obsolete in R12. Edit Text Mark for purge indicator Obsolete in 11i Set of Books name Company wide default for Actual Cost material component class for raw materials. Company wide default for Actual Cost material analysis code for raw materials. Stores the cost method used for inventory valuation to GL. Cost Revaluation current cost type Cost Revaluation current cost calendar Cost Revaluation current cost period Cost Revaluation previous cost type Cost Revaluation previous cost calendar Cost Revaluation previous cost period Cost Revaluation GL date for journals 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. Set of Books identifier Obsolete Obsolete WHO column WHO column WHO column WHO column WHO column Descriptive Flexfield Descriptive Flexfield
Destination Column in GMF_FISCAL_POLICIES

LEGAL_ENTITY_ID, LEGAL_ENTITY_NAME
BASE_CURRENCY_CODE In R12, this column will be derived from the legal entitys primary ledgers currency.
FRONT_CURR_IND VOUCHER_REVERSAL_DAY PRIMARY_LEDGER_CODE UPD_OPEN_BAL SEGMENT_DELIMITER TRANS_CNT TEXT_CODE DELETE_MARK DFLTS_IND SET_OF_BOOKS_NAME MTL_CMPNTCLS_ID MTL_ANALYSIS_CODE GL_COST_MTHD CREV_CURR_MTHD CREV_CURR_CALENDAR CREV_CURR_PERIOD CREV_PRIOR_MTHD CREV_PRIOR_CALENDAR CREV_PRIOR_PERIOD GL_TRANS_DATE COST_BASIS
TEXT_CODE DELETE_MARK LEDGER_NAME Name of the primary ledger in R12. MTL_CMPNTCLS_ID MTL_ANALYSIS_CODE COST_TYPE Obsolete Obsolete Obsolete Obsolete Obsolete Obsolete Obsolete Obsolete
SOB_ID OPERATING_UNIT ORG_ID CREATED_BY CREATION_DATE LAST_UPDATE_LOGIN LAST_UPDATE_DATE LAST_UPDATED_BY ATTRIBUTE1 thru ATTRIBUTE30 ATTRIBUTE_CATEGORY
LEDGER_ID Id of the primary ledger in R12
CREATED_BY CREATION_DATE LAST_UPDATE_LOGIN LAST_UPDATE_DATE LAST_UPDATED_BY ATTRIBUTE1 thru ATTRIBUTE30 ATTRIBUTE_CATEGORY
Version: 1.10
Page 65 of 67
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.
Column Name
ASSIGNMENT_ID CALENDAR_CODE LEGAL_ENTITY_ID COST_TYPE_ID CREATION_DATE CREATED_BY LAST_UPDATE_DATE LAST_UPDATED_BY LAST_UPDATE_LOGIN TEXT_CODE DELETE_MARK ATTRIBUTE1 ATTRIBUTE2 ATTRIBUTE3 ATTRIBUTE4 ATTRIBUTE5 ATTRIBUTE6 ATTRIBUTE7 ATTRIBUTE8 ATTRIBUTE9 ATTRIBUTE10 ATTRIBUTE11 ATTRIBUTE12 ATTRIBUTE13 ATTRIBUTE14 ATTRIBUTE15 ATTRIBUTE16 ATTRIBUTE17 ATTRIBUTE18 ATTRIBUTE19 ATTRIBUTE20 ATTRIBUTE21 ATTRIBUTE22 ATTRIBUTE23 ATTRIBUTE24 ATTRIBUTE25 ATTRIBUTE26 ATTRIBUTE27 ATTRIBUTE28 ATTRIBUTE29 ATTRIBUTE30
Data Type
NUMBER VARCHAR2 NUMBER NUMBER DATE NUMBER DATE NUMBER NUMBER NUMBER NUMBER VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2
Size
15 4 15
Column Description
Assignmnt Id Calendar Code Legal Entity Id Cost Type Id Standard Columns Standard Columns Standard Columns Standard Columns Standard Columns Text Code Delete Mark Indicator Standard Attribute Column Standard Attribute Column Standard Attribute Column Standard Attribute Column Standard Attribute Column Standard Attribute Column Standard Attribute Column Standard Attribute Column Standard Attribute Column Standard Attribute Column Standard Attribute Column Standard Attribute Column Standard Attribute Column Standard Attribute Column Standard Attribute Column Standard Attribute Column Standard Attribute Column Standard Attribute Column Standard Attribute Column Standard Attribute Column Standard Attribute Column Standard Attribute Column Standard Attribute Column Standard Attribute Column Standard Attribute Column Standard Attribute Column Standard Attribute Column Standard Attribute Column Standard Attribute Column Standard Attribute Column
15 15 15 10 1 240 240 240 240 240 240 240 240 240 240 240 240 240 240 240 240 240 240 240 240 240 240 240 240 240 240 240 240 240 240
Version: 1.10
Page 66 of 67
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.
Column Name
PERIOD_ID LEGAL_ENTITY_ID COST_TYPE_ID CALENDAR_CODE PERIOD_CODE PERIOD_ID PERIOD_STATUS START_DATE END_DATE CREATION_DATE CREATED_BY LAST_UPDATE_DATE LAST_UPDATED_BY LAST_UPDATE_LOGIN TEXT_CODE DELETE_MARK ATTRIBUTE1 ATTRIBUTE2 ATTRIBUTE3 ATTRIBUTE4 ATTRIBUTE5 ATTRIBUTE6 ATTRIBUTE7 ATTRIBUTE8 ATTRIBUTE9 ATTRIBUTE10 ATTRIBUTE11 ATTRIBUTE12 ATTRIBUTE13 ATTRIBUTE14 ATTRIBUTE15 ATTRIBUTE16 ATTRIBUTE17 ATTRIBUTE18 ATTRIBUTE19 ATTRIBUTE20 ATTRIBUTE21 ATTRIBUTE22 ATTRIBUTE23 ATTRIBUTE24 ATTRIBUTE25 ATTRIBUTE26 ATTRIBUTE27 ATTRIBUTE28 ATTRIBUTE29 ATTRIBUTE30
Data Type
NUMBER NUMBER NUMBER VARCHAR2 VARCHAR2 NUMBER VARCHAR2 DATE DATE DATE NUMBER DATE NUMBER NUMBER NUMBER NUMBER VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2
Size
15 15 4 4 15 1
Column Description
Period Id Legal Entity Id Cost Type Id Calendar Code Period Code Period Unique Identifier Period Status Period Start Date Period End Date Standard Columns Standard Columns Standard Columns Standard Columns Standard Columns Text Code Delete Mark Indicator Standard Attribute Column Standard Attribute Column Standard Attribute Column Standard Attribute Column Standard Attribute Column Standard Attribute Column Standard Attribute Column Standard Attribute Column Standard Attribute Column Standard Attribute Column Standard Attribute Column Standard Attribute Column Standard Attribute Column Standard Attribute Column Standard Attribute Column Standard Attribute Column Standard Attribute Column Standard Attribute Column Standard Attribute Column Standard Attribute Column Standard Attribute Column Standard Attribute Column Standard Attribute Column Standard Attribute Column Standard Attribute Column Standard Attribute Column Standard Attribute Column Standard Attribute Column Standard Attribute Column Standard Attribute Column
15 15 15 10 1 240 240 240 240 240 240 240 240 240 240 240 240 240 240 240 240 240 240 240 240 240 240 240 240 240 240 240 240 240 240
Version: 1.10
Page 67 of 67

Oracle OPM 11i to 12 Migration Guide and Reference

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Oracle OPM 11i to 12 Migration Guide and Reference

Uploaded by

Copyright:

Available Formats

ORACLE PROCESS MANUFACTURING RELEASE 11I TO 12/12.

1 MIGRATION Migration Messages and Technical Reference

Date Published: 01/05/2010

Date Published: 01/05/2010

Pre-Migration Validation Messages

GMD: Quality Management

Date Published: 01/05/2010

GMI: Process Inventory

Date Published: 01/05/2010

Migration Name Pre-Migration Validation

Date Published: 01/05/2010

GR: Process Regulatory

Date Published: 01/05/2010

GMF: Process Financials

Date Published: 01/05/2010

Date Published: 01/05/2010

Migration Name Migrate Action Codes

Attachment for this form needs to be defined.

5. Click Entities, and add the following:

Date Published: 01/05/2010

Migration Name Migrate Items

Comments Attachment for this form needs to be defined.

5. Click Entities, and add the following:

Date Published: 01/05/2010

Migration Name Migrate Lots

Comments Attachment for this form needs to be defined.

5. Click Entities, and add the following:

Date Published: 01/05/2010

Migration Name Migrade Grades

Comments Attachment for this form needs to be defined.

5. Click Entities, and add the following:

Date Published: 01/05/2010

Migration Name Migrate

Comments Attachment for this form needs to be defined.

Entity Name: Reason Codes Prompt: Reason Codes Application: Inventory

5. Click Entities, and add the following:

Date Published: 01/05/2010

Migration Name Migrate

Comments Attachment for this form needs to be defined.

5. Click Entities, and add the following:

Date Published: 01/05/2010

Migration Name Migrate Organizations

<ERROR> Message Type: Error

Invalid OPM Item id <ITEM_ID> Message Type: Error

Unable to get <NAME> for value <VALUE> Message Type: Error

Migration Process failed due to DB_ERROR: <DB_ERROR> Message Type: Error

Validate Item Controls

Date Published: 01/05/2010

Migration Name Validate Flexfield Definitions

Migration Process failed due to DB_ERROR: <DB_ERROR> Message Type: Error

Migrate Obsolete Columns

Invalid parameters for obsolete column migration

Migrate Obsolete Columns

Invalid obsolete column <OBSOLETE_COLUMN_NAME> specified Message Type: Error

Migrate Obsolete Columns

Obsolete column already migrated to different flexfield column

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

Date Published: 01/05/2010