05/05/2020 Document 1063689.

1
Copyright (c) 2020, Oracle. All rights reserved. Oracle Confidential.

Transactions Interface MTL_TRANSACTIONS_INTERFACE MTI Error Messages, Meanings, and

Solutions (Doc ID 1063689.1)

In this Document

Purpose
This guide has been created to give a clear explanation of the common errors found in Transactions Interface
MTL_TRANSACTIONS_INTERFACE (MTI) and how to resolve these errors.
Troubleshooting Steps
Script to pick-up errors
Script to reset locked MTI transactions
Table of common error messages and reasons errors occur
Possible Solutions
1) An error occurred while relieving Reservations
2) CSTPACIT.COST_DET_VALIDATE: An invalid cost change is associated with the item being transacted
3) Error. CSTPACIT.cost_det_move
4) For this transaction row either the lot records are missing or the lot quantity does not match the transaction
quantity
5) For this transaction row the serial records are missing
6) Invalid Serial Number
7) Invalid Item
8) Code:Item control mismatch
9) Negative balances not allowed
10) No open period found for date entered
11) Oracle error
12) Organization ID is either blank or invalid
13) Status not applicable for this subinventory
14) Transaction date cannot be a future date
15) Transaction quantity has an incorrect sign for the given transaction
16) The expenditure organization information is invalid
17) The item revision is not valid
18) The value of expiration date is required. Need to add EXPIRATION_DATE to the lots
19) Freight code is not valid. Please re-enter
Transaction Codes
SOURCE_TYPE_ID
TRANSACTION_TYPE_ID
TRANSACTION_ACTION_ID
References

APPLIES TO:

Oracle Inventory Management - Version 11.5.10 and later

Information in this document applies to any platform.
This document includes all versions of Oracle EBS 11i and R12 and later

PURPOSE

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=o02b35yub_4&id=1063689.1 1/10
05/05/2020 Document 1063689.1

This guide has been created to give a clear explanation of the common errors found in Transactions
Interface MTL_TRANSACTIONS_INTERFACE (MTI) and how to resolve these errors.

This is a working document and as new solutions or issues come to light, they will be added to the document.

TROUBLESHOOTING STEPS

Script to pick-up errors

The following script can be used to report all the errors found grouped by the TRANSACTION_TYPE_ID, ERROR_CODE and
ERROR_EXPLANATION.

SELECT TRANSACTION_TYPE_ID,
TRANSACTION_ACTION_ID,
ERROR_CODE,
ERROR_EXPLANATION,
COUNT(*)
FROM MTL_TRANSACTIONS_INTERFACE
GROUP BY TRANSACTION_TYPE_ID,
TRANSACTION_ACTION_ID,
ERROR_CODE,
ERROR_EXPLANATION
;

MTL_TRANSACTIONS_INTERFACE (MTI) transaction error messages.

Script to reset locked MTI transactions

Sometimes issues happen that stop MTI transactions from processing. The following sql statement can be safely used to
reset transactions to be picked up by the transaction manager for reprocessing. Be sure to issue a commit after running:

UPDATE MTL_TRANSACTIONS_INTERFACE
SET PROCESS_FLAG = 1,
LOCK_FLAG = NULL ,
TRANSACTION_MODE = 3 ,
ERROR_CODE = NULL ,
ERROR_EXPLANATION = NULL
WHERE TRANSACTION_INTERFACE_ID =&TRANSACTION_INTERFACE_ID
;

If the script is run, the interface is reprocessed, and transactions re-error, there is most likely a problem with the
transactions. Review the common errors below.

Table of common error messages and reasons errors occur

Here are some the standard error messages and the reason why the error may have occurred.

Error Explanation Reason

1. An error occurred while relieving reservations. There is no available quantity for relieving reservations.

2. CSTPACIT.COST_DET_VALIDATE: An invalid cost New average cost is zero or negative for invalid cost
change is associated with the item being transacted.

