🔗 The 7920 Chain — one field, click by click, to the money

You type one 4-digit number on one screen when creating a material. This page follows that number like a detective: where you click it, where it hides, which numbers it wakes up at posting time, and how the chain ends as a real accounting document. Real values throughout: FERT-REBAR-01 · 7920 · ₨7,000,000.

🖼️ The whole connection as ONE picture

One material, one label, two accounts — every box shows the number, the screen where it is defined, and its job. Follow the arrows. Colors: 🔵 where data lives · 🟢 what happens · 🟠 the address book · 🟣 the money book.

🟢 YOU — one click, once Screen: MM01 → Accounting 1 tab Field: “Valuation Class” the ONLY number a human types here 🟢 A MOVEMENT happens Screen: MIGO → movement 561 “Receive 20 TO — I need accounts!” could also be 101, 201, 351… you type it → saved movement picks keys 7920 🔵 the material’s LABEL lives in: MBEW (price card of FERT-REBAR-01 in plant PK01) BSX  ·  GBB·BSA 🔵 SAP’s fixed drawer-type keys BSX = “the stock drawer” · GBB·BSA = “the offset drawer” defined by SAP, same worldwide — nobody types these the label enters the keys enter 🟠 OBYC — THE ADDRESS BOOK Screen: t-code OBYC · for chart of accounts INT · filled by Finance ONCE BSX + 7920 → 792000 GBB·BSA + 7920 → 893010 key + label meet in a row → the row answers with an account number row 1 answers row 2 answers 792000 G/L: Inventory finished goods a balance-sheet drawer (“what we OWN”) defined in: FS00 — chart INT + comp. code PSPK 893010 G/L: Inventory change (offset) a P&L drawer (“where it came from”) defined in: FS00 — chart INT + comp. code PSPK Dr line Cr line 🟣 THE POSTING — one row each in ACDOCA (the General Ledger book) Dr 792000 ₨7,000,000   ·   Cr 893010 ₨7,000,000 see it: MIGO → display document → “FI Documents” button

Two side-notes the picture skips to stay clean: ① why F4 offered only 7900/7920 — material type FERT → OMSK → allowed labels; ② the amount ₨7,000,000 = 20 TO × the ₨350,000 standard price from the same MBEW card. Everything below walks this exact picture click by click.

1

The click — where 7920 enters the world

MM01 → tab Accounting 1 → section "General Valuation Data" → field Valuation Class. This is the ONLY place you ever type it:

Create Material FERT-REBAR-01 (Finished product)
MRP 4Plant dataAccounting 1Costing 1
General Valuation Data
Valuation Class7920 ← you type this (F4 helps)
ML Act.✓
Price Determ.2

Why does F4 offer only 7900 and 7920? Because of a small pre-chain: material type FERT → its account category reference (set in OMSK) → the list of allowed classes. So even the F4 list is itself a chain — SAP never shows you classes that would post finished goods like raw iron.

2

The hiding place — the label is glued to the material, per plant

On Save, 7920 is written into table MBEW (field BKLAS) — the material's price card for THIS plant. From now on the material "wears" the label 7920 in PK01. Extend to PK02 → PK02's own card gets its own label (usually the same 7920).

See it: SE16N → MBEW → FERT-REBAR-01 → column Valuation Class, one row per plant.

3

The trigger — a posting asks TWO questions at once

Months later, someone posts a movement — say our MIGO 561 (receive 20 TO). Before touching any account, SAP asks:

Q1 — What KIND of move is this?
The movement type answers with transaction keys — SAP's fixed internal drawer-type codes:
561 → BSX (stock drawer) + GBB·BSA (offset drawer, sub-kind "initial entry")
Q2 — What KIND of material?
Read the label from step 2:
MBEW → 7920
…and the price: 20 TO × ₨350,000 = ₨7,000,000

Plain words for the codes: BSX = "the stock account itself" · GBB = "the offsetting side" (its 3-letter sub-code says which flavor: BSA initial entry, VBR consumption…) · WRX = "the GR/IR clearing account". You never invent these — SAP fixed them decades ago, same in every company on earth.

4

The address book — OBYC marries the two answers

Now SAP opens OBYC (for chart INT) and finds the row where key + label meet. This is the ENTIRE magic — one lookup:

Key
Valuation class
→ G/L account
BSX
3000 (raw)
300000
BSX
7920 (finished)
792000 ✓
GBB · VBR
3000
400000
GBB · BSA
7920
893010 ✓

Read the green rows aloud: "Stock posting for a finished good → account 792000. Initial-entry offset for a finished good → account 893010." Finance fills this book once; after that, thousands of materials post themselves.

See it yourself: OBYC → double-click BSX → chart of accounts INT → the class→account rows.

5

The drawer check — do these accounts exist HERE?

The address book returned 792000 and 893010 — but an account is two parts: the name card in chart INT + the local card in company code PSPK (FS00). If the local card is missing, the chain stops with the error you met live: "G/L account 893010 does not exist in company code PSPK" → create it With Template → chain continues. This drawer opens once and stays open.

6

The destination — two lines in the Universal Journal

The chain ends as a real accounting document in ACDOCA (one table for FI and CO — FI vs CO):

Dr  792000  Inventory finished goods  ₨7,000,000
Cr  893010  Inventory change           ₨7,000,000

See it: display the material document in MIGO → FI Documents button — or SE16N → ACDOCA.

Who owns which number?
You (MM) pick the label 7920 per material — one field, once. · SAP owns the keys BSX/GBB/WRX — fixed, worldwide, never typed by anyone. · Finance owns the accounts 792000/893010 and fills the OBYC book once. · Nobody touches anything at posting time — that's the whole point: the chain runs alone, identically, millions of times.

♻️ Same chain, different moves — only step 3's answer changes

You postStep 3 picks keysStep 4 finds (label 7920 / 3000)Step 6 writes
561 initial stockBSX + GBB·BSA792000 + 893010Dr Inventory / Cr Inventory change
101 GR against PO (Scen. 1)BSX + WRX792000 + GR/IR clearingDr Inventory / Cr GR/IR (vendor's IOU, cleared by MIRO)
201/261 issue to cost center / order (Scen. 3)GBB·VBR + BSXconsumption account + stock accountDr Consumption (P&L) / Cr Inventory
351→101 STO plant-to-plant (Scen. 7)BSX ↔ BSX (both plants)792000 (PK01) ↔ 792000 (PK02)Inventory moves; a value line only if the two plants' prices differ

Notice: the label never changes — the material always wears 7920. Only the kind of move (step 3) changes, so the address book opens different rows.

🧠 The chain in one breath (interview version)
"The valuation class is typed once on the material's Accounting 1 view and stored in MBEW. At posting time, the movement type resolves to transaction keys like BSX and GBB, and OBYC maps key + valuation class to the G/L accounts, which must exist in the company code. The result is the FI document in ACDOCA. So MM decides the label, SAP fixes the keys, FI wires the accounts — and account determination runs untouched forever."

Zoom out: 🗺️ the full MM ↔ FI Map · follow the money all the way to payment: 💸 the P2P Money Trail · deeper money basics: Accounting 101 · every chain-break error: Troubleshooting Center