6/17/2019 Document 837777.

1
Copyright (c) 2019, Oracle. All rights reserved. Oracle Confidential.

FAQ: Troubleshooting Cross-Product Issues Between Shipping and Inventory (Doc ID

837777.1)

In this Document

Purpose
Troubleshooting Steps
1. OVERVIEW
2. COMMON CROSS-PRODUCT ISSUES
2.1. Stuck Transactions in the Inventory Table MTL_TRANSACTIONS_INTERFACE with ERROR_EXPLANATION
"ORACLE ERROR"
2.1.1. How to View the Transactions in the Application
2.2. NEGATIVE BALANCES NOT ALLOWED
3. RESOURCES
3.1. Debug/Profiles & Trace Files for Data Analysis
3.2. Diagnostics
3.3. Demos/White Papers/Webinars
3.4. Critical and Recommended Patch List (**Work in Progress**)

References

APPLIES TO:

Oracle Inventory Management - Version 11.5.10.0 and later

Oracle Shipping Execution - Version 11.5.10.0 and later
Information in this document applies to any platform.

PURPOSE

To provide assistance and guidance in the resolution for some common cross-product issues within Inventory and
Shipping.

TROUBLESHOOTING STEPS

1. OVERVIEW

The purpose of this note is to provide information to users about the best method of troubleshooting, diagnosing and
resolving cross-product issues within Inventory and Shipping.

For troubleshooting guidelines from the shipping perspective please see the shipping FAQ Note 863761.1

2. COMMON CROSS-PRODUCT ISSUES

2.1. Stuck Transactions in the Inventory Table MTL_TRANSACTIONS_INTERFACE with

ERROR_EXPLANATION "ORACLE ERROR"

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=mh9dhtg15_119&id=837777.1 1/5
6/17/2019 Document 837777.1

Oracle Error is a generic error which can sometimes be seen in the Error Explanation column or in a debug log. Most of the
time, this indicates that the transactions are duplicates.

To find and resolve Duplicate Sales Order Issue Transactions, please review the following note: Note 1472074.1 -
Inventory Standard Datafix Instruction #17: Fixing Duplicate Sales Order Transactions In MTI, MMTT and MMT

Note: Transactions stuck in the table MTL_TRANSACTIONS_INTERFACE will not prevent the period from closing,
unless they are sales order issue transactions which are associated with Unprocessed Shipping transactions.

2.1.1. How to View the Transactions in the Application

Details of interface transactions can be viewed through the application by navigating to the Transaction Open Interface
form:

Inventory -> Transactions -> Transaction Open Interface

2.2. NEGATIVE BALANCES NOT ALLOWED

There can be many problems which will cause the Negative Balances Not Allowed Error.

One reason for negative balances is that there was sufficient quantity on hand and transactable when the order was pick
released and the delivery details were staged, but since that time somehow the quantity in the Staging Subinventory was
reduced. This can happen when the items that were staged are not reservable. Recommended fix: make the items
reservable, and create reservations for these items when the sales order is entered.

A. Possibles Causes:

1. There is not enough available quantity.

Many customers confuse the Onhand Quantity and the Available Quantity. The available quantity is the Onhand less
any reservations, allocations, and any pending transactions for the item. As such, the first thing you should do is to
verify the available Quantity. There are several methods to do this. One is to use the script onhand.sql from Note
268974.1 - To Review The Stock Picture For an Item in a Given Organization / Subinventory.

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=mh9dhtg15_119&id=837777.1 2/5
6/17/2019 Document 837777.1

Itemqty.sql Output
==================

The following headings will be used in the output:

qoh quantity on hand
rqoh reservable quantity on hand
qr quantity reserved
qs quantity suggested
att available to transact
atr available to reserve

The output of itemqty.sql will look like this:

Quantity on hand100
Quantity res oh100
Quantity res 0
Quantity sug 0
Quantity ATT100
Quantity ATR100

From the above output, you will see the onhand on the 1st line, the quantity reserved on the 3rd line. The quantity
suggested (allocations or pending transactions) on the 4th line, the available to transact(ATT) on the 5th line and the
available to reserve(ATR) on the 6th line.

If the ATT is not large than the transaction quantity on the pending transaction, then the Negative Balances error will
be received.

This could be legitimate and you may not have enough available to transact. If so, then you will need to do a receipt
to increase the available quantity.

2. Outstanding Reservations

Itemqty.sql Output
==================

The following headings will be used in the output:

qoh quantity on hand
rqoh reservable quantity on hand
qr quantity reserved
qs quantity suggested
att available to transact
atr available to reserve

The output of itemqty.sql will look like this:

Quantity on hand100
Quantity res oh100
Quantity res
Quantity sug 0
Quantity ATT100
Quantity ATR100

If you see the Quantity reserved (QR) and you believe you have incorrect reservation records, that is reservations
from closed or cancelled sales orders, then you should run the appropriate script provided by development as
outlined in Note 1322105.1 (Old Note 199887.1) - i2471362.sql - Remove old reservations. See the note for more
details about the datafix and root-cause patches by version.

3. Pending Transactions

Itemqty.sql Output
==================

The following headings will be used in the output:

qoh quantity on hand
rqoh reservable quantity on hand

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=mh9dhtg15_119&id=837777.1 3/5
6/17/2019 Document 837777.1
qr quantity reserved
qs quantity suggested
att available to transact
atr available to reserve

The output of itemqty.sql will look like this:

Quantity on hand100
Quantity res oh100
Quantity res 0
Quantity sug 25
Quantity ATT100
Quantity ATR100