3. Error. CSTPACIT.cost_det_move A FIFO Layer Cost Update is being interfaced

4. For this transaction row either the lot records are Make sure that for lot controlled items, lot numbers are
missing or the lot quantity does not match the transaction populated in the mtl_transaction_lots_interface with the
quantity correct quantity and then reprocess.

5. For this transaction row the serial records are missing Make sure that for serial controlled items, serial numbers
are populated in the mtl_serial_numbers_interface with the
correct quantity and then reprocess.

6. Invalid Serial Number Lot and/or Serial Number quantity does not match
transaction quantity

7. Invalid Item Inventory item ID is invalid or does not have the flags
enabled correctly to be processed by material processor

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=o02b35yub_4&id=1063689.1 2/10
05/05/2020 Document 1063689.1

8. Item Control Mismatch The defined Lot or Serial or Revision control combination
for the item under source organization and destination
organization is not supported by Inventory direct inter-org
transfer transaction

9. Negative balances not allowed Ensure that there is enough onhand quantity for the items
and SKU and then reprocess the transactions.

10. No open period found for date entered Period is not open for the transaction date

11. Oracle error Database error. Can be due to duplicate WIP transactions

12. Organization ID is either blank or invalid. The Organization ID field is either blank or invalid.

13. Status not applicable for this Subinventory Subinventory is assigned a status which does not allow the
transaction

14. Transaction date cannot be a future date The date for this transaction type cannot be in the future

15. Transaction quantity has an incorrect sign for the given The transaction has an incorrect quantity sign eg. a receipt
transaction action with a negative quantity. Correct the quantity sign and
then re-process the transaction.

16. The expenditure organization information is invalid Ensure that the PA_EXPENDITURE_ORG_ID populated is
the correct org_id and then re-process the transaction.

17. The item revision is not valid. Item revision is invalid or revision qty control is incorrect

18. The value of expiration date is required. Expiration date is missing on the Lots

Possible Solutions

*** Please Note these are only possible solutions and the issue needs to be fully investigated. As standard practice
ALWAYS test on a copy of Production following a suitable backup and fully check results before applying to Production.
***

1) An error occurred while relieving Reservations

Use the steps in document 'Stuck Transaction Interface Sales Order Issues: An Error Occurred While Relieving
Reservations (INV_RSV_RLF_FAILED) (Doc ID 280400.1)' to diagnose the issue.

Typical steps to diagnose:

Not enough available stock to relieve reservation. This issue can be worked around in Release 12 by setting the profiles
'INV_OVERRIDE_RSV_FOR_BACKFLUSH' & "INV:Override Reservation for Transactions" to "Yes", see Note: 1083006.1.
The issue can be due to the following:

A. Hard reservations that have a date that is fixed in the future, these reservations prevent other lines to be interfaced as
they take the available stock.

Run onhand.sql from Note 330284.1 - check reservations section

Remove unnecessary reservation(s)

B. Not enough quantity onhand to process the sales order issues.

Run onhand.sql from Note 330284.1 - check onhand section

If the onhand should exist create more onhand by doing a cycle count or by creating a miscellaneous receipt

C. Enough quantity was available but another order or job used the quantity because reservations was not enabled on the
item or subinventory.

Run onhand.sql from Note 330284.1 - check reservations flag in Subinventory controls and item attributes

Reset Subinventory / item attribute through the standard forms

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=o02b35yub_4&id=1063689.1 3/10
05/05/2020 Document 1063689.1

D. Enough quantity is onhand but not enough is reservable. An old reservation remains that should have been removed.

Run onhand.sql from Note 330284.1 - check reservations section for unwanted reservations

Please use note FAQ: Inventory Standard Datafixes (Doc ID 568012.1), Standard Datafix #16 for the i2471362.sql,
INVCLRMO.sql sql's to clear any 'orphan' reservations. You can also get the scripts from main Doc ID 1322105.1.

E. The transaction in error is a duplicate transaction that was already processed.

