COSPD table — CO Object: Settled Primary Cost Totals

COSPD belongs to the classic CO settlement data model and stores primary-cost totals that have been settled from controlling objects. Its 'D' suffix should not be interpreted as a long-field extension of COSP. The table supports settlement/reconciliation logic by retaining aggregated settled values under the relevant CO object, cost element, fiscal year, version, and business-transaction dimensions.

The table key and value fields reflect aggregate Controlling settlement rather than a business document line.

Resolve OBJNR through the owning object master such as AUFK, PRPS, or another CO object. Compare source cost totals/line items with settlement rules in COBRA/COBRB and settlement documents. COSPD is not a substitute for COEP/ACDOCA line items because its data is already aggregated and specifically settlement-oriented.

Always restrict by object number, fiscal year, value type, version, and cost element before interpreting totals. Keep currencies aligned. A value in COSPD means settled primary cost under those dimensions; it does not by itself say which original invoice, material document, or confirmation created the source cost. Follow the settlement and source document chain for that.

When an order or WBS settlement appears incomplete, identify the sender OBJNR and settlement rule, compare source actual costs with the settlement document and the corresponding COSPD settled totals for the same fiscal year, value type, version, and cost element. A difference should be explained by settlement period, rule, status, residual balance, or value category before assuming table inconsistency.

Identify the controlling object number and fiscal year, then distinguish the source actual postings from settlement receiver postings and the corresponding settled totals. Compare the value type, version, cost element and business transaction dimensions before aggregating. Confirm the settlement document and reversal status through standard CO reporting. In S/4HANA, validate the target release's data model and released accounting/controlling views.

COSPD is a classic CO settlement totals structure. In S/4HANA, actual-cost and settlement analysis should start with released CO/Universal Journal views and the standard settlement documents because core FI/CO persistence has been simplified. Existing classic tables can remain relevant for compatibility or specific settlement logic, but new analytics should not be designed around COSPD alone.

Production incident: a settlement report disagrees with the controlling object's source cost report after a period-end job. COSPD contains settled primary-cost totals in a classic CO data context; that is not the same grain as every original posting. Settlement rules, periods, cost-element types, versions and reversal runs can cause differences. An ECC report that uses COSPD directly may not be appropriate for an S/4HANA Universal Journal reconciliation.

Primary ownership is Controlling/settlement, with PS, PM, or PP joining according to the sender object type. Finance joins when the settlement receiver creates FI-relevant postings. ABAP is needed only for a proven custom settlement or reporting defect.

COSP/COSS are classic CO totals for external/internal postings, COEP is the classic CO line-item interface, ACDOCA is central to S/4HANA actuals, COBRA/COBRB contain settlement rules, and KOB1/CJI3 or application-specific line-item reports provide document-level operational analysis.