EBS待定资源事物处理

There are a variety of reasons for pending transactions. The scope of this paper is to identify data, and product affecting Period Close process. This information will assist troubleshooting pending transactions that may affect the Period Close process.

VIEWING PENDING TRANSACTIONS

Users can see the number of pending transactions by navigating to the Inventory Accounting Periods Form.

Navigate > Cost > Accounting Close Cycle > Inventory Accounting Periods

Place cursor on the appropriate open accounting period and click on the [Pending] Button. There are three zones titled“Resolution Required”, “Resolution Recommended” and “Unprocessed Shipping Transactions”.

The Resolution Required zone displays the number of unprocessed material, uncosted material, Pending WIP Costing, Uncosted WSM txn and Pending WSM interfaces transactions existing in this period. 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. Transactions appearing in this zone will not prevent closing of the accounting period. However, once the accounting period is closed, unresolved transactions in this zone cannot be processed because they have a transaction date for a closed period. The Unprocessed Shipping Transactions zone displays the number of Pending Transactions existing in this period. Transactions appearing in this zone must be resolved before the period can be closed.

Resolution Required Transactions:

“Unprocessed Material” indicate there are unprocessed material transactions in the

MTL_MATERIAL_TRANSACTONS_TEMP table.

“Uncosted Material” indicate there are material transactions in the

MTL_MATERIAL_TRANSACTIONS table with unprocessed accounting entries.

“Pending WIP Costing” transactions indicate there are unprocessed resource and overhead accounting transactions in the WIP_COST_TXN_INTERFACE table.

“Uncosted WSM txn” indicate there are uncosted transactions in the

WSM_SPLIT_MERGE_TRANSACTIONS table.

“Pending WSM interface” indicate there are pending transactions in the

WSM_SPLIT_MERGE_TXN_INTERFACE table.

Resolution Recommended Transactions:

“Pending Receiving” transactions indicate there are unprocessed purchasing transactions in the RCV_TRANSACTIONS_INTERFACE table. These transactions include purchase order receipts and returns for inventory. These transactions are not included in your receiving value if they are not resolved prior to closing the period.

“Pending Material” transactions indicate there are unprocessed material transactions in the MTL_TRANSACTIONS_INTERFACE table.

“Pending Shop Floor Move” transactions indicate there are unprocessed shop floor move transactions in the WIP_MOVE_TXN_INTERFACE table.

Unprocessed Shipping Transactions:

“Pending Transactions” in the Unprocessed Shipping Transactions zone indicate there are transactions in the WSH_DELIVERY_DETAILS table in a status of shipped.

UNPROCESSED MATERIAL TRANSACTIONS:

To resolve Unprocessed Material transactions, users need to identify and resolve the errors and issues preventing a record from being processed through the MTL_MATERIAL_TRANSACTIONS_TEMP table. Details of transactions can be viewed through the Applications by navigating to the Pending Transactions form.

Inventory > Transactions > Pending Transactions

By using the Pending Transactions window, users view, edit, correct and resubmit unprocessed material transactions. There are five tabs to select the type of information: Error, Location, Source, Intransit and Others, which provide detailed Information on the transactions.

Resubmitting Unprocessed Material Transactions:

Before re-submitting records through the Pending Transactions Form, you can gather information regarding your data and the Inventory Transaction Managers and workers

The following Diagnostic Scripts should be used to identify data, errors, and status of concurrent and interface managers/workers.

Inventory Period Close Diagnostic Test - for the period in question  (INVPeriodClose115.sql) Note: 206576.1

Oracle Inventory Support Svc Req Instrumentation for Stuck Transactions MMTT (INVMMTT115h.sql) Note: 204577.1

In the Pending Transactions window either select the Resubmit check box to resubmit one record or choose Select All to Resubmit from the Special Menu and selectively deselect individual transaction you do not want to resubmit, save your work. Transactions can also be resubmitted via the following SQL statement

SQL>UPDATE MTL_MATERIAL_TRANSACTIONS_TEMP

SET PROCESS_FLAG = ‘Y’,

LOCK_FLAG = ‘N’,

TRANSACTION_MODE = 3,

ERROR_CODE = NULL

WHERE TRANSACTION_HEADER_ID = ‘& TRANSACTION_HEADER_ID’;

*** Warmning ***

