Resolving Period Close Inventory Pending Transaction

PURPOSE
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.

Pending Transactions Guide

1 of 32

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.

Pending Transactions Guide

2 of 32

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.

The Main Descriptive fields give detailed information on the type of transaction:
Primary UOM, Transaction quantity in terms of the primary uom of the item Qty, Quantity of this transaction Date, Transaction date Item Description, Inventory item description Error Explanation, detailed explanation of error Lot/Serial (Used if transaction is associated with a Lot or Serial number) Submit, When checked and saved the erred transaction line will be resubmitted. If the line is not in error, and it cannot be resubmitted using the Submit check box but will have to be resubmitted through a SQL*Plus script. All failed transactions can be resubmitted by clicking on „Tools‟ resubmit all.

Fields Common to all Tabs:
Item, Inventory item referenced by the line item.
Pending Transactions Guide

3 of 32

Transaction Header Id. Serial Number Fields in Source Tab region are as follows: Transaction Action. Organization code of the destination organization. such as concurrent processing. Destination subinventory. Method used to process the line item. Lot number Lot Expiration Date. The transaction action Transaction Source Type. Cost to process the transaction Transaction Reference. Owning organization identifier Planning Org. Error Explanation. Quantity of this transaction. Date the transaction was entered for processing. Transfer Subinv. Indicates if it has to be processed or just saved. supplier name Cartonized LPN. such as account number Distribution Account. Transaction Type. Destination location. 2 is save only. Overcompletion quantity Transaction Date. Lot expiration date Serial Number. Transfer Org Code. Transaction Temp Id. Source type of the transaction. Subinventory. Distribution account for the line item Transaction Cost. Transaction UOM. Process flag. Organization code of the organization referenced by the line item. 3 is ready to process Error Code.used by WMS only Lot Number. Sequential LPN Id generated by cartonization . Org Code.Transaction Qty. Subinventory referenced by the line item. Locator referenced by the line item. indicates whether the row has been processed by the Concurrent manager. NULL or 1 is default behavior. Fields in Error Tab region are as follows: Overcompletion Transactions. Code describing the error on the last attempt to process the line item. Unit of measure used in the transaction. Revision of the inventory item referenced by the line item. Transfer Location. Source of the transaction. Full explanation of the error that occurred when attempting to process the line item Fields in Location Tab region are as follows: Revision. Transaction line identifier used to join to lot or serial table when under these controls Transaction Mode. Planning organization identifier Supplier. Owning Org. Displays the transaction type. Locator. Reference text describing the transaction Pending Transactions Guide 4 of 32 . The process flag codes are: 1 = Pending 2 = Running 3 = Error Transaction Status. such as WIP Job or Schedule Source. Line item‟s header ID used to group transactions in concurrent manager.

The expenditure organization Resubmitting Unprocessed Material Transactions: Before re-submitting records through the Pending Transactions Form. such as freight carrier charges Transportation Account. The to project number To Task Number. Cost to process the transfer Transportation Cost. Percentage Change. Date you expect to receive the material at the destination organization Fields in the Others Tab region are as follows: Line Code. The source task number Project Number. Request ID assigned by the concurrent manager to the line item Employee Code. Fields in the Intransit Tab region are as follows: Shipment Number. Employee who entered the transaction Operation Seq Num. Number associated with the job or schedule referenced by the line item Department Code. Oracle Work in Process department code for the line item Transaction Source Line ID. Location Code. The waybill or airbill number for the transfer Expected Arrival Date. The transaction reason. The source project number Source Task Number. Freight carrier for the transaction Containers. you can gather information regarding your data and the Inventory Transaction Managers and workers.Reason Name. Oracle Work in Process line description for the item Transaction Source Delivery ID. The to task number Expenditure Type. Line item detail identifier of the demand source Encumbrance Amount. General ledger distribution account that collects the costs associated with using the freight carrier for the transfer Freight Code. Ship–to location Source Project Number. Shipment number for the line item Transfer Cost. when the purchase order or requisition was approved New Average Cost. The expenditure type Expenditure Org. Cost to physically transfer the material. The project number Task Number. Pending Transactions Guide 5 of 32 . Cost group identifier Value Change. reserved against funds. Amount encumbered. Amount used to increment the current inventory value. Percentage used to update the item cost. The task number To Project Number. Number of containers in which the material is stored for the transfer Waybill Airbill. Recalculated average unit cost for the item Cost Group ID.

