OBYC — Automatic Account Determination for MM
OBYC is used to configure G/L account determination for inventory management transactions such as BSX, WRX and GBB. It is most useful when goods movements or invoice postings hit the wrong account or fail with missing account determination. Start with the exact organizational keys and business date, then prove the result from SAP documents, balances or logs before changing configuration or reposting data.
This page explains OBYC — Automatic Account Determination for MM — from a consultant's point of view: what it changes or displays, when it belongs in the process, which keys matter, how to prove the result, and the mistakes that create avoidable reconciliation work.
Published 19 Sept 2026· 631 words
Purpose
configure G/L account determination for inventory management transactions such as BSX, WRX and GBB. The transaction should be read in the context of the full accounting or logistics flow: source document, organizational assignment, posting date, configuration and resulting document all matter. A technically successful save is not enough; the output must reconcile to the intended business event.
When it is used
OBYC is typically used when goods movements or invoice postings hit the wrong account or fail with missing account determination. In project testing it is equally useful for proving configuration and master data with a controlled example. In production, narrow the scope first and capture the before-state so any posting, clearing, settlement or master-data change can be reconciled afterward.
How to use it in practice
- Read the exact account-determination error key or accounting simulation first.
- Identify transaction key and valuation class.
- Check valuation grouping code/plant context.
- Compare the intended posting with existing configuration patterns.
- Change account determination only with MM and FI approval, then test the accounting document.
Key data objects
These are the fields and business objects that usually explain the result in OBYC. Capture them in test evidence and incident handovers, because a mismatch in company code, plant, fiscal period, account or reference document is often more important than the screen message itself.
- chart of accounts — verify the exact value, validity/date context and source of derivation.
- transaction key — verify the exact value, validity/date context and source of derivation.
- valuation grouping code — verify the exact value, validity/date context and source of derivation.
- valuation class — verify the exact value, validity/date context and source of derivation.
- G/L account — verify the exact value, validity/date context and source of derivation.
How to prove it in the data
Prove the result end to end: identify the source document/master record, inspect the transaction's proposal or status, then open the resulting accounting or logistics document and reconcile amounts, quantities and account assignments. Use document flow, line-item displays and master-data history with the same fiscal period and organizational scope. That distinguishes a true configuration defect from a selection, timing or historical-data difference.
ECC vs S/4HANA
OBYC remains critical in S/4HANA Inventory Management. Material Ledger and Universal Journal increase integration, but the underlying MM-FI account-determination principles remain. On S/4HANA, Universal Journal, Business Partner, Material Ledger or Fiori may change the preferred analysis surface, but the business control behind the transaction still has to be understood and tested.
Common pitfalls and how to diagnose them
- Adding a G/L account against the wrong valuation class. Reconcile the exact document and period before making a configuration change.
- Changing OBYC before confirming the material and movement type are correct. Reconcile the exact document and period before making a configuration change.
- Testing stock quantity but not the generated FI document. Reconcile the exact document and period before making a configuration change.
Whose problem this is
Primary ownership is MM with FI involvement for accounting effects, with Basis or ABAP involved only when runtime, authorization or custom-code evidence points there. A useful escalation includes the business document, organizational keys, posting/valuation date, expected accounting result and the exact mismatch already proven.
Related SAP objects
Reviewed pages this object connects to in the ERPClimb knowledge graph.
Source: ERPClimb — https://erpclimb.com/sap-tcodes/obycERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.