Verify transactions to be resubmitted since there may be Move Order Transactions that must be processed through the Transact Move Order Form.

The “Process transaction interface”(short name INCTCM) is the manager that will launch the “Inventory transaction worker” (short name INCTCW) to process the transactions in the MTL_MATERIAL_TRANSACTIONS_TEMP table. If the error message in the Pending Transactions window is not clear reviewing the log file of the“Inventory transactions Worker” may provide more information that could help in resolving the error. Resubmitting the transactions with the profile options:

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 through the Applications by navigating to the Material Transactions form.

Cost > View Transactions > Material Transactions

In the find Parameter Window there is a field “Costed” and from the list of values “Yes, No, Error or Null” can be selected. The failed transactions are the ones that will need to be corrected and the transactions that are not costed will need to be costed to close the period.

Cost > View Transactions > Material Transactions

By using the Material Transaction window, you can view, edit, correct and resubmit erred costed transactions. There are five tabs to select the type of information:Location, Intransit, Reason, Reference, Transaction ID and Transaction Type which provide detailed information to help you resolve erred and uncosted transactions

In the Material Transactions Form failed transactions can be resubmitted by clicking on “Tools”, “Select All”, and then clicking on “Tools, Submit all”. Or Submit the number of transactions found through the search criteria in the find window. The erred and uncosted transactions can also be resubmitted through the following SQL*Plus statement:

SQL> UPDATE MTL_MATERIAL_TRANSACTIONS

SET COSTED_FLAG = ‘N’, TRANSACTION_GROUP_ID = NULL

WHERE COSTED_FLAG is not null;

First shut down the Cost Manager:

The “Cost Manger” (module CMCTCM) is the manager that will launch the “Material cost transaction worker” (module CMCMCW) for a standard costing environment or the “Actual Cost Worker” (module CMCACW) for an average, fifo, lifo or perpetual costing environment. If the error message in the Material Transaction form is not clear or not available reviewing the log file of the “Cost Worker” may provide more information that could help in resolving the error.

In an Average, FIFO or LIFO costing organization if there is one transaction that is in error the Cost Manager will not launch a Cost Worker to process the uncosted transactions. This is standard functionality because in an Average, FIFO or LIFO costing organization the item cost is recalculated during receiving transactions and if they were not costed in order the item cost would not be correct.

In the Organization Parameter screen under the Costing Information tab there is a field “Cost Cutoff Date” and a Cost Manager will not launch any Cost Workers past this date. This is most commonly used to update item cost and all transactions past the cost cutoff date will be transacted at the new cost, once the Cost Cutoff Date is changed.

Pending WIP Costing transactions

(Resource and Overhead Transactions)

Resolving Pending WIP Cost transaction is a process of determining and fixing what is preventing a record form being processed through the WIP_COST_TXN_INTERFACE table. Details of pending transactions can be viewed through the applications by navigating to the pending resource transaction form.

WIP > Resource Transactions > Pending Resource Transactions

In the Pending Resource Transaction window you can view, update and resubmit resource transactions that have failed validation and remain in the WIP_COST_TXN_INTERFACE table. You can also resubmit and delete transactions whose concurrent process has failed and have a processing phase of Complete and a process status of Error. There are seven tabs to select the type of information: Processing, Source, Concurrent Request, Job or Schedule Name, Operation, Resource, Transaction, Comments and Project Information which provide detailed information to help in resolving pending resource transactions.

Failed 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 transaction and click on the [Error] button. The Pending Resource Transaction error window appears. Columnindicates the name of the column in the resource transaction interface table (WIP_COST_TXN_INTERFACE) THAT FAILED VALIDATION. Message indicates why the transaction failed.

Resubmitting Failed or Pending Resource Transactions

Before re-submitting records through the Pending Resource Transactions Form, you can gather information regarding your data and the Inventory Transaction Managers and workers. The following Diagnostic Scripts should be used to identify data, errors, and status of concurrent and interface managers/workers.

Inventory Period Close Diagnostic Test - for the period in question

(INVPeriodClose115.sql) Note: 206576.1

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 and selectively deselect individual transaction you do not want to resubmit, save your work. Erred transactions can also be resubmitted via the following SQL statement

SQL> UPDATE WIP_COST_TXN_INTERFACE

SET GROUP_ID = NULL,

TRANSACTION_ID = NULL,

REQUEST_ID = NULL,