148651.sql) Note: 206576.for the period in question (INVPeriodClose115. Please enable inventory debug per Metalink Note. Pending Transactions Guide 6 of 32 . ERROR_CODE = NULL WHERE TRANSACTION_HEADER_ID = „& TRANSACTION_HEADER_ID‟. “Inventory transaction worker” (short name INCTCW) to process the d transactions in the MTL_MATERIAL_TRANSACTIONS_TEMP table.1. errors.db.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.1 Oracle Inventory Support Svc Req Instrumentation for Stuck Transactions MMTT (INVMMTT115h. 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. TRANSACTION_MODE = 3. Please ensure the debug file is set with a directory existing in utl_file_dir that can be found with this sql: SQL> SELECT value FROM v$parameter WHER name = 'utl_file_dir'.The following Diagnostic Scripts should be used to identify data. The “Process transaction *** Warmning *** interface”(short name Verify transactions to be resubmitted since there may INCTCM) is the manager be Move Order Transactions that must be processed that will launch the through the Transact Move Order Form. Resubmitting the transactions with the profile options: „MRP: Debug Mode‟ set to „Yes‟ may provide even more information in the log file. Inventory Period Close Diagnostic Test . LOCK_FLAG = „N‟. Transactions can also be resubmitted via the following SQL statement: SQL>UPDATE MTL_MATERIAL_TRANSACTIONS_TEMP SET PROCESS_FLAG = „Y‟. The details follow for your convenience: INV: Debug Trace = YES INV: Debug Level = 11 INV: Debug File = Please set it with the full path where you would like to write the debug messages. and status of concurrent and interface managers/workers. By default.sql) Note: 204577. it will be written in /tmp/invdbg. save your work.

Cost > View Transactions > Material Transactions Pending Transactions Guide 7 of 32 . Cost > View Transactions > Material Transactions In the find Parameter Window there is a field “Costed” and from the list of values “Yes. Details of uncosted transactions can be viewed through the Applications by navigating to the Material Transactions form.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. 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.

Transaction date Distributions (to view distributions of costed transactions) Pending Transactions Guide 8 of 32 . Reference. you can view.Cost > View Transactions > Material Transactions By using the Material Transaction window. correct and resubmit erred costed transactions. Intransit. Transaction quantity in terms of the primary uom of the item Primary Qty. Reason. There are five tabs to select the type of information: Location. Transaction quantity in terms of primary uom of the item Date. Inventory item description Primary UOM. The Main Descriptive fields give detailed information on they type of transaction: Item Description. Transaction ID and Transaction Type which provide detailed information to help you resolve erred and uncosted transactions. edit.

Revision of the inventory item referenced by the line item Transfer Subinventory.Lot/Serial (Used if transaction is associated with a Lot or Serial number) Fields common to all Tabs: Item. supplier lot number. Destination Locator Owning Org. The waybill or airbill number for the transfer Freight Code. Planning organization identifier Supplier. Destination subinventory Transfer Locator. Source of the transaction. Line level transaction source id Pending Transactions Guide 9 of 32 . Inventory item reference by the line item Transaction UOM. Quantity of this transaction Transaction ID. Reference Tab are as follows: Reason. Indicates the costing status Transferred to Projects. Source type of the transaction. Full explanation of the error that occurred when attempting to process the line item Supplier Lot. Date the transaction was entered for processing Source Type. Locator referenced by the line item Revision. Subinventory referenced by the line items Locator. Unit of measure used in the transaction Transaction Quantity. Freight carrier for the transaction Containers. Transaction quantity in terms of primary uom of the item Primary UOM. Displays the item. Owning organization identifier Planning Org. The transaction reason Reference. such as account number Transaction Type. transfer transaction ID Transaction Date. Displays the transaction type Fields in the Location Tab are as follows: Subinventory. Indicates the transfer to cost status Error Code. Source Line ID. Shipment number for the line item Waybill/Airbill. Reference text describing the transaction Costed. such as WIP Job or Schedule Source. Code describing the error on the last attempt to process the line items Error Explanation. Supplier Primary Quantity. Number of containers in which the material is stored for the transfer Fields in the Reason. Transaction quantity in terms of the primary uom of the item Fields in the Intransit Tab are as follows: Shipment Number.

for the period in question (INVPeriodClose115. the transaction action Resubmitting Uncosted Transactions: Before re-submitting records through the Material Transactions Form. the source task number Project Number. Operation sequence number within a routing Source Project Number.sql) Note: 206576. Number used to group transactions in the concurrent manager Receiving Transaction ID. full explanation of the error that occurred when attempting to process the line item Fields in the Transaction Type tab are as follows: Transaction Action. the to task number Expenditure Type. Oracle Work in Process department code for the line item Operation Sequence. the project number Task Number.. the task number To Project Number. Completion transaction cross reference Department Code. Pending Transactions Guide 10 of 32 .1 For more debug information use the following: „MRP: Debug Mode‟ set to „Yes‟ may provide even more information in the log file.Fields in the Transaction ID Tab are as follows: Transfer Transaction ID. errors. the source project number Source Task Number. the to project number To Task Number. the expenditure type Expenditure Org. and status of concurrent and interface managers/workers. Transaction id of the opposing transfer transaction Transaction Header. you can gather information regarding your data and the Inventory Transaction Managers and workers. code describing the error on the last attempt to process the line item Error Explanation. the expenditure organization Error Code.sql) Note.246467.Run from the operating system prompt (CstCheck. Receiving transaction cross reference Move Transaction ID. Inventory Period Close Diagnostic Test . Move transaction cross reference Completion Transaction ID. The following Diagnostic Scripts should be used to identify data.1 Uncosted Transaction Check .

lifo or perpetual costing environment. “Select All”. This is most commonly used to update item cost and all transactions past the cost cutoff date will be transacted at the new cost. TRANSACTION_GROUP_ID = NULL WHERE COSTED_FLAG is not null. 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. This is standard functionality because in an Average. 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. 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 an Average. SQL> UPDATE MTL_MATERIAL_TRANSACTIONS SET COSTED_FLAG = „N‟. Or Submit the number of transactions found through the search criteria in the find window. Submit all”. once the Cost Cutoff Date is changed. Pending Transactions Guide 11 of 32 . 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 the Material Transactions Form failed transactions can be resubmitted by clicking on “Tools”. and then clicking on “Tools. The erred and uncosted transactions can also be resubmitted through the following SQL*Plus statement: 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. 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. Details of pending transactions can be viewed through the applications by navigating to the pending resource transaction form.

Column indicates the name of the column in the resource transaction interface table (WIP_COST_TXN_INTERFACE) THAT FAILED VALIDATION. Job or Schedule Name. Concurrent Request. Resource. Pending Transactions Guide 12 of 32 . Transaction. The Pending Resource Transaction error window appears. There are seven tabs to select the type of information: Processing. 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. Failed transactions will have the Transaction Id And Group ID populated and the Status will be “Error”. Comments and Project Information which provide detailed information to help in resolving pending resource transactions. Operation. To view error details for failed resource transactions. select the transaction and click on the [Error] button. Message indicates why the transaction failed.WIP > Resource Transactions > Pending Resource Transactions In the Pending Resource Transaction window you can view. Source. Pending transactions will have the Transaction ID and Group ID fields blank and the Status will be “Pending”.

Transaction processing phase Status. WIP line identifier Assembly. Transaction group identifier Phase. Inventory item identifier of assembly that job or schedule creates Fields in Operation Name Tab: Op Seq. Resource type Employee Number. Department Identifier Res Seq. Request Id Phase. WIP job or repetitive assembly name Line. Organization identifier Job or Schedule Name. Purchase order Identifier that the receipt is against Pending Transactions Guide 13 of 32 . Transaction processing status Fields in Source Tab: Source Code. Transaction Identifier Fields in Processing Tab: Group Id. Concurrent Message Fields in Job or Schedule Name Tab: Organization.Fields Common to all Tabs: Transaction ID. Operation sequence number within a routing Dept. Code of the shop floor control system that generated the transaction record (null if created by Oracle Work in Process) Source Line. Activity name Charge Type. Username of person that created the record Fields in Concurrent Request Tab: Request ID. Resource code Type. Method of charging the resource PO Number. Identifier used by source shop floor control system (null if created by Oracle Work in Process) Created By. Transaction processing status Message. Resource sequence number Name. Employee number Fields in Resource Tab: Activity. Transaction processing phase Status.

Actual rate of the resource Fields in Transaction Tab: UOM. Date transaction was performed Type. errors.sql) Note: 206576. Transaction reference descriptive text Fields in Project Information Tab: Project Number. Project task Identifier Resubmitting Failed or Pending Resource Transactions Before re-submitting records through the Pending Resource Transactions Form. Project Identifier Task Number. The following Diagnostic Scripts should be used to identify data. Transaction quantity Date. PROCESS_STATUS = 1 WHERE PROCESS_STATUS = 3.Currency. Erred transactions can also be resubmitted via the following SQL statement: SQL> UPDATE WIP_COST_TXN_INTERFACE SET GROUP_ID = NULL. Transaction type Fields in Comments Tab: Reason. you can gather information regarding your data and the Inventory Transaction Managers and workers. group id and concurrent request id and change the process status to pending. Inventory Period Close Diagnostic Test . Unit of measure used for transaction Quantity. 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 Pending Transactions Guide 14 of 32 .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. TRANSACTION_ID = NULL. REQUEST_ID = NULL. Unique Identifier for the currency Actual Rate. Standard transaction reason name Reference.for the period in question (INVPeriodClose115. This will resubmit records in PROCESS_STATUS = 3 (Error). and status of concurrent and interface managers/workers. nulling out the transaction id.

FIFO. Pending Transactions Guide 15 of 32 .name CMCOCW) to process the resources or resource overhead transactions for a standard costing environment. 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. 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. In an Average. reviewing the log file of the “Cost Worker” may provide more information that could help in resolving the error. If the error message in the Pending Resource Transaction screen widow is not clear. selecting something other than complete in the „Costed‟ field and the „Transaction Dates‟ for the period to query uncosted transactions. Uncosted WSM txn Transactions Uncosted WSM transactions in the WSM_SPLIT_MERGE_TRANSACTIONS table. Selecting Null in the „Transaction Type‟ field will select all WIP Lot Transactions. LIFO. or Perpetual costing environment the "Cost Manager" will launch an "Actual Cost Worker" (short name CMCACW) for processing resources or resource overhead transactions.

