Document 279205.

1 10/5/18, 5(42 PM

Copyright (c) 2018, Oracle. All rights reserved. Oracle Confidential.

Current Onhand Quantity and Total Transactions History Quantity Mismatch Diagnosis (Doc
ID 279205.1)

In this Document

Symptoms
Changes
Cause
Solution
References

APPLIES TO:

Oracle Inventory Management - Version 11.5.10.CU2 and later

Information in this document applies to any platform.
The information contained on this document apply for Application Releases from 11.5.10.2 and higher.
This is an extension to the topics in Datafix Note 568012.1

SYMPTOMS

You may suspect a quantity mismatch when any of the following (but not limited to) errors are seen in the application:

There is not enough quantity... at pick release a Sales Order, but physical quantities are in stock.
Negative Balances not Allowed.... at Sales Order Issue.
Insufficient quantity to perform the requested operation... at load task.
Quantities are not available for transactions.
Invalid LPN... at pick drop (outbound)
Quantity reports does not match physical inventory

CHANGES

CAUSE

This is described in Bug 5085603 INCTCW Getting Intermittent Locks

There is a mismatch between onhand quantity and the transactions table.
This results in incorrect reporting of transaction information. This may be just part of the cause.
Even after transactions and onhand match, it does NOT guarantee that the register will match the distribution
report. We might have other things to fix from a costing point of view next.
This has been fixed in earlier releases and you can find below the available patch for your current release.

SOLUTION

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=15anly2mci_1098&id=279205.1 Page 1 of 3
Document 279205.1 10/5/18, 5(42 PM

If you think your onhand is not accurate and you may be facing a quantity mismatch, you can try the following steps as
a starting point of analysis. Provide the output for the following queries in excel format with column headings:

Note: The standard scripts try to compare aggregated quantity in MMT with MOQD. (from the start date). If a
purge was run, some of the transaction history is lost, so, the aggregated qty in MMT will not match MOQD from
the scripts. In this scenario, it is technically impossible to provide a datafix for onhand quantity. The only
workaround / alternative here is to perform a cycle count or Misc Receipt to fix any missing quantity.

1. Identification Scripts and Datafix:

a. Get the script which will identify if you have this issue: mmt_moqd_mismatch_at_sublevel.sql If this script returns
data, then please continue with these steps.

b. Download the following script (attached to this note) which is intended to validate if the data on your system is
eligible to be fixed (i.e. no purge has been run):

retrieve_validation_data.sql

c. Download and unzip the Patch 18839067 to obtain the following files which you should place in a folder on your
server where the database resides:

invmtmqt.sql
invmtmqd.sql

* or Run script invmtmqd_for_item.sql to specify the particular item.

Note: Oracle Development also released INVMTMQD.sql by item. See invmtmqd_for_item.sql. The script will prompt
for organization and item id.

Continue with the steps listed under MMT MOQD Mismatch in Note 568012.1 - FAQ: Inventory Standard Datafixes.
If issue is not resolved:

2. Create an SR and Upload Data to Support:

Execute the following queries

a. Run the script retrieve_validation_data.sql and upload the results in excel format with column headings.
b. Run the scripts invmtmqt.sql and invmtmqd.sql in the given order
c. Execute the following query and upload the results in excel format with column headings.

select * from temp_disc_inv_cg_loose;

d. Execute the following query to obtain the root cause file version:

set serveroutput on;

execute fnd_aolj_util.getClassVersionfromDB('oracle.apps.inv.transaction.server.QtyManager');

3. Available Patch:

Release 11i:
Apply Patch 13772375 if your file version is lower than QtyManager.java 115.106.115100.38

Release 12:
A root-cause patch was released on R12.1.3 and included in the latest rollup (RUP5 and higher). The latest rollup is

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=15anly2mci_1098&id=279205.1 Page 2 of 3
Document 279205.1 10/5/18, 5(42 PM

Patch 22598102 Inventory RUP 14 (R12.INV.B.delta.14). There was also a one-off Patch 13864094 -
1OFF:13772375:12.1.3:12.1.3:AFTER APPLYING PATCH:9241879,MMT-MOQD MISMATCH STILL fixing the issue in
QtyManager.java 120.26.12010000.26.

* New Root Causes of this issue is under investigation in Bug 9279555

REFERENCES

BUG:6205118 - DATAFIX: CSTRINVR DOES NOT REFLECT QTY IN INVMATWB

BUG:8672584 - ADD PROGRAM RUN TO TABLE MTL_PURGE_HEADERS
BUG:5085603 - **INCTCW GETTING INTERMITTENT LOCKS
NOTE:568012.1 - FAQ: Inventory Standard Datafixes
Didn't find what you are looking for?

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=15anly2mci_1098&id=279205.1 Page 3 of 3