Please use note FAQ: Inventory Standard Datafixes (Doc ID 568012.1) Standard Datafix #17 for the
Duplicates_for_mmt_mti_mmtt.sql to help clear any possible duplicate transactions. You can also get the Standard Datafix
from Doc ID 1472074.1.

2) CSTPACIT.COST_DET_VALIDATE: An invalid cost change is associated with the item being transacted

An invalid cost change is associated with the item being transacted. The MTI.new_average_cost field is null or zero. Need
to update the row with a valid new average cost:

Issue Verification:

SELECT TRANSACTION_INTERFACE_ID,
NEW_AVERAGE_COST
FROM MTL_TRANSACTIONS_INTERFACE
WHERE ERROR_EXPLANATION LIKE 'CSTPACIT.COST_DET_VALIDATE%';

3) Error. CSTPACIT.cost_det_move

A FIFO Layer Cost Update is being interfaced. Layer cost updates through the Interface is not recommended and not
currently supported. Remove the transaction and do the layer cost updates from Applications.

4) For this transaction row either the lot records are missing or the lot quantity does not match the transaction
quantity

Lot numbers are missing for lot controlled items, or the lot quantity populated in the
MTL_TRANSACTION_LOTS_INTERFACE does not match the TRANSACTION_QUANTITY in the associated MTI row. Check
the correct number and quantity of lots are available in MTL_TRANSACTION_LOTS_INTERFACE:

Issue Verification:

SELECT *
FROM MTL_TRANSACTION_LOTS_INTERFACE
WHERE TRANSACTION_INTERFACE_ID = &TRANS_ID;

5) For this transaction row the serial records are missing

Serial numbers are missing for serial controlled items in the MTL_SERIAL_NUMBERS_INTERFACE so the number of serial
numbers does not match with the TRANSACTION_QUANTITY in the associated MTI row.
Check the correct number of serial numbers exist in MTL_SERIAL_NUMBERS_INTERFACE.

Issue Verification:

SELECT *
FROM MTL_SERIAL_NUMBERS_INTERFACE
WHERE TRANSACTION_INTERFACE_ID = &TRANS_ID;

Where serial numbers are known and were issued Add missing serial rows in MTL_SERIAL_NUMBERS_INTERFACE:

INSERT INTO MTL_SERIAL_NUMBERS_INTERFACE

(
TRANSACTION_INTERFACE_ID,
LAST_UPDATE_DATE,
LAST_UPDATED_BY,
CREATION_DATE,

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=o02b35yub_4&id=1063689.1 4/10
05/05/2020 Document 1063689.1
CREATED_BY,
FM_SERIAL_NUMBER,
TO_SERIAL_NUMBER
)
SELECT TRANSACTION_INTERFACE_ID,
LAST_UPDATE_DATE,
LAST_UPDATED_BY,
CREATION_DATE,
5328,
'&SERIAL_NUMBER',
'&SERIAL_NUMBER'
FROM MTL_TRANSACTIONS_INTERFACE
WHERE TRANSACTION_INTERFACE_ID = &TRANS_ID;
COMMIT;

6) Invalid Serial Number

Lot and/or Serial Number quantity does not match transaction quantity. See 4 and 5. Also check if serial number exists and
whether the subinventory is correct for the serial number:

Issue Verification:

SELECT *
FROM MTL_SERIAL_NUMBERS_INTERFACE
WHERE TRANSACTION_INTERFACE_ID = &TRANS_ID;

Solution:
Add missing serial number row / correct subinventory

7) Invalid Item

ITEM_SEGMENT1 is being populated instead of the inventory_item_id OR the inventory_item_id is invalid or for a non
inventory item.

Use the INVENTORY_ITEM_ID in the MTL_TRANSACTIONS_INTERFACE instead of ITEM_SEGMENT1.

Ensure item_id is populated and item is enabled and is an inventory asset item.

SELECT MTI.ORGANIZATION_ID MTI_ORG_ID,