PROCESS_STATUS = 1

WHERE PROCESS_STATUS = 3;

This will resubmit records in PROCESS_STATUS = 3 (Error), nulling out the transaction id, group id and concurrent request id and change the process status to pending.

The “Cost Manager” (short name CMCTCM) is the manager that will launch the “Resource Cost Worker” (short name CMCCTW) or the “Overhead Cost Worker” (short name CMCOCW) to process the resources or resource overhead transactions for a standard costing environment. In an Average, LIFO, FIFO, or Perpetual costing environment the "Cost Manager" will launch an "Actual Cost Worker" (short name CMCACW) for processing resources or resource overhead transactions. If the error message in the Pending Resource Transaction screen widow is not clear, reviewing the

log file of the “Cost Worker” may provide more information that could help in resolving the error. Changing the profile opting “MRP: Debug Mode” set to Yes and then resubmit the erred resource transactions and the log file may provide more information on the error.

Uncosted WSM txn Transactions

Uncosted WSM transactions in the WSM_SPLIT_MERGE_TRANSACTIONS table, preventing a period from closing can be viewed through the WIP Lot Transactions form:

Shop Floor Manager > Lot Transactions > WIP Lot Transactions

Clicking on the ‘Flash Light’ icon will bring up the find window. Selecting Null in the

‘Transaction Type’ field will select all WIP Lot Transactions, selecting something other than complete in the ‘Costed’ field and the ‘Transaction Dates’ for the period to query uncosted transactions.

Shop Floor Manager > Lot Transactions > WIP Lot Transactions

By using the WIP Lot Transaction window, you can view uncosted transactions. If there is more than one uncosted transactions clicking on the down arrow will toggle through these transactions. There are five tabs to select detailed information on the WIP Lot; Job Bill, Routing, Operations and Others.

Resolution Recommended Transactions Pending Receiving Transactions:

Pending Receiving Transactions are transactions that have not processed through the

RCV_TRANSACTIONS_INTERFACE table. These transactions can be viewed and deleted through the ‘Transaction Status Summary’ form:

Purchasing > Receiving > Transactions Status Summary

A find window will appear and to query all of the unprocessed transactions for that period select from the field Source Type ‘All’, from the Transactions Details tab input the start and completion dates of the period in question and click ‘Find’:

Purchasing > Receiving > Transactions Status Summary

Using the Transaction Statuses window, pending transactions can be viewed and deleted. There are four tabs to select: Transactions, Details, and Order Information, Outside Services.

Resolving Pending Receiving Transactions:

In resolving Pending Receiving Transactions the status and quantity received of the actual purchase order of the receiving transaction should be reviewed. If after reviewing the Purchase Order if the status is closed or complete and the purchase order quantity is equal to the quantity received then most likely the Pending Receiving transaction is a duplicate. Duplicate transactions can be deleted through the ‘Transaction Status Summary’ screen by clicking on the transaction line and then clicking on the delete icon.

If after reviewing the Purchase Order of the Pending Receiving Transactions it is determined that the transaction should be processed it is recommended that a new receipt is created and processed. The original Pending Receiving Transaction should be deleted through the ‘Transaction Status Summary’ screen.

Receiving transactions are processed through the RCV_TRANSACTIONS_INTERFACE table by submitting the ‘Receiving Transactions Processor’ (short name RVCTP).

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 four tabs to view information:

Error, Location, Source, Intransit and Other, which provide detailed information to help you resolved pending transactions. Select a tabbed region to display a type of information:

Error: Interface transaction error information.

Location: Interface transaction location information

Source: Interlace source information

Intransit: Interface intransit shipping information.

Others: Miscellaneous header and costing information.

Resubmitting Pending Material Transactions

Before re-submitting records through the Transactions Interface Form, you can gather information regarding your data and the Inventory Transaction Managers and workers. The following Diagnostic Scripts should be used to identify data, errors, and status of concurrent and interface managers/workers.

Inventory Period Close Diagnostic Test - for the period in question

(INVPeriodClose115.sql) Note: 206576.1

Oracle Inventory Support Svc Req Instrumentation for Stuck Transactions MTI

(INVMTI115h.sql) Note: 209928.1

In the Transaction Interface window, check the Submit option next to the transactions you want to resubmit or choose Resubmit All. If you have many transaction to resubmit, use the Resubmit All button to select all transactions for processing and then selectively

