SKA1 table — G/L Account Master Chart of Accounts Segment

One row in SKA1 represents a G/L account defined at chart of accounts level, identified by chart of accounts plus account number. This is the account's global shell: it exists here before it is extended to any company code. The row carries classification data that is meant to be identical everywhere the account is used, chiefly whether the account is a balance sheet account or a P&L account, and the account group that governs its number range and field status. It does not hold the account description, which lives in the language-dependent text table, and it does not hold anything company-code specific such as account currency, tax category, open item management, or the field status group used for postings, all of which live in the company code segment table. SKA1 without the company code segment is an account that has been created but not made usable for posting anywhere.

SKA1 is client-dependent through MANDT but not company-code-dependent, so restricting on client alone still returns every account in every chart of accounts used by that client. Always restrict on KTOPL first; without it, an account number like 400000 can collide across two unrelated charts of accounts and produce a join that looks correct but pairs the wrong rows. The table is small relative to line item tables, so performance is rarely the issue; correctness of the KTOPL filter is. If working from a company code rather than a chart of accounts, resolve KTOPL from T001 first rather than guessing it.

Symptom: a posting fails with an account blocked message and it is not obvious whether the block is company-code specific or global. Read SKA1 for the chart of accounts and account number and check XSPERR; if set, the account is blocked everywhere regardless of company code. If XSPERR is not set here, the block is coming from the company code segment in SKB1 for that specific company code, not from SKA1.

SKA1 continues to exist as a table in S/4HANA and the split between chart of accounts segment, company code segment, and text table is unchanged. G/L account master maintenance is typically done through a single transaction or Fiori app that writes to SKA1, SKB1, and SKAT together, but the underlying table structure and the fact that they are separate tables persists. No specific version detail beyond that general continuity is claimed here.

Chart of accounts structure and the accounts defined in SKA1 are owned centrally by FI configuration, usually the team responsible for the corporate chart of accounts, not by local company code finance teams. Extending an existing account to a new company code is a company-code-level activity and often delegated locally, but creating or changing the account at chart of accounts level is a central decision.

SKB1 holds the company-code segment written alongside SKA1 when an account is created or extended. SKAT holds the language-dependent description. T004 is the chart of accounts master, and T001 links company codes to their chart of accounts. Maintenance transactions for creating, changing, and displaying the full G/L account master typically write to all three tables in a single transaction.