MTI.INVENTORY_ITEM_ID MTI_ITEM_ID,
MTI.ITEM_SEGMENT1 MTI_SEGMENT1,
MSIB.ENABLED_FLAG,
MSIB.INVENTORY_ASSET_FLAG
FROM MTL_SYSTEM_ITEMS_B MSIB,
MTL_TRANSACTIONS_INTERFACE MTI
WHERE MSIB.ORGANIZATION_ID = MTI.ORGANIZATION_ID
AND (MSIB.INVENTORY_ITEM_ID = MTI.INVENTORY_ITEM_ID
OR MSIB.SEGMENT1 = MTI.ITEM_SEGMENT1)
AND UPPER(MTI.ERROR_CODE) LIKE 'INVALID ITEM%';

8) Code:Item control mismatch

The defined Lot or Serial or Revision control combination for the item under source organization and destination
organization is not allowed - for example trying to move Lot controlled inventory into a non-lot controlled organization.

Solution:
(1) Note down the quantity in the destination organization and issue out all the on-hand for the item so it is zero.
(2) Change the item control of the item in the destination organization for example as not lot controlled.
(3) Resubmit the transaction. The interface record should process and the on-hand should be created in the destination
organization for example without lot.
(4) Do a Miscellaneous Issue of the transferred quantity in the destination org so the on-hand becomes zero again.
(5) Change the item control back in the destination org for example to LOT controlled again.
(6) Receive the quantity back which was issued in step(1).
(7) Receive the quantity back which was issued in step(4)

9) Negative balances not allowed

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=o02b35yub_4&id=1063689.1 5/10
05/05/2020 Document 1063689.1

You can follow the steps in document 'Resolve Inventory Error: Negative balances not allowed (Doc ID 1916111.1)' in
order to diagnose the issue.

Typical steps to review:

Ensure that there is enough onhand quantity for the respective items and SKU and then reprocess the transactions:

A. Not enough quantity is onhand

Issue Verification:
Run onhand.sql from Note 330284.1 - onhand section

Solution:
Create more onhand by doing a cycle count or by creating a miscellaneous receipt

B. Enough onhand exists but available quantity has been reduced by reservations:

Issue Verification:
Check onhand.sql - reservations section.

Solution:
Please use note FAQ: Inventory Standard Datafixes (Doc ID 568012.1), Standard Datafix #16 for the i2471362.sql,
INVCLRMO.sql sql's to clear any 'orphan' reservations. You can also get the scripts from main Doc ID 1322105.1.

C. Can be due to duplicate transactions

Please use note FAQ: Inventory Standard Datafixes (Doc ID 568012.1) Standard Datafix #17 for the
Duplicates_for_mmt_mti_mmtt.sql to help clear any possible duplicate transactions. You can also get the Standard Datafix
from Doc ID 1472074.1.

D. Issue occurs with -- transaction_type_id 86 Cost Group Transfer:

Possibly due to missing cost_group_id. The cost group id needs to be stamped in the MTL_TRANSACTIONS_INTERFACE
record along with the Xfer Cost group id.

10) No open period found for date entered

Open the accounting period for the transaction date in the Accounting Periods form.

11) Oracle error

See 'Error Code=Oracle error : Stuck Inventory Material Transactions Open Interface (MTI) or Failing Interface Trip Stop
(ITS) Request (Doc ID 1601941.1)' for a Standard Datafix for the error.

Typical steps to diagnose:

Normally down to a system or database issue. This can be due to database locks or duplicate WIP transactions.

Issue verification: Check for other locks, check the version of INVLOCKB.pls is latest

Check for duplicate transactions related to WIP Component Issues:

a.
SELECT COUNT(*)
FROM MTL_MATERIAL_TRANSACTIONS B, MTL_TRANSACTIONS_INTERFACE A
WHERE A.TRANSACTION_SOURCE_ID = B.TRANSACTION_SOURCE_ID
AND A.INVENTORY_ITEM_ID = B.INVENTORY_ITEM_ID
AND B.TRANSACTION_TYPE_ID = A.TRANSACTION_TYPE_ID
AND B.TRANSACTION_SOURCE_TYPE_ID =5;

