S Shortlisted
Home / Troubleshooting / Cost Processor Errors
Oracle Fusion Cost Management · 19 errors · cause and fix

Oracle Fusion cost processor errors, and how to fix them.

When the cost processor stops, it stops on a specific error. Find yours below. Each one has the plain-language cause and the exact steps to clear it. Or, if you have the error text in front of you, paste it into the interactive triage and get the answer instantly.

Perpetual average cost was not found (outgoing)Existing layer cost was not found, actual cost (incoming)The standard cost for this transaction does not existReceiving transaction information is missingThe costing period is not openThe transaction period is closed for General LedgerIssue transaction was put on hold to avoid generating negative inventoryCST_QTYFL_NEVER_PENDINGIssue fully costed but not fully depleted, unresolved negative inventoryCST_CPROC_UNRESOLVED_NEG_INVTransfer receipt cannot be costed until the issue is fully processedThe receipt is missing a cost (work orders)Distributions were not created for the COGS transactionCST_DPROC_UNCOSTED_COGS_TXNWork order or operation information does not exist in the source systemORA-01400: cannot insert NULL into CST_PREP_ERRORS_GT.ERROR_CODEORA-01400ORA-01652: unable to extend temp segment in FUSION_TEMPORA-01652ORA-00001: unique constraint CMR_AUTO_ACCRUAL_CLR_DTLS_PK violatedORA-00001ORA-01555: snapshot too oldORA-01555FND_CMN_PROC_INTERNAL_ERRORA perpetual average cost is required to cost the outgoing transactionThe item cost profile was not generated

Where to next

Beyond the error list: