Professional Documents
Culture Documents
Document 568012
Document 568012
In this Document
Goal
Frequently Asked Questions (FAQ)
1. Where do I get the datafixes?
2. Can I run the datafix proactively?
3. What are the Top 5 Datafixes?
4. Why do I need to keep running the same datafixes over and over?
5. What are other common datafix notes?
6. Where can I discuss datafixes?
Solution
A. STANDARD DATAFIXES
1. Reservations
2. Move Orders
3. Zero Onhand
4. Inventory Items
5. Duplicate Bills of Material (BOM)
6. Inventory Manager
B. SR DATAFIXES
1. MMT MOQD Mismatch
2. Closed Move Orders
3. Missing Move Orders
4. Marked Serial Numbers
5. Serial number with leading/trailing spaces
6. Lot number with leading/trailing spaces
7. Corrupted Onhand related to Lots
8. Physical Inventory Adjustment Errors
9. Sales Order reservations created with Zero demand header
10. Error while costing Material transactions
11. Incorrect Demand header id
12. Onhand records with locator populated when sub inventory is not locator controlled
13. Locator stamped on onhand record is different from the one existing in mtl_item_locations for the subinventory
14. Onhand have records with Null Locator when Sub inventory is locator controlled
15. The Update Standard Costs program is failing with the following error:Invalid value for intransit_owning_org_id in table
MTL_SUPPLY
16. Stuck transaction with 'Error occurred while relieving reservations' due to incorrect or negative availability
17. Duplicate transactions in MTI already posted in MMTT and MMT and in MMTT already posted into MMT
18. View material transactions screen raise error APP-FND-00756:CANNOT FIND COMBINATION CCID=40225 CODE=MKTS
19. Negative TRANSACTION_SOURCE_ID in the inventory transactions table (MTL_MATERIAL_TRANSACTIONS)
20. 'CST_INVALID_INTERORG' Error while costing Material transactions
21. Sales Order Issue transaction missing in MTI and MMT for a drop ship PO receipt and Sales Order line Shipped Qty not updated
22. Missing move order header
23. Missing record in MTL_SALES_ORDERS
1 of 14 1/10/2018 11:44 PM
Document 568012.1 https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state...
References
APPLIES TO:
GOAL
Answer: Many of the datafixes are already available now downloadnig from a note. Log a service request if the datafix is not listed.
Note: Many datafixes relate to period close. You could review Note 357997.1 to see what tables are involved in period close and the
"pending transactions" screen. So far, we have gotten approvals to post some but not all of the standard datafixes. If the datafix is available,
it will be listed or a related note will link to the details.
Yes, you can identify data issues and fix issues before users report them. If you also install the root-cause patches, you could avoid the issue
going forward too. A proactive "Inventory Analyzer" script is being developed via Note 1499475.1 looking for data issues, missing critical
patches, and performance concerns. See more in Note 1499475.1.
4. Why do I need to keep running the same datafixes over and over?
Answer: Our goal is to FIX the cause of the data corruption so you do not experience the issue anymore. The datafix itself is a quick fix for
you to get your business up and running again. If you can replicate any data corruption, please log a Service Request and we will work with
you to ensure the problem is corrected.
2 of 14 1/10/2018 11:44 PM
Document 568012.1 https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state...
Use the communities to discuss datafixes. This is an example thread where we ask for your input:
https://community.oracle.com/thread/3030257
We also had a webinar presentation in February 2014 on Published Standard Datafixes called "Smoother Period Close With Inventory
Standard Datafixes" - Powerpoint.
SOLUTION
Yes, there are a number of standard datafixes available for the inventory application. There is also a set of standard identification scripts in
Note 330284.1. Suggest you run those for your specific area like serial numbers. We will continue to grow this note listing them. Some are
available directly for customers and others require logging a Service Request to get the datafix. We will try to keep this page updated going
forward.
WARNING: Remember to NOT ONLY apply the datafix but any related root cause patch to avoid the issue going forward! Also
periodically review the Recommended Patch List (RPL) via the Patches and Updates tab on MyOracleSupport. This lists patches for your
environment that Oracle Development recommends applying. Also note that you can find the latest Inventory Rollup (RUP) in Note
726226.1.
A. STANDARD DATAFIXES
1. Reservations
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. Here is a quick overview of some patches available:
In R12.1.1, Patch 9252341:R12.INV.B (as forward port for patch 8826082) was released with INVVRVAB.pls 120.12.12010000.6.
In R12.0.x, Patch 8826082 was released with INVVRVAB.pls 120.12.12000000.4 for one cause of orphan reservations.
In R11.5.10, this issue was fixed with one-off Patch 6121372 INVRSV3B.pls 115.129.115100.14. This version was already included
in INV RUP5 and above.
In 11.5.9, this issue was fixed with Patch 3827307 INVRSV3B.pls 115.106.11590.7.
2. Move Orders
Purge Move Orders: For 11.5.10 and above, there is a purge move order concurrent program. The purge will remove older move
orders. However, it does not remove orphan move orders.
Note 169677.1 INVCLRMOv115.5.sql or INVCLRMO.sql - Clear old orphan move orders. Avoid the issue in the future with Patch
5958760 from the recommended patch list. (We also have an Internal bug logged to investigate any new occurences of this issue in
RCA Bug 9137821 for R12 and Bug 9293096 for R11.5.10.)
Note 301524.1 INVINBUP.sql to create missing move order lines. See section B-3: Missing Move Orders for new notes on this for
3 of 14 1/10/2018 11:44 PM
Document 568012.1 https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state...
3. Zero Onhand
4. Inventory Items
There are two notes related to multiple bills of material (BOM) found for the same item. The first attempts to correct the bill and delete
using standard bill forms. The second uses the Oracle Diagnostics to check for the duplicates. The Oracle Diagnostics provide the delete.
The second note also provides the root-cause patch to prevent the issue in the future.
Note.357785.1 Duplicate Bills Of Material Can Be Created Same Item/Org/Alternate Designator Combination
Note.370841.1 Find Two Bills of Material (BOM) for the Same Item (BOMFDBOM)
6. Inventory Manager
Note 740039.1 Timeout is 45 minutes but expect it to be 0 minutes. Note provides fix.
B. SR DATAFIXES
** Initially requiring a Service Request (SR), many Section-B datafixes NO LONGER require service requests and notes are referenced that
include the fix directly...
Many of the datafixes have been introduced in notes where you can directly download them.
Note: This section earlier ONLY listed datafixes that need a service request (SR). This is no longer the case.
4 of 14 1/10/2018 11:44 PM
Document 568012.1 https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state...
14. Onhand have records with Null Locator when Sub inventory is locator controlled
15. The Update Standard Costs program is failing with the following error:Invalid value for intransit_owning_org_id in table MTL_SUPPLY
16. Stuck transaction with 'Error occurred while relieving reservations' due to incorrect or negative availability
17. Duplicate transactions in MTI already posted in MMTT and MMT and in MMTT already posted into MMT
18. View material transactions screen raise error APP-FND-00756:CANNOT FIND COMBINATION CCID=40225 CODE=MKTS
19. Negative TRANSACTION_SOURCE_ID in the inventory transactions table (MTL_MATERIAL_TRANSACTIONS)
20. 'CST_INVALID_INTERORG' Error while costing Material transactions
21. Sales Order Issue transaction missing in MTI and MMT for a drop ship PO receipt and Sales Order line Shipped Qty not updated
Identification Scripts ** Datafix Script: Require an SR Root Cause (RCA) Fixes Fix
Included In
1) Run the scripts in Patch 18839067 For R11i: Apply Patch 9241879 11.5.10 INV
See Note 279205.1 for more details. (You do not need to run again if just and Patch 13772375. Older patch RUP19+
run to identify the issue.) was Patch 5085603.
Here is a summary:
1) Run the query mmt_moqd_mismatch_at_sublevel.sql
2) Apply script
to check whether the mismatch exists at the subinventory
revloc_mismatch_fix.sql
level.
to fix the revision and locator
mismatch in MMT and MOQD.
* This does NOT currently account correctly for logical
transactions that cause transaction history but NOT
3) Re-run the sql script invmtmqd.sql.
onhand quantity. If you have logical transactions, this
or Run script invmtmqd_for_item.sql
script will not help as of now.
to specify the particular item
Identification Scripts ** Datafix Script: Require an SR Root Cause (RCA) Fixes Fix
Included In
Identification Scripts ** Datafix Script: Require an SR Root Cause (RCA) Fixes Fix
Included In
5 of 14 1/10/2018 11:44 PM
Document 568012.1 https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state...
Identification Scripts ** Datafix Script: Require an SR Root Cause (RCA) Fixes Fix
Included In
Identification Scripts ** Datafix Script: Require an SR Root Cause (RCA) Fixes Fix
Included In
If script invtrimsn-bakup.sql is run Apply patch Patch 4764047 and INV RUP5+
successful then only run script Patch 6156209 or equivalent patch
(1) Run the script identify.sql to check whether there
invtrimsn.sql with same on your patchset level.
any serial number exists with leading or trailing spaces.
inventory_item_id for which data
(2) Only if the above script returns records then run the backup is taken. This script will correct
the data for given inventory_item_id.
script invtrimsn-bakup.sql first with inventory_item_id
for which date correction is required thisscript will take
back of relevant tables before making any changes.
6 of 14 1/10/2018 11:44 PM
Document 568012.1 https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state...
Identification Scripts ** Datafix Script: Require an SR Root Cause (RCA) Fixes Fix
Included In
Identification Scripts ** Datafix Script: Require an SR Root Cause (RCA) Fixes Fix
Included In
If the item is lot controlled but onhand doesn't have lot Use script Patch 6603375 Fixes the root INV RUP5+
itemlotcontrl_moqdnolot_per_org.sql. cause. initially, and
numbers use Onhand without Lot . * A new root-cause patch will be then INV
included in INV RUP20 and higher RUP20 for
See Note 1538728.1 for details (which includes datafix). though this is NOT yet released. latest fix
coming soon.
If the item is not lot controlled but onhand has lot Use script itemnolot_moqdlot.sql. ApplyPatch 4413586 which would N/A
prevent the item controls to be
numbers use Onhand with Lot . changed when there are open
sales orders.
See Note 1538728.1 for details (which includes datafix).
Identification Scripts ** Datafix Script: Require an SR Root Cause (RCA) Fixes Fix
Included In
Physical Inventory Adjustments Report errors out. Use script fix_physical_inv_error.sql to Root cause patch will be updated N/A
See Note 1942897.1 for details (which includes datafix). Reject the erroneous Adjustments and soon.
delete the corresponding records in
temporary tables.
7 of 14 1/10/2018 11:44 PM
Document 568012.1 https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state...
Identification Scripts ** Datafix Script: Require an SR Root Cause (RCA) Fixes Fix
Included In
Identification Scripts ** Datafix Script: Require an SR Root Cause (RCA) Fixes Fix
Included In
Account Alias transactions in MMT error out Use script Apply Patch 5998987 to stop MMT Patch
(CST_INVALID_ACCT_ALIAS) while getting costed with populate_mmtsrcid_for_accntalias.sql being populated with NULL 5998987
missing transaction source. to resolve the issue . transaction source. Also see Note included in
428403.1 suggesting Patch 10G: 10.2.0.4
13020024 for R12.1.
* Use identify script to identify the issue.
Identification Scripts ** Datafix Script: Require an SR Root Cause (RCA) Fixes Fix
Included In
12. Onhand records with locator populated when sub inventory is not locator controlled
Identification Scripts ** Datafix Script: Require an SR Root Cause (RCA) Fixes Fix
Included In
8 of 14 1/10/2018 11:44 PM
Document 568012.1 https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state...
in RPL.
13. Locator stamped on onhand record is different from the one existing in mtl_item_locations for the subinventory
Identification Scripts ** Datafix Script: Require an SR Root Cause (RCA) Fixes Fix
Included In
Use Script subloc_moqmismatch.sql For R12, see Note 604251.1. For 12.0.7+
See Note 282480.1 for more details. Or refer to bug 11.5.10, apply root cause patch
4264604. 3969714, patch 3462946, patch
3703919, patch 4170327 or
equivalent patches on their
Also see Note 282480.1 (which includes datafix). patchset level as mentioned in RPL
before running the data fix script.
14. Onhand have records with Null Locator when Sub inventory is locator controlled
Identification Scripts ** Datafix Script: Require an SR Root Cause (RCA) Fixes Fix
Included In
Patch:13812691:R12.PO.B
Also see Note 282480.1 (which includes datafix).
15. The Update Standard Costs program is failing with the following error:Invalid value for intransit_owning_org_id in table MTL_SUPPLY
Identification Scripts ** Datafix Script: Require an SR Root Cause (RCA) Fixes Fix
Included In
Refer Bug 4234883 for steps to identify the issue. Use script mtl_supply_4234883.sql Apply Patch 10111967 for the root INV RUP4+
cause
*Also see Note 1455057.1 (which includes datafix).
16. Stuck transaction with 'Error occurred while relieving reservations' due to incorrect or negative availability
9 of 14 1/10/2018 11:44 PM
Document 568012.1 https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state...
Identification Scripts ** Datafix Script: Require an SR Root Cause (RCA) Fixes Fix
Included In
17. Duplicate transactions in MTI already posted in MMTT and MMT and in MMTT already posted into MMT
Identification Scripts ** Datafix Script: Require an SR Root Cause (RCA) Fixes Fix
Included In
18. View material transactions screen raise error APP-FND-00756:CANNOT FIND COMBINATION CCID=40225 CODE=MKTS
Identification Scripts ** Datafix Script: Require an SR Root Cause (RCA) Fixes Fix
Included In
Use script mmt_txn_src_mismatch.sql Apply one of the root cause 11.5.10 INV
Refer bug 5008181 for steps to identify the issue. (Also patches -- Patch 4182913 for RUP3+
discussed in Note 315946.1). 11.5.9, Patch 4455715 for 11.5.10
on your patchset level as
mentioned in RPL before running
See Note 1471880.1 (which includes datafix). the data fix script.
10 of 14 1/10/2018 11:44 PM
Document 568012.1 https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state...
Identification Scripts ** Datafix Script: Require an SR Root Cause (RCA) Fixes Fix
Included In
Identification Scripts ** Datafix Script: Require an SR Root Cause (RCA) Fixes Fix
Included In
To fix the issue, run one or more of Patch 7574671:R12.PO.A / Patch 987880
Identification Scripts following scripts R12.PO.B INV RUP22
Use "Identify.sql" based on Transaction Type return by
to identify the issue. "Identify.sql":
Intransit_Receipt.sql
Also see Note 1461380.1 (which includes datafix).
Int_Req_Intr_Rcpt.sql
21. Sales Order Issue transaction missing in MTI and MMT for a drop ship PO receipt and Sales Order line Shipped Qty not updated
11 of 14 1/10/2018 11:44 PM
Document 568012.1 https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state...
Identification Scripts ** Datafix Script: Require an SR Root Cause (RCA) Fixes Fix
Included In
Use Script missing_dropship_issue.sql N/A N/A
Identification Scripts: Use
"identify_missing_dropship_issue.sql" to identify the issue.
Identification Scripts ** Datafix Script: Require an SR Root Cause (RCA) Fixes Fix
Included In
Use Patch 9921274:R12.WSH.B N/A
Identification Scripts Scriptinsert_missing_mo_hdr_new.sql
Use "ident_insert_missing_mo_hdr.sql"to identify the issue.
Note:
As a test, the identification scripts from Section B were merged into one file. This is only for a test of a merged script and is only
You might also find these other datafix related notes helpful:
Note 264372.1 MTL_MATERIAL_TRANSACTIONS records with The transaction date and period do not match in the interface table.
different TRANSACTION_DATE and ACCT_PERIOD_ID
Note 803790.1 MTL_MATERIAL_TRANSACTIONS records with See note 803790.1 for identification scripts and patches to avoid the
Negative Source ID issue.
Note 438935.1 for details of the datafix Consigned Inventory with Transaction Source NULL:
and Note 452970.1 for the root-cause patch. Datafix 6085031.sql stamps the TRANSACTION_SOURCE_ID on
MTL_MATERIAL_TRANSACTIONS for Consigned Inventory
Transactions When the source Is Null.
12 of 14 1/10/2018 11:44 PM
Document 568012.1 https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state...
Note 330284.1
Note 402574.1 Serial Number vs. Onhand Mismatch (Serial Mismatch)
Note 1063592.1 * Suggest running 'serial_diagnostic.sql' from Note 330284.1.
Note 565604.1 Spaces at the start or end of a column may cause the error
"FRM-40654 :Record Has Been Updated". We have a standard
datafix to fix this issue: Use $FND_TOP/sql/afchrchk.sql which
includes datafix and identification and correction utility, see Note
565604.1.
Note 981792.1 Nonshippable Item Stuck Find that a Sales Order Issue tries to issue non-shippable material.
The material gets stuck in the MTI with 'Oracle error' and a
duplicate record is created in MMTT. The trip stop
(WSHINTERFACE) completes in warning.
Note 1230896.1 How To Identify Duplicate Lot Numbers for Lot Working on RCA Bug 10164831. Bug contains file "MSCA 2 Different
Uniqueness Across Items Setup PO Receipt Concurrently-2.doc", please ask your customer to follow
steps and check if issue is reproducible.
Note 201537.1 - Transactions Stuck
MTL_TRANSACTIONS_INTERFACE Table with error: 'For This Provides an insert script to add missing serial interface transaction
Transaction Row The Serial Records Are Missing' records.
Note 209118.1 - Datafix: Fix for Cost Group Mismatch Causes Errors:
UE:CREATE_TREE and QTY_QUERY2 Cost group mismatches can cause quantity to appear unavailable
(Or Note 367511.1 - Fix for Cost Group ID when Negative Balances when the cost group onhand is different than the organization for
Not Allowed Error) average and different than the
13 of 14 1/10/2018 11:44 PM
Document 568012.1 https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state...
For commonly used Items, Product Information Management (PIM/PLM), and Bills (BOM) issues, see Note 1295001.1 - FAQ: Item And PIM
(APC/PLM) Standard Datafixes. Here are a few related notes:
1. Steps to cancel ECO via interface for both Engineering and PLM- link .
2. Duplicate Bills of Material (BOMs)
See details in Note 370841.1 or Note 357785.1
3. Uncommon a Bill
Unfortunately, not available in the application. See Note 878976.1 for details.
4. FRM-40735 SPECIAL12 trigger raised unhandled exception ORA-20002
Note 406148.1 for an identification script. If it returns rows, log a service request to get a datafix to reset the workflow.
REFERENCES
NOTE:2041773.1 - Dual Unit of Measure (UOM) Control Item Has Wrong / Zero / Out of Sync Onhand and Available In Secondary UOM -
Data Fix Scripts
Didn't find what you are looking for?
14 of 14 1/10/2018 11:44 PM