SAP automatic account determination (OBYC and VKOA): preventing posting errors before go-live
How MM account determination (OBYC) and SD revenue account determination (VKOA) resolve G/L accounts from valuation classes and account assignment groups, and why postings fail after transports.
- Last reviewed:
- Target releases:
- SAP ECC 6.0, SAP S/4HANA, SAP S/4HANA Cloud
- Version:
- 1
- Source provenance:
- Editorial content, technically reviewed
How automatic account determination works
When a goods movement is posted in Materials Management or a billing document is released to Financial Accounting, SAP determines the general ledger (G/L) accounts automatically from configuration tables:
- Materials Management (OBYC / T030): combines chart of accounts, transaction key (such as BSX, WRX, GBB), valuation grouping code, account modification (general modification) and valuation class from the material master.
- Sales and Distribution (VKOA): uses condition tables (such as application V, condition type KOFI) matching chart of accounts, sales organisation, account assignment group of the customer, account assignment group of the material and account key (such as ERL, ERS, MWS).
Why postings fail in test or production
- Missing combination for a new valuation class or account assignment group. Master data introduces a new classification value that has no row in T030 or the VKOA condition tables.
- Uncreated or blocked G/L account in company code (FS00 / SKB1). The determination table points to a G/L account that exists in the chart of accounts (SKA1) but is not extended to the posting company code or is blocked for posting.
- Tax code or field status conflict. The G/L account requires a tax category or cost object (cost center, profit center, WBS element) that the document flow does not supply.
- Incomplete transport across systems. Account determination rows were maintained in development without transporting all dependent valuation grouping codes or company code G/L segments.
How to verify account determination before import
- Cross-check every active valuation class and customer/material account assignment group against the OBYC and VKOA assignment matrices for each chart of accounts.
- Verify that every target G/L account exists in all active company codes, is not blocked, and has compatible tax and field status settings.
ERP Preflight's Account Determination Preflight engine validates exported OBYC, VKOA and G/L master tables to flag missing combinations and unextended accounts before a transport reaches production. See Operations.
This article is general information about SAP concepts and does not replace SAP documentation for your specific release.
Sources
Related solution areas
Related engines: Account Determination Preflight
Related
SAP problems covered by this article
- CriticalDetermined G/L account is blocked for posting
- CriticalDetermined account not created in the company code
- CriticalExpected combination resolves to no account
- CriticalNo G/L account determined for a required combination
- CriticalMovement type / plant / valuation class without OBYC account
- MajorConflicting determination entries for the same key