Before costing can process an item it must decide the RULES for that item, which cost method, which valuation structure. That decision is the cost profile, and costing couldn't create one: a setup gap, not a data problem. Four switches decide it.
Costing couldn't attach a cost profile to the item, setup gap.
My Oracle Support document IDs for readers with access: 1414932.1 · 1572712.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.