MM / P2Pintermediate

MM Account Determination Part 3: Transaction Keys, Modifiers and Movement Types

Key takeaway

Understand how movement types drive keys: value strings, transaction/event keys (BSX, WRX, GBB, PRD, UMB, KON, BSD... ), account modifiers for GBB (VBR, VAX, VAY, VNG, INV, BSA, AUF... ), PRD modifiers, and how custom movement types inherit account logic.

Explanation

📌 KEY POINTS
✅ Each movement type has a value string listing possible keys; account grouping (modifier) comes from movement type settings.
✅ GBB modifiers separate offsetting cases: VBR consumption, VAX/VAY sales-related, VNG scrapping, INV inventory differences, BSA initial entry, AUF order settlement.
✅ PRD covers price differences; KON consignment/pipeline payables; UMB revaluation.
✅ Custom movement types copied from standard inherit keys and modifiers — check them.
⚠️ Using a copied movement type with the wrong modifier sends postings to wrong accounts.

━━━━━━━━━━━━━━━━━━━━
▶ WHERE WE ARE
Part 2 configured blocks. Now keys and modifiers.

━━━━━━━━━━━━━━━━━━━━
▶ 1. VALUE STRINGS

Movement type → value string → posting keys.

━━━━━━━━━━━━━━━━━━━━
▶ 2. MAIN KEYS

BSX, WRX, GBB, PRD, KON, UMB, AUM (transfer differences).

━━━━━━━━━━━━━━━━━━━━
▶ 3. GBB MODIFIERS

VBR, VNG, INV, BSA, VAX/VAY, AUF.

━━━━━━━━━━━━━━━━━━━━
▶ 4. PRD MODIFIERS

Separate price differences by case where configured.

━━━━━━━━━━━━━━━━━━━━
▶ 5. CUSTOM MOVEMENT TYPES

Verify value string and account grouping.

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

Compare 201, 551 and 701 postings.
Identify GBB modifiers.
Check a Z movement type's account grouping.

✅ CHECKPOINT: you can predict keys and modifiers for common movement types.

Code example

ABAP Code

===== STEP 1: examples =====201 → GBB-VBR | 551 scrapping → GBB-VNG | 701 PI gain → GBB-INV | 561 initial entry → GBB-BSASales delivery 601 → GBB-VAX (without account assignment) / VAY ===== STEP 2: other keys =====KON consignment payable | PRD price difference | UMB revaluation | AUM transfer posting differences ===== STEP 3: where =====OMJJ movement type → account grouping | OBYC per key/modifier

Real project scenario

A goods movement using a custom Z movement type copied from 201 was meant for scrapping, but it kept the VBR modifier. Scrapping costs landed in normal consumption accounts. Changing the account grouping to VNG and testing fixed reporting.

Common mistakes

Ignoring modifiers.
Copying movement types blindly.
Missing PRD/KON entries.
No test per movement type.
Mixing scrapping and consumption.

Best practices

Map keys per movement type.
Review custom movement types.
Complete entries for all keys.
Test with finance.
Document modifiers.

Interview angle

Questions: "What is an account modifier?", "Which key for scrapping?", "How do movement types determine keys?"
Strong answer: value strings, keys, GBB modifiers, PRD, custom movement type checks.

Practice this lesson

Quick check

1. Within the GBB transaction/event key, which additional field is used to differentiate postings for different business scenarios such as goods issue to a cost center (VBR), scrapping (VNG), or goods receipt without a purchase order (BSA)?

2. A Z movement type copied from 201 is used for scrapping, but costs post to consumption. What is the likely fix?

3. During goods receipt for a purchase order with account assignment 'Goods Receipt/Invoice Receipt' (GR/IR), which transaction/event key in OBYC determines the clearing account used to bridge the timing difference between goods receipt and invoice receipt?

Interview questions

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

Answer it in your own words first, then compare.

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