ERPClimb logoERPClimb

SAP MM / P2P Automatic Account Determination Interview Questions

Interviewers use automatic account determination to test depth rather than coverage: the follow-up question is almost always "why does the system behave that way?", and that is where prepared answers usually run out.

Automatic Account Determination governs how SAP MM derives General Ledger accounts for goods movements and invoice postings without manual account entry, using valuation classes, movement type-derived transaction keys, and configuration maintained through account determination tables. This topic covers the business purpose, master data dependencies, configuration structure, integration with Finance and Controlling, and the troubleshooting skills consultants need to diagnose posting errors across ECC and S/4HANA.

This page carries 32 reviewed SAP MM / P2P automatic account determination interview questions, each with a complete written answer and no sign-in required. The set breaks down into 3 foundational, 24 mid-level and 5 advanced questions, so you can start at the top for a first interview or skip ahead to the scenario-based items for a senior round.

If you can handle every question here without hesitating, automatic account determination is unlikely to be what costs you an SAP MM / P2P interview — and the same reasoning pattern transfers to the neighbouring topics linked at the bottom of this page.

32 Automatic Account Determination questions with answers

easyAutomatic Account Determination

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?

Movement type 101 triggers BSX, which determines the stock/inventory account debited based on valuation class, and WRX, which determines the GR/IR clearing account credited for the invoice-verification offset. BSX depends on valuation class and account category reference from the material master, while WRX is generally independent of valuation class and posts a provisional liability until the vendor invoice is matched in MIRO.
easyAutomatic Account Determination

2. When a goods receipt is posted against a purchase order, which account determination transaction keys drive the postings to the GR/IR clearing account and the stock account, and how does the system decide which G/L accounts to use?

Goods receipt for a PO triggers two postings: the stock account debit via transaction key BSX (valuation class based) and the GR/IR clearing account credit via transaction key WRX. OBYC maps these keys to G/L accounts based on chart of accounts, valuation grouping code, and valuation class from the material master. Movement type 101 uses these keys by default; the actual accounts are never hardcoded in the movement type itself.
easyAutomatic Account Determination

3. What is the accounting impact of a transfer posting between two plants using movement type 301, and which G/L accounts are typically affected?

A 301 movement debits inventory in the receiving plant and credits inventory in the issuing plant, both determined via account determination (transaction key BSX) using the valuation class of the material. If the plants belong to different company codes, an intercompany clearing entry is also generated using the appropriate posting keys and clearing accounts configured in OBYC.
mediumAutomatic Account Determination

4. A goods receipt for a new plant fails with an account determination error even though OBYC settings appear correct for existing plants. What sequence of checks would you perform to resolve it?

First verify the valuation grouping code is correctly assigned to the new plant in OMWD, since account determination in OBYC is grouped by valuation grouping code, not directly by plant. Next check that the material's valuation class and the plant's valuation area are consistent, and confirm chart of accounts assigned to the new plant's company code matches the OBYC configuration for that grouping code and transaction key. Finally validate that the GL account exists and is not blocked for automatic posting.
mediumAutomatic Account Determination

5. In OBYC, how does the combination of valuation class and transaction key ensure the correct GL account is derived for a warehouse goods movement, and what configuration elements must align for this to work correctly?

OBYC maps each transaction key (e.g., BSX, GBB, PRD) to GL accounts per chart of accounts, optionally refined by valuation modifier (valuation area grouping), valuation class, and account modifier (e.g., movement type-derived VBR, INV). The material master's valuation class links the material to a set of accounts; the movement type triggers the transaction key logic. All three—chart of accounts, valuation class, and modifier—must be consistently maintained, or the system throws an account determination error at posting.
mediumAutomatic Account Determination

6. A batch of shelf-life-controlled material was moved to blocked stock upon expiration, but the write-off posting hit the wrong GL account, causing an incorrect scrap expense classification. How would you troubleshoot the account determination for this movement?

I'd identify the movement type used for the expiration write-off (typically 551/552 for scrapping) and check its account modifier assignment in OMJJ, then trace that account modifier combined with the material's valuation class in OBYC under transaction key GBB to see which GL account is mapped. If the account modifier for scrapping isn't distinctly configured from normal issues, the posting could default to a generic expense account instead of the intended scrap account, requiring an OMJJ update to assign a specific account modifier for the scrap movement type.
mediumAutomatic Account Determination

