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

A perpetual average cost is required to cost the outgoing transaction

Issues are queuing behind transactions stuck at PARTIALLY costed, receipts that started costing but never finished because no usable cost layer formed. The count in the error will exactly match the count from the SQL below; that's your suspect list.

Root cause

Transactions stuck at cost_status = P (partial), a layer with a usable cost never formed.

How to fix it
  1. Run the SQL, the partials it returns are the blockage
  2. Create a misc receipt WITH a proper cost, same valuation unit, dated BEFORE the stuck transaction
  3. Rerun all cost processes in sequence and confirm the partials turn fully costed
  4. Misc-issue the replenishment back out to true-up onhand
Where to go in Fusion
Diagnostic SQL

The partially costed culprits

select * from cst_transactions where cost_status = 'P' and cost_org_id = &cost_org and cost_book_id = &cost_book

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

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