There are five tabs to select detailed information on the WIP Lot.Shop Floor Manager > Lot Transactions > WIP Lot Transactions By using the WIP Lot Transaction window. Operations and Others. Routing. Type of WIP Job Costed. Transaction processing status Transaction Type. Transaction reference descriptive text Pending Transactions Guide 16 of 32 . The main descriptive fields give detailed information on the transaction: Transaction Id. Standard transaction reason identifier Reference. Job Bill. you can view uncosted transactions. Date transaction was performed Status. Transaction Identifier Transaction Date. Transaction costing status Reason. Transaction Type Identifier Job Type. If there is more than one uncosted transactions clicking on the down arrow will toggle through these transactions.

Assembly identifier used as bill of material reference for explosions of nonstandard job Alternate. Last unit scheduled completion date Accounting Class. Inventory item Identifier for the assembly the job or schedule creates Quantity. Assembly identifier used as routing reference for explosions of nonstandard job Alternate. Standard Operation Code Step. Routing revision date Subinventory. WIP Accounting class for the job Co Product Supply. WIP Job Name Representative Job. MRP Net Quantity Fields in Bill Tab: Reference. Representative Job Flag Fields in Job Tab: Description. Date on which job is scheduled to start Completion. Available Quantity MRP Net Quantity. Date of assembly item revision used to explode the bills of material used in the job Fields in the Routing Tab: Reference. Default completion locator identifier for assemblies completed by the job Fields in Operation Tab: Job Seq. Intraoperation step Description. Routing revision for the primary assembly Revision Date. Coproducts Supply Pending Transactions Guide 17 of 32 . Alternate BOM Designator used in a Job Rev. Operation Description Dept. Default completion subinventory for assemblies completed by the job Locator. Description of the discrete job or repetitive assembly Type. Operation Sequence Number Code. Alternate Routing Designator used in a Job Rev. BOM revision for the primary assembly Revision Date.Fields common to all Tabs: Job Name. Department Code Fields in Other Tab: Start. Type of WIP Job Assembly.

