INV>Guide To Resolving Pending Transaction Issues

PURPOSE
--------------
There are a variety of reasons for pending transactions. This paper will serve as a guide for
troubleshooting and resolving pending transaction issues which are preventing you from closing
an inventory accounting period.
PENDING TRANSACTIONS
--------------------------------------
I. VIEWING PENDING TRANSACTIONS
You can view the number of pending transactions by navigating to the Inventory Accounting
Periods form.
Nav > Cost > Accounting Close Cycle > Inventory Accounting Periods
Put your cursor on the appropriate open accounting period and click on the [Pending]
button. There are two zones titled “Resolution Required” and “Resolution Recommended.”
The Resolution Required zone displays the number of unprocessed material, uncosted
material, and pending WIP costing transactions existing in this period. Pending transactions
appearing in this zone must be resolved before the period can be closed.
The Resolution Recommended zone displays the number of pending receiving, pending
material and pending shop floor move transactions existing in this period. Pending transactions
appearing in this zone will not prevent closing of the accounting period. However, once the
accounting period is closed, unresolved pending transactions in this zone cannot be processed
because they have a transaction date for a closed period.
Pending transactions in the Unprocessed Material field indicate you have unprocessed
material transactions in the MTL_MATERIAL_TRANSACTONS_TEMP table .
Pending transactions in the Uncosted Material field indicate you have material transactions in
the MTL_MATERIAL_TRANSACTIONS table with unprocessed accounting entries.
Pending WIP Costing transactions indicate you have unprocessed resource and overhead
accounting transactions in the WIP_COST_TXN_INTERFACE TABLE.
Pending Receiving transactions indicate you have unprocessed purchasing transactions in the
RCV_TRANSACTIONS_INTERFACE table. These transactions include purchase order
receipts and returns for inventory. If this condition exists, you will receive a warning but will be
able to close the accounting period. These transactions are not included in your receiving value
if they are not resolved prior to closing the period.
Pending Material transactions indicate you have unprocessed material transactions in the
MTL_TRANSACTIONS_INTERFACE table.
Pending Move transactions indicate you have unprocessed shop floor move transactions in the
WIP_MOVE_TXN_INTERFACE table.

II. RESOLVING UNPROCESSED AND UNCOSTED MATERIAL
TRANSACTIONS
1. Unprocessed Material Transactions:
To resolve unprocessed Material Transactions, you need to determine and fix what is
preventing a record from being processed through the
MTL_MATERIAL_TRANSACTIONS_TEMP table. Details of pending transactions
can be viewed through the Applications by navigating to the Pending Transactions form.
Nav > Inventory > Transactions > Pending Transactions
By using the Pending Transactions window, you can view, edit, correct and resubmit
unprocessed material transactions. There are five selections in the alternate region list of
values: Error, Location, Source, Intransit and Other which provide detailed
information to help you resolve pending transactions. The key fields in these alternate
regions are called out below.
a) The Error alternate region:
- The error code describes the error on the last attempt to process the line
item.
- The error explanation gives a reason for the error.
- The process flag indicates whether the row has been processed by the
concurrent manager. The process flag codes are:
1 = Pending
2 = Running
3 = Error
- The transaction header ID is the number used to group transactions in
the concurrent manager.
- The transaction mode is the method used to process the line item, i.e.,
concurrent processing.
b) The Source alternate region:
- The Transaction Source Type, such as WIP Job or Schedule, is given.
c) The Others alternate region:
- The Department Code for the line item is given.
- The Employee Code identifies the employee who entered the
transaction.
2. Resubmitting Unprocessed Material Transactions:
In the Pending Transactions window either check the transaction’s Resubmit check box
to resubmit one record or chose Select All for Resubmit from the Special Menu. Now
save your work. The records can also be resubmitted via the following SQL statement:
Update MTL_MATERIAL_TRANSACTIONS_TEMP
Set PROCESS_FLAG = ‘Y’,
LOCK_FLAG = ‘N’,
TRANSACTION_MODE = 3,
ERROR_CODE = NULL
Where TRANSACTION_ID = ‘& TRANSACTION_ID’;
3. Uncosted Material Transactions:
To resolve uncosted Material Transactions you need to determine and fix what is
preventing a record from being processed through the
MTL_MATERIAL_TRANSACTIONS table. Details of uncosted transactions can be
viewed using SQL*PLUS.
Using SQL*PLUS you can determine how many records have been costed, are
pending or are in error by selecting the row COSTED_FLAG. The status codes for the
COSTED_FLAG are:
N = Not Costed
E = Error
Null = Costed
The following SQL select statements can be used to determine:
a) The number of erred rows in MTL_MATERIAL_TRANSACTIONS:
select count (*)
from MTL_MATERIAL_TRANSACTIONS
where COSTED_FLAG = ‘E’;
b) The number of unprocessed rows in MTL_MATERIAL_TRANSACTIONS:
select count (*)
from MTL_MATERIAL_TRANSACTIONS
where COSTED_FLAG = ‘N’;
c) The number of processed rows in MTL_MATERIAL_TRANSACTIONS:
select count (*)
from MTL_MATERIAL_TRANSACTIONS
where COSTED_FLAG like NULL;
To resubmit the erred records in the MTL_MATERIAL_TRANSACTIONS table, it
must be done via a SQL statement by updating the costed_flag = ‘N’ and the
transaction_group_id = NULL.
Update MTL_MATERIAL_TRANSACTIONS
set COSTED_FLAG = ‘N’,
set TRANSACTION_GROUP_ID = NULL
where COSTED_FLAG = ‘E’ or COSTED_FLAG = ‘N’;
If there is a record that is in error, look for a concurrent process that has erred. To view
a concurrent process that is in a status of error, navigate to:
Nav > System Administrator > Concurrent > Request
Run the query by entering %ost%orker% in the Name field and Error in the status field
of the Find Requests window.
In some cases, changing the profile option MRP:Debug Mode to ‘YES’, and resubmitting the
erred records may give you more information in the log files. You do this by navigating to:
System Administrator > Profile > System

