Resolving Period Close Pending Transactions in R12

A troubleshooting guide for clearing pending transactions before closing your inventory period.

Purpose of this Guide

One of the most common challenges when closing an Inventory period in Oracle EBS R12 is the presence of pending transactions. The system will not allow you to close a period if there are transactions that have not been fully processed. This guide, based on Oracle's official documentation (Doc ID 1069492.1), provides a structured approach to identifying, troubleshooting, and resolving these pending records.

Affected Modules

This issue can be caused by pending transactions in any of the following modules:

Oracle Inventory Management

Oracle Cost Management

Oracle Work in Process (WIP)

Oracle Purchasing

Oracle Shipping Execution

Oracle LCM (Landed Cost Management)

Types of Pending Transactions

Pending Material Transactions

Standard inventory transactions (subinventory transfers, issues, etc.) that have not been processed.

Uncosted Material/WSM Transactions

Transactions that have been processed by the inventory manager but not by the cost manager.

Pending Receiving Transactions

Purchase order receipts that are stuck in the receiving interface.

Unprocessed Shipping Transactions

Sales order shipments that have not been successfully interfaced to inventory.

Pending WIP Costing Transactions

Resource, material, or move transactions related to manufacturing jobs that have not been costed.

Pending Shop Floor Moves

Transactions related to the movement of assemblies within a WIP job.

Pending LCM Interface Transactions

Transactions from Landed Cost Management that are waiting to be interfaced to Inventory and Costing.

General Troubleshooting Steps

Locate the Transactions

Use the Inventory accounting periods window or specific diagnostic scripts to identify which transactions are pending and in which module.

Find the Error Message

Once located, query the transaction in its respective interface or error table to find the specific error message explaining why it failed.

Resolve the Error

Based on the error message, take corrective action. This could involve correcting setup data, fixing a data entry mistake, or opening a closed period.

Resubmit the Pending Record

After fixing the underlying issue, resubmit the transaction through the standard interface forms. In some rare cases, a data fix script may be required to resubmit.

Detailed Guide: Resolving Unprocessed Shipping Transactions

Identifying Unprocessed Shipping Transactions

To resolve this, you need to find shipping transactions that are 'Shipped' but not yet interfaced to Order Management or Inventory. These are stored in the WSH_DELIVERY_DETAILS table.

Step 1: Find Shipped Transactions

Navigate to the Shipping Transactions window to query for transactions with a 'Shipped' status for the period you are trying to close.

Navigation: Order Management > Shipping > Transactions

The Shipping Transactions window provides tabs for Trips, Stops, and Contents, allowing you to manage all aspects of your shipments.

Step 2: Run Interface Concurrent Processes

Transactions with a 'Shipped' status must be processed by two key concurrent programs to interface them correctly. Run them in the following order:

Order Management Interface
Inventory Interface

Navigation to run these processes: Order Management > Shipping > Interface > Run

Step 3: Review Concurrent Request Logs

These programs can be submitted by the Trip Stop. You can find the Trip Stop for the pending transaction in the 'Stops' tab of the Shipping Transactions window. If a process fails, review its log file to find the specific error message. Resolving this error and re-running the interface will clear the pending transaction.

Detailed Guide: Resolving Pending Shop Floor Move Transactions

Identifying Pending Shop Floor Moves

Unprocessed move transactions are records in the WIP_MOVE_TXN_INTERFACE table. You can manage them through the Pending Move Transactions window.

Step 1: Find Pending Move Transactions

Navigate to the Pending Move Transactions window to find records that have failed validation.

Navigation: WIP > Move Transactions > Pending Move Transactions

This window allows you to view, update, delete, and resubmit move transaction records.

Step 2: Analyze and Fix Errors

For failed records (Status: 'Error'), click the Errors button to see a detailed message. Use the information across the various tabs (Source, Job Name, Operations, Transaction) to understand the context and fix the underlying data or setup issue.

Step 3: Resubmit or Delete Transactions

Once the issue is fixed, you can resubmit the transaction:

From the form: Check the 'Resubmit' checkbox for the transaction and save your work.
Using SQL: For transactions not in an error state or for bulk updates, you can use the following SQL script to mark them for reprocessing.

SQL/PLSQL Code

Update WIP_MOVE_TXN_INTERFACE
Set GROP_ID = NULL,
    TRANSACTIONS_ID = NULL,
    PROCESS_STATUS = 1
Where TRANSACTION_ID = <&TRANSACTION_ID>;

Warning on Deletion

Do not delete records that failed in the Backflush setup phase. Deleting these records can lead to data corruption as the backflush processing will never occur. Only delete records if you are certain they are invalid and cannot be fixed.

Conclusion

The key to resolving period close issues is a methodical approach. By systematically checking for pending transactions in each of the key areas (Material, WIP, Receiving, Shipping), you can identify the root cause of the error, fix it, and resubmit the transaction. If a transaction is pending but shows no error, it may require a specific script from Oracle Support to resubmit. Always refer to the official Oracle documentation or log a service request for complex cases.

Disclaimer: This guide is based on our experience and official Oracle documentation (Doc ID 1069492.1) to be understandable for developers and functional consultants.