if any. Errors and Validations: Whenever any one row errors out within a given group. Shop Floor Manager > Run Requests > WIP Lot Transactions Processor To find the error message review the log file of the WIP Lot Transactions Processor. you need to determine and fix what is preventing a record from being processed through the WSM_SPLIT_MERGE_TXN_INTERFACE table. Errors and warnings. WSM_STARTING_JOBS_INTERFACE (WSJI). Pending Transactions Guide 18 of 32 . To run the WIP lot transactions processor: Navigate to the WIP Lot Transactions Processor window. and WSM_RESULTING_JOBS_INTERFACE (WRJI) tables. Transactions in WSMTI are joined with the transactions in WSJI and WRJI by the HEADER_ID column in these tables. The user inserts rows into WSM_SPLIT_MERGE_TXN_INTERFACE (WSMTI). But only the transactions that actually erred out will have the ERROR_MESSAGE column containing the error message. will be written into the WSM_INTERFACE_ERRORS table.Resubmitting Uncosted WSM transactions: Running the "WIP Lot transactions Processor" (short name WSMPJUPD) will automatically pick up all the erred and pending transactions (ie. turning the profile option „MRP: Debug Mode‟ to Yes and then running the WIP Lot Transactions Processor may give a better error message in the log file. with status=3 (ERROR) or status=1 (PENDING) in WSM_SPLIT_MERGE_TRANSACTIONS). Resubmitting Pending WSM Interface transactions: To resubmit the erred transactions for processing. the user has to rectify the Error and change the PROCESS_STATUS of the required transactions from 3(ERROR) to 1 (PENDING). Choose Submit. the PROCESS_STATUS of the entire group is set to ERROR. Appropriate messages will be given in the parent and child interface tables to refer to WSM_INTERFACE_ERRORS table when there is any error. Pending WSM interface To resolve transactions in the WSM interface.

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 Pending Transactions Guide 19 of 32 .Resolution Recommended Transactions Pending Receiving Transactions: Pending Receiving Transactions are transactions that have not processed through the RCV_TRANSACTIONS_INTERFACE table.

