T030 table — Standard account determination table for automatic postings

T030 is the delivered table underlying automatic account determination for the simplified transaction and event keys used across FI and MM-FI integration, configured through transactions such as OBYC and related account determination screens for tax, cash discount, exchange rate differences and rounding. One row represents a single G/L account, or an account pair for debit and credit sides, assigned to one chart of accounts for one transaction key, with no further split by valuation class, valuation grouping code, or account modifier. Transaction keys that need that finer differentiation, such as stock postings split by valuation class or bank clearing split by house bank, are held in separate satellite tables layered on top of T030, so T030 is only the base of the account determination framework, not the whole of it.

T030 is small and low-volume, so selectivity is rarely a performance concern, but misreading the key structure is common. Restrict on MANDT and KTOPL first, never on company code, because company code is not part of the key. If a search by transaction key alone returns nothing, confirm the chart of accounts being used is correct before assuming the configuration is missing. When a value looks present but the posting still fails, check whether the transaction key in question is actually resolved through this table at all, or through one of the satellite tables that layer additional differentiation on top of it.

Symptom: a posting fails with no account determined for a transaction key in company code 1000. Resolve the chart of accounts for 1000 in T001, then select T030 with that chart of accounts and the transaction key from the error. If no row exists, the base account determination is genuinely missing. If a row exists with an account in KONTS, check whether that account exists in SKB1 for company code 1000; a T030 row with no matching company-code master record produces the identical error message.

T030 continues to exist in S/4HANA as a configuration table for automatic account determination. It is not one of the tables affected by the move to ACDOCA and the universal journal, since that change concerns posted document data, not the account determination configuration itself. No structural change to this table should be assumed without checking the current system directly, but its role as the base account determination table has not been replaced by a CDS compatibility view.

Account determination configuration in T030 belongs to the FI functional consultant responsible for automatic postings, typically the same person configuring OBYC and related settings. Whether the assigned account actually exists and is usable belongs to whoever owns G/L master data maintenance. This table is not something Basis or an ABAP developer should edit directly outside the configuration transactions.

The satellite tables that extend T030 with valuation class, house bank, or cash discount differentiation are configured through the same account determination transactions and should be checked whenever a T030 lookup alone does not explain a posting failure. On the master data side, SKA1, SKB1 and SKAT hold the account records that a T030 entry ultimately points to, and T001 supplies the chart of accounts used to select the correct T030 row for a given company code.