T004 table — Chart of Accounts Master Table

One row in T004 represents one chart of accounts: a named account plan identified by a four character key (KTOPL), such as INT or a client specific key. It is the top of the GL account master hierarchy. A chart of accounts is not tied to a single company code; multiple company codes can share the same chart of accounts, and a company code can additionally reference a group chart of accounts and a country chart of accounts for consolidation and local statutory reporting. T004 only defines the plan itself and a few structural attributes of that plan. The actual GL accounts, their descriptions, and their company code specific control data live in other tables that reference KTOPL as a foreign key.

Only fields that are safe to rely on are listed here; anything else should be checked in the data dictionary before being used in a query.

The joins a consultant actually writes against T004 are almost always outbound from KTOPL into the account master and into company code assignment. T001-KTOPL = T004-KTOPL confirms which chart of accounts a given company code operates on. SKA1-KTOPL = T004-KTOPL confirms a GL account exists at the chart of accounts level under a valid plan. SKAT-KTOPL = T004-KTOPL is used to pull the account description in a given language for that chart. T030-KTOPL = T004-KTOPL is relevant when tracing automatic account determination, since account determination keys are also scoped by chart of accounts, not by company code directly.

T004 is a small configuration table, typically a handful of rows per client, so selectivity is not a concern the way it is for BSEG or ACDOCA. The only thing worth restricting on is MANDT, and even that is usually implicit in any client-dependent read. The table is worth querying directly only to answer a structural question: does this chart of accounts key exist, and is it flagged in a way that blocks new account creation. It is not the table to query to find out what accounts exist or what their balances are; that pull belongs to SKA1, SKB1, or the account balance tables.

Symptom: a GL account creation fails with a message saying the chart of accounts does not exist or is blocked. Selection: read T004 for the client and the KTOPL value shown on the error, and check its blocking indicator. If the row is missing entirely, the chart of accounts was never configured for that client, which is a Basis or transport issue, not a master data issue. If the row exists but is flagged, someone has deliberately closed that chart of accounts to new entries.

T004 is a configuration table, not a transactional one, so it was not absorbed into the universal journal and is not superseded by ACDOCA or a compatibility CDS view the way many FI line item tables were. It continues to exist in S/4HANA in essentially the same shape, maintained through the same chart of accounts configuration activity in the IMG. The practical difference in S/4HANA is that the chart of accounts decision has more downstream weight, because GL account master data now also underpins the merged ledger structure that feeds ACDOCA directly.

Most incidents involving T004 come from misreading what the table represents, not from the table itself being wrong.

The chart of accounts design belongs to the FI general ledger lead during the initial build, since it is a foundational, hard to reverse decision. Once live, questions about a specific KTOPL entry, including blocking flags, are handled by whoever owns FI configuration in the support team, not by a functional GL analyst working account by account.

Directly related tables are the text table for chart of accounts descriptions, and the GL account master tables SKA1 and SKB1 that reference KTOPL as a foreign key. T001 supplies the company code to chart of accounts mapping, and T030 uses the same key to scope automatic account determination. The relevant maintenance transaction is the chart of accounts configuration activity in the IMG under general ledger accounting; GL account maintenance transactions write to SKA1 and SKB1 but validate against T004 on save.