7. How does the system determine which transaction key (e.g., BSX, GBB, PRD) is used to post the G/L account for a given movement type, and what configuration steps control this?

Each movement type is linked to one or more transaction/event keys in OMJJ configuration, which map to specific account modification keys (e.g., GBB with modifiers like VBR, AUF, VAX). OBYC then assigns actual G/L accounts to these transaction keys per valuation class and chart of accounts. The combination of movement type, special stock indicator, and account modifier ultimately drives the account posted.
mediumAutomatic Account Determination

8. A finance controller asks you to explain, end-to-end, how a physical inventory difference posted via MI07 flows through automatic account determination into the Universal Journal, including which tables and transaction key are involved. How would you walk them through this integration?

Posting the count difference in MI07 triggers a goods movement (typically 701/702) that calls OBYC account determination using transaction key GBB with the applicable general modification for inventory differences and the material's valuation class. This generates a material document (MSEG) and an accounting document (BKPF/BSEG), which in S/4HANA also creates a corresponding ACDOCA line carrying the GL account, cost object, and material data for real-time financial reporting.
mediumAutomatic Account Determination

9. A company wants to report and financially provision for slow-moving/aging inventory, but SAP Inventory Management does not natively flag aged stock for automatic write-down postings. How does automatic account determination integrate when a manual or batch-driven aging provision is eventually posted, and what design would you recommend?

Standard IM has no automatic aging trigger; aging is typically identified through custom reporting (e.g., stock aging list by GR date or batch) outside OBYC logic. When management decides to write down aged stock, the actual posting is usually a manual FI journal entry or a physical inventory count adjustment (movement type like 551/552 for scrapping) that then flows through GBB/PRD as normal. Design recommendation: build aging analytics in reporting layer, then route confirmed write-downs through standard scrapping or valuation adjustment movement types so account determination stays consistent with existing OBYC configuration rather than creating parallel logic.
mediumAutomatic Account Determination

10. At period-end close, goods issues for cost center consumption are posting to an unexpected GL account different from prior periods, even though no OBYC configuration changes were made. What integration factors would you check between MM and FI-GL?

I would check whether the valuation class on the material master was changed, since that alone can redirect postings without touching OBYC. I would also verify if a new movement type or account modifier combination is now in use, whether the cost center or account assignment category changed on the goods issue document, and whether a valuation area or plant reassignment occurred. Additionally, I would confirm no parallel account determination rule (e.g., split valuation) was newly triggered for that material.
mediumAutomatic Account Determination

11. A physical inventory count reveals a batch of material that has passed its shelf-life expiration date, and the write-off posting hits an unexpected general ledger account instead of the expected scrapping expense account. What would you check to diagnose the root cause?

I would check which movement type was used for the inventory difference posting, since physical inventory adjustments and manual scrapping can use different movement types mapping to different transaction keys. Likely the discrepancy is a valuation class mismatch on the batch or an incorrect OBYC assignment for the GBB transaction key with the relevant account modifier, such as VNG for scrapping versus the general inventory difference key used for count adjustments. I'd verify the account modifier configuration per movement type and confirm the material's valuation class matches expectations for expired stock handling.
mediumAutomatic Account Determination

12. In a Central Procurement (SAP S/4HANA hub) landscape sourcing requisitions from multiple connected ECC/S4 backend systems, how does account assignment get resolved when the requisition originates in a backend system but the PO is created centrally?

Central Procurement typically keeps requisitioning in the backend system (via SAP Fiori app 'Process Purchase Requisitions - Central Procurement' or replication), and account assignment data (cost center, WBS, order) from the backend requisition is replicated to the hub via the integration model (CDS-based replication/SOA) and preserved when the PO is created centrally, then the resulting PO is either created in the hub or pushed back to the backend depending on the sourcing model. Validity of account assignment objects (cost center existing in backend company code) must be checked during replication to avoid failures.
mediumAutomatic Account Determination

13. During physical inventory processing, which transaction key determines the GL account for posting inventory differences, and how is it configured?