Item description Errors. pending transactions can be viewed and deleted. Error message Order. Parent transaction type Routing. and Order Information. Receipt number Supplier. The Main Descriptive fields give detailed information on the type of transaction that the cursor is on: Receipt. Details. Order Number Parent Type. Outside Services. Source of the receipt Description.Using the Transaction Statuses window. There are four tabs to select: Transactions. Receiving routing name Pending Transactions Guide 20 of 32 .

Vendor Customer. WIP line identifier Operation Sequence. Purchase order number Rel. 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. Ordered UOM Due Date. The original Pending Receiving Transaction should be deleted through the „Transaction Status Summary‟ screen. Standard transaction reason identifier Comments.Fields common to all Tabs: Quantity. Packing slip number Fields in Order Information Tab: Order Type. Primary unit of measure of the item Fields in Details Tab: Transaction Date. WIP Job or Schedule name Line. Transaction quantity UOM. Comments Packing Slip. Purchase order release number Line. Ordered quantity UOM. Purchase order shipment number Supplier. WIP operation sequence number within a routing Department. Purchase order types Order Num. Customer Qty Ordered. WIP department name 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. Pending Transactions Guide 21 of 32 . Duplicate transactions can be deleted through the „Transaction Status Summary‟ screen by clicking on the transaction line and then clicking on the delete icon. Expected due date Fields in Outside Services Tab: Job/Schedule. Date of transaction Reason. Purchase order line number Shipment.

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. Location: Interface transaction location information. which provide detailed information to help you resolved pending transactions. you can view. correct and resubmit transactions received through the open interface. There are four tabs to view information: Error. 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. Select a tabbed region to display a type of information: Error: Interface transaction error information. Pending Transactions Guide 22 of 32 . edit. Intransit and Other. Location. Source.

