CK24 — Mark and Release Standard Cost Estimate
CK24 is used to mark future standard prices and release approved material cost estimates as standard price. It is most useful during controlled standard-cost roll when Finance approves new costs for a posting period. Start with the exact organizational keys and business date, then prove the result from SAP documents, balances or logs before changing configuration or reposting data.
This page explains CK24 — Mark and Release Standard Cost Estimate — from a consultant's point of view: what it changes or displays, when it belongs in the process, which keys matter, how to prove the result, and the mistakes that create avoidable reconciliation work.
Published 19 Sept 2026· 602 words
Esta página ainda não está disponível em português.
Purpose
mark future standard prices and release approved material cost estimates as standard price. The transaction should be read in the context of the full accounting or logistics flow: source document, organizational assignment, posting date, configuration and resulting document all matter. A technically successful save is not enough; the output must reconcile to the intended business event.
When it is used
CK24 is typically used during controlled standard-cost roll when Finance approves new costs for a posting period. In project testing it is equally useful for proving configuration and master data with a controlled example. In production, narrow the scope first and capture the before-state so any posting, clearing, settlement or master-data change can be reconciled afterward.
How to use it in practice
- Ensure cost estimates are complete and reviewed before marking.
- Confirm period and organizational scope.
- Mark prices first and verify future-price results.
- Release only after approval and period controls are ready.
- Reconcile material master standard price and accounting impact.
Key data objects
These are the fields and business objects that usually explain the result in CK24. Capture them in test evidence and incident handovers, because a mismatch in company code, plant, fiscal period, account or reference document is often more important than the screen message itself.
- company code/plant — verify the exact value, validity/date context and source of derivation.
- fiscal period — verify the exact value, validity/date context and source of derivation.
- costing run/estimate — verify the exact value, validity/date context and source of derivation.
- marking allowance — verify the exact value, validity/date context and source of derivation.
- released standard price — verify the exact value, validity/date context and source of derivation.
How to prove it in the data
Prove the result end to end: identify the source document/master record, inspect the transaction's proposal or status, then open the resulting accounting or logistics document and reconcile amounts, quantities and account assignments. Use document flow, line-item displays and master-data history with the same fiscal period and organizational scope. That distinguishes a true configuration defect from a selection, timing or historical-data difference.
ECC vs S/4HANA
CK24 remains a key standard-cost release control in S/4HANA product costing. On S/4HANA, Universal Journal, Business Partner, Material Ledger or Fiori may change the preferred analysis surface, but the business control behind the transaction still has to be understood and tested.
Common pitfalls and how to diagnose them
- Releasing before all costing errors are resolved. Reconcile the exact document and period before making a configuration change.
- Using the wrong period and overwriting an intended future cost. Reconcile the exact document and period before making a configuration change.
- Treating CK24 as a calculation transaction rather than a controlled price-release step. Reconcile the exact document and period before making a configuration change.
Whose problem this is
Primary ownership is Finance/Controlling, with Basis or ABAP involved only when runtime, authorization or custom-code evidence points there. A useful escalation includes the business document, organizational keys, posting/valuation date, expected accounting result and the exact mismatch already proven.
Related SAP objects
Reviewed pages this object connects to in the ERPClimb knowledge graph.
Source: ERPClimb — https://erpclimb.com/sap-tcodes/ck24ERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.