Inventory differences identified during physical inventory count and cleared via MI07 post to the GL account assigned to transaction key GBB with account modifier VBR (or a similar modifier depending on movement type) in OBYC, differentiated by valuation class. Configuration requires assigning valuation class-specific G/L accounts under GBB in the account determination table, ensuring the difference posts to the correct inventory-adjustment or expense account per material valuation class and chart of accounts.
mediumAutomatic Account Determination

14. A service PO needs to be split across three cost centers with different percentages, and finance wants each split to hit a different GL account based on the service category. How would you configure account assignment for this scenario?

Use multiple account assignment on the service PO item with account assignment category K and distribution indicator set to percentage, entering the cost center and percentage split for each of the three lines. Since GL account derivation for services is normally driven by the valuation class/account category reference on the service master or a manually entered G/L account per account assignment line, ensure each split line can carry its own G/L account override if service categories require different postings; otherwise use different service line items (each with its own account assignment) rather than a single split line if the accounts must differ.
mediumAutomatic Account Determination

15. When Material Ledger with actual costing is active, how does automatic account determination in OBYC interact with the material's standard price versus the periodic unit price?

During the period, goods movements post at the standard price via OBYC transaction keys (BSX, PRD, etc.), so inventory and consumption accounts reflect standard cost. At period-end settlement (CKMLCP), the Material Ledger calculates the actual periodic unit price and revalues consumption and stock, posting price differences to the accounts defined for the relevant transaction keys, not changing the OBYC-driven real-time postings retroactively but adjusting via ML settlement documents.
mediumAutomatic Account Determination

16. A company wants finished goods and raw materials in the same plant to post to different valuation classes and GL accounts automatically during goods movements. How does the valuation area, material type, and account determination configuration work together to achieve this?

Valuation area (typically the plant) defines the scope for valuation and account determination via the valuation grouping code linked to the plant. Material type governs which valuation classes are allowed for a material, and the valuation class on the material master's accounting view, combined with the movement type and transaction/event key, determines the GL account hit in OBYC. So raw materials and finished goods, though in the same plant, post differently because they use different valuation classes tied to their material types.
mediumAutomatic Account Determination

17. At period-end close, a scrapping goods issue using movement type 551 unexpectedly posts to a different general ledger account than the cost center's normal consumption account. Walk through how you would trace the transaction key and general modifier combination responsible and correct the account determination.

I would first check the movement type's account grouping and general modifier assigned in OMWN, since scrapping typically maps to transaction key GBB with a distinct general modifier such as VBR or VNG rather than the general consumption modifier used for cost center issues. Then I would review OBYC for GBB against that specific modifier, valuation class, and valuation area combination to confirm which GL account is assigned, since scrapping is deliberately routed to a separate expense account for reporting visibility, which may explain the difference rather than indicate an error.
mediumAutomatic Account Determination

18. A physical inventory count reveals a stock discrepancy, and after posting the adjustment via MI07, the GL account that receives the posting is not the expected inventory adjustment account. How would you investigate the OBYC transaction key involved and correct the account determination?

Physical inventory differences typically post via transaction key GBB with account modifier VNG (inventory difference/scrapping) or similar, depending on movement type used by the count adjustment. I'd trace the posting document to identify the movement type, then check OBYC for GBB with the relevant valuation modifier and valuation class combination assigned to that material, verify the account assignment in the configuration, and correct the account or valuation class mapping if it points to the wrong GL account.
mediumAutomatic Account Determination

19. During physical inventory processing, how does the system determine which GL accounts are hit when posting inventory differences, and what configuration governs this?

Inventory differences from physical inventory count postings (movement type 701/702) are valuated using the material's current price control and posted via automatic account determination in OBYC under transaction key GI/GA (inventory difference offsetting) or similar keys tied to the valuation class. The account is determined by combining chart of accounts, valuation grouping code, valuation class, and the general modification key configured for that transaction key, ensuring differences flow to the correct P&L or inventory-adjustment accounts.
mediumAutomatic Account Determination

20. During period-end close, automatically created purchase orders (generated via source list or scheduling agreement with the automatic PO indicator) for a material trigger goods receipts that post to a different valuation class GL account than manually created POs for the same material. How would you investigate this account determination discrepancy?