deselect individual transaction you do not want to resubmit. Save your work to submit the transactions for processing.

The failed records can also be resubmitted via the following SQL statement:

SQL> UPDATE MTL_TRANSACTIONS_INTERFACE

SET PROCESS_FLAG = 1,

LOCK_FLAG = 2,

TRANSACTION_MODE = 3,

ERROR_CODE = NULL

WHERE PROCESS_FLAG = 3;

The “Process transaction interface” (short name INCTCM) is the manager that will launch the “Inventory transaction worker” (short name INCTCW) to process the transactions in the MTL_TRANSACTIONS_INTERFACE table. If the error message in the Transactions Interface window is not clear reviewing the log file of the “Inventory transactions Worker” may provide more information that could help in resolving the error.

Pending Shop Floor Move

Resolving unprocessed Move Transactions is a process of determining and fixing what is preventing a record from 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 transactions form:

WIP > Move Transactions > Pending Move Transactions

Through the Pending Move Transactions window you can view, update, delete, and resubmit Move transaction records that have failed validation and remain in the Open Move Transaction Interface table (WIP_MOVE_TXN_INTERFACE). You can also resubmit transactions whose concurrent process has failed and have a processing phase of Complete and process status of Error. You can view error messages associated with failed records. Error messages can assist you in updating failed records before resubmission.

There are seven tabs to select information on the move transaction; Processing, Source, Concurrent Request, Job or Schedule Name, Operations, Transactions and Comments and Scrap Account which provide detailed information to help you resolve pending move transactions

Resubmitting Failed Move Transactions:

In the Pending Move Transactions window, either checks the transaction’s Resubmit check box to resubmit one record or chose Select All from the Special Menu. Now save your work. The records can also be resubmitted using the following SQL statement

SQL> UPDATE WIP_MOVE_TXN_INTERFACE

Set GROUP_ID = NULL,

TRANSACTION_ID = NULL,

PROCESS_STATUS = 1

Where TRANSACTION_ID = ‘&TRANSACTION_ID’;

The “WIP Move Transaction Manager”(short name WICTMS) is the manager that will launch the “WIP Move Transaction Worker” (short name WICTWS) to process the transactions in the WIP_MOVE_TXN_INTERFACE table. If the error message in the Pending Move Transactions window is not clear reviewing the log file of the “WIP Move Transaction Worker” may provide more information that could help in resolving the error. Resubmitting the transactions with the profile option ‘MRP: Debug Mode’ set to ‘Yes’ may provide even more information in the log file.

Deleting Pending Move Transactions Records:

To delete pending move transactions, in the Pending Move Transactions window, select the transaction choose Delete from the Edit Menu. You can delete failed records that have a processing status of Error regardless of their processing phase. When you delete transaction records, their corresponding error messages are also deleted.

UNPROCESSED SHIPPING TRANSACTIONS

To resolve unprocessed shipping transactions, users need to identify and resolve shipping transactions that are in a status of shipped in the WSH_DELIVERY_DETAILS table. Details of the Shipping transactions in a status of shipped can be viewed through the application by navigating to the Transaction screen through Order Management and quarrying on the status ‘Shipped’ and the Date of period:

The Shipping Transactions window provides a consolidated workbench for three major shipping functions: planning, pick releasing, and ship confirming. It enables you to plan and manage trips, stops, deliveries, delivery lines, and LPNs (Containers). There are four tabs to select they type of information: Trips, Stops, Contents by Delivery, and Contents by Line/Lpn.

Transactions that are in a in a status of ‘Shipped’ have been shipped confirmed but have not yet been interfaced to Oracle Inventory. These must be processed and resolved before the period is closed. The concurrent process “Order Management Interface” (short name WSHOMIS) and the concurrent process “Inventory Interface –SRS” (short name WSHINVIS) populate Inventory Interface and Order Management Interface and upon completing successfully the status of the line changes to “Invoice Eligible”. These concurrent processes can be submitted through the applications by navigating to:

Order Management > Shipping > Interface > Run

Run the Order Management Interface-SRS first then the Inventory Interface-SRS. Trip Stop can submit these concurrent processes. The Trip Stop of the pending shipping transaction can be found in the Shipping Transactions window under the Stops tab in the Trip column. Reviewing the log file will supply an error message if the concurrent process does not complete successfully