S Shortlisted
Oracle Fusion Cost Management · cost processor error · cause and fix

Issue transaction was put on hold to avoid generating negative inventory

Error code: CST_QTYFL_NEVER_PENDING

You issued stock that, as far as costing can see, doesn't exist. How? Inventory counts onhand at the ORGANIZATION level and happily processed the issue. Costing counts inside the VALUATION UNIT and found that particular shelf empty. The item's cost profile says “NEVER process negative quantity”, so costing froze the issue rather than invent stock.

Root cause

No onhand in the VALUATION UNIT to deplete + cost profile Process Negative Quantity = NEVER.

How to fix it
  1. First rule out the setup trap: an Asset/Expense flag mismatch on the subinventory can fake this error (see the ref note)
  2. Run the first SQL below to list exactly which transactions are stuck
  3. Run the second SQL per item to confirm onhand really was missing at that date, in that valuation unit
  4. Replenish: create a misc receipt for the missing quantity, in the SAME valuation unit, dated inside the processor's cutoff
  5. Run Transfer Transactions from Inventory to Costing, then the cost processor, the frozen issue thaws
  6. If the transfer's own receipt leg later restores the quantity, misc-issue your replenishment back out to true-up onhand
Where to go in Fusion
Diagnostic SQL

Which transactions are stuck on negative onhand?

select transaction_date, transaction_id, transaction_quantity, inventory_item_id, organization_id from inv_material_txns where transaction_id in (select cte.external_system_ref_id from cst_transaction_errors cte, cst_cp_errors ce where cte.cp_error_id = ce.cp_error_id and ce.error_code in ('CST_CPROC_UNRESOLVED_NEG_INV','CST_QTYFL_NEVER_PENDING') and ce.request_id = &request_id)

Was there really onhand at that date?

select sum(transaction_quantity) from inv_material_txns where inventory_item_id = &item_id and organization_id = &org_id and transaction_date <= to_date('&txn_date','YYYY-MM-DD HH24:MI:SS')

Read-only diagnostic queries. Substitute the bind values for your instance; run in a test environment first.

Oracle references

My Oracle Support document IDs for readers with access: 2187643.1 · 2261010.1. We do not reproduce their content.

Checked Cost processor behavior for Oracle Fusion Cost Management, rewritten in plain words from publicly known troubleshooting practice and reviewed by a working consultant. Checked against the current release, Jul 2026. Amounts, account names and navigation vary by configuration; verify in your own instance and test before acting.

Solve it, then prevent it

This page explains one error. These help with the rest:

More cost processor errors