COEP table — CO Line Items (Legacy Name; Compatibility View in S/4HANA)
COEP is the classic Controlling line-item table name used for CO actual, plan, commitment, and other value types by CO object, document, cost element, period, and currency. In S/4HANA, direct reads of COEP are redirected to compatibility view V_COEP, which derives relevant data from new persistence such as ACDOCA and supporting sources.
This page covers what a COEP row represents, the fields consultants actually filter and join on, and the joins to CO master and header tables. It focuses on the practical failure modes: mixing value types and versions, misreading currency fields, and assuming COEP is the whole story once S/4HANA and ACDOCA are in play.
Published 20 Sept 2026· 1,018 words
Esta página aún no está disponible en español.
What it stores
Each row in COEP is one CO line item: a value posted against a single CO object (identified by OBJNR, which resolves to a cost center, order, WBS element, or similar) for one combination of controlling area, fiscal year, posting period, value type (actual, plan, commitment) and version, on one cost element. The same underlying business transaction can generate several COEP rows if it splits across periods, cost elements, or partner objects. COEP is where postings originating in CO-only processes land - internal allocations, settlements, assessments, distributions - alongside the CO side of transactions that also touch FI. It does not by itself tell the reader what happened in accounting; it tells what happened on the controlling object.
Key fields
- CO document and line item — identify the controlling posting.
- OBJNR — receiving or sending CO object.
- Cost element or G/L account and value type — define the accounting meaning.
- Fiscal year, period, and version — define the reporting slice.
- Currency and quantity fields — compare using the same currency type.
- S/4HANA — use ACDOCA and released views for new analytics; COEP reads are compatibility-oriented.
How it joins the data model
- COEP-BELNR = COBK-BELNR and COEP-KOKRS = COBK-KOKRS to reach the CO document header (posting date, user, reference transaction)
- COEP-OBJNR = CSKS-OBJNR to resolve the object number to a cost center master record
- COEP-KSTAR = CSKB-KSTAR to reach the cost element master, and CSKB-KSTAR = CSKT-KSTAR for the cost element description
- COEP-REFBN and COEP-REFBZ, when populated, point to the originating FI document, joinable loosely to BKPF-BELNR or BSEG-BELNR depending on how the reference was stored
- In S/4HANA, the same economic event usually also appears in ACDOCA; COEP-OBJNR, KSTAR and BELNR-style keys have counterparts there, but the join is not a clean key match and needs to go through the universal journal's CO fields rather than a direct COEP-ACDOCA link
How to read it safely
Always restrict on MANDT implicitly and on KOKRS, GJAHR and VERSN explicitly before touching COEP; without a fiscal year and version filter the table is effectively unbounded on any productive system with years of history. WRTTP is not optional either - actual, plan and commitment rows sit in the same table, so a query without a WRTTP filter silently blends categories that no report should mix. OBJNR is not human-readable; do not filter on it directly unless it has already been resolved from a cost center, order, or WBS number through the appropriate master table. Period fields (PERBL/PERIO) follow the fiscal year variant, so period 1 is not always calendar January.
How to prove it in the data
To confirm a cost center shows an unexpected actual charge in a given period: resolve the cost center to its OBJNR via CSKS, then select COEP for that KOKRS, GJAHR, PERBL, WRTTP = 04 (or the actual value type in use), VERSN = 000, and OBJNR, and inspect KSTAR and WKGBTR per row. If the amount does not appear, check whether it landed as a commitment (WRTTP for commitments) or in a different version before assuming the posting never happened.
ECC vs S/4HANA
SAP compatibility-view documentation uses COEP as a primary example: in S/4HANA, database-interface reads are redirected to V_COEP and new postings update underlying new tables such as ACDOCA rather than the old COEP table. New custom development should use released CDS views and Universal Journal semantics instead of assuming COEP remains the authoritative physical store.
Common pitfalls
- Filtering COEP without a value type restriction and then summing WKGBTR across actual, plan and commitment rows in the same query, producing a number that matches nothing in any report
- Treating BELNR on COEP as the FI document number; it is the CO document number, and reconciling it directly against BKPF or BSEG without going through REFBN/REFBZ produces false negatives
- Reading OBJNR as if it were a cost center or order number; it must be resolved through the object number tables first, otherwise filters silently return zero rows
- Ignoring VERSN and assuming version 000 is the only version present, especially on systems where multiple plan versions or simulation versions are actively maintained
- Comparing COEP totals to ACDOCA/FI totals line by line in S/4HANA without accounting for the fact that pure CO-internal postings (allocations, settlements) exist only in COEP and have no FI counterpart, so a mismatch does not automatically mean an error
- Selecting across GJAHR without limits on a long-lived production system, which turns a simple lookup into a full table scan on one of the larger tables in a CO-heavy landscape
- Assuming currency fields are interchangeable; WKGBTR, the object currency amount, and the transaction currency amount can all differ, and picking the wrong one skews any variance analysis
Whose problem this is
Controlling (CO) functional consultants and cost center or project controllers own questions about what COEP should contain for a given object and period. FI consultants get pulled in when the discrepancy is between COEP and the FI ledger, and Basis or the data archiving team owns questions about missing history once older fiscal years have been archived out of the table.
Related SAP objects
Reviewed pages this object connects to in the ERPClimb knowledge graph.
Source: ERPClimb — https://erpclimb.com/sap-tables/coepERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.