CEPCT table — Profit Center Description Texts
CEPCT stores the language-dependent short and long text descriptions for profit centers. Each row is one profit center, in one controlling area, in one language, valid up to a given date. It never carries the actual master data attributes (person responsible, segment, company code assignment) — those live on CEPC. CEPCT is joined purely to resolve a profit center code to a readable name.
This page covers CEPCT, the text table behind profit center master data, and how it is used and misread during reporting and reconciliation work. It focuses on the joins that pull profit center descriptions into line-item and totals reporting, and the recurring mistake of treating this table as if it held validity or organizational assignment data.
Published 15 Sept 2026· 991 words
What it stores
One row in CEPCT is the description of a single profit center, in a single controlling area, in a single language, for a validity period ending on a given date. It exists purely to decouple the profit center's technical key from its human-readable name so that the same code can be labelled differently in German, English, or any other maintained language without touching the master record itself. It carries no financial attributes, no company code assignment, no hierarchy node, and no status flag. When a profit center's description changes, a new CEPCT row is created with a new validity end date rather than overwriting the old one, so history of naming is preserved. Any report showing 'profit center 1000 - North Region Sales' is joining CEPC or a reporting table to CEPCT to get that text.
Key fields
- MANDT - client
- SPRAS - language key controlling which text row is returned for a given locale
- KOKRS - controlling area, part of the profit center's compound key
- PRCTR - profit center code
- DATBI - validity end date of this text version; the current record has the highest DATBI
- KTEXT - short description, shown in most list reports
- LTEXT - long description, shown on detail screens
How it joins the data model
- ACDOCA-PRCTR = CEPCT-PRCTR (and ACDOCA-RCNTR/KOKRS context) to label profit center on universal journal line items
- FAGLFLEXA-PRCTR = CEPCT-PRCTR for classic New GL line item text lookup
- FAGLFLEXT-PRCTR = CEPCT-PRCTR for classic New GL totals reporting
- COEP-PRCTR = CEPCT-PRCTR when resolving profit center names on CO line item extracts
- CEPC-PRCTR = CEPCT-PRCTR (master record to its own text, not in the allowed list but the join every report actually starts from)
How to read it safely
Always restrict on MANDT and KOKRS before PRCTR; controlling area is part of the key and a profit center number is frequently reused across controlling areas with different descriptions. SPRAS must be restricted to the logon language or the report will either duplicate rows or silently return no text. DATBI is not a simple 'active flag' — the current text is the row with the maximum DATBI greater than or equal to today, so filtering on DATBI = a fixed high date without checking the pattern used in that system produces wrong results. The table itself is small and not a performance risk; the risk is joining it without SPRAS and returning one row per language instead of one.
How to prove it in the data
Symptom: a report shows a profit center code with no description, or the wrong description, for a specific user. Select CEPCT where KOKRS equals the controlling area in question, PRCTR equals the code, and SPRAS equals the user's logon language. If no row comes back, the text was never maintained in that language even though the profit center exists in CEPC. If multiple rows come back, compare DATBI values — the report may be picking up an expired text if the join logic does not filter on the current date correctly.
ECC vs S/4HANA
CEPCT is unchanged in S/4HANA. Profit center master data and its text table were not part of the totals-table consolidation that folded classic aggregate tables into the universal journal, because CEPCT is master data, not a transaction or totals table. It is still maintained through the standard profit center maintenance transactions and still joined the same way from ACDOCA and the classic reporting tables. No CDS compatibility view replacement was required for this table.
Common pitfalls
- Assuming a missing description means the profit center does not exist. It usually means CEPCT has no row for the requested language, while CEPC and the assignment tables are perfectly populated.
- Treating DATBI as a status field. It is a validity end date on the text version, not an indicator that the profit center itself is blocked or inactive; that status lives on CEPC, not here.
- Forgetting KOKRS in the selection and pulling a text for the same profit center number from a different controlling area, which produces a description that looks plausible but belongs to an unrelated org unit.
- Joining without SPRAS and getting a Cartesian multiplication of rows in a report, then blaming the extraction logic instead of the missing language filter.
- Editing CEPCT directly through a table maintenance transaction to fix a typo instead of going through profit center master data maintenance. Direct edits bypass change documents and can leave KTEXT and LTEXT out of sync with each other or with translated variants.
- Assuming a text exists in every maintained language just because it exists in the base language. Translation of profit center descriptions is a separate maintenance step and is frequently skipped for lower-priority languages.
Whose problem this is
Profit center description questions belong to the FI/CO master data or controlling team that owns the profit center hierarchy, not the reporting or basis team. If a description is wrong or missing in a specific language, it is a master data maintenance gap, not a data extraction bug, and should be routed back to whoever owns profit center creation and translation.
Related SAP objects
Reviewed pages this object connects to in the ERPClimb knowledge graph.
Source: ERPClimb — https://erpclimb.com/sap-tables/cepctERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.