KA02 — Change Primary Cost Element - Classic
KA02 is used to change attributes of a classic primary cost element in ECC Controlling. It is most useful when correcting valid legacy CO master-data attributes in an ECC or migration context. Start with the exact organizational keys and business date, then prove the result from SAP documents, balances or logs before changing configuration or reposting data.
This page explains KA02 — Change Primary Cost Element - Classic — from a consultant's point of view: what it changes or displays, when it belongs in the process, which keys matter, how to prove the result, and the mistakes that create avoidable reconciliation work.
Published 19 Sept 2026· 601 words
Purpose
change attributes of a classic primary cost element in ECC Controlling. The transaction should be read in the context of the full accounting or logistics flow: source document, organizational assignment, posting date, configuration and resulting document all matter. A technically successful save is not enough; the output must reconcile to the intended business event.
When it is used
KA02 is typically used when correcting valid legacy CO master-data attributes in an ECC or migration context. In project testing it is equally useful for proving configuration and master data with a controlled example. In production, narrow the scope first and capture the before-state so any posting, clearing, settlement or master-data change can be reconciled afterward.
How to use it in practice
- Confirm the transaction is appropriate for the system release.
- Display the current master and dependent postings.
- Change only attributes permitted by accounting design.
- Test CO integration after the change.
- Capture migration implications for S/4HANA.
Key data objects
These are the fields and business objects that usually explain the result in KA02. Capture them in test evidence and incident handovers, because a mismatch in company code, plant, fiscal period, account or reference document is often more important than the screen message itself.
- controlling area — verify the exact value, validity/date context and source of derivation.
- cost element — verify the exact value, validity/date context and source of derivation.
- validity — verify the exact value, validity/date context and source of derivation.
- cost element category — verify the exact value, validity/date context and source of derivation.
- change history — verify the exact value, validity/date context and source of derivation.
How to prove it in the data
Prove the result end to end: identify the source document/master record, inspect the transaction's proposal or status, then open the resulting accounting or logistics document and reconcile amounts, quantities and account assignments. Use document flow, line-item displays and master-data history with the same fiscal period and organizational scope. That distinguishes a true configuration defect from a selection, timing or historical-data difference.
ECC vs S/4HANA
S/4HANA merges primary cost elements into G/L accounts; KA02 is therefore mainly a classic ECC reference transaction. On S/4HANA, Universal Journal, Business Partner, Material Ledger or Fiori may change the preferred analysis surface, but the business control behind the transaction still has to be understood and tested.
Common pitfalls and how to diagnose them
- Changing cost-element category after postings without impact analysis. Reconcile the exact document and period before making a configuration change.
- Using classic cost-element maintenance on S/4HANA instead of G/L master maintenance. Reconcile the exact document and period before making a configuration change.
- Treating a posting error as master data when account assignment is missing. Reconcile the exact document and period before making a configuration change.
Whose problem this is
Primary ownership is Finance/Controlling, with Basis or ABAP involved only when runtime, authorization or custom-code evidence points there. A useful escalation includes the business document, organizational keys, posting/valuation date, expected accounting result and the exact mismatch already proven.
Related SAP objects
Reviewed pages this object connects to in the ERPClimb knowledge graph.
Source: ERPClimb — https://erpclimb.com/sap-tcodes/ka02ERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.