b.
SELECT COUNT(*)
FROM MTL_MATERIAL_TRANSACTIONS_TEMP B, MTL_TRANSACTIONS_INTERFACE A
WHERE A.TRANSACTION_SOURCE_ID = B.TRANSACTION_SOURCE_ID
AND A.INVENTORY_ITEM_ID = B.INVENTORY_ITEM_ID
AND B.TRANSACTION_TYPE_ID = A.TRANSACTION_TYPE_ID

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=o02b35yub_4&id=1063689.1 6/10
05/05/2020 Document 1063689.1
AND B.TRANSACTION_SOURCE_TYPE_ID = 5;

c.
SELECT COUNT(*)
FROM MTL_MATERIAL_TRANSACTIONS B, MTL_MATERIAL_TRANSACTIONS_TEMP A
WHERE A.TRANSACTION_SOURCE_ID = B.TRANSACTION_SOURCE_ID
AND A.INVENTORY_ITEM_ID = B.INVENTORY_ITEM_ID
AND B.TRANSACTION_TYPE_ID = A.TRANSACTION_TYPE_ID
AND B.TRANSACTION_SOURCE_TYPE_ID = 5;

Solution: Kill locked process, load latest file version of INVLOCKB.pls.

If duplicate WIP transactions exist, please use note FAQ: Inventory Standard Datafixes (Doc ID 568012.1)
, section 'C.
Other Datafix Related Notes' for the link to Doc ID 1073279.1. You can also get the solution by going straight to Doc
ID 1073279.1.

12) Organization ID is either blank or invalid

The ORGANIZATION_ID being passed is invalid or null

Issue verification:

SELECT MTI.TRANSACTION_INTERFACE_ID,
MTI.ORGANIZATION_ID
FROM MTL_TRANSACTIONS_INTERFACE MTI
WHERE NOT EXISTS (SELECT * FROM MTL_PARAMETERS MP
WHERE MTI.ORGANIZATION_ID = MP.ORGANIZATION_ID);

13) Status not applicable for this subinventory

The subinventory is assigned a status which does not allow the transactions.

A. Run the following to see what subinventories are affected:

SELECT DISTINCT(SUBINVENTORY_CODE)
FROM MTL_TRANSACTIONS_INTERFACE
WHERE ERROR_EXPLANATION LIKE 'STATUS NOT APPLICABLE FOR THIS SUBINVENTORY%';

B. If on R12 ensure Patch 6905385:R12.WSH.A containing WSHDEACB.pls 120.42.12000000.9 has been loaded

Load Patch 6905385:R12.WSH.A or later version of WSHDEACB.pls

C. Check subinventory status:

SELECT STATUS_ID
FROM MTL_SECONDARY_INVENTORIES
WHERE ORGANIZATION_ID = &ORG_ID
AND SECONDARY_INVENTORY_NAME = '&SUBINV_NAME';

SELECT IS_ALLOWED
FROM MTL_STATUS_TRANSACTION_CONTROL
WHERE STATUS_ID = (SELECT STATUS_ID FROM MTL_SECONDARY_INVENTORIES
WHERE ORGANIZATION_ID = &ORG_ID
AND SECONDARY_INVENTORY_NAME = '&SUBINV_NAME')
AND TRANSACTION_TYPE_ID = &TRANS_TYPE_ID;

Set status for transaction to allowed

14) Transaction date cannot be a future date

Update TRANSACTION_DATE to current date:

UPDATE MTL_TRANSACTIONS_INTERFACE
SET TRANSACTION_DATE = &DATE

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=o02b35yub_4&id=1063689.1 7/10
05/05/2020 Document 1063689.1
WHERE TRANSACTION_INTERFACE_ID = &TRANS_ID
AND ERROR_EXPLANATION LIKE 'TRANSACTION DATE CANNOT BE A FUTURE DATE%';

