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

The costing period is not open

Every transaction books into a month on the COSTING calendar. The month this transaction's cost date falls into is closed, the door is locked. Note it's the COST date that matters, which for backdated transactions is not always the transaction date you see in inventory.

Root cause

The transaction's cost date lands in a closed costing period.

How to fix it
  1. Open Manage Cost Accounting Periods for the cost org + cost book
  2. Make sure at least one current/future period is OPEN
  3. Check the processor's cost cutoff date includes at least one day inside that open period
  4. Rerun, costing books the transaction into the open month
Where to go in Fusion
Oracle references

My Oracle Support document IDs for readers with access: 1304094.1 (cost date vs transaction date FAQ). 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