Frequently Asked Questions (FAQ)
1. Where do I get the datafixes?
Answer: Log a service request if the datafix is not listed.2. Why are identification scripts posted but NOT the datafix too?
Answer: So far, we have not gotten approvals but we are working with on an initiative as of May 2012 to post datafixes where appropriate.3. What are the Top 5 Datafixes?
Answer: The top 5 datafixes are :- Orphan Move Order or Reservation: A-1 & A2
- MOQD-MMT Mismatch: B-1
- Marked Serials: B-4
- Duplicate transactions: B-17
- Locator Corruption: B-12 to B14
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.5. What are other common datafix notes?
Answer: See the following :- Note 1295001.1 - FAQ: Item And PIM (APC/PLM) Standard Datafixes
- Note 601639.1 - Generic Receiving Datafix Scripts and Root Cause Patches
- Note 108185.1 - Oracle Applications Object Library SQL scripts
- FAQ: Inventory Standard Datafixes [ID 568012.1]
6. Where can I discuss datafixes?
Use the communities to discuss datafixes. This is an example thread where we ask for your input:https://communities.oracle.com/portal/server.pt/community/view_discussion_topic/216?threadid=404595
7.Are there standard datafixes for inventory?
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.
** These standard datafixes are available via patches or download:
1. Reservations
2. Move Orders
3. Zero Onhand
4. Inventory Items
5. Duplicate Bill of Materials
6. Inventory
Check FAQ: Inventory Standard Datafixes [ID 568012.1]
8. Are there SR data fixes ? Why Log SR?
Yes there are SR data fixes,Oracle Development requires that you log an SR to get the datafix even though it is a standard fix. This is because Oracle wants to ensure that the root-cause patches are suggested to each customer to avoid the issue in the future. Also, if you already have the root-cause patches, Oracle wants to capture information that might help identify the new root-cause situations so that too can be fixed. Oracle does not want customers constantly running datafixes as this is not going to promote satisfaction with the product. Instead, Oracle wants to fix the cause of the data corruption. This is why the note requests you to log an SR to get the datafix.
** All the datafixes below require service requests:
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
Comments
Post a Comment