15) Transaction quantity has an incorrect sign for the given transaction

The quantity is showing the wrong sign for the transaction type, for example a receipt transaction, but the quantity sign is
-ve:

UPDATE MTL_TRANSACTIONS_INTERFACE
SET TRANSACTION_QUANTITY = TRANSACTION_QUANTITY * -1 -- , PRIMARY_QUANTITY = PRIMARY_QUANTITY * -1
-- REMOVE HYPHENS IF PRIMARY QTY ALSO NEEDS TO BE CHANGED
WHERE TRANSACTION_INTERFACE_ID = &TEMP_ID;

16) The expenditure organization information is invalid

Ensure that the PA_EXPENDITURE_ORG_ID is populated:

SELECT PA_EXPENDITURE_ORG_ID FROM MTL_TRANSACTIONS_INTERFACE

WHERE TRANSACTION_INTERFACE_ID = &TEMP_ID;

17) The item revision is not valid

The Item revision is invalid or REVISION_QTY_CONTROL_CODE is null in MTL_SYSTEM_ITEMS_B. This field should always
be populated, NULL is illegal.

A. Check the Item revision field to see if it is a valid revision:

SELECT *
FROM MTL_TRANSACTIONS_INTERFACE MTI
WHERE NOT EXISTS (SELECT 'X' FROM MTL_ITEM_REVISIONS MIV
WHERE MTI.ORGANIZATION_ID = MIV.ORGANIZATION_ID
AND MTI.INVENTORY_ITEM_ID = MIV.INVENTORY_ITEM_ID
AND MTI.REVISION = MIV.REVISION)
AND MTI.REVISION IS NOT NULL;

B. Check if revision quantity control code is set correctly:

SELECT MSIB.ORGANIZATION_ID, MSIB.INVENTORY_ITEM_ID, DECODE(REVISION_QTY_CONTROL_CODE,1,'1-N',2,'2-

Y')REV_CONT
FROM MTL_SYSTEM_ITEMS_B MSIB, MTL_TRANSACTIONS_INTERFACE MTI
WHERE MSIB.ORGANIZATION_ID = MTI. ORGANIZATION_ID
AND MSIB.INVENTORY_ITEM_ID = MTI.INVENTORY_ITEM_ID
AND UPPER(MTI.ERROR_CODE) LIKE 'INVALID ITEM REVISION%';

18) The value of expiration date is required. Need to add EXPIRATION_DATE to the lots

SELECT MTLI.TRANSACTION_INTERFACE_ID, MTLI.LOT_NUMBER, MTLI.LOT_EXPIRATION_DATE

FROM MTL_TRANSACTION_LOTS_INTERFACE MTLI, MTL_TRANSACTIONS_INTERFACE MTI
WHERE MTI.TRANSACTION_INTERFACE_ID = MTLI.TRANSACTION_INTERFACE_ID
AND UPPER(MTI.ERROR_CODE) LIKE 'THE VALUE OF EXPIRATION DATE IS REQUIRED%';

19) Freight code is not valid. Please re-enter

When attempting to submit the interface trip stop program, the following error occurred in MTI table.

ERROR
-----------------------
Error Code: Invalid freight code
Error Explanation: Freight code is not valid. Please re-enter

See Doc ID 1624074.1 for the full details and solution.

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=o02b35yub_4&id=1063689.1 8/10
05/05/2020 Document 1063689.1

Transaction Codes

SOURCE_TYPE_ID

1 Purchase order
2 Sales order
3 Account
4 Move order
5 Job or Schedule
6 Account alias
7 Internal requisition
8 Internal order
9 Cycle Count
10 Physical Inventory
11 Standard cost update
12 RMA
13 Inventory
14 Periodic Cost Update
15 Layer Cost Update
16 Project Contract
17 External Requisition

TRANSACTION_TYPE_ID

Transaction Types can be selected from MTL_TRANSACTION_TYPES using the TRANSACTION_TYPE_ID.