If the line is not in error. Line item request ID Transaction Mode. Fields Common to all Tabs: Item. Transaction quantity in primary unit of measure Date. Lock Flag. such as WIP Job or Schedule. Process Flag. Full explanation of the error that occurred when attempting to process the line item. Line item‟s transaction header ID. The Main Descriptive fields give detailed information on the type of transaction that the cursor is on: Primary UOM. Locator referenced by the line item. Others: Miscellaneous header and costing information. Header ID. Method used to process the line item. such as concurrent processing. Fields in the Location Tabbed Region: Locator. Inventory item description Error Explanation. is available for processing. Indicates if the row and its child rows are locked to update from other processes. This field will display if you have Oracle Pending Transactions Guide 23 of 32 . Request ID. Fields in the Error Tabbed Region: Error Code. Full explanation of the error that occurred when attempting to process the line item Lot/Serial (Button). Transaction quantity in terms of the primary uom of the item Qty. All failed transactions can be resubmitted by clicking on „Tools‟ resubmit all. Inventory item referenced by the line item. or processed with an error. Transaction Date Item Description. Source type of the transaction. when checked and saved the failed transaction line will be resubmitted. Used if transaction is associated with a Lot or Serial Number Submit (Box). Indicates whether the concurrent manager has success-fully processed the row. The LPN put away. Transaction Source Type. Error Explanation.Source: Interlace source information Intransit: Interface intransit shipping information. Interface ID. then it will have to be resubmitted using SQL script. Interface ID that is assigned by the external system to track a set of transactions through the Oracle Inventory transaction interface processor. and it cannot be resubmitted using the Submit check box. LPN. Code describing the error on the last attempt to process the line item.

Subinventory. Subinventory referenced by the line item. Destination location. Oracle Work in Process department code for the line item Employee Code. Transfer Org. Source of the transaction. The transaction type. Organization name of the destination organization Transfer Subinventory. Organization code of the organization referenced by the line item. The transaction reason. The freight carrier for the transfer Shipment Number. such as account number Source Line ID. Account used by Oracle Purchasing to receive the item Pending Transactions Guide 24 of 32 . General ledger account charged with the value entered in the Transportation Cost field Transportation Cost. such as freight carrier charges Waybill Airbill. Transaction Action Name. Supplier. Date the transaction was entered for processing. Employee who entered the transaction Encumbrance Account. Cost to process the transaction. Transaction Quantity. Distribution account for the line item. The transaction action Transaction Cost. Reference text describing the transaction Transaction Type. User–entered line ID of the source code for the line item. Number of containers in which the material is stored Expected Arrival Date. Organization code of the destination organization Transfer Org Name. Unit of measure used in the transaction. and you are working with a WMS enabled organization. Name.Warehouse Management installed. Source of the transaction. Distribution Account. Cost to process the transfer Transportation Account. Date you expected to receive the material at the destination organization Freight Code. Transfer Locator. Reason Name. Cost to physically transfer the material. Intransit Tabbed Region: Containers. Transaction Date. Revision of the inventory item referenced by the line item. Planning Organization Code Source Tabbed Region: Transaction Source. such as account number. Organization Name Revision. The waybill or airbill number for the transfer Others Tabbed Region: Department. Source Code. Transaction Reference. Destination subinventory. Number uniquely identifying the item or items transferred Transfer Cost. Supplier Planning Org. Quantity of the transaction Transaction UOM. Org.

