Professional Documents
Culture Documents
1
Copyright (c) 2023, Oracle. All rights reserved. Oracle Confidential.
In this Document
Purpose
Questions and Answers
Unprocessed Transactions / Closing INV Accounting Period FAQ
What is the MTL_TRANSACTIONS_INTERFACE table used for?
What is the MTL_MATERIAL_TRANSACTIONS_TEMP table used for?
What type of issues will you see with the MTL__TRANSACTIONS_INTERFACE and
MTL_MATERIAL_TRANSACTIONS_TEMP tables?
What type of issues will you see with the MTL_MATERIAL_TRANSACTIONS table?
What type of issues will you see with the MTL_TRANSACTION_ACCOUNTS table?
Where do you find Pending/Errored Inventory Transactions?
Where do you find Pending/Errored WIP Move and WIP Resource Transactions?
What are the major tables involved in Material Movement for Inventory and WIP Material, Move, and Resource
Transactions?
How do you resolve Pending Material Transactions?
How do you resolve Pending WIP Cost Transactions?
When attempting to load legacy data into the MTL_TRANSACTIONS_INTERFACE table, into what column is the PO
number input?
Why is the distribution account ID required in MTL_TRANSACTIONS_INTERFACE?
References
APPLIES TO:
PURPOSE
This document provides a basic understanding of the Oracle Inventory Transactions and Cost processing procedure and
explains the flow of transactions from the MTL_TRANSACTIONS_INTERFACE to the GL_INTERFACE.
https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=i49oyav3h_45&id=110424.1 1/7
04/01/2023, 12:56 Document 110424.1
The aim of this document is to help and assist in the resolution of transaction Interface related issues.
This is the Interface between non-Inventory applications and the Inventory Transactions module.
In other words any other module other than Inventory that wants to update Inventory has to come through this table.
Modules such as WIP (Work In Progress) and OE (Order Entry) first pass their records to the
MTL_TRANSACTIONS_INTERFACE (MTI) for validation.
The Transactions Manager (INCTCM) reads records from the MTI table, validates them and moves the successful
transactions into the MTL_MATERIAL_TRANSACTIONS_TEMP table, and submits Transaction workers (sub-processes -
INCTCW) which then process these records through inventory. This process consists of data derivation, validation, and the
transfer of records from MTL_TRANSCTIONS_INTERFACE, MTL_TRANSACTIONS_LOTS_INTERFACE and
MTL_SERIAL_NUMBERS_INTERFACE into their associated TEMP (temporary) tables from where the transactions processor
processes them.
Both the Lots and Serial number tables above are used when items being updated are under 'Lot' or 'Serial' number
control. For example :- In the case of a Sales Order, if the item is being shipped to a client and the lot and serial number
are being used, these tables need to be updated to show that the lot or serial number is no longer available in the
Inventory stock.
It is important to note that in general the processors will not move the transactions from this table if the following fields
are not set as follows.
LOCK_FLAG = 2
PROCESS_FLAG = 1
transaction_mode = 3
The transactions are passed to the MTL_MATERIAL_TRANSACTONS_TEMP table after initial validation by the Transactions
Manager (INCTCM) from the MTL_TRANSACTIONS_INTERFACE. A job id is attached and a Transactions Worker (INCTCW)
is submitted by the INCTCM process to get the records processed and moved to the MTL_MATERIAL_TRANSACTONS table.
This table is also used by the Inventory and Purchasing modules which write transactions directly into this table after
validation.
Inventory Module Forms like the Miscellaneous transactions form write directly into this table. The transactions which are
created through these form are via on-line processing. It is from this table that the inventory quantities finally get updated
and serial/lot numbers get updated.
What type of issues will you see with the MTL__TRANSACTIONS_INTERFACE and
MTL_MATERIAL_TRANSACTIONS_TEMP tables?
The following is a list of errors that you may see in the error_code, error_explanation columns in the above tables:
https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=i49oyav3h_45&id=110424.1 2/7
04/01/2023, 12:56 Document 110424.1
Check the subinventory against the available MTL_SECONDARY_INVENTORIES on the system for the given
ORGANIZATION_ID against this transaction.
If the subinventory exists, check the TRANSACTION_TYPE_ID, for example:
If it is a Purchase Order then you need to check the MTL_SUPPLY to ensure that the supply exists for this transaction.
Check under Inventory Responsibility -> set-up -> flexfields -> key -> segments 'stock locators'. Ensure each segment has
been enabled.
Ensure that the segments point to a valid row in the GL_CODE_COMBINATIONS table.
This message will be given if there is not enough on hand inventory to satisfy all the transactions within a batch.
Therefore, ensure that the transaction quantity is enough to satisfy the sum of all the transaction quantities for a particular
batch.
APP-05064 Quantity must be less than or equal to Available to transact for that item at its specific control level. (For
Example: subinventory,locator,lot,serial)
1. If you specify a subinventory/locator while entering the order, the system will attempt to ship the items from that
subinventory/locator. If there is not enough available stock to reserve/transact in that particular subinventory/locator the
program will error out with the above error. However, if there are no subinventories/locators specified while entering the
order, the system will pick the stock from where it finds available stock in that Organization.
3. The records would have errored out due to some other row in the batch not having enough stock, so the entire batch
would fail. Find the row that has the error explanation populated. Resubmit all the other rows except the one which has
error explanation , if the same error occurs for other rows, do the same process once again excluding that row.
4. Please note that Available Quantity = On Hand Quantity - Reservations (Soft and Hard Reservations).
What type of issues will you see with the MTL_MATERIAL_TRANSACTIONS table?
The Cost Manager is a concurrent job that runs in the background. (CMCTCM)
When the COSTED_FLAG = 'N' (Not Processed) - this means the record is awaiting costing.
If the COSTED_FLAG = NULL then the transaction has already been processed.
If the COSTED_FLAG = 'E' then the transaction has errored during costing and the ERROR_CODE and
ERROR_EXPLANATION fields need to be checked.
What type of issues will you see with the MTL_TRANSACTION_ACCOUNTS table?
The details of the transactions are written into this table as Debits and Credits. This data is picked up when running the
General Ledger Transfer routine:
Navigation Path -> Inventory Responsibility -> Accounting Close Cycle -> General Ledger Transfers)
This concurrent request takes the transactions with a GL_BATCH_ID of -1 and passes them to the
GL_INTERFACE for processing and the batch is given it's proper batch number.
When the transfer to GL is completed, a column called GROUP_ID gets populated in the GL_INTERFACE table with a
gl_batch_id. The GL BATCH identifier is used in the GROUP ID field,
so only the batch which is in error is prevented from being imported and posted. Also, adding a GROUP ID allows for a
more definitive level of control not only across locations but within a location.
1. Navigate to Inventory Responsibility -> Accounting Close Cycle -> Inventory Accounting Periods
-- Select Pending Button related to an OPEN period.
-- In the top region -- Resolution Required
-- If it shows pending records, These must be fixed prior to the system allowing the period to be closed.
-- The form only shows a count of pending records against the period.
https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=i49oyav3h_45&id=110424.1 4/7
04/01/2023, 12:56 Document 110424.1
Where do you find Pending/Errored WIP Move and WIP Resource Transactions?
1. Navigate Work in Process Responsibility -> Move Transactions -> Pending Move Transactions
-- This form queries the WIP_MOVE_TXN_INTERFACE table
-- Records can be updated, deleted, and resubmitted via the form.
2. Navigate Work in Process Responsibility -> Resource Transactions -> Pending Resource Transactions
-- This form queries the WIP_COST_TXN_INTERFACE table
-- Records can be updated, deleted, and resubmitted via the form.
What are the major tables involved in Material Movement for Inventory and WIP Material, Move, and
Resource Transactions?
See below:
MTL_TRANSACTIONS_INTERFACE
-- INCTCM is the Transaction Manager for this Table.
MTL_MATERIAL_TRANSACTIONS_TEMP
-- INCTCM is the Transaction Manager for this Table
MTL_MATERIAL_TRANSACTIONS
-- CMCTCM is the Cost Manager for the records to be costed in this table.
-- CMCCCM is the Cost Collection Manager for the records to be imported to Project Mfg.
WIP_MOVE_TXN_INTERFACE
-- WIP Move Transaction Worker processes records in this table (WICTCM)
WIP_MOVE_TRANSACTIONS
-- Must be viewed and resubmitted via SQL with the scripts below
WIP_COST_TXN_INTERFACE
-- Resource Cost Worker processes records in this table.
Resolving Pending Material Transactions is a process of determining and fixing what is preventing a record from being
processed through the MTL_TRANSACTIONS_INTERFACE table. Details of pending transactions can be viewed through the
application by navigating to the Transaction
Open Interface form.
Using the Transaction Open Interface window, you can view, edit, correct and resubmit transactions received through the
open interface.
There are five selections in the alternate region list of values: Error, Location, Source, Intransit and Other. These provide
detailed information to help you resolve pending transactions. In the Error alternate region:
a. The error code describes the error on the last attempt to process the line item.
b. The error explanation gives a reason for the error.
c. The process flag indicates whether the row has been processed by the concurrent manager.
Resolving Pending WIP Cost transactions is a process of determining and fixing what is preventing a record from being
processed through the WIP_COST_TXN_INTERFACE table. Pending transactions can be viewed through the application by
navigating to the WIP Responsibility -> pending resource transaction form.
In the Pending Resource Transaction window you can view, update, delete, and resubmit resource transactions that have
failed validation and remain in the WIP_COST_TXN_INTERFACE table. You can also resubmit transactions whose
concurrent process has failed and have a processing phase of Complete and process status of Error. There are eight
selections in the alternative region list of values: Processing,
Source, Concurrent Request, Job or Schedule Name, Operation, Resource, Transaction and Comments.
Errored transactions will have the Transaction ID and Group ID populated and the Status will be error. Pending transactions
will have the Transaction Id and Group ID fields blank and the Status will be pending.
To view error details for failed resource transactions, select the errored transaction and click on the [Error] button. The
Pending Resource Transaction error window appears. Column indicates the name of the column in the resource transaction
interface table (WIP_COST_TXN_INTERFACE) that failed validation. Message indicates why the transaction failed.
When attempting to load legacy data into the MTL_TRANSACTIONS_INTERFACE table, into what column is
the PO number input?
There is not a direct column for PO number.In the Oracle Manufacturing Implementation Manual, locate the section on
Open Transactions Interfaces. This section describes the transaction type id's and
there is not a PO number. The transaction_reference column can be used to hold the PO number. This column is optional
and shows up on reports and transaction displays. Since a column for the PO number does not directly exist, a
transaction_reference field can be used to input this information.
In Release 10.7, we do a Miscellaneous Receipt (PO Receipts are not supported).
In Release 11, Purchasing Module has a Receiving Interface and we do not see any data coming to this table anymore.
Customers that currently have release 10.7 and do not have this functionality will need to upgrade to release 11.0 or
higher, which contains the production version of this functionality.
All issues and receipts of asset items to an asset subinventory and sales order shipments require the distribution account
id that originates from the GL code combinations. This account id is required to
create a complete audit trail of the transaction.
REFERENCES
NOTE:272154.1 - FAQ: Sales Order Processing within Inventory / Drop Ship Transactions Hungup In Transaction Open
Interface
NOTE:298695.1 - Reviewing and Fixing Pending, Stuck Transactions for Period Close
NOTE:404036.1 - FAQ: Common Questions About Transfer to General Ledger (GL) -- Close Inventory Period Without
Transfer to GL
NOTE:461716.1 - FAQ AX Inventory
NOTE:568012.1 - FAQ: Inventory Standard Datafixes
NOTE:143004.1 - Inventory Close Period Notes - Uncosted or Pending Transactions Diagnostic SQL Scripts
https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=i49oyav3h_45&id=110424.1 6/7
04/01/2023, 12:56 Document 110424.1
Didn't find what you are looking for?
https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=i49oyav3h_45&id=110424.1 7/7