MM / P2Pbeginner

MM Account Determination Part 1: Why Automatic Account Determination Exists

Key takeaway

Warehouse users post goods movements, not journal entries — SAP finds the G/L accounts automatically. Learn the idea, the key ingredients (chart of accounts, valuation area grouping, valuation class, transaction key, modifier), and how a GR and a GI find their accounts.

What this complete series covers

Learn Automatic Account Determination in a clear, practical sequence — from the basic idea to real project use, troubleshooting, and interview-ready understanding.

Who it is for: Best for SAP consultants, developers, and learners who want a practical understanding of Automatic Account Determination.
Prerequisites: Basic SAP S/4HANA navigation and an understanding of the business process are helpful. Configuration or transaction steps require suitable access to a practice or project system.
Final outcome: By the end, you should be able to explain Automatic Account Determination clearly, follow the main end-to-end flow, apply it in a project scenario, and troubleshoot the most common issues.

Part 1: MM Account Determination Part 1: Why Automatic Account Determination Exists
Understand the business problem automatic account determination solves, where it fits in the P2P document flow, and which master data drives it.
Part 2: MM Account Determination Part 2: Configuring Valuation Classes, Grouping Codes and OBYC
Learn the configuration structure behind automatic account determination, including transaction keys, valuation classes, and how the OBYC transaction ties them together to determine GL accounts.
Part 3: MM Account Determination Part 3: Transaction Keys, Modifiers and Movement Types
Learn how transaction/event keys such as BSX, GBB, PRD, and WRX combine with valuation modifiers and account grouping codes to determine the exact G/L account posted for each material movement.
Part 4: MM Account Determination Part 4: Architecture for Multi-Entity, Multi-System Landscapes
Explores the architectural decisions, governance model, and migration strategy required to design a scalable, auditable automatic account determination framework across multiple co
Part 5: MM Account Determination Part 5: Troubleshooting and Production Support
Develop a systematic diagnostic approach for resolving account determination failures in production, covering root-cause analysis tools, common error patterns, cross-module impacts

System and release assumptions: Examples focus on SAP S/4HANA. Exact apps, transaction codes, configuration paths, and field names can vary by release and deployment model.

Explanation

📌 KEY POINTS
✅ Logistics users post movements; SAP derives G/L accounts automatically.
✅ Inputs: chart of accounts (from company code), valuation grouping code (from valuation area), valuation class (from material), transaction key and account modifier (from movement type).
✅ Main keys: BSX stock, WRX GR/IR, GBB offsetting entries, PRD price differences.
✅ Configuration is maintained in OBYC with finance.
⚠️ Missing entries stop postings; wrong entries post silently to wrong accounts.

━━━━━━━━━━━━━━━━━━━━
▶ WHAT THIS SERIES COVERS
Part 1: Why account determination exists
Part 2: Configuration — valuation classes, grouping codes and OBYC
Part 3: Transaction keys, modifiers and movement types
Part 4: Architecture for multi-entity landscapes
Part 5: Troubleshooting and production support

━━━━━━━━━━━━━━━━━━━━
▶ 1. THE PROBLEM

Thousands of movements; consistent postings without FI knowledge.

━━━━━━━━━━━━━━━━━━━━
▶ 2. INGREDIENTS

Chart of accounts, grouping code, valuation class, key, modifier.

━━━━━━━━━━━━━━━━━━━━
▶ 3. MAIN KEYS

BSX, WRX, GBB, PRD.

━━━━━━━━━━━━━━━━━━━━
▶ 4. EXAMPLES

GR: BSX/WRX; GI to cost center: GBB-VBR/BSX.

━━━━━━━━━━━━━━━━━━━━
▶ 5. OWNERSHIP

Joint MM–FI responsibility.

━━━━━━━━━━━━━━━━━━━━
▶ STEP BY STEP

Post a GR; open the accounting document.
Map each line to a transaction key.

✅ CHECKPOINT: you can explain how SAP found each account.

Code example

ABAP Code

===== STEP 1: determination chain =====Company code → chart of accounts | plant → valuation area → grouping code | material → valuation class | movement type → key + modifier ===== STEP 2: GR example =====101: BSX (stock) Dr | WRX (GR/IR) Cr ===== STEP 3: GI example =====201: GBB-VBR (consumption) Dr | BSX Cr

Real project scenario

During a plant rollout, goods receipts began failing with account determination errors. The new plant had a new valuation grouping code but no OBYC entries. Copying the approved entries from the existing grouping code with finance review fixed it within hours.

Common mistakes

Thinking MM users choose accounts.
Ignoring grouping codes.
Editing OBYC without finance.
Not testing movements.
Forgetting modifiers.

Best practices

Learn the determination chain.
Involve finance.
Test movements.
Document entries.
Review after changes.

Interview angle

Questions: "Why is account determination automatic?", "What are its inputs?", "What does BSX mean?"
Strong answer: determination chain, main keys, examples, MM–FI ownership.

Practice this lesson

Quick check

1. Which transaction/event key determines the stock (inventory) G/L account that is debited when goods are received against a purchase order for a valuated material?

2. When an invoice is posted with a price higher than the purchase order price for a material valuated at moving average price, and sufficient stock quantity exists to absorb the difference, which transaction/event key typically receives the price difference so it is capitalized into inventory value rather than expensed?

3. When goods are issued to a cost center using a consumption movement type, which transaction/event key determines the offsetting expense account for that posting?

Interview questions

1. When a standard goods receipt against a purchase order is posted with movement type 101, which two OBYC transaction keys are typically triggered, and what does each one control in the resulting accounting document?

Answer it in your own words first, then compare.

2. How do transaction keys in OBYC ensure that inventory postings from goods movements correctly integrate with the general ledger during period-end inventory closing, and what risk arises if a transaction key is left unmapped for a new valuation class?