2 AM, the processor errored, nobody remembers what CST_QTYFL_NEVER_PENDING means. Pick your symptom, an error message, a transaction that won't cost, a stuck process, a report that won't reconcile, and get the cause in one line, the fix in five taps, and the diagnostic SQL on a copy button. Built from the checklists working costing consultants actually use on real projects.
Checked Community-reported patterns rewritten in plain words and reviewed by a working consultant, Jul 2026 · Diagnostic guidance, not a substitute for your instance: verify each fix in a test environment first.
Prefer a page per error? Browse every cost processor error and its fix, one page each. Community-rewritten quick reference for widely-known Oracle Fusion Cost Management troubleshooting practice; Oracle doc references (e.g. 2257853.1) point to My Oracle Support for the authoritative deep dives. Table names and behavior vary by release, verify in your instance. Companion: P2P Live (where these entries come from) · Period Close Checklist · Troubleshooting.
Check the costed flag in Review Completed Transactions first: N means Transfer Transactions from Inventory to Costing hasn't run; blank means it's already interfaced and the problem is inside costing, trace the four doors (interface → picked up → cost transaction → distributions) with the SQL chain in the review above, then check the processor's captured errors.
Costing found no onhand in the valuation unit to deplete, and the cost profile says Process Negative Quantity = NEVER. The trap: inventory checks onhand at org level, costing at valuation-unit level, so inventory processed what costing now refuses. Fix: a misc receipt for the missing quantity in the same valuation unit (dated inside the cutoff), transfer to costing, rerun.
An earlier run for the same cost org and cost book is still in Running or Canceling. Blocked is the queue, not the disease, find and clear the earlier stuck run (usually a performance casualty) and Blocked resolves itself.
The reconciliation only works if the GL account is pure: used exclusively by costing journals of accounting line type INVENTORY VALUATION, with no manual journals ever posted to it. Break either rule and the mismatch is permanent by design. Also remember transaction date ≠ cost date for backdated transactions.