III. RESOLVING PENDING MATERIAL TRANSACTIONS.
1. 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. Details of pending transactions
can be viewed through the application by navigating to the Transaction Open
Interface form:
Inventory > Transactions > Transaction Open Interface
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. The process flag status codes are:
1 = Pending
2 = Running
3 = Error
2. Resubmitting Transactions for Processing:
In the Transaction Interface window, check the Resubmit [] box next to the transaction
you want to resubmit or choose Resubmit All from the Special menu. If you have many
transactions to resubmit, use the Resubmit All button to select all transactions for
processing and then selectively deselect individual transactions you do not want to
resubmit. Save your work to submit the transactions for processing.
The records can also be resubmitted using the following SQL statement:
Update MTL_TRANSACTIONS_INTERFACE
Set PROCESS_FLAG = 1,
LOCK_FLAG = 2,
TRANSACTION_MODE = 3,
ERROR_CODE = NULL
Where PROCESS_FLAG = 3;

IV. RESOLVING PENDING WIP COST TRANSACTIONS
1. 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. Details of pending transactions can be
viewed through the application by navigating to the pending resource transaction form.
WIP > Resource Transactions > Pending Resource Transactions
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.
Erred 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 erred 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.
2. To resubmit failed resource transactions:
In the Pending Resource Transactions window, either check the transaction’s Resubmit
check box to resubmit one record or chose Select All for Resubmit from the Special
Menu. Now save your work. The records can also be resubmitted using the following
SQL statement:
Update WIP_COST_TXN_INTERFACE
Set GROUP_ID = NULL,
TRANSACTION_ID = NULL,
REQUEST_ID = NULL,
PROCESS_STATUS = 1
Where PROCESS_STATUS = 3;
When you resubmit a record, the system nulls the Transaction ID, Group ID,
and concurrent Request ID and changes the processing status to “Pending.”
3. To delete pending resource transaction records:
In the Pending Resource Transaction window, select the transaction and choose
delete from the edit window or choose the delete icon on the tool bar.

V. RESOLVING PENDING MOVE TRANSACTIONS
1. Pending Move Transactions:
Resolving unprocessed Move Transactions is a process of determining and fixing what is
preventing a record form being processed through the
WIP_MOVE_TXN_INTERFACE table. Details of pending move transactions can be
viewed through the applications by navigating to the pending move transaction form:
WIP > Move Transactions > Pending Move Transactions
Through the Pending Move Transaction window you can view, update, delete, and
resubmit move transaction records that have failed validation. You can also resubmit
transactions whose concurrent process has failed and have a processing phase of
complete and process status of “Error.”
There are seven selections in the alternative region list of values in the Pending Move
Transactions window: Processing, Source, Concurrent Request, Job or Schedule
Name, Operations, Transaction, Comments and Scrap Account.
Erred 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 transaction, select the erred transaction and
click on the error button. The Pending Move Transaction error window appears.
Column indicates the name of the column in the resource transaction interface table
(WIP_MOVE_TXN_INTERFACE) that failed validation. Message indicates why the
transaction failed.
2. To resubmit failed move transactions:
In the Pending Move Transactions window, either check the transaction’s Resubmit
check box to resubmit one record or chose Select All for Resubmit from the Special
Menu. Now save your work. The records can also be resubmitted using the following
SQL statement:
Update WIP_MOVE_TXN_INTERFACE
Set GROUP_ID = NULL,
TRANSACTION_ID = NULL,
PROCESS_STATUS = 1
Where TRANSACTION_ID = ‘&TRANSACTION_ID’;
When you resubmit a record, the system nulls the Transaction ID, Group ID, and
concurrent Request ID and changes the processing status to “Pending.”
3. To delete pending move transaction records:
In the Pending Move Transaction window, select the transaction and choose delete
from the edit window or choose the delete icon on the tool bar.

VI. CONCLUSION
The key steps to resolving pending transactions are:
1. Locate the transaction.
2. Find the error message to determine what is preventing the transaction from
processing.
3. Resolve the error.
4. Resubmit the pending record.
If transactions are pending but not in error, you will need to resubmit them via SQL, using the
relevant SQL statement provided above.