Transaction Types
1 Account issue 37 RMA Return 67 Project Transfer

2 Subinventory Transfer 38 WIP Neg Comp Issue 68 Project Payback

3 Direct Org Transfer 40 Account Receipt 70 Shipment Rcpt Adjust

4 Cycle Count Adjust 41 Account alias receipt 71 PO Rcpt Adjust

5 Cycle Count Transfer 42 Miscellaneous Receipt 72 Int Req Rcpt Adjust

8 Physical Inv Adjust 43 WIP Component Return 73 Planning Transfer

9 Physical Inv Transfer 44 WIP Assy Completion 74 Transfer to Regular

12 Intransit Receipt 48 WIP Neg Comp Return 75 Transfer to Consigned

15 RMA Receipt 50 Internal Order Xfer 77 Project Contract Issue

17 WIP Assembly Return 51 Backflush Transfer 82 Inventory Lot Split

18 PO Receipt 52 Sales Order Pick 83 Inventory Lot Merge

21 Intransit Shipment 53 Internal Order Pick 84 Inventory Lot Translate

24 Standard cost update 54 Int Order Direct Ship 86 Cost Group Transfer

25 WIP cost update 55 WIP Lot Split 87 Container Pack

26 Periodic Cost Update 56 WIP Lot Merge 88 Container Unpack

28 Layer Cost Update 57 WIP Lot Bonus 89 Container Split

31 Account alias issue 58 WIP Lot Quantity Update 90 WIP Assembly Scrap

32 Miscellaneous issue 61 Int Req Intr Rcpt 91 WIP return from scrap

33 Sales order issue 62 Int Order Intr Ship 92 WIP estimated scrap

34 Internal order issue 63 Move Order Issue 93 Field Service Usage

35 WIP component issue 64 Move Order Transfer

36 Return to Vendor 66 Project Borrow

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=o02b35yub_4&id=1063689.1 9/10
05/05/2020 Document 1063689.1

TRANSACTION_ACTION_ID

1 Issue from stores

2 Subinventory transfer
3 Direct org transfer
4 Cycle count adjustment
8 Inventory adjustment
12 Intransit receipt
21 Intransit shipment
24 Cost update
27 Receipt into stores
28 Staging transfer
29 Delivery adjustments
30 WIP scrap transaction
31 Assembly completion
32 Assembly return

REFERENCES

NOTE:1322105.1 - Inventory Reservations Not Relieved for Closed or Canceled Sales Orders and Some are Orphaned:
Clean up scripts for Releases 11i and 12
NOTE:330284.1 - How To Check Onhand / Serial Number Setup?
NOTE:1070343.1 - Pending Transactions MTL_MATERIAL_TRANSACTIONS_TEMP MMTT Error Messages, Meanings and
Solutions
NOTE:568012.1 - FAQ: Inventory Standard Datafixes
NOTE:1499475.1 - EBS Inventory Transactions Analyzer
NOTE:1472074.1 - Inventory Standard Datafix Instruction #17: HowTo Find and Fix Duplicate Sales Order Transactions In
MTI, MMTT and MMT
NOTE:1073279.1 - Duplicate Pending (MMTT) WIP : How To Verify If Pending WIP Completion And Issue Transactions In
MMTT Are Duplicates Or Not (Before Resubmitting Or Deleting)
NOTE:280400.1 - Stuck Transaction Interface Sales Order Issues: An Error Occurred While Relieving Reservations
(INV_RSV_RLF_FAILED)
NOTE:1916111.1 - Resolve Inventory Error: Negative Balances Not Allowed
NOTE:1601941.1 - Error Code=Oracle error : Stuck Inventory Material Transactions Open Interface (MTI) or Failing
Interface Trip Stop (ITS) Request
NOTE:1624074.1 - Internal Order Getting Stuck In Transaction Interface Table With Invalid Freight Code Error
Didn't find what you are looking for?

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=o02b35yub_4&id=1063689.1 10/10