S Shortlisted
Home / Troubleshooting / Cost Processor Errors / this error
Oracle Fusion Cost Management · cost processor error · cause and fix

Distributions were not created for the COGS transaction

Error code: CST_DPROC_UNCOSTED_COGS_TXN

COGS is the last domino in a chain: the sales-order issue behind it must cost first, and that issue needed an inventory layer with a real cost, which never formed, usually because the receipt that should have created it came in costless. You can't fix the last domino; you stand up the first one.

Root cause

The sales-order issue never costed (no layer with a cost), so COGS has nothing to distribute.

How to fix it
  1. Find the sales-order issue's own error, usually “no layer cost for the item” (the layer-cost card above)
  2. Fix THAT (costed misc receipt in the same valuation unit, or wait for the costed receipt that's coming)
  3. Rerun, the issue costs, then COGS costs itself right behind it
Where to go in Fusion
Oracle references

My Oracle Support document IDs for readers with access: 2374018.1 · 2242665.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:

🔧Search any cost processor errorThe interactive triage: paste your error, get the card.→🧾The setup behind these errorsThe Cost Management implementation guide.→✅Close without surprisesThe dependency-ordered SCM period close checklist.→
More cost processor errors