Scenario 6 — Asset Procurement (New CNC Machine)
100000 (AS01, class 1110) → PO with account assignment A (ME21N) → goods receipt that capitalized the machine onto the asset (MIGO) → invoice (MIRO) → payment (F-53, vendor cleared). Hit an error? Every message has its plain cause and fix in the Troubleshooting Center — see the 🏭 Asset Accounting group.
📊 Business Case — When & Why You Use This
Asset procurement is how you buy capital equipment — machinery, vehicles, IT hardware — that the company will use for years rather than consume at once. The PO carries account assignment A (Asset), so the goods receipt capitalizes the cost onto a fixed asset in the FI-AA module instead of expensing it. From there the asset depreciates over its useful life, spreading the cost across the years it earns revenue. This is the MM ↔ FI-AA integration point.
🕐 When to use it
Buying anything that meets the company's capitalization policy and lasts beyond one year — a CNC machine, a delivery truck, a server, a furnace rebuild — where the cost must sit on the balance sheet, not the P&L.
❓ Why it matters
It links the physical purchase to the fixed-asset register and depreciation engine in one chain. The asset's value, depreciation, and book value all trace back to this PO and GR — essential for audit and tax.
👤 Who triggers it
A capex request from Production/Engineering, approved by management; FI-AA sets up the asset master and account determination; MM raises the PO against the asset and receives it.
🔁 The key distinction
Capitalize, don't expense. Account assignment A sends the GR value to a fixed-asset G/L (Machinery & equipment, 11000), not to a consumption account — so the cost hits the P&L gradually as depreciation, never all at once.
💰 Financial Impact — The Easy-Money Example
PakSteel buys a CNC milling machine for ₨4,500,000, useful life 10 years (straight-line). Watch how the rupees behave very differently from a consumable: nothing hits the P&L at purchase — it lands on the balance sheet and then trickles into expense as depreciation:
The big idea: a capital purchase is not an immediate expense — at GR it is an asset swap (Machinery & equipment Dr / GR/IR Cr), exactly like inventory in Scenario 1 but on the fixed-asset side. The expense appears only as depreciation (AFAB) over the useful life, so each year carries only its fair share of the cost. MIRO afterward clears GR/IR against the vendor payable.
A is what turns a procurement into a capitalization. The GR value goes to a balance-sheet asset, and the P&L is touched only later, in slices, by AFAB depreciation. Get the asset class and depreciation key right and the whole 10-year expense profile follows automatically.
🇵🇰 The Business Story
🎯 What you'll learn — Asset accounting touches FI-AA
- Account Assignment
A(Asset) on PO line - Requires FI-AA setup (asset class, depreciation key) — usually done by FI consultant, MM uses what's there
- GR posts to AuC (Asset Under Construction) if asset not yet commissioned
- After install, transfer AuC → final asset via AIAB / AIBU
- Depreciation runs monthly via AFAB
This scenario needs FI-AA (Asset Accounting) module activated — typically FI consultant work, not MM:
- Asset Classes defined (e.g., 1110 Plant & machinery – others)
- Depreciation areas configured (01 Book, 15 Tax for Pakistan)
- Account determination for Asset Class (AO90)
- 🪂 Alternative: If FI-AA not set up, skip this scenario or substitute with Scenario 5 (Consumable Direct) — similar MM mechanics but goes to expense instead of asset
📋 Prerequisites (FI-AA)
- Asset Class exists (e.g.,
1110Plant & machinery – others) - Depreciation Areas configured (01 Book, 15 Tax for Pakistan)
- Account Determination for Asset Class (links to G/L 11000 Machinery & equipment)
- Above is FI consultant territory; just ask "is asset class 1110 ready?" before starting
The asset (e.g. CAP-CNC-01) is an asset master, not a material — this scenario creates it below with AS01. Reference: Create the asset.
- Org structure + MM-FI integration are built — Setup Guide.
- The posting-period and number-range gates are open (this scenario posts a goods receipt) — Stock-Readiness Checklist.
- Asset Accounting is ACTIVE for your company code. The tell-tale: if AS01 doesn't even show your company code, FI-AA was never switched on — do the activation chain in step 6.0 first (chart of depreciation → OAOB → OBCL → AS08 → class annex OAYZ → transfer date → technical clearing account → balance carryforward). Usually FI-consultant work; step 6.0 teaches you to do it yourself.
- A suitable asset class exists and is usable in your chart (e.g.
1110Plant & machinery – others) with its AO90 acquisition account wired (e.g.11000). - The asset master is created with AS01 (the card the PO points at) — Create the asset.
- The vendor (Business Partner) exists — BP Guide.
🔧 Step-by-Step
| Step | T-code | What it does | Why this step exists |
|---|---|---|---|
| 6.0 | EC08 → OAYZ (config) | Switches Asset Accounting ON for the company code | the asset register must exist before value can land on it |
| 6.1 | AS01 | Creates the machine's identity card in the asset register | the money needs an asset card to land on |
| 6.2 | ME21N | Creates the PO; account assignment A points money at the asset | a promise needs a document |
| 6.3 | MIGO (101) | Receives the machine and capitalizes ₨4.5M onto the asset | arrival is the moment the asset value becomes real |
| 6.4 | AIAB / AIBU | Optional: park cost on an AuC pot, settle later | no depreciation until the machine really works |
| 6.5 | MIRO | Records the vendor's bill; GR/IR clears, real debt appears | goods must match a bill before paying |
| 6.6 | F-53 | Pays the bill; vendor cleared, bank down ₨4.5M | a purchase isn't finished until the vendor is paid |
| 6.7 | AFAB | FYI: FI posts ₨37,500 depreciation expense every month | each year carries its fair share of the cost |
6.0 — Foundations: the Asset Class, and what to do when AS01 misbehaves (LIVE-CONFIRMED on a fresh company code)
⚡ This step will: switch Asset Accounting ON for a fresh company code — pure configuration, so that AS01 finally lists your company code and the asset class can be used. 📄 paper: — (customizing settings only) · 📦 stock: no change · 💰 money: no posting
What is an asset class? The asset class is to assets what the material type is to materials (Scenario 19's pattern, again!): one choice that brings the whole rule book — which G/L accounts the money posts to, which number range new assets draw from, which fields the master shows, and the default depreciation rule (how many years, which method). Standard classes exist for buildings, vehicles, machinery, IT — e.g. 1110 "Plant & machinery – others" fits a CNC machine.
Problem A — "I can't find a Machinery class in the F4 list." Check before creating anything:
- Search by name, not number — it may be called "Plant & machinery", "Technical equipment" or a 1100/2000-series number.
- OAOA shows every class in the system — if it exists there but not in AS01, it's only locked (unlock in OAOA / OAYZ), not missing.
- Nothing suitable at all? For learning, any equipment-like class works — the flow (AS01 → PO with
A→ GR capitalizes) is identical for every class; the class only changes the accounts and depreciation defaults.
Problem B — "AS01 doesn't even show MY company code." Asset Accounting was never switched on for that company code — AS01 only lists company codes that have a chart of depreciation assigned (a fresh company code has none). The activation chain, in true build order:
| # | T-code · Step | What it asks (plain words) | Why — and the impact if skipped |
|---|---|---|---|
| 1 | EC08 — copy a reference chart of depreciation (e.g. sample 0DE → your ZPKD) | Which RULE BOOK of depreciation areas will this country/company use? | A chart of depreciation = FI-AA's equivalent of a chart of accounts. You always copy a reference, never build blank. Impact: without one, FI-AA simply does not exist for you. |
| 2 | OAOB — assign the chart to the company code | Which company code uses that rule book? | The switch itself: this one row is what makes the company code appear in AS01. Impact: skipped = AS01 hides your company code entirely. |
| 3 | AS08 — asset number ranges | What numbers do new assets get? | Same idea as every number range on this site. Impact: AS01 saves fail without an interval. |
| 4 | AO90 — accounts per class (acquisition · accumulated depreciation · depreciation expense) | WHICH G/L pages does each asset class post to? | The key→account wiring (same OBYC idea). Impact: the GR computes but cannot post — "account not created in company code" errors. |
| 5 | Technical clearing account for integrated asset acquisition (SPRO → FI-AA → Integration) | S/4HANA-only: the in-between account a PO-based asset purchase passes through | New Asset Accounting posts the vendor side and asset side as two linked documents through this account. Impact: PO/GR throws an AA-error naming it. |
| 6 | OAYZ — per-class depreciation key + useful life defaults | How is each class's cost sliced over the years? | E.g. straight-line over 10 years → 450,000/year of a 4,500,000 machine becomes expense annually. Impact: you type key + life manually on every AS01 instead. |
🧗 The full gauntlet — every gate on a fresh company code, in the order you meet them (live-verified)
| When it appears | What SAP says (short) | Fix in one line + registry link |
|---|---|---|
| 1. AS01 hides the company code | Company code not listed (no chart of depreciation) | Assign a chart with OAOB after the EC08 copy. |
| 2. Saving the freshly copied chart | "Area 01: accounting principle is not assigned" / "Assign a target ledger group to area NN" | OADB → keep only area 01 → set accounting principle + target ledger group 0L. more |
| 3. OAOB assign / activation | "Input tax code for non-taxable transactions … missing" | OBCL → Input 0% (I0/V0) · Output A0. more |
| 4. AS01 picks the class | AA130 "Asset class NNNN cannot be used in company code XXXX" | OAYZ → un-tick "Area Deact." on area 01 + screen layout 1000. more |
| 5. AS01 tries to create | "Information about last completed fiscal year is incomplete" | FAA_CMP_LDT (last day of previous FY); else OAAQ. more |
| 6. AS08 number roll | No error — the interval is just empty | AS08 → add the asset number interval. |
| 7. PO save (ME21N) | "Technical clearing account is not maintained for chart of accounts XXXX" | Create a fresh recon-A doorway account + wire it in IMG. more |
| 8. Making the doorway in FS00 | The "Recon. account for acct type" field is not on the screen | OBD4 → account group → Reconciliation account: Suppress → Optional. more |
| 9. Doorway checks (FS00) | "must be reconciliation acct for type A" / "already used in T095" / "'Post auto. only' and recon cancel out" | Recon type A · pick an unused number · one lock only (recon OR post-auto). more |
| 10. PO save (ME21N) | ME045 "G/L account NNNNNN cannot be used (please correct)" | Copy the asset account's Field Status Group onto the blocked account. more |
| 11. AO90 Balance Sheet Accounts empty | Bal.Sh.Acct APC blank — GR/PO cannot find the balance-sheet home | AO90 → Bal.Sh.Acct APC = a machinery account (e.g. 11000); create it recon-A if prompted. more |
| 12. MIRO / asset posting | "Account … has been set as not relevant for tax" · FAA_POST124 "Balance carryforward is required … ledger 0L" | Tax: FS00 → tech-clearing account → Tax Category * + "posting without tax allowed" (more). Carryforward: FAGLGVTR → 0L · CC · current year — write the new year's opening line (more). |
Creating your OWN asset class (e.g. a dedicated ZMCH "CNC machines") uses parts 3–6 above plus: an account determination key (SPRO → FI-AA → Integration with G/L), a screen layout rule, then OAOA → New Entries glues them together. Same assembly pattern as the custom material type in Scenario 19.
Honest boundary: all of this is FI-AA (Asset Accounting) — on a real project it's the FI consultant's setup. An MM consultant should understand the chain (interview gold: "asset class : assets = material type : materials") and know whom to ask. Related errors: asset class / AO90 account determination · account not created in company code · target ledger group (OADB) · non-taxable tax code (OBCL) · AA130 class annex (OAYZ) · last fiscal year (FAA_CMP_LDT / OAAQ) · technical clearing account · recon field hidden (OBD4) · ME045 field status · FAA_POST124 balance carryforward (FAGLGVTR).
6.1 — Create Asset Master · AS01
⚡ This step will: create the machine's identity card in the asset register, so SAP knows where the money will land and how the value will fall over the years — nothing is bought yet. 📄 paper: — (asset master = master data, not a document) · 📦 stock: no change · 💰 money: no posting
Do: AS01 → fill the fields below → Save. An asset master = the identity card SAP keeps for one machine: what it is, whose books it sits on, and how its value will fall over the years.
| Field | Fill | What the field asks (plain words) | Why we choose this — and the impact if wrong |
|---|---|---|---|
| Asset Class | 1110 | What FAMILY of asset is this? Like drawers in a filing cabinet — one for machines, one for vehicles, one for buildings. | 1110 = Plant & machinery – others, the right drawer for a CNC machine. The class carries the G/L link (via AO90, FI's setup). Impact: pick the wrong drawer and the ₨4.5M posts to the wrong balance-sheet account. |
| Company Code | PSPK | WHOSE books does the machine sit on? | PSPK is the legal entity that owns it — PakSteel Pakistan. Impact: the wrong company code books the asset on the wrong entity's balance sheet. |
| Description | CNC Milling Machine - Karachi Line 1 | What plain-language name identifies this exact machine? | Write it so an auditor five years later knows which machine on which line. Impact: a vague name and nobody can tell your assets apart in the register. |
| Cost Center | PKKHI-PROD | Which department CARRIES the depreciation? | Production uses the machine, so Production's cost center takes the ₨37,500/month depreciation — not Finance, not Admin. Impact: the wrong cost center charges another team for a machine it does not use. |
| Plant | PK01 | WHERE does the machine physically stand? | PK01 = the Karachi factory where the machine is installed. Impact: the wrong plant records the asset's location incorrectly. |
| Useful Life (Time-dependent tab) | 10 years | Over HOW MANY years is the cost spread? | ₨4.5M ÷ 10 years sets the yearly expense; a shorter life means bigger slices, sooner. This number comes from company policy and tax rules. Impact: a wrong life over- or under-charges depreciation every single month. |
| Depreciation Key (Depreciation Areas tab, area 01) | LINK | In what PATTERN does the value fall — steady, or faster at the start? | LINK = straight-line: the same slice every month, like equal installments. Impact: choose a declining key and the machine loses value faster in early years — only correct if company policy says so. |
Save → Asset # assigned (e.g., 100000). SAP gives the number, like a new ID-card number. Note it down — the PO in 6.2 must point at exactly this asset.
6.2 — PO with Account Assignment A · ME21N
⚡ This step will: turn the purchase into a binding promise to the vendor, with account assignment A pointing the future ₨4.5M at asset 100000 — nothing arrives and nothing posts yet. 📄 paper: purchase order · 📦 stock: no change (and never — acct A bypasses stock) · 💰 money: no posting
The ME21N screen has 3 zones — know them and every field find itself: ① the Header (top: doc type, vendor, date — with header tabs like Org Data below it), ② the Item overview grid (middle: one ROW per thing you buy — most typing happens here), ③ the Item detail tabs (bottom: Material Data · Quantities · Delivery · Invoice · Conditions · Account Assignment · Texts — always for the line selected above).
| Where on screen · Field | Fill | What it asks (plain words) | Why we choose this — and the impact if wrong |
|---|---|---|---|
| Header · Document type | NB Standard PO | Which rule book governs this PO? | A machine purchase is a normal PO — no special type needed. Impact: none here; special types matter in Scenario 20. |
| Header · Vendor | your machinery vendor BP (or any working vendor) | WHO are we buying from? | Any vendor with finance + purchasing roles in PSPK/PKLO works — account assignment A asks nothing special of the vendor. Impact: a vendor without the purchasing role for PKLO fails at PO entry. |
| Header → Org Data tab · Purch Org / Group / Company Code | PKLO · your group · PSPK | Which buying desk, of which company? | Same org trio as every PO. Impact: the wrong company code would put the machine in the wrong legal entity's books. |
| Item grid · column A (AcctAssCat) — fill this FIRST | A (Asset) | Where does the money LAND — stock, expense, or an asset? | A = "this purchase becomes a Balance-Sheet asset". Filling it first unlocks the Asset field in the detail tabs. Impact: blank = SAP treats it as stock and demands a material with stock views. |
| Item grid · Material | leave EMPTY | Does this purchase need a material record? | A one-off machine is never stocked or reordered — no master; you describe it by text instead (like the service in Scenario 4). Impact: with Material blank, Short Text + Matl Group + unit become mandatory — that is why SAP "asks". |
| Item grid · Short Text | e.g. CNC Machine XYZ-500 | What is it, in words? | Replaces the material master's description. Impact: this text is what prints on the PO and shows in every report. |
| Item grid · PO Quantity + OUn (the unit column right after it) | 1 · EA | How many, in which unit? | One machine = 1 EA. Impact: more than 1 would capitalize several machines onto one asset card. |
| Item grid · Deliv. Date | a future date | When should it arrive? | Impact: a past date only warns — you know that one from the registry. |
| Item grid · Net Price | 4500000 PKR | Price of ONE unit — typed HERE in the grid, not in the detail section | ₨4,500,000 — the exact amount that capitalizes at GR and then depreciates for 10 years. Impact: a wrong price sets the wrong asset value and every future depreciation slice. |
| Item grid · Matl Group | F4 → any sensible group (e.g. machinery/general) | Which reporting category, since no material master provides one? | Mandatory when Material is blank. Impact: spend reports group the machine under whatever you pick. |
| Item grid · Plant | PK01 | WHERE is it delivered and installed? | The Karachi factory. Impact: the wrong plant records the machine at the wrong site. |
| Item detail → Account Assignment tab · Asset | your asset number from 6.1 (e.g. 100000; sub-number blank/0) | WHICH asset card exactly receives the money? | Type the NUMBER — don't hunt by name. The GR posts the ₨4.5M onto this card. Impact: a wrong number puts the right money on the wrong machine. |
| Item detail → Account Assignment tab · G/L Account | fills automatically after you enter the asset | On which balance-sheet page does the value land? (asks nothing of you) | The asset class (e.g. 1110) looks up its acquisition account via AO90 — the class doing its job. Impact: if it stays empty, the FI-AA account determination is missing — see the registry links in 6.0. |
Enter → all green → Save → note the PO number.
6.3 — GR — the machine arrives & capitalizes · MIGO · mvt 101
⚡ This step will: receive the machine and CAPITALIZE it — the full ₨4,500,000 lands on asset 100000 as a balance-sheet asset; no shelf fills, because acct A sends the value to the asset register, not to stock. 📄 paper: material + accounting document · 📦 stock: no change (value goes to the asset, not the warehouse) · 💰 money: Dr Machinery & equipment 11000 / Cr GR/IR
Do: MIGO → set the two top-left dropdowns → load the PO → tick Item OK → Post:
| Field / Action | Fill | What the field asks (plain words) | Why we choose this — and the impact if wrong |
|---|---|---|---|
| Top bar · Action dropdown (left) | Goods Receipt | What are you DOING — receiving, issuing, transferring? | The machine is arriving → Goods Receipt. Impact: the wrong action shows the wrong screen and movement types. |
| Top bar · Reference dropdown + PO number field | Purchase Order + your PO number → Enter | Against WHICH document is this happening? | The PO brings the item, price, the asset number and the G/L with it — you type almost nothing. Impact: no reference = a manual receipt with none of the PO's asset link. |
| Top bar · Movement Type box (top-right) | 101 (auto) | Which KIND of movement is this? | 101 = goods receipt for a PO, proposed automatically. Leave it. |
| Item detail → Quantity tab · Qty in Unit of Entry | 1 EA (proposed) | How many machines actually arrived? | One machine = 1 EA. Impact: a wrong quantity capitalizes the wrong value onto the asset. |
| Item detail → Where tab · Storage Location | field is ABSENT / greyed — correct! | Where should the stock be put? | It doesn't accept an entry because nothing goes to stock — account assignment A sends the value to the asset, not to a shelf (same as the NLAG line in Scenario 5). Impact: none here; if this field WERE active, you'd have missed the A on the PO. |
| Item detail → Account Assignment tab | shows Asset 100000 + G/L 11000, read-only | Where will the value land? | Decided on the PO in 6.2 — MIGO only executes it. Check it reads right before posting. Impact: a wrong asset number would capitalize the right money onto the wrong machine. |
| Item detail · ☑ Item OK checkbox (bottom) | ✅ tick | Do you confirm THIS line? | Impact: forget the tick and Post fails with "no items selected" — the #1 MIGO beginner error. |
| Toolbar · Check then Post | lights green → Post → note the material doc number | Any problems before it becomes real? | Check simulates first; Post writes the material + accounting documents and capitalizes the asset. |
What changes at this exact moment: the full ₨4,500,000 capitalizes onto asset 100000 — it becomes a balance-sheet asset and its depreciation base is set (depreciation starts from the capitalization date). No expense and no stock — just an asset swap:
| Machinery & equipment (11000) | Dr 4,500,000 | Asset: 100000 |
| GR/IR (191100) | Cr 4,500,000 | — |
In Scenario 1 the GR created inventory you can see in MMBE. Here the GR creates a fixed asset instead — account assignment A sends the value straight to the asset register (FI-AA), never to stock. So MMBE shows nothing for this machine — that's correct, not a bug. The machine now lives in the Asset Explorer, not the warehouse.
See the posting: ME23N → your PO → Purchase Order History → click the material document → its FI document shows the two lines above; or open AW01N → asset 100000 → the ₨4.5M acquisition value.
6.4 — Optional — AuC route (when asset takes months to install)
⚡ This step will: park the cost on a temporary "collecting pot" asset (AuC) during installation, then empty the pot onto the final asset at commissioning — so depreciation starts only when the machine really works. 📄 paper: GR + AIBU settlement documents · 📦 stock: no change · 💰 money: at GR Dr AuC / Cr GR/IR · at AIBU Dr final asset / Cr AuC
AuC = Asset under Construction — a temporary "collecting pot" asset. While the machine is still being installed it isn't working yet, so it shouldn't depreciate yet. Costs collect on the AuC first; depreciation starts only after hand-over to the final asset.
- Create AuC asset first (Class 4000 — the AuC drawer of the filing cabinet) → procure → GR hits the AuC pot
- Once commissioned: AIAB distribute AuC costs → AIBU settle to final asset — the pot is emptied onto the real asset card, which then starts depreciating
6.5 — Invoice Verification · MIRO
⚡ This step will: record the vendor's bill: the GR/IR IOU clears and a real debt to Pak Machine Tools appears — the asset's ₨4.5M value does not change here. 📄 paper: invoice document · 📦 stock: no change · 💰 money: Dr GR/IR / Cr Vendor
Do: MIRO → Transaction Invoice → type the vendor's total in the header Amount → PO Reference tab → your asset PO → Enter → Balance 0.00 · green → Post. It is the same three-way-match screen as Scenario 1, with one key difference explained below.
| Field / Action | Fill | What the field asks (plain words) | Why we choose this — and the impact if wrong |
|---|---|---|---|
| Header · Transaction dropdown (top-left) | Invoice | A normal bill, or a credit note? | Pak Machine Tools is billing you → Invoice. Impact: Credit Memo reverses the sign. |
| Header · Basic Data tab · Invoice Date | the date on the vendor's bill | When did the vendor write this bill? | Drives the payment due date. Impact: a wrong date shifts when payment falls due. |
| Header · Basic Data tab · Reference | the vendor's bill number | What number does the VENDOR call this bill? | The audit link between your books and theirs. Impact: matching disputes later become painful without it. |
| Header · Basic Data tab · Amount | 4,500,000 (the vendor's total) | What is the TOTAL on the vendor's paper bill? | You type this; SAP compares it with what the PO + GR promised. Impact: a different amount shows a red Balance ≠ 0. |
| Allocation area · PO Reference tab · Purchase Order | your asset PO → Enter | Which purchase is being billed? | Loads the ₨4,500,000 line from the GR into the item grid below. Impact: no reference = no three-way-match protection. |
| Header · top-right · Balance indicator | must be 0.00 · green | Does the bill match PO + GR? | Zero = PO ↔ GR ↔ invoice agree → Post. Impact: red = qty/price differs; check before forcing. |
What changes at this exact moment: the invoice clears the GR/IR that the goods receipt filled, and books the payable to the vendor. The asset value does NOT change here — it was already fixed at ₨4,500,000 by the GR in 6.3. MIRO only settles who you owe:
| GR/IR (191100) | Dr 4,500,000 | clears the GR credit |
| Vendor — Trade Payables | Cr 4,500,000 | now a real payable to Pak Machine Tools |
Then pay the vendor — full execution step in 6.6 below. Trace the whole chain any time in ME23N → Purchase Order History (GR + invoice lines).
6.6 — Pay the vendor · F-53
⚡ This step will: pay the debt: the vendor's account clears and the bank shrinks by ₨4,500,000 — the asset keeps its value and keeps depreciating. 📄 paper: payment document · 📦 stock: no change · 💰 money: Dr Vendor / Cr Bank
Do: F-53 → fill the header (dates + company code) → Bank data (which cash account + how much) → Open Item Selection (the vendor) → Process Open Items → double-click the invoice so Not assigned = 0.00 → Post.
| Where on screen · Field | Fill | What it asks (plain words) | Why — and the impact if wrong |
|---|---|---|---|
| Header · Document Date / Posting Date | today (proposed) | When is the payment made / in which period does it post? | Same-day defaults are right. Impact: a wrong posting date can land in a closed period. |
| Header · Company Code | PSPK | WHOSE books release the cash? | PSPK owes Pak Machine Tools and pays. Impact: the wrong company code pays from the wrong firm's bank. |
| Bank data · G/L Account + Amount | 113100 · 4,500,000 | From WHICH cash account, and HOW MUCH leaves? | 113100 = Bank Main Account, the same bank G/L as Scenario 1; ₨4,500,000 is the full payable from 6.5. Impact: a wrong account credits the wrong cash line; a wrong amount leaves a balance that will not post. |
| Open Item Selection · Account (vendor) | Pak Machine Tools Ltd | WHOSE unpaid bills are we clearing? | The machine supplier that carries the payable MIRO booked in 6.5. Impact: the wrong vendor shows no matching open item. |
| Button · Process Open Items | click | Show this vendor's open (unpaid) invoices. | Opens the open-items list so you can pick the exact invoice. Impact: skip it and there is nothing selected to pay. |
| Open-items screen · the invoice line | double-click it → Not assigned = 0.00 | WHICH bill exactly are you paying? | Activating the line makes Assigned = Amount Entered, so Not assigned falls to 0. Impact: if it is not 0 the payment is unbalanced and will not post. |
| Toolbar · Post | save → payment doc number | Commit the payment? | Post writes the FI document and clears the invoice. Impact: nothing is real until you Post. |
What changes at this exact moment: the ₨4,500,000 leaves the bank and Pak Machine Tools' account goes to zero; the invoice's open item flips to CLEARED:
| Vendor payable (via Pak Machine Tools) | Dr 4,500,000 | the payable is cleared |
| Bank (113100) | Cr 4,500,000 | cash leaves the bank |
The CNC machine is already capitalised and depreciating (6.3), and this payment does not touch its asset value — that was fixed at GR. F-53 settles only the ordinary vendor liability MIRO booked to Pak Machine Tools in 6.5: Vendor Dr / Bank Cr, exactly as in Scenario 1. Capitalisation decides where the cost sits on the balance sheet; it does not change how you pay the supplier.
Verify: FBL1N → Pak Machine Tools → the invoice now shows as cleared, no open items left. Full F-53 walkthrough with every field: Scenario 1.
6.7 — FYI: the asset's monthly life afterwards · AFAB (FI's job — no MM step, but know the story)
⚡ This step will: (run monthly by FI, not you) turn one slice of the machine into expense: ₨37,500 hits the cost center and the book value falls by the same amount. 📄 paper: depreciation posting document · 📦 stock: no change · 💰 money: Dr Depreciation expense / Cr Accumulated depreciation
MM's part of the story ends here — machine bought, capitalized, invoiced, paid. But the asset now lives for 10 years, and every month-end FI runs the depreciation posting run (AFAB) — on real systems a scheduled background job, like the MMPV month-roll and the balance carryforward (the month-end trio).
What it posts, every month for 10 years:
| Depreciation expense (P&L) | Dr 37,500 | charged to the cost center on the asset's Time-dependent tab — this is why AS01 asked for one! |
| Accumulated depreciation (Balance Sheet) | Cr 37,500 | the "minus pocket" next to the asset — book value falls month by month |
4,500,000 ÷ 10 years ÷ 12 months = ₨37,500/month — the machine "becoming expense" slice by slice, exactly what the depreciation key and useful life you set in AS01/OAYZ command. Watch it in AW01N (planned values per year).
Prerequisite before the first run (FI's wire, not yours): AO90's Depreciation folder — the accumulated-depreciation and expense accounts — must be filled for the account determination; on a fresh activation it is still empty. Boundary to state in interviews: an MM consultant knows this story cold, but AFAB and its accounts belong to the FI consultant — same division as KO88 settlement.
🚨 Common Errors
| "Asset class 1110 has not been created" | FI-AA setup needed — talk to FI consultant → more |
| "Account determination not possible (account assignment A)" | AO90 config missing — FI-AA → more |
| "Asset capitalization date not set" | AS02 → fill Capitalized On date |
✅ Verification — Confirm Scenario 6 Worked
- AW01N Asset Explorer → asset 100000 → values updated
- AS03 → asset master with values
- S_ALR_87011990 Asset balance sheet → P&M increased by 4.5M
- Run AFAB (depreciation run) for current period → depreciation expense posted
🎓 Interview-Ready Answers
Q: What does account assignment A do on a purchase order?
It tells SAP the purchase is a fixed asset, not stock or a consumable. The line is linked to an asset master (here 100000), and at goods receipt the value capitalizes to the asset's balance-sheet G/L (Machinery & equipment 11000) instead of inventory or expense. The cost then leaves the P&L untouched until depreciation runs.
Q: When does a capital purchase actually become an expense?
Not at GR — that's an asset swap (Machinery & equipment Dr / GR/IR Cr). The expense appears gradually as depreciation, posted monthly by AFAB over the asset's useful life (₨4.5M over 10 years = ₨37,500/month here), charged to the asset's cost center.
Q: What is an Asset Under Construction (AuC) and when do you use it?
An AuC (asset class 4000) collects costs for an asset that isn't ready to use yet — e.g. a machine being installed over several months. GRs post to the AuC; once commissioned you use AIAB to distribute the collected costs and AIBU to settle them to the final asset, which then begins depreciating.
Q: Where does the asset G/L (11000) come from at goods receipt?
From FI-AA account determination set up per asset class via AO90. The asset class (1110) points to the balance-sheet account for acquisitions (Machinery & equipment 11000). If AO90 is incomplete you get "account determination not possible for account assignment A" at GR.