CSKT table — Cost Center Text Table CSKT

One row in CSKT is the description of a single cost center, in one language, valid up to one date. SAP splits cost center master data into a control table (CSKS), which carries the organizational attributes such as responsible person, hierarchy area and cost center category, and a text table (CSKT), which carries only the human-readable name. This split is standard practice across master data objects that need multilingual support. A cost center that exists for several years with attribute changes in between will have multiple CSKS rows for different validity periods, and correspondingly it can have multiple CSKT rows per language if the description itself changed at some point, or just one row per language if the name never changed even though the underlying CSKS validity period did.

Always restrict on MANDT implicitly and on KOKRS explicitly; skipping the controlling area on a large system returns text rows for cost centers that share a number across controlling areas and produces false matches. Restrict on SPRAS to the language actually needed, otherwise the same cost center returns once per maintained language and any downstream join multiplies row counts. DATBI is not a simple date filter, it is part of the key that defines validity periods, so selecting on DATBI equal to today's date misses periods that end in the future; use DATBI greater than or equal to the date of interest and take the lowest qualifying value, mirroring the standard pattern used against CSKS.

Symptom: a cost center report shows the correct number but a blank or 'unknown' description. Selection: read CSKT for that MANDT, KOKRS, KOSTL and the reporting SPRAS with DATBI greater than or equal to the report's key date, taking the smallest DATBI that satisfies it. No row at all means the text was never maintained in that language, most often because the cost center was created via a mass load that only populated the logon language. A row exists but with an old DATBI earlier than the key date points to a validity gap.

CSKT is unchanged in S/4HANA and continues to exist as a standard, directly maintained table. It was not absorbed into the universal journal because it is master data text, not a transactional or balance table, and the universal journal redesign in S/4HANA touched line-item and totals tables such as ACDOCA, not master data text tables. Cost center maintenance transactions still write to CSKS and CSKT exactly as in ECC.

Cost center descriptions are controlling master data, owned by the controlling or cost center accounting team, not by the technical basis team or the FI team running the general ledger. Language gaps are a data governance issue for whoever runs mass cost center creation or upload jobs, since a missing translation is a maintenance omission rather than a system defect.

CSKS is the paired control table carrying the actual organizational attributes and is where most cost center master maintenance transactions write; CSKT only ever receives the description fields from the same maintenance screens. CSKA holds cost element group texts by a similar pattern and is worth checking when a description problem turns out to be on the cost element side rather than the cost center side. COEP and ACDOCA are the transactional tables consultants typically join CSKT to when a report needs readable names instead of codes.