If you see the Quantity suggested (QS) has a value, then there are pending transactions in
mtl_material_transactions_temp which would need to be investigated and resolved. Please note that the quantity for
pending transactions is held by the code so that those transactions can process. A common type of pending
transaction which will show up here is Move Order Allocation records.

If the ATT is present but ATR is 0, this could indicate that the subinventory or item is not reservable. Please verify
the subinventory and item setup.

4. Cost Group Problems

Cost group issues can also produce Negative Balances Not allowed errors. Please verify the cost group setup
using Note 367511.1 - Fix for Cost Group ID when Negative Balances Not Allowed Error.

     5. Move Order Allocations

Orphan move order allocation records can get stuck in mtl_material_transactions_temp. These are normally
transaction_type_id = 52 and 64 with a transaction_status = 2. If you see these types of transactions pending
in the script output from mtl_material_transactions_temp, please do the following.

Navigate to Move Orders -> Transact Move Orders and query the move orders for the item involved. Then
either Transact the move order or if you do not want to at this time, then you can do Tools -> Cancel
Allocations.

If the move order is not available to transact in the Transact Move Order form, then it is likely that the move
order line status is already closed. (This would have a status of 5 in mtl_txn_request_lines.) In this case, the
correct clean up script (INVCLRMO.sql or INVCLRMOv115.5.sql) would need to be run. This is detailed in Note
169677.1 -  How to Clean Corrupt (Orphan) Move Order Records From the Database.

There is also the possibility that the move orders have a status of Cancelled by Source. This would have a
status of 9 in mtl_txn_request_lines. Please review Note 396523.1 - Stuck Pending Move Order Transactions
(MMTT) / Available Shows Zero Because Records Are Stuck In MMTT, Move Order Cancelled By Source in
Transact Move Order (INVTOTRX) Form. In some cases these allocations can be fixed via the form. In other
cases a bug will need to be logged to get development permission to use the script
cancel_source_allocation.sql.

3. RESOURCES

3.1. Debug/Profiles & Trace Files for Data Analysis

Note 290432.1 How to Create a Debug File in Shipping Excecution

Note 148651.1 How to get Debug Information for Inventory Material Transactions
Note.338291.1 Howto Enable WMS / MSCA Logging
Note 277655.1 SQL*Trace with WMS-MWA: Mobile Applications (Tracing SQL Via Database Trace To Allow For
TKPROF Of Results Of User Actions)

3.2. Diagnostics

Note 133464.1 - HTMOMSE Sales Order Diagnostic Script

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=mh9dhtg15_119&id=837777.1 4/5
6/17/2019 Document 837777.1

Item Data Collection:

Note 223702.1 - Inventory Item Setup Data Collection Tool
Note 398723.1 - Oracle Inventory Item Data Collection Data Collection Test
Apps Check
Note 156860.1 - OMCHECK.SQL Oracle Order Management Diagnostic Tool
Note 276207.1 - Diagnostics : Apps Check
LPN
Note 228600.1 - WMSCheckLPN.sql : Script to Query Data in all LPN-related Tables for a License Plate
Number ( LPN )
Note 298052.1 - Oracle Warehouse Management LPN Transaction Data Collection Test
Note 402245.1 - Receiving Transactions Data Collection Script rcv11i_sa.sql
Note: 221211.1 - Inventory Move Order Transaction Diagnostic
Transaction Open Interface
Note 398700.1 - Oracle Inventory Open Interface Transactions (MTI) Data
Collection Test
Note 209928.1 - Oracle Inventory Support Svc Req Instrumentation for Stuck
Transactions MTI
Note 262979.1 - Unprocessed Shipping Transactions Troubleshooting Techniques
Period Close
Note 206576.1 - Oracle Inventory Period Closing Activity Test
Note 246467.1 - BDEprdcls.sql - CstCheck.sql Diagnostics Scripts

Inventory Diagnostics Release 12

Note 463602.1 - Inventory Item Data Collection Setup Test

Note 463601.1 - Inventory Organization Data Collection Setup Test for a specific organization.
Note 463574.1 - Inventory Pending Transactions Setup Test
Note 463577.1 - Pending Transactions Data Collection Tool
Note 463580.1 - Inventory Allocations for canceled Sales Order Setup Test
Note 463581.1 - Inventory Move Order Orphan Allocations Setup
Note 463673.1 - Oracle Order Management Sales Order Setup Test (can also use Note 133464.1 - Script
HTMomse12.sql.
Note 463637.1 - Inventory Internal Sales Orders Data Collection Test
Note 463636.1 - Inventory Purchase Orders Data Collection Test
Note 246467.1 - Inventory Period Close Diagnostic Test – Script bdeprdcl.sql

WMS Diagnostics Release 12

Note 463601.1 - Inventory Organization Data Collection Setup Test for a specific organization (for WMS).
Note 228600.1 - WMS LPN Diagnostic, use Attachment File WMSCheckLPN.sql

3.3. Demos/White Papers/Webinars

Note 418492.1 - How to Process Standard Sales Orders in Order Management for Application Release 11.5.10
WMS TOI - http://logistics.us.oracle.com/collat/toi/index.html has the demos and white papers
Note 262979.1 - Unprocessed Shipping Transactions Troubleshooting Techniques
Note 430528.1 - How To Use the HTMomse11i Output To Resolve Pending Sales and Move Order Transactions

3.4. Critical and Recommended Patch List (**Work in Progress**)

Didn't find what you are looking for?

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=mh9dhtg15_119&id=837777.1 5/5