KS03 — Display Cost Center Master Record

KS03 displays a cost center master record: the controlling area, cost center, and validity period combination, spread across tabs for basic data (name, person responsible, hierarchy area, cost center category), control indicators (which record types the cost center accepts - actual primary costs, actual secondary costs, revenues, commitments), templates, address, communication, and history. The one structural fact that explains most confusion is that a cost center master record is time-dependent: each field group can have a different value in a different validity segment, and KS03 only shows the segment that covers the date you enter on the initial screen. A cost center that looks wrong today may simply be displaying last year's segment because nobody typed a current date.

KS03 is reached for whenever a posting to a cost center fails, behaves unexpectedly, or a report shows a cost center with no activity, and the first question is whether the master data explains it. Typical triggers: a posting is blocked with a message about a control indicator, a cost center does not appear in a report because its validity period does not cover the posting date, or a cost center category restricts what account assignments are allowed. It is used ahead of KS01 or KS02 to see current state before changing anything, and instead of a Fiori app when the consultant wants the raw tab structure rather than a summarized display. For actual postings on the cost center, KSB1 is the follow-up transaction, not KS03.

Pull CSKS with controlling area and cost center as keys, restrict on DATBI (valid-to date) greater than or equal to the posting date in question and DATAB (valid-from date) less than or equal to it, to find the exact validity segment covering the disputed transaction date. Compare the control indicator fields in that segment against the record type the posting used. If a report shows the cost center missing, check whether any segment covers the report period at all; a gap between two DATBI/DATAB ranges means the cost center was inactive during that window.

KS03 still exists and behaves the same way on S/4HANA; the transaction has not been replaced. S/4HANA does add Fiori apps for managing and displaying cost center master data through the manage cost centers app family, and some organizations route consultants there for a friendlier view with search and mass display, but the underlying master data structure and validity logic KS03 exposes are unchanged. For deep diagnostic work, especially checking exact validity segments, KS03 or a direct table read remains more reliable than the Fiori summary view.

This is a functional CO master data issue, owned by the controlling or FI/CO consultant maintaining organizational structures, not Basis or ABAP unless a change document or authorization trace is needed. A good handover includes the controlling area, cost center, the exact posting or report date in question, the validity segment pulled from CSKS covering that date, and which specific control indicator or hierarchy field appears inconsistent with the observed behavior.

KS01 and KS02 are the create and change counterparts and are the natural next stop once KS03 confirms what needs to change. KSB1 shows actual line items posted to the cost center and is the transaction to run when KS03 confirms the master data is fine but the posting itself is in question. KP06 is relevant when the investigation shifts from actual postings to planned values on the same cost center. FS00 is worth comparing against for anyone learning cost center master data for the first time, since it follows the same time-dependent-segment pattern on the GL account master side.