SAP tableObjectCEPCModuleFI_FICO

CEPC table — Profit Center Master Data Table

CEPC stores the time-dependent master record for a profit center within a controlling area: its validity period, responsible person, department, plant assignment, and segment link. It does not hold balances or transactions. Financial values sit in ACDOCA, FAGLFLEXT or BSEG, all of which carry PRCTR as a field that joins back to CEPC for the descriptive attributes.

This page covers what a CEPC record actually represents versus what people assume it holds, the time-dependency trap that causes the most support tickets, and how to prove a profit center master data problem against a posting problem using the actual line item tables. It also covers the S/4HANA shift where profit center attributes matter less for reporting because ACDOCA already carries PRCTR directly.

Published 15 Sept 2026· 1,144 words

What it stores

One row in CEPC is one version of a profit center's master data, valid for a specific date range within a controlling area. A profit center can have several rows over time if its responsible person, department, plant, or segment assignment changed, because CEPC is time-dependent on the DATAB to DATBI range rather than a single static record. The table holds descriptive and organizational attributes only: who is responsible for the profit center, which plant or department it maps to, whether it is locked from posting, and which segment it feeds for segment reporting. It does not store a single actual or plan value. Financial figures for a profit center live in the posting and reporting tables that carry PRCTR as a field, not in CEPC itself.

Key fields

  • MANDT - client
  • KOKRS - controlling area the profit center belongs to
  • PRCTR - profit center code, the join key used everywhere else
  • DATAB - start of validity for this version of the record
  • DATBI - end of validity for this version of the record, commonly 31.12.9999 for the current row
  • ERSDA - date the record was created
  • USNAM - user who created the record
  • ABTEI - department assigned to the profit center
  • WERKS - plant assigned to the profit center
  • SEGMENT - segment derived for this profit center, used in document splitting and segment reporting
  • BKZKP - lock indicator preventing further postings to the profit center

How it joins the data model

  • CEPC-PRCTR = CSKS-PRCTR, cost center master carries a profit center assignment that has to line up with an active CEPC record
  • CEPC-PRCTR = ACDOCA-PRCTR, the universal journal line item table carries the profit center directly for every posting
  • CEPC-PRCTR = FAGLFLEXT-PRCTR, the New GL totals table carries the profit center for balance reporting outside ACDOCA setups
  • CEPC-PRCTR = BSEG-PRCTR, classic FI line items carry the profit center field derived at posting time
  • CEPC-KOKRS = CSKS-KOKRS, the controlling area has to match between cost center and profit center master data

How to read it safely

Always restrict on MANDT and KOKRS before touching PRCTR, because the same profit center code can exist in multiple controlling areas with entirely different master data. Because the table is time-dependent, a query without a date filter against DATAB and DATBI will return every historical version of a profit center, including versions that were valid years ago and are no longer usable. When checking whether a profit center is currently valid, filter DATBI greater than or equal to today's date and take the row with the latest DATAB. The table itself is small relative to posting tables, so the real risk is not performance, it is picking up a stale or superseded version of the record.

How to prove it in the data

Symptom: a document fails or is rejected with an invalid profit center message. Select CEPC by KOKRS and PRCTR for the code in question, with DATBI greater than or equal to the posting date and DATAB less than or equal to the posting date. No row returned means the profit center does not exist for that controlling area on that date, either not created yet or already time-expired. A row returned with BKZKP set means the profit center exists but is locked, which is a different fix than a missing master record.

ECC vs S/4HANA

CEPC continues to exist in S/4HANA and remains the master data store for profit center attributes. What has changed is how much weight the table carries for reporting: since ACDOCA holds PRCTR on every universal journal line, profit center based financial reporting no longer depends on separate profit center accounting totals tables the way it did in classic EC-PCA, and CEPC's role narrows to master data attributes, validity, and segment derivation feeding document splitting rather than being part of a parallel ledger structure.

Common pitfalls

  • Treating CEPC as if it held balances. It does not. Anyone querying CEPC looking for actual or plan amounts is looking in the wrong table; those live in ACDOCA, FAGLFLEXT or the classic totals tables.
  • Forgetting the time-dependency and reading an old row. A profit center that was reorganized under a new responsible person or department will have multiple CEPC rows, and a query without a date filter can pick up an obsolete version and report the wrong owner.
  • Assuming a profit center visible in CEPC is postable everywhere it is needed. Company code usability for a profit center is controlled separately from the CEPC master record itself, so existence in CEPC does not guarantee a document in a given company code will accept it.
  • Missing the lock flag. A profit center can exist, be within its valid date range, and still reject postings because it has been locked. Checking only for record existence and skipping the lock indicator produces a false all clear.
  • Confusing short and long text absence with a missing master record. Descriptive texts live in a separate text table, not in CEPC, so a blank description does not mean the profit center master record is missing.
  • Reading segment assignment as fixed. SEGMENT on a CEPC row reflects the assignment valid for that time slice; a profit center moved to a different segment will show the old segment on historical postings and the new one going forward, which explains apparent segment inconsistency in reporting that is actually correct historical behavior.

Whose problem this is

Master data questions on CEPC sit with the controlling or profit center accounting team, often the same group that owns cost center master data, since profit center and cost center governance usually run through the same master data process. Segment and document splitting behavior tied to CEPC is a finance design question, owned by whoever configured the document splitting characteristic assignment.

Related SAP objects

Reviewed pages this object connects to in the ERPClimb knowledge graph.

Source: ERPClimb — https://erpclimb.com/sap-tables/cepcERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.