KS02 — Change Cost Center Master Data

KS02 opens an existing cost center for change within a controlling area. It covers the same field groups as creation: basic data (name, description, cost center category, person responsible), control data (currency, record quantity), templates, address, and communication. The structural fact that explains most confusion: cost center master data is time-dependent. Every field group lives inside a validity interval bounded by a start date and an end date. A change does not overwrite the current record in place; it either extends the existing interval or splits it into two, closing one segment and opening a new one from the change date forward. Reporting that joins postings to current master data by date will show different attributes for the same cost center depending on which period is being reported.

Used whenever an already-created cost center needs a correction or a business change: reassigning the person responsible after a reorg, renaming the cost center, moving it to a different node in the standard hierarchy, changing its category to allow or block certain postings, or toggling the lock indicators that control which transaction types (actual primary postings, secondary postings, revenues, commitments, planning) are allowed against it. It sits in the same maintenance family as KS01 and KS03 and is reached directly by transaction code far more often than through a Fiori app, because most CO teams still run master data changes through the classic GUI transaction or a batch input program for mass changes. Mass changes across many cost centers at once go through the mass maintenance transaction instead of KS02 one record at a time.

Pull CSKS filtered on controlling area and cost center number and sort by the validity start date; this shows every segment and exposes gaps or overlaps at a glance. Cross-check CSKT on the same key plus language for the description that was active on a given date. To see who changed what and when, pull CDHDR filtered on object class for cost centers and the specific cost center as the object value, then join to CDPOS for the field-level old and new values. Compare the change timestamp against posting document dates to explain why a report shows attributes that do not match what the requester expects today.

The master data model and the time-dependent segment structure are unchanged on S/4HANA; KS02 still works exactly as in ECC. A Fiori app for managing cost centers exists and covers the same field groups with a modern UI, but the underlying tables and validity logic are identical, so diagnostics performed against CSKS and CSKT apply regardless of which front end was used to make the change.

Functional CO ownership. A controlling consultant maintains the cost center; changes that affect company code or account assignment logic may need FI sign-off. Basis involvement is limited to authorization group setup on the cost center or change document configuration. A good handover includes the cost center number, the change date used, the old and new field values, and whether the change was a segment extension or a split.

Read KS01 first to understand the fields being changed here, since KS02 exposes the identical field groups on an existing record rather than a new one. KS03 is the display-only counterpart, useful for confirming a change landed correctly without risking an accidental edit. KSB1 pulls the actual line items posted to the cost center, the fastest way to check whether a lock indicator or category change actually affected postings as expected. KP06 is where planning data for the cost center lives, relevant when a hierarchy or category change has knock-on effects on planning layouts.