1. Check for batch_id: Select count (*) from mtl_consumption_transcations Where nvl (batch_id, -1) <> -1 And consumption_processed_flag in (N,E); If count is greater then ZERO, do the foll: Update mtl_consumption_transactions Set batch_id = NULL Where batch_id is NOT NULL And consumption_processed_flag in (N,E); COMMIT; Ask customer to apply patch 5036673 (for 11.5.9) and 5200436 (for 11.5.10) 2. Check for NULL transaction_source_id (Note: This is a VERY common problem that customers are facing. We have logged a root cause bug on Inventory to track this issue). Select count (*) from mtl_consumption_transctions mct, mtl_material_transactions mmt Where mct.transaction_id = mmt.transaction_id And consumption_processed_flag in (N,E) And transaction_source_id is NULL; If Count is greater then ZERO, Create Consumption Advice will fail. We have a script for this data-fix. Please run the script and log a bug on Inventory for the root cause (populate null txn src id.sql).
3. Check for INVALID blankets:
Check if the blankets are valid at the time Create Consumption Advice is run. By design, the blankets MUST BE OPEN/ACTIVE when Create Consumption is run. You have to check the validity at: a. The blanket header / line level b. Expiry dates set if any at the line level and in the Terms of the blanket c. Purcahse Order Control Options. The Create Consumption Advice Worker will show an ****INVALID LINE error for invalid blankets. 4. Check the billing cycle Check the billing cycle in the approved supplier list. The Consumption Advice will NOT be created unless the billing cyle has been elapsed. 5. Check for NULL blanket_price: Select count (*) from mtl_consumption_transactions Where consumption_processed_flag in (N,E) And blanket_price is NULL;
A script will have to be run to populate the blanket price(b4649230.sql). Create
consumption Advice will fail for NULL blanket prices. 6. Check for PO Auto Create failure: If the log file contains INV_SUP_CONS_AUTO_CREATE_FAIL, you have to log a bug on Purchasing (502) for Auto Create Failure. DUPLICATE RELEASES CREATED Customer should be on a very old version of the Consigned files. Please ask the customer to apply patch 5200436 (for 11.5.10) and 5036673 (for 11.5.9) In order to retrieve the duplicate releases, the following query will have to be run: SELECT DISTINCT por.po_release_id FROM po_releases_all por, po_line_locations_all poll WHERE por.po_release_id = poll.po_release_id AND poll.shipment_type = BLANKET And por.consigned_consumption_flag = Y AND por.po_release_id NOT IN (Select DISTINCT consumption_release_id FROM MTL_CONSUMPTION_TRANSACTIONS Where consumption_release_id is NOT NULL); We have scripts to cancel the duplicates. First run invgcacl.pls invgposf.sql
followed by
CONSIGNED STOCK NOT ISSUED
Check if regular stock and consigned stock are co-mingled for the same item in a given subinventory. Should this be the case, the stock is always issued on FIFO basis. This may be the reason why regular stock may be issued ahead of Consigned stock. OWNERSHIP TRANSFER NOT OCCURING FOR CONSIGNED STOCK: INVALID BLANKET 1. Check if any of the blanket or any of the lines in the blanket is closed. 2. Check the expiration date on the lines 3. Check the End Date on the TERMS page in the blanket 4. Item Revision (if any) must exist on the blanket 5. If there is no blanket number specified on the ASL, ensure that the profile PO %Automatic Document Sourcing is set to Yes. This would pick up the latest blanket. 6. Ensure that vendor product number is less than 10 characters if patch 3223055 is not applied SUBINVENTORY TRANSFER NOT TRIGGERING CONSUMPTION: Check the Consumption/VMI Rules setup: By default, a subinventory transfer carried the Consigned Stock status to the destination subinventory in subinventory transfers. If explicit rules have been setup (using the Consigned / VMI Rules setup form), the consumption will be triggered and the destination subinventory would have regular stock.
ACCRUAL RECONCIALIATION FAILURE / MISSING PO_DISTRIBUTION_ID IN
MTL_CONSUMPTION_TRANSACTIONS PO_DISTRITIBUTION_ID is automatiacally populated when Create Consumption Advice is run. However, for customers who have not applied patch 5200436, the Accrual Reconcialiation process may fail. So, please ask the customers to appy 5200436. Note: This fix is available only for 11.5.10 CONSUMPTION ADVICE IS SPLITTING SHIPMENTS ON A DAILY BASIS FOR LOCAL BLANKETS Check the Profile option: INV: Summarize Consumption By Need By Date. By default, the value is NULL. If set to Yes, the shipments in a release will be grouped according to the transaction dates. Note: This profile option does NOT affect consumptions referring to global blankets.