Demand Source Line. errors. Line item detail identifier of the demand source. To Task Number. The task number. and status of concurrent and interface managers/workers. Operation Seq Number.1 Oracle Inventory Support Svc Req Instrumentation for Stuck Transactions MTI (INVMTI115h.for the period in question (INVPeriodClose115.1 In the Transaction Interface window. Task Number.sql) Note: 206576. Line number from the demand source. Inventory Period Close Diagnostic Test . Source of the demand for the line item.Encumbrance Amount. Percentage used to update the item cost. The expenditure type. Demand Source Delivery. New Average Cost. Resubmitting Pending Material Transactions Before re-submitting records through the Transactions Interface Form. The expenditure organization Expenditure Type. Transaction Source Line ID. The following Diagnostic Scripts should be used to identify data. check the Submit option next to the transactions you want to resubmit or choose Resubmit All. Amount encumbered. Number associated with the job or schedule referenced by the line item Percentage Change. The to task number. use the Resubmit All button to select all transactions for processing and then selectively deselect individual transaction you do not want to resubmit. Source Task Number. User–entered line ID of the source code for the line item. such as an account number. The project number. If you have many transaction to resubmit. Save your work to submit the transactions for processing. when the purchase order or requisition was approved Expenditure Org. Pending Transactions Guide 25 of 32 . you can gather information regarding your data and the Inventory Transaction Managers and workers. The source task number. reserved against funds. To Project Number. such as Sales Order line number. Demand Source Header ID.sql) Note: 209928. Source Project Number. Value Change. Project Number. Line item detail identifier of the demand source. Transaction Source Delivery ID. The to project number. Recalculated average unit cost for the item. Amount used to increment the current inventory value. The source project number.

1. To get more debug information in the Log file and Debug file use the following profiles: Please enable inventory debug per Metalink Note. ERROR_CODE = NULL WHERE PROCESS_FLAG = 3.148651. 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. LOCK_FLAG = 2. By default. TRANSACTION_MODE = 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.db. Please ensure the debug file is set with a directory existing in utl_file_dir that can be found with this sql: SQL> SELECT value FROM v$parameter WHER name = 'utl_file_dir'. The details follow for your convenience: INV: Debug Trace = YES INV: Debug Level = 11 INV: Debug File = Please set it with the full path where you would like to write the debug messages.The failed records can also be resubmitted via the following SQL statement: SQL> UPDATE MTL_TRANSACTIONS_INTERFACE SET PROCESS_FLAG = 1. it will be written in /tmp/invdbg. Details of pending move transactions can be viewed through the applications by navigating to the pending move transactions form: Pending Transactions Guide 26 of 32 . 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.

Transactions Id. Operations. 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 tabs to select information on the move transaction. Transactions and Comments and Scrap Account which provide detailed information to help you resolve pending move transactions. Pending Transactions Guide 27 of 32 . Fields Common to all Tabs: Resubmit (check Box). Concurrent Request. You can view error messages associated with failed records. update. Column indicates the name of the column in the wip move transaction interface that failed validation. Transaction Identifier Errors (button).WIP > Move Transactions > Pending Move Transactions Through the Pending Move Transactions window you can view. delete. Source. Error messages can assist you in updating failed records before resubmission. When Checked and saved the erred transaction line will be resubmitted. Job or Schedule Name. Processing. The error details of erred transactions can be viewed by selecting the transaction and then clicking on the Errors button. and resubmit Move transaction records that have failed validation and remain in the Open Move Transaction Interface table (WIP_MOVE_TXN_INTERFACE). Message indicates why the transactions failed. if the line is not in error it can not be resubmitted using the Submit check box but will have to be resubmitted through a sqlplus script.

