T001 table — Company Code Master Table

Each row in T001 represents one company code, the smallest legally independent unit for which a complete, self-contained set of accounts can be produced in FI. The row carries the identifying attributes needed to post and report: the company code key, its descriptive name, city, country, local currency, language, chart of accounts, and fiscal year variant. It does not carry transactional data and it does not carry every control parameter a company code needs; several of those live in satellite tables keyed by company code but maintained separately (global parameters, tax procedures, document number ranges). T001 is the parent record that those satellite tables and every FI document ultimately point back to.

T001 is small and fully client-dependent; always filter on MANDT and never assume a company code visible in one client exists in another. Selection is almost always by BUKRS, either a single code or a short explicit list; there is no reason to run this table without restricting on company code unless the goal is a full client inventory. The table rarely exceeds a few hundred rows even in a large enterprise, so performance is never the concern here, accuracy of the read is. The real risk is misreading a field's scope: currency, chart of accounts, and fiscal year variant shown here are the company code's own settings, not necessarily what a specific document or account actually used, since those can be overridden or derived elsewhere.

Symptom: a posting fails with a foreign currency or fiscal year period error and the consultant suspects the company code itself is misconfigured. Select T001 for the exact BUKRS in question and check WAERS against the currency used on the document, and PERIV against the fiscal year variant expected by the posting period control. A mismatch here explains a currency translation error or a 'period not open' message that otherwise looks like a document-level problem; agreement here means the fault lies downstream in period control or account assignment, not in the company code definition.

T001 is unchanged in structure and continues to exist as a transparent table on S/4HANA; it was not absorbed into the universal journal and was not replaced by a compatibility view. The universal journal (ACDOCA) carries its own company code field for the journal entry line and still relies on T001 as the master reference for company code attributes such as currency and chart of accounts. Consultants reading company code master data on S/4HANA use T001 exactly as on ECC.

Company code creation and its core attributes (currency, chart of accounts, fiscal year variant) are an FI configuration decision, owned by the FI/CO functional lead and typically locked down after go-live since changing currency or chart of accounts on a live company code is a major project in itself. Basis has no stake in this table beyond client transport; any change request touching T001 belongs with the FI configuration team, not with technical support.

Company codes are created and maintained through the standard company code configuration transaction in the IMG, which writes T001 along with linked entries for address and global parameters. Downstream, BKPF and BSEG carry the company code onto every posted document, ACDOCA carries it onto every universal journal line, SKB1 governs whether a given G/L account is actually usable in the company code, and T030 governs automatic account determination scoped by company code and chart of accounts.