SAP Reference

CEPC

master S/4HANA status: Active

Profit Center Master Data Table

Identity
Module: CO · ControllingType: transparent
Key fields

MANDT · PRCTR · DATBI · KOKRS

All 4 fields
What the badges mean
S/4HANA status: Active
Active and unchanged in S/4HANA.
S/4HANA status: Deprecated
Still readable today, but no longer SAP's strategic path — plan around it.
S/4HANA status: Replaced
Replaced by a new persistence in S/4HANA; the classic name may still answer reads (see read mechanism).
S/4HANA status: Migrating to IBP
Planning scope is moving from APO toward IBP.
S/4HANA status: Active (StRM) · Replaced (EWM)
Path-dependent: active with SAP Stock Room Management, replaced where EWM is the warehouse path.
S/4HANA status: Replaced · Compat View
Compatibility view: the classic table name is redirected to a view over the new persistence — see how the physical model moved.
S/4HANA status: Active · Proxy View
Proxy view: reads route through NSDM proxy/CDS views — see how the physical model moved.
master
Data class: what the table holds — master data, transaction documents, org structure, config, or texts (one row per language — see the quirks guide).
Linked type codes

CLNT — the client key; filter it explicitly and carry it through every join.

NUMC — fixed-width numeric text; keep it a string and keep the leading zeros.

DATS, TIMS — character date (YYYYMMDD) and time (HHMMSS), zero-filled when initial.

CURR, CUKY, QUAN, UNIT — amounts and quantities, meaningful only beside the currency key or unit that qualifies them.

LANG — a language key in a text table — one row per language.

In field listings, K marks a primary-key field, and linked type codes in the Type column jump to the matching quirks-guide section.
Modeling guide
Quality — What was inspected, what was decided, and what was reported?

What CEPC is for

One row per profit center per controlling area per validity period — the key is PRCTR + KOKRS + DATBI (valid-to). CEPC is not a lookup table, it is a type-2 dimension SAP maintains for you: the validity intervals are the history.

Joins that work — and the traps

  • Every PRCTR column in this reference points here

    Among them LIPS (delivery items), AUFK (orders), ACDOCA (accounting lines), and EKKN (purchasing account assignments).

    LIPSAUFKACDOCAEKKN

  • The join is as-of, never plain

    Transaction date between valid-from and valid-to, plus KOKRS. On PRCTR alone, every historical validity period matches and fact rows duplicate.

  • Texts live in CEPCT

    Not in this reference's catalog.

    CEPCT

What CEPC does not contain

No hierarchy — profit-center groups live in the set tables, not here; no company-code assignments (separate assignment table); no postings (ACDOCA is where profit-center actuals accumulate).

What breaks in practice

  • The validity-duplicate join is the classic: metrics inflate by the number of times the profit center was re-organized.
  • Cross-controlling-area joins without KOKRS pick up same-named profit centers from other areas.
  • Reorganizations move responsibility, not history: an as-of join shows the profit center that owned the transaction then, which is usually — but not always — what the business wants reported now. Ask which before building.

Shape & growth

Small and slowly changing — full extract every run; never bother with CDC here.

ECC vs S/4HANA

CEPC persists in S/4HANA; profit-center actuals consolidated into ACDOCA (the universal journal) rather than classic PCA tables.

Fields

4 fields · 4 key

The join key is all 4 key fields together — matching on any single one fans out. See composite keys in the quirks guide.

4 fields.

Table fields: key flag, field name, description, data type (linked to the data quirks guide where the type carries a known trap), length, and check-table references. 4 fields.
KeyFieldDescriptionTypeLengthReferences
Primary keyMANDTClientCLNT3
Primary keyPRCTRProfit CenterCHAR10
Primary keyDATBIValid To DateDATS8
Primary keyKOKRSControlling AreaCHAR4

Linked type codes in the Type column jump to the matching section of the SAP data quirks guide.

Field provenance: hand-curated.

Boilerplate SQL

Starting point for reading CEPC on Databricks. Set your Unity Catalog location and filter values below — they’re substituted into the SQL and the copy button.

Query parameters

4 parameters not filled: <catalog>, <schema>, <MANDT>, <KOKRS>

-- ============================================================
-- Table  : CEPC Profit Center Master Data Table
-- Purpose: Column-selected read of CEPC — auto-generated from field metadata
-- Grain  : One row per PRCTR + DATBI + KOKRS
-- Notes  : Auto-generated skeleton. For multi-table transaction query patterns, see the linked t-codes on this page. Set catalog/schema to your Unity Catalog location; fill remaining placeholders (<...>) for your tenant.
-- ============================================================
SELECT
  c.MANDT AS "Client",
  c.PRCTR AS "Profit Center",
  c.DATBI AS "Valid To Date",
  c.KOKRS AS "Controlling Area"
FROM <catalog>.<schema>.cepc c
WHERE
  c.MANDT = '<MANDT>'
  -- AND c.KOKRS = '<KOKRS>'
ORDER BY c.PRCTR;

Verified August 2026

More query patterns: KE51

Released CDS views over this table

Released SAP standard VDM views that read over CEPC. Prefer these over classic-table reads on S/4HANA where available.

Relationships

Diagram of 1-hop neighbors — join details below.

Join details

  • EKKNCEPCforeign key · N:1
    ON ekkn.PRCTR = cepc.PRCTR
  • LIPSCEPCforeign key · N:1
    ON lips.PRCTR = cepc.PRCTR
  • AUFKCEPCforeign key · N:1
    ON aufk.PRCTR = cepc.PRCTR
  • ACDOCACEPCforeign key · N:1
    ON acdoca.PRCTR = cepc.PRCTR

Transaction Codes That Use This Table

R read · W write · R/W read + write

More Controlling tables