First confirm the material master's valuation class is identical regardless of PO creation method; if so, the automatic PO likely references a different plant, purchasing info record, or account assignment category that changes valuation. Check whether the automatic PO used a different document type or was created against a subcontracting/consignment info record versus a standard one, since these use different transaction keys (BSX vs. GBB or FRL). Also verify if the automatic PO indicator triggered a different account assignment category (e.g., cost center vs. stock) that redirects the GR posting entirely.
mediumAutomatic Account Determination

21. A goods receipt posting fails with an account determination error referencing a missing entry for transaction key BSX. How would you diagnose and resolve this?

I would open OBYC for transaction key BSX and check whether an entry exists for the combination of chart of accounts, valuation grouping code, and valuation class assigned to the material in question. Missing entries commonly occur when a new valuation class was created but not mapped in BSX, or when valuation grouping code activation was toggled without maintaining all required combinations. I would add the missing account assignment, confirm it aligns with the balance sheet inventory account strategy, and reprocess the goods receipt.
mediumAutomatic Account Determination

22. A purchasing group manages procurement across multiple plants for both raw materials (material type ROH) and finished goods spares (material type ERSA). How does material type configuration interact with purchasing group assignment and downstream account determination?

Purchasing group is an organizational attribute on the purchasing document/info record, independent of material type; it doesn't restrict which material types a buyer can procure. However, material type drives the valuation class options, account category reference, and whether the material requires quantity/value updating in inventory. So while the purchasing group can freely operate across ROH and ERSA materials, the account determination for GR postings differs based on each material type's valuation class, meaning the same purchasing group's POs post to different GL accounts depending on material type.
mediumAutomatic Account Determination

23. An employee raises a self-service shopping cart through an OCI-connected catalog for office supplies, and the account assignment defaults to a cost center that no longer exists after a recent org restructuring, causing the requisition to error out. Walk through where the account assignment default originates and how you would resolve the root cause.

Account assignment defaults typically derive from the requester's HR/org assignment (position, cost center in infotype 0001 or SRM/Ariba org replication), mapped through catalog OCI return parameters or default account assignment tables. The immediate fix is correcting or reassigning the requester's cost center master data and re-triggering org replication; the root cause fix is validating that org structure changes are synchronized with procurement master data before go-live of restructuring, plus adding validation checks to prevent invalid cost centers from populating new PRs.
mediumAutomatic Account Determination

24. A warehouse team posts a goods issue for internal consumption using movement type 201, and finance reports it hit an unexpected GL account different from the cost center's usual expense account. How would you investigate and resolve this using transaction key logic?

I would check OBYC for the relevant transaction key, typically GBB with account modifier VBR for consumption, and verify the valuation class assigned to the material combined with the modifier determines the GL account. Likely causes are an incorrect valuation class on the material master, a missing or wrong account modification in the movement type's account grouping, or a valuation area/company code combination not maintained. I'd trace via MIGO document, check MSEG valuation class, then confirm OBYC entries for GBB/VBR against that class.
mediumAutomatic Account Determination

25. During a physical inventory count, a material shows a stock overage that is posted via movement type 702. Which account determination logic is used for this posting, and what factors influence which GL account is ultimately hit?

Movement type 702 (inventory gain) posts via transaction key GBB with account modifier INV, using the material's valuation class to derive the GL account from OBYC. The account hit depends on the combination of chart of accounts, valuation grouping code, valuation class, and the GBB/INV modifier configured for that plant's valuation area. If the account isn't maintained for that valuation class and modifier combination, the posting fails with an account determination error requiring OBYC maintenance.
mediumAutomatic Account Determination

26. During configuration for materials using Moving Average Price, how does the automatic account determination in OBYC interact with valuation class to ensure correct GL posting when the stock account balance goes negative or insufficient to absorb a price difference?

OBYC maps valuation class to GL accounts via transaction keys like BSX (stock account) and PRD (price differences). Under V-price, if a goods receipt or invoice variance exceeds the available stock value (insufficient quantity or value), the system automatically posts the excess to the PRD price difference account instead of fully adjusting BSX, preventing negative or unrealistic stock valuation. Configuration must ensure PRD is assigned per valuation class/movement type combination to avoid postings failing.
mediumAutomatic Account Determination

27. 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?

