Oracle SCM Functional
Interview Questions & Answers - Inventory Module – Part XI
What is the “mtl_transactions_interface”
table used for?
This table is an Interface table used between non-Inventory applications and the Oracle Inventory Transactions module.
In other words any other module other than Inventory that needs to update the Inventory is processed through this table.
This table is an Interface table used between non-Inventory applications and the Oracle Inventory Transactions module.
In other words any other module other than Inventory that needs to update the Inventory is processed through this table.
Modules such as Work In Progress (WIP) and Order Entry
(OE) first inserts the records to the mtl_transactions_interface (MTI) for
validation.
The Interface Manager called the Transactions Manager (INCTCM) which reads records from this table, validates them and moves the successful transactions into mtl_material_transactions_temp, and submits Transaction workers (sub-processes - INCTCW) which then processes these records through inventory. This process consists of data derivation, validation and transfer of records from mtl_transctions_interface, mtl_transactions_lots_interface and mtl_serial_numbers_interface into their respective temporary (temp) tables from where the transactions processor processes them.
What is the “mtl_material_transactions_temp” table used for?
“mtl_material_transactions_temp” is a temporary table, once the transactions have been passed to this table after initial validation by the Transactions Manager (INCTCM) from the “mtl_transactions_interface” table a job id is attached and Transactions Worker (INCTCW) is submitted by the INCTCM process in order to the get the records processed and moved to the “mtl_material_transactons” table.
This table is also used by Inventory Module and Purchasing module which inserts / updates directly into this table for any transactions entered within itself and each transaction in turn through a process of strict validation.
The Interface Manager called the Transactions Manager (INCTCM) which reads records from this table, validates them and moves the successful transactions into mtl_material_transactions_temp, and submits Transaction workers (sub-processes - INCTCW) which then processes these records through inventory. This process consists of data derivation, validation and transfer of records from mtl_transctions_interface, mtl_transactions_lots_interface and mtl_serial_numbers_interface into their respective temporary (temp) tables from where the transactions processor processes them.
What is the “mtl_material_transactions_temp” table used for?
“mtl_material_transactions_temp” is a temporary table, once the transactions have been passed to this table after initial validation by the Transactions Manager (INCTCM) from the “mtl_transactions_interface” table a job id is attached and Transactions Worker (INCTCW) is submitted by the INCTCM process in order to the get the records processed and moved to the “mtl_material_transactons” table.
This table is also used by Inventory Module and Purchasing module which inserts / updates directly into this table for any transactions entered within itself and each transaction in turn through a process of strict validation.
What type of
issues can been seen in the “mtl_transactions_interface” and “mtl_material_transactions_temp”
tables?
The issues can be related to stuck transactions in these tables.
Below list of errors may be seen in the mentioned tables:
The issues can be related to stuck transactions in these tables.
Below list of errors may be seen in the mentioned tables:
What type of
issues can been seen in the “mtl_material_transactions” table?
“mtl_material_transactions” table is a transactional historical table.
“mtl_material_transactions” table is a transactional historical table.
Transaction is valued (unit cost*quantity = amount), once
the data inserted into this table the transaction is almost complete except for
the fact that it needs to have the costing details finally updated and inserted
into the Transaction Accounts table for transfer to General Ledger.
However, it is the holding point for transactions to be
cost.
What is purpose of
“mtl_transaction_accounts” table?
The details of the transactions are usually inserted into this table as Debits and Credits and from here it is transferred to GL
The details of the transactions are usually inserted into this table as Debits and Credits and from here it is transferred to GL
What are the major
tables involved in Material Movement for Inventory and WIP Material, Move, and
Resource Transactions?
Major tables involved in material movement for inventory, WIP Material, Move & Resource Transactions are:
mtl_transactions_interface
mtl_material_transactions_temp
mtl_material_transactions
wip_move_txn_interface
wip_move_transactions
wip_cost_txn_interface
Major tables involved in material movement for inventory, WIP Material, Move & Resource Transactions are:
mtl_transactions_interface
mtl_material_transactions_temp
mtl_material_transactions
wip_move_txn_interface
wip_move_transactions
wip_cost_txn_interface
How to resolve the
Pending Material Transactions?
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.
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, user 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 & Other.
Using the Transaction Open Interface window, user 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 & Other.
These provide detailed information to help the user to resolve
the 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.
The process flag status codes are:
1 = Pending
2 = Running
3 = Error
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.
The process flag status codes are:
1 = Pending
2 = Running
3 = Error
Resubmitting Transactions for Processing:
In the Transaction Open Interface window, check the Resubmit box next to the transaction that user wants to resubmit or choose Resubmit All from the Special menu. If user have many transactions to resubmit, use the Resubmit All button to select all transactions for processing and then selectively deselect individual transactions user don’t need to resubmit.
In the Transaction Open Interface window, check the Resubmit box next to the transaction that user wants to resubmit or choose Resubmit All from the Special menu. If user have many transactions to resubmit, use the Resubmit All button to select all transactions for processing and then selectively deselect individual transactions user don’t need to resubmit.
Save the work to submit the transactions for processing.
How to resolve Pending WIP Cost Transactions?
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.
How to resolve Pending WIP Cost Transactions?
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.
User 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.
Transaction and Comments.
Error 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.
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.
To resubmit failed resource transactions:
In the Pending Resource Transactions widow either check the transaction's Resubmit check box to resubmit one record or choose select All for Resubmit from the Special Menu then save the work.
In the Pending Resource Transactions widow either check the transaction's Resubmit check box to resubmit one record or choose select All for Resubmit from the Special Menu then save the work.
In which column
the PO number is inserted, when attempting to load legacy data into the “mtl_transactions_interface”
table?
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. Refer to the column of transaction_reference and this column will allow the po number. The 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.
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. Refer to the column of transaction_reference and this column will allow the po number. The 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.
Why is the
distribution account ID required in “mtl_transactions_interface” table?
All issues and receipts of asset items to an asset subinventory and sales order shipments require the distribution account id that originates from GL code combinations. This account id is required to create a complete audit trail of the transaction.
All issues and receipts of asset items to an asset subinventory and sales order shipments require the distribution account id that originates from GL code combinations. This account id is required to create a complete audit trail of the transaction.
Reference:
Collected from various web sources.
Please do refer below links for Oracle SCM Functional
interview questions & Answers on inventory module.
