KS01 — Create Cost Center Master Record
KS01 creates a new cost center master record in a given controlling area, defining its validity period, cost center category, hierarchy assignment, responsible person and company code link. It writes to the time-dependent cost center tables and is the entry point for any cost center that will later receive planning, actual postings or allocations.
This page covers the KS01 transaction for creating cost center master data, the fields and tables it writes, and the diagnostic patterns behind the most common posting and reporting failures traced back to a badly created cost center. It focuses on validity periods, controlling area consistency and hierarchy assignment, since these three drive nearly every downstream problem.
Reviewed by an ERPClimb SAP consultant on 15 Sept 2026· 1,135 words
Purpose
KS01 creates a cost center master record within a controlling area. A cost center is a time-dependent object: every attribute (category, hierarchy node, person responsible, company code, currency, lock indicators) is stored against a validity period, not once and for all. The single structural fact that explains most confusion downstream is that a cost center does not exist as one flat record; it exists as a stack of time slices, and a change made through KS02 outside an existing slice creates a new one automatically while a change inside a slice just overwrites it. Consultants who treat the cost center as a static object get caught out when a field they 'changed' was actually only changed from a later date, leaving old postings still governed by the earlier values.
When it is used
KS01 is used during enterprise structure build-out, cost center restructuring, new department or project setup, or whenever a new organizational unit needs to receive costs. It is reached for before any planning (KP06), allocation (KB11N, KB21N) or actual posting can target that unit. In S/4HANA landscapes many teams still use KS01 directly for one-off creation, while mass creation or template-driven rollout is handled through LSMW, migration cockpit, or a Fiori app for cost center management; KS01 remains the reference transaction consultants use to check what a correctly built record should look like before troubleshooting a batch load.
How to use it in practice
- Enter the cost center ID and controlling area, and specify the validity date range (from-date is critical, cannot be changed later without a new time slice).
- Optionally create with reference to an existing cost center to copy its category, hierarchy node and other defaults.
- On the basic data screen, set cost center category, currency, person responsible, department and cost center hierarchy node.
- On the control screen, review the lock indicators for actual primary/secondary postings, planning and revenue postings.
- On the templates or address tabs, optionally assign a costing sheet template or address details.
- Save; the system confirms the cost center number and validity period created.
Key data objects
- CSKS - the time-dependent cost center master record: controlling area, validity period, category, hierarchy node, company code, person responsible, currency, lock indicators.
- CSKT - the language-dependent short and long text for the cost center, keyed by controlling area, cost center and language.
- Standard hierarchy set/node tables - the cost center's position in the controlling area standard hierarchy, used for aggregated reporting.
- Change document tables (CDHDR/CDPOS) - if changed later via KS02, these log which field changed, old and new value, and the validity segment affected.
How to prove it in the data
Pull CSKS filtered on controlling area and cost center number, sorted by the validity date-from field, to see the full stack of time slices and which one is active on the posting date in question. Cross-check the company code stored on the cost center against the company code assigned to the same controlling area in the enterprise structure. Pull CSKT for the same key to confirm the text matches what users see on-screen, since a mismatch between category shown in KS03 and category stored in an old slice is a frequent source of 'it looks right but the posting still fails' tickets.
ECC vs S/4HANA
The transaction and its underlying time-dependent master data model are unchanged on S/4HANA. What differs is the increased use of cost center as a dimension inside universal journal reporting, and the availability of Fiori apps for managing cost center master data and hierarchies as an alternative front end. The classic tables and KS01/KS02/KS03 transaction codes remain valid and are still the ones consultants reach for when tracing history or comparing time slices directly.
Common pitfalls and how to diagnose them
- Validity gap or wrong start date: a posting with a date earlier than the earliest CSKS validity segment fails with a cost center not found for that date error. Check the from-date on the oldest segment before assuming the cost center is missing entirely.
- Controlling area to company code mismatch: the cost center's stored company code does not match the company code actually assigned to its controlling area in the enterprise structure, causing postings from that company code to be rejected or misrouted. Verify the controlling area-to-company code assignment first, not the cost center itself.
- Wrong cost center category: category controls which posting types (revenue, primary cost, secondary cost) are permitted. A posting rejected with a category-related error usually means the record was created from the wrong reference cost center and inherited the wrong category rather than having a genuine authorization problem.
- Lock indicators left on from a copied reference: creating with reference silently copies lock flags for actual postings, planning or revenues. A cost center that 'accepts nothing' is almost always a locked flag carried over from the template, not a missing assignment.
- Hierarchy node misassignment: the cost center lands under the wrong standard hierarchy node because the reference record used had a different node. This does not block postings but silently distorts cost center group reports and comparisons (KSU5-style analysis) until someone notices totals in the wrong node.
- Time-dependent overwrite confusion: a field changed via KS02 without opening a new validity segment overwrites history for the current segment, while a change made from a future date creates a new segment; consultants unaware of this misdiagnose 'the change did not take' when it actually took, just not for the period they are looking at.
Whose problem this is
Functional (CO) territory, owned by whoever maintains the controlling area's organizational structure. A clean handover to Basis or ABAP only happens if mass creation via a load program or interface is failing at a technical level; otherwise the fix is always a master data correction in KS02, not code. Handover notes should include the cost center ID, controlling area, and the exact validity date in question.
Related SAP objects
Reviewed pages this object connects to in the ERPClimb knowledge graph.
Source: ERPClimb — https://erpclimb.com/sap-tcodes/ks01ERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.