Transaction keys such as BSX, WRX, GBB, and PRD each define which GL account is hit for stock, GR/IR, offsetting, and price variance postings respectively, based on valuation class, account modifier, and chart of accounts. If a new valuation class is introduced without a corresponding OBYC entry for a required transaction key, postings for movements using that valuation class will fail with an account determination error, blocking goods movements and delaying period-end closing until the mapping is corrected.
hardAutomatic Account Determination

28. A warehouse uses stock determination rules to prioritize consumption from quality inspection stock before unrestricted-use stock across materials assigned to different valuation classes. During period-end close, GBB consumption postings show inconsistent GL accounts because the stock determination strategy pulled from different valuation classes than the planner expected. As the architect, how would you diagnose and correct this?

Review the stock determination group and rule assigned to the material/plant combination in the stock determination configuration to confirm the intended withdrawal sequence and source stock categories. Cross-check the valuation class on the material master for each stock category involved, since GBB account determination is valuation-class-driven, not stock-category-driven. If quality stock and unrestricted stock share the same material but different batches with different valuation classes (via split valuation), the GBB postings will legitimately differ. Correct by aligning valuation class assignment or documenting the expected account variance for finance.
hardAutomatic Account Determination

29. From an architect's perspective, what authorization design principles should govern who can post directly to GR/IR clearing accounts versus who can only clear them through standard MM transactions like MIRO or MIGO, especially in a landscape integrated with PP order settlements?

GR/IR clearing accounts should be flagged as reconciliation-relevant or restricted via account group settings so direct FI postings (FB01/FB50) are blocked for standard users, forcing all activity through MM transactions that maintain the three-way match audit trail. Authorization objects like F_BKPF_BUK combined with account-level restrictions should limit manual clearing (F.13/F-44 style) to a controlled finance team, while PP order settlement postings should route through automatic account determination, not manual entry, preserving segregation of duties.
hardAutomatic Account Determination

30. Your organization runs continuous cycle counting using movement types 711/712 for count differences, but finance notices these adjustments are posting differently in the GL than the annual physical inventory differences posted via 701/702, creating inconsistent reporting between cycle count and periodic count results. As the architect across multiple plants, how would you diagnose and standardize this?

Check the OBYC configuration for transaction key GBB and confirm whether different general modifications (e.g., VAX/VAY-style groupings used for inventory differences) are assigned inconsistently to movement types 701/702 versus 711/712 across plants or valuation classes. Standardize by mapping both movement type sets to the same general modification and account per valuation class where the business intent is identical, then validate through test postings in a non-production client before rolling out globally.
hardAutomatic Account Determination

31. A plant-to-plant transfer posting using movement type 301 is creating unexpected inter-company clearing entries even though both plants belong to the same company code. How would you determine whether this is expected system behavior or a configuration defect?

First I would confirm whether the two plants are assigned to different valuation areas or different profit centers, since cross-plant transfers can trigger internal clearing postings for profit center or segment reporting even within one company code, independent of true inter-company accounting. I would review the movement type's account determination logic, check if document splitting by profit center is active, and validate whether this is intended internal stock transfer accounting rather than a genuine inter-company transaction.
hardAutomatic Account Determination

32. During warehouse goods receipt, postings are unexpectedly hitting a generic inventory clearing account instead of the material-specific stock account, causing reconciliation failures across multiple valuation classes. As the architect, how would you diagnose the root cause?

I would first verify the valuation class assigned on the material master accounting view actually maps to a valid account in OBYC for transaction key BSX per valuation grouping code. Common causes include a missing or newly created valuation class not yet mapped in account determination, an incorrect chart of accounts assignment for the plant's valuation area, or a movement type routing to an unexpected transaction key. I would trace the accounting document, confirm the valuation class in MBEW, then cross-check OBYC configuration for that combination before adjusting mappings.

Related lesson

Configuring Account Determination: Valuation Classes, Transaction Keys, and OBYC

Related topics

Invoice VerificationValuationService ProcurementSupplier and Business PartnerSource DeterminationS/4HANA MM Transformation, Ariba, Migration, Public Cloud and ArchitectureMaterial MasterPurchase OrderRelease StrategyFlexible WorkflowPhysical InventoryGoods Receipt and Goods Issue

Next practice step

Practice with Interview AITake a mock test