TKA02 table — Company Code Assignment to Controlling Area

Each row in TKA02 represents one company code assigned to one controlling area. This is the Customizing content behind the enterprise structure step that answers the question of which controlling area a given company code's postings flow into for cost and profit reporting. In a single controlling area setup there is one row per company code, all pointing to the same KOKRS, enabling cross-company-code cost center accounting, internal orders, and profit center reporting across those company codes. The table does not carry currency, fiscal year variant, or operating concern information for the controlling area itself, only the linkage between the two organizational units. It is read constantly at runtime by CO postings to determine which controlling area a financial document derives into, even though it is maintained rarely, usually only during system setup or a legal entity restructuring.

TKA02 is a Customizing table, not a transactional one, so it is small, has no meaningful selectivity concerns, and every read should be scoped by client anyway since MANDT is always the leading key. There is normally no need to restrict further, a full table dump for the client in question is typically a handful to a few dozen rows. The only trap is treating a stale copy from a sandbox or golden client as representative of production, since assignments can differ between systems during a phased rollout or after a merger where a company code has not yet been reassigned everywhere.

Symptom: a cost center report or internal order shows no data for a company code that should be posting, or a posting fails with an error that the company code is not assigned to any controlling area. Select TKA02 for MANDT equal to the current client and BUKRS equal to the company code in question. No row means the company code has never been assigned and CO postings will be rejected at document derivation. A row pointing to an unexpected KOKRS confirms the company code is live but reporting into a different controlling area than the one being queried.

TKA02 continues to exist in S/4HANA in the same shape, it is untouched by the Universal Journal changes because it is a lean Customizing table rather than a document or totals table. The assignment logic it drives still governs how a company code's postings derive a controlling area on ACDOCA lines. No compatibility view is needed for it since there was never a redundant totals table equivalent to replace, the assignment step and its underlying table are functionally identical to the classic ECC behavior.

This is an enterprise structure decision, owned by the FI-CO configuration lead during system design or a legal entity change project, not something touched during routine support. A missing or wrong assignment is escalated to whoever owns organizational structure configuration, not to a functional CO cost center or profit center consultant, since the fix sits one layer below where they normally work.

The controlling area master data itself sits in a separate table alongside TKA02 and carries currency and fiscal year variant settings, it should be checked first for anything currency or period related. Downstream, cost center master data in CSKS and CSKA, and cost element master data, only make sense within the controlling area a company code has been assigned into via TKA02. The assignment is maintained through the enterprise structure IMG activity for assigning a company code to a controlling area, typically accessed through transaction OX19, while the controlling area itself is created and maintained through transaction OKKP.