From operation sequence number Department. Line name Assembly. Line items request ID Phase. To intra-operation step Fields in Transaction Tab: UOM. Overcompletion quantity specified in the transaction UOM Date. Pending Transactions Guide 28 of 32 . Transaction processing status Message. General Ledger account charged when material is scrapped Erred transactions will have the Transactions ID and Group ID populated and the Status will be “Error”. Date transaction was performed Type. Transaction quantity (between operations) Overcompletion Quantity. Transaction type Fields in Comments and Scrap Account Tab: Reason. From intra-operation step To Operation: Seq. Concurrent Message Fields in Job or Schedule Name: Organization. WIP job or repetitive assembly name Line. Pending transactions will have the Transactions ID and Group Id fields blank and the Status will be “Pending”. To department code Step. Organization code Job or Schedule Name. Code of the shop floor control system that generated the transaction record (null if created by Oracle Work in Process) Source Line. Unit of measure used in transaction Quantity. Identifier used by source shop floor control system (null if created by Oracle Work in Process) Created By. From department code Step. To operation sequence number Department. Standard transaction reason name Reference.Fields in Source Tab: Source Code. Inventory item Identifier for the assembly the job or schedule creates Fields in Operations Tab: From Operation: Seq. Transaction processing phase Status. User name of the person who created the record Fields in Concurrent Request: Request ID. Transaction reference descriptive text Scrap Account.

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. 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. Now save your work.sql) Note: 206576.for the period in question (INVPeriodClose115.1 Pending Shipping Transactions Troubleshooting Techniques Note: 262979. Deleting Pending Move Transactions Records: To delete pending move transactions. Resubmitting the transactions with the profile option „MRP: Debug Mode‟ set to „Yes‟ may provide even more information in the log file. When you delete transaction records. PROCESS_STATUS = 1 Where TRANSACTION_ID = „&TRANSACTION_ID‟. The records can also be resubmitted using the following SQL statement: SQL> UPDATE WIP_MOVE_TXN_INTERFACE Set GROUP_ID = NULL. their corresponding error messages are also deleted. 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: Please review the following notes for Unprocessed Shipping Transactions: Inventory Period Close Diagnostic Test . either checks the transaction‟s Resubmit check box to resubmit one record or chose Select All from the Special Menu. UNPROCESSED SHIPPING TRANSACTIONS To resolve unprocessed shipping transactions. You can delete failed records that have a processing status of Error regardless of their processing phase. in the Pending Move Transactions window.Resubmitting Failed Move Transactions: In the Pending Move Transactions window.1 Pending Transactions Guide 29 of 32 . TRANSACTION_ID = NULL. select the transaction choose Delete from the Edit Menu.

Order Management > Shipping > Transactions Pending Transactions Guide 30 of 32 .

and Contents by Line/Lpn. delivery lines. Transactions that are in a in a status of „Shipped‟ have been shipped confirmed but have not yet been interfaced to Oracle Inventory. CONCLUSION When resolving and working with Pending Transactions users must collect and identify data in order to address the source product and complete the Period Close process. pick releasing. 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. Reviewing the log file will supply an error message if the concurrent process does not complete successfully. stops. deliveries. Stops. 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”. and ship confirming. Pending Transactions Guide 31 of 32 . There are four tabs to select they type of information: Trips. Trip Stop can submit these concurrent processes. and LPNs (Containers). Contents by Delivery. The Trip Stop of the pending shipping transaction can be found in the Shipping Transactions window under the Stops tab in the Trip column. These must be processed and resolved before the period is closed. It enables you to plan and manage trips.The Shipping Transactions window provides a consolidated workbench for three major shipping functions: planning.

com Copyright © 2003. Worldwide Inquiries: Phone: +1. nor subject to any other warranties or conditions. Engineering. Warehouse Management Systems. Oracle is a registered trademark of Oracle Corporation and/or its affiliates.S. Experience includes Inventory. Pending Transactions Guide July 2004 Author: Edgar Arroyo Contributing Authors: Steven V.7200 www.506. and Product Lifecycle Product Applications. CA 94065 U.7000 Fax: +1. We specifically disclaim any liability with respect to this document and no contractual obligations are formed either directly or indirectly by this document. Michele Veilleux Oracle Corporation World Headquarters 500 Oracle Parkway Redwood Shores. All rights reserved. Bills of Materials. without our prior written permission. Oracle. whether expressed orally or implied in law. Other names may be trademarks of their respective owners.650. Mobile Wireless Applications. Oracle Support Services. This document is not warranted to be error-free. including implied warranties and conditions of merchantability or fitness for a particular purpose. Pending Transactions Guide 32 of 32 .A.oracle.About the Author Edgar Arroyo. Cooper. This document is provided for information purposes only and the contents hereof are subject to change without notice. for any purpose.650. electronic or mechanical.506. This document may not be reproduced or transmitted in any form or by any means. Principal Support Enginer.

Sign up to vote on this title
UsefulNot useful