P2P Scenarios — 24 Real-World SAP MM Scenarios

🎯 Why 26 scenarios (and not just one P2P walkthrough)?

Real businesses don't do one type of procurement. A typical Pakistani manufacturer like PakSteel will, in the same week, buy raw materials (stock), pay consultants (services), import machinery (asset + foreign currency), reject defective bearings (return), transfer stock between Karachi and Lahore plants (STO), and send fabric to a subcontractor for stitching. Each is a different MM scenario with different config.

This page walks you through 24 scenarios that cover 95% of what an MM functional consultant actually configures on real projects. You'll learn them in progression — basic foundations first, then complexity layers on top.

🧭 How to use this page

Start at Scenario 1 — it teaches the core P2P pattern (PR → PO → GR → IV → Payment). Every other scenario is a variation of this.
Do Tier 1 first (Scenarios 1-3) — basic flows you can run with just the CC + plant we set up
Then Tier 2-3 (Scenarios 4-8) — adds CO settings, multi-plant flows
Then Tiers 4-7 — special procurement (subcon/consign), process controls (release/source), master data features (batch/QM), customization
Tier 8 is Pakistani-specific — import procurement, withholding tax (skip if you'll work in other geographies)
Each scenario tells you exactly what config it needs. Don't pre-configure everything — configure as you learn each scenario.

🔗 MM doesn't live alone — Cross-Module Integration

As an MM consultant, your job is to understand how MM connects to OTHER SAP modules. Every MM transaction touches at least FI; many touch SD, CO, PP, QM, PM, or PS. Each scenario below is tagged with the modules it integrates — so when discussing with clients, you can immediately say which areas to involve.

🏷️ Module tags used throughout scenarios

Tag	Module	What it means for MM
MM	Materials Management	Always present — the core module
FI	Financial Accounting	G/L postings, AP, AR — every MM doc creates FI doc
CO	Controlling	Cost center / order / project assignments on PO lines
SD	Sales & Distribution	Outbound deliveries, billing — needed for STO cross-CC, third-party
PP	Production Planning	BOMs, production orders, work centers, MRP-driven PRs
QM	Quality Management	GR to inspection stock, usage decisions, quality certs
PM	Plant Maintenance	Maintenance order spare part procurement, refurbishment
PS	Project System	WBS-assigned POs (account assignment P)
AM	Asset Management (FI-AA)	Asset procurement (account assignment A)
WM	Warehouse Management	Storage bin, putaway, picking (advanced)

📚 How prerequisite setup works in this guide

Most scenarios only need MM + FI setup (covered in Setup Guide Steps 1-15). Some scenarios need additional setup in other modules:

Scenario 8 (Inter-Co STO) needs SD setup → Setup Guide Step 16 (Reference)
Scenario 9 (Subcontracting) needs BOM (PP master data) → Setup Guide Step 17B (Reference)
Scenario 12 (Third-Party) needs SD knowledge (item cat TAS) → Step 16 (Reference)
Scenario 18 (QM Integration) needs QM module activated → covered in scenario itself
Scenarios 25-26 (NEW — MM+PM, MM+PS) need PM/PS module references → covered in scenario itself

Setup just-in-time: Don't pre-configure SD/PP/QM/etc. at the start. Wait until you reach a scenario that needs it, then go to the relevant Setup Guide step (16 or 17), do that piece, come back to the scenario. This way you learn modules ONLY when MM actually touches them — efficient and contextual.

📋 The 26 scenarios at a glance

Click any row to jump to the scenario. Estimated time = full hands-on in IDES from config to verification.

🔗 Modules legend — colored tags show every module touched in each scenario. Helps you know what to activate/setup:

MM Materials Management FI Financial Accounting CO Controlling SD Sales & Distribution PP Production Planning QM Quality Management PM Plant Maintenance PS Project System AM Asset Management WM Warehouse Management

#	Tier	Scenario	Difficulty	Modules Needed	Time	Key T-codes
1	T1 Foundation	Stock Procurement (basic P2P)	★☆☆☆☆	MM FI	2h	ME51N, ME21N, MIGO, MIRO, F-53
2	T1 Foundation	Return to Vendor (quality reject)	★☆☆☆☆	MM FI	1h	MIGO (122/161), MIRO
3	T1 Foundation	Goods Issue & Stock Transfers	★☆☆☆☆	MM FI CO	1h	MIGO (201/261/311)
4	T2 Account-Assigned	Service Procurement (consultants)	★★☆☆☆	MM FI CO	2h	AC03, ME21N (item D), ML81N, MIRO
5	T2 Account-Assigned	Consumable Direct Purchase (NLAG)	★★☆☆☆	MM FI CO	1.5h	MM01 (NLAG), ME21N (acct K)
6	T2 Account-Assigned	Asset Procurement (machinery)	★★★☆☆	MM FI AM CO	2h	AS01, ME21N (acct A), MIGO, AIAB
7	T3 Multi-Plant	Intra-Company STO (PK01 → PK02)	★★☆☆☆	MM FI	1.5h	ME21N (UB), MIGO (351/101)
8	T3 Multi-Plant	Inter-Company STO (PSPK → PSAE)	★★★★☆	MM SD FI	3h	ME21N (NB w/ vendor), VL10B, VF01, MIGO, MIRO
9	T4 Special	Subcontracting (BOM + components)	★★★★☆	MM PP FI	2.5h	CS01, ME21N (item L), MIGO (541/543/101)
10	T4 Special	Consignment Procurement	★★★★☆	MM FI	2h	ME11 (cons), MIGO (101-K/411-K), MRKO
11	T4 Special	Pipeline Material (gas/electricity)	★★★☆☆	MM FI CO	1h	MM01 (pipeline), MB1A (201-P), MRKO
12	T4 Special	Third-Party Drop-Ship	★★★★☆	MM SD FI	2.5h	VA01 (SO item S), ME21N (TAS), MIRO
13	T5 Controls	Release Strategy (PO approval)	★★★★☆	MM	3h	CT04, CL02, OMGS, OMGSCK
14	T5 Controls	Source Management Mastery (9 sub-scenarios) — Source List, Fixed/MRP flags, Quota, Block, Time-Dependent, MRP-PR, Contract refs	★★★★☆	MM	3-4h	ME01, ME0M, MEQ1, MEQ3, OMQM, MD03
15	T5 Controls	Outline Agreements (Contracts + Scheduling)	★★★☆☆	MM FI	2h	ME31K, ME31L, ME38
16	T6 Master Data	Batch Management (steel grades)	★★★★☆	MM WM	2.5h	OMCD, MSC1N, MIGO (w/ batch)
17	T6 Master Data	Split Valuation (origin/grade)	★★★★☆	MM FI	2h	OMWC, MM01 (val type), MIGO
18	T6 Master Data	QM Integration in P2P	★★★★☆	MM QM FI	2h	QA32, QA11, MIGO (w/ QM)
19	T7 Customization	Custom Material Type	★★★★★	MM	2h	OMS2, OMSK, MM01
20	T7 Customization	Custom Document Type (PO / PR)	★★★★★	MM	2h	OMEC, OMEB, SNRO
21	T7 Customization	Pricing Procedure (custom conditions)	★★★★★	MM	3h	M/06, M/08, OMFO
22	T7 Customization	Output Determination (printable PO)	★★★☆☆	MM	2h	NACE, MN04, condition records
23	T8 Pakistani	Import Procurement (foreign vendor + LC + customs)	★★★★★	MM FI	3h	ME21N (NB import), MIRO (planned costs)
24	T8 Pakistani	Withholding Tax on vendor payments (FBR)	★★★★☆	MM FI	1.5h	FBKP, FK02 (WHT), F-53
25	T9 Cross-Module	MM ↔ PM Plant Maintenance Spare Parts	★★★★☆	MM PM FI CO	2.5h	IW31, ME51N (from PM order), ME21N, MIGO
26	T9 Cross-Module	MM ↔ PS Project System WBS Procurement	★★★★☆	MM PS FI CO	3h	CJ20N, ME51N (WBS acct P), ME21N, MIGO

📊 Coverage analysis — what 26 scenarios give you

Tier 1 (Sc 1-3): The base 80% pattern every PO uses · MM FI CO
Tier 2 (Sc 4-6): Account-assigned procurement → ~30% of real POs (services, consumables, capex) · adds AM
Tier 3 (Sc 7-8): Multi-location → essential for multi-plant company · adds SD
Tier 4 (Sc 9-12): Special procurement → 10-15% of POs · adds PP
Tier 5 (Sc 13-15): Process controls → release + source list + agreements · pure MM
Tier 6 (Sc 16-18): Master data depth → pharma/food/steel/textile · adds QM WM
Tier 7 (Sc 19-22): Customization → what makes you a CONSULTANT vs end-user · pure MM config
Tier 8 (Sc 23-24): Pakistani fiscal compliance → LC + customs + FBR WHT
Tier 9 (Sc 25-26): Cross-module integration → MM ↔ PM, MM ↔ PS · adds PM PS

🎯 Module activation cheat sheet — when to ask Basis to activate

Use this when joining a real project — tells you which modules MUST be active for each scenario family:

Module	Always Active?	Needed For Scenarios	Pakistani Industries
MM Materials Management	✅ ALWAYS (core)	ALL (1-26)	All
FI Financial Accounting	✅ ALWAYS (core)	1, 2, 4-12, 15, 17, 18, 23, 24, 25, 26	All
CO Controlling	✅ Usually active	3, 4, 5, 6, 11, 25, 26	All (cost centers/orders)
SD Sales & Distribution	⚠️ Depends	8 (Inter-CC STO), 12 (Drop-Ship)	Manufacturing, Trading, Distribution
PP Production Planning	⚠️ Depends	9 (Subcontracting)	Steel, Textile, FMCG, Pharma manufacturing
QM Quality Management	⚠️ Optional	18 (QM in P2P)	Pharma, Food, Steel (ISO clients)
PM Plant Maintenance	⚠️ Depends	25 (Spare parts)	Manufacturing, Utilities, Cement, Power
PS Project System	⚠️ Depends	26 (WBS procurement)	Construction, EPC, IT projects, Engineering
AM Asset Management (FI-AA)	⚠️ Usually active	6 (Asset Procurement)	All capex-heavy industries
WM Warehouse Management	⚠️ Optional	16 (Batch in WM bins)	Pharma, FMCG distributors, 3PL

💡 How to read this in real consulting: When client says "we need MM only" — check if scenarios 8, 9, 18, 25, 26 are needed. If yes, you also need SD/PP/QM/PM/PS active. Many "MM-only" projects discover they need SD or PP halfway through. This table prevents that surprise.

✅ Prerequisites — config you need before scenario 1

If you completed the Setup Guide Steps 1-15, you're ready for Scenarios 1-3. For Scenarios 4+, you'll add config as you go (each scenario tells you what's needed).

Required for...	Config needed	Setup Guide step	Status check (SE16N)
Any scenario	Company Code PSPK fully configured (OBY6, OB52, FBN1, OBA4)	Step 1 (1A-1H)	T001 row populated
Any scenario	Plant PK01 + assignment to PSPK	Steps 3 + 4	T001W row, BUKRS = PSPK
Any scenario	Valuation Area = Plant (OX14)	Step 5	T001K row per plant
Any scenario	Storage Locations (GNRL at minimum)	Step 7	T001L rows
Any scenario	Purchasing Org PKLO + assignment to PSPK + plant	Steps 8-10	T024E row, T024W row
Any scenario	Purchasing Group RMT (or similar)	Step 13	T024 row
Any scenario	OBYC G/L account assignments for valuation class	Step 15	T030 row for GBB/BSX/WRX
Sc 4+ (account-assigned)	CO Area + Cost Centers + OBY6 linking CC to CO Area	See "CO Setup" below	TKA01, CSKS rows
Sc 6 (asset)	Asset Accounting (FI-AA) config — asset classes, depreciation areas	Outside MM scope (CO/FI consultant)	ANKA rows
Sc 13 (release)	Characteristics + Class + Release Strategy	Scenario 13 itself	—
Sc 16 (batch)	Batch level set system-wide (OMCD)	Scenario 16 itself	T133 row

💡 Smoke test before starting: Run ME21N and try to create a PO header. Vendor field, plant, purch org, purch group — if all dropdowns populate, you're ready for Scenario 1.

📦 Master Data Baseline — what we'll create & reuse

Instead of creating new materials/vendors for each scenario, we build a reusable baseline in Scenario 1 that subsequent scenarios extend. This mirrors real projects where you cut over master data once and POs reuse it.

Materials (9 cover 90% of MM scenarios)

Code	Type	Description	Pak Context	Used in Sc#
`RM-IRON-01`	ROH (raw material)	Iron ore lump, Grade A	From Mughal Steel	1, 9, 16, 17
`RM-COAL-01`	ROH	Coking coal	From Indonesian supplier	1, 23
`SP-BEARING-01`	ERSA (spare part)	Bearing 6205-ZZ	For maintenance use	2, 5
`HALB-BILLET-01`	HALB (semi-finished)	Steel billet 100mm	WIP inventory	3, 9
`FERT-REBAR-01`	FERT (finished good)	TMT Rebar 12mm	For sale	3, 7, 8
`HAWA-CEMENT-01`	HAWA (trading good)	Cement bags 50kg	Resale only	10 (consignment)
`OFFC-PAPER-01`	NLAG (non-stock)	Office paper A4	Direct to office	5
`UTIL-GAS-01`	UNBW (non-valuated)	Natural gas (SSGC)	Continuous flow	11 (pipeline)
`SVC-CONSULT-01`	DIEN (service)	Consulting hours	Audit / SAP support	4

Vendors (Pakistani context — Business Partners)

Code	Name	Type	NTN / Tax	Used in Sc#
`VEN-MUGHAL`	Mughal Steel Industries Ltd	Local PK	NTN: 0742510-3	1, 2, 16
`VEN-AISHA`	Aisha Steel Mills	Local PK	NTN: 1145-7782	1, 14
`VEN-LCK-CON`	Lucky Consulting (Pvt) Ltd	Local PK (services)	NTN: 2233-4455	4
`VEN-PCABLE`	Pakistan Cables Ltd	Local PK	NTN: 0123-9876	9 (subcontractor)
`VEN-SSGC`	Sui Southern Gas Co.	Local PK (utility)	NTN: 0001-1111	11 (pipeline)
`VEN-IMPCH`	Shanghai Steel Trade Co.	Foreign (CNY)	—	23 (import)
`VEN-CONSIG`	DG Cement (consignment)	Local PK	NTN: 4567-8901	10 (consignment)
`VEN-3RD`	Karachi Drop-Ship Logistics	Local PK	NTN: 7890-1234	12 (third-party)

⏱️ Time-saver: Create all 9 materials + 8 vendors UP-FRONT in one session (~2 hours). Then every scenario just runs transactions on existing data. Without this baseline, you'll waste time creating master data per scenario.

⚙️ Controlling (CO) — needed from Scenario 4 onwards

Scenarios 1-3 don't need CO. From Scenario 4 (service, consumable, asset) the PO posts to a cost object (cost center / internal order / asset / WBS) — which requires a Controlling Area + cost centers set up first.

🏗️ CO configuration now lives in the Setup Guide — it's one-time foundation work, not a P2P scenario. Full click-by-click steps, real field values, and the live gotchas (the "configured CO after postings" trap → FINS_ACDOC_CUST116 + the mass-data project) are documented in Setup Guide → Step 19: Controlling Area & Cost Centers ⭐. Do that step ONCE, then come back here for Scenarios 4+.

🎯 Why an MM consultant must know CO basics (even if FI/CO configures it)

You won't usually configure the controlling area — but you touch it daily: every service PO, consumption posting, and asset purchase routes a cost object through your MM transactions. You must know what to type (the cost center / order on the PO line) and why. The iron rule you'll learn in Step 19: the controlling area must exist BEFORE any postings — configure it after, and S/4HANA forces a journal-entry mass-update project to repair consistency.

💡 Account Assignment Categories in MM (memorize these)

Every PO line either goes to stock (blank) or to a cost object. Account Assignment Category in ME21N controls where:

AAC	Cost Object	Used When	Scenario
blank	Stock (Inventory G/L)	Material has stock view, going to warehouse	1, 2, 7, 8, 9
`K`	Cost Center	Direct consumption — office supplies, MRO	4, 5, 11
`F`	Internal Order	Repair jobs, marketing campaigns — temp cost bucket	(optional)
`A`	Asset	Machinery, IT equipment, furniture	6
`P`	Project (WBS)	Capex projects, construction	(advanced)
`U`	Unknown / Multiple	Decide later (rare)	—
`C`	Sales Order	Third-party drop-ship (TAS item)	12
`X`	All auxiliary	Internal use general	—

🟢 Tier 1: Foundation — start here

The three scenarios every MM consultant must master. Scenario 1 is the master P2P pattern — every other scenario is a variation. Build a strong base here.

Stock Procurement — The Basic P2P Cycle

FOUNDATION ★☆☆☆☆ ⏱️ ~2 hours ME51N → ME21N → MIGO → MIRO → F-53

🇵🇰 Business Story

PakSteel Karachi Factory (PK01) needs to procure 50 tons of iron ore lump (Grade A) from local supplier Mughal Steel Industries. The material goes to the raw material warehouse (storage location RAWM). Standard 30-day payment terms. Total order value: ~PKR 12,500,000 (₨2.5 lac/ton × 50 tons).

🎯 What you'll learn in this scenario

This is the master pattern all other scenarios extend. You'll see exactly:

How the 5-step P2P cycle moves through SAP tables (EBAN → EKKO/EKPO → MSEG → BKPF/BSEG)
Why valuation class + OBYC drive every accounting entry
When/where automatic G/L determination kicks in (no manual posting needed)
How GR/IR clearing works (the famous "GR/IR" account)
How to verify each step actually worked at the database level

📋 Prerequisites

Item	Status check
CC PSPK fully configured (Setup Guide Step 1)	SE16N → T001 → BUKRS=PSPK row populated
Plant PK01 + assignment to PSPK	T001W → PK01 with BUKRS=PSPK
Storage Location RAWM at PK01	T001L → WERKS=PK01, LGORT=RAWM
Purchasing Org PKLO + PSPK + PK01 assignments	T024E, T024W rows
Purchasing Group RMT	T024 → EKGRP=RMT
OBYC entries for valuation class 3000 (raw materials)	T030 → BSX, WRX, GBB rows for VKO=0001, BKLAS=3000

⚙️ New config needed for this scenario

None beyond Setup Guide Steps 1-15. This is pure transactional — no new IMG config. If your CC + Plant + Org Units work, this scenario runs.

📦 Master Data Setup

1.1. Create Material — MM01 · Iron Ore Lump (RM-IRON-01)

What: Material master = the central record SAP uses across all modules. ~50 fields organized into "views" — only fill the views relevant to MM + FI.

Action:

Run MM01
Material: RM-IRON-01 · Industry Sector: M (Mechanical Engineering) · Material Type: ROH (Raw Material)
Select views (Ctrl+click multiple):
- Basic Data 1 + 2
- Purchasing
- Purchase Order Text (optional)
- General Plant Data / Storage 1
- Accounting 1
- Costing 1 (optional)
Organizational levels: Plant = PK01 · Storage Location = RAWM · Purch Org = PKLO
Fill the fields below per view → Save

Required fields per view:

View	Field	Value	Why
Basic Data 1	Description	Iron Ore Lump Grade A 50-100mm	What it is
	Base Unit	`TO` (Ton)	UOM for stock + valuation
	Material Group	`001` (Raw materials)	Reporting grouping
Purchasing	Purchasing Group	`RMT`	Buyer responsible
	Order Unit	`TO`	How vendor sells (can differ from base UOM)
	GR Processing Time	`2` days	Inspection lead time
Plant Data / Storage	Plant	`PK01`	Where stock kept
	Storage Conditions	`02`	Outdoor OK
	Temperature Conditions	blank	N/A for ore
Accounting 1	Valuation Class	`3000` (Raw materials)	Critical — drives OBYC G/L determination
	Price Control	`V` (Moving Average) or `S` (Standard)	V = price varies per GR; S = fixed price + variance
	Moving Price	`250000` (if V chosen)	Initial PKR 2.5 lac/ton
	Standard Price	`250000` (if S chosen)	Fixed price
	Price Unit	`1`	Per 1 TO

Verify: SE16N → MARA (general) + MARC (plant) + MBEW (valuation) + MARD (storage) — all 4 tables should have a row for RM-IRON-01.

1.2. Create Vendor (Business Partner) — BP · Mughal Steel Industries

S/4HANA note: Vendors are no longer created via XK01/MK01 alone — they're created via BP (Business Partner) which writes to LFA1/LFB1/LFM1 + BUT000 in the background.

Action:

Run BP
Create → Organization → BP Role: FLVN00 (Supplier in FI) — gives the General + FI views
Header:
- BP Category: Organization
- Grouping: BPG1 (default external numbering) — or system assigns
- Name: Mughal Steel Industries Ltd
- Search Term: MUGHAL
Address tab: Street, Karachi, Postal Code 74900, Country PK, Region SD, Phone +92-21-XXX
Identification tab: Tax Number Cat: PK0 (NTN), Number: 0742510-3
Save header → BP # auto-assigned (ours: 21) — and when the popup asks for the external supplier number, type your alphanumeric vendor code (ours: MUGHAL21)
💡 If popup asks for "External Supplier Number": Your IDES vendor account group may use external alphabetic numbering (range A→ZZZZZZZZZZ). Numeric values like 21 get rejected. Use vendor name pattern: MUGHAL21, AISHA22, ANGLO23, GLENCO24, etc. This is actually better practice — meaningful vendor codes are readable in reports (ME2L/ME2N) and used by many real Pakistani companies (Engro, Lucky, ICI). To get pure numeric same-as-BP behavior, see Setup Guide Step 18 (XKN1 + OBAS + V_TBD001 Same Number flag).
Switch role to FLVN01 (Supplier — extended with FI Co.Code) → enter Company Code PSPK
Recon Account: 160000 (Trade Payables Domestic) · Payment Terms: 0003 (14d 2% / 30d net — standard SAP) · Save
💡 Payment Terms options in your IDES (standard SAP, pre-shipped): 0001 Immediate · 0002 14d 3%/30d 2%/45d net · 0003 14d 2%/30d net ⭐ · 0005 10d 2%/30d net · 0009 Net 30 days · 0008 End of month/14 days. For custom Pakistani terms (PK30, LC30, ADV100) → create via OBB8 — see Setup Guide Step 18F.
Switch role to FLVN02 (Supplier — Purchasing Org) → enter Purch Org PKLO
Order Currency: PKR · Terms of Payment: 0003 · Save

Verify: SE16N → LFA1 (general) + LFB1 (CC=PSPK) + LFM1 (EKORG=PKLO) — all 3 tables should have rows for vendor MUGHAL21.

1.3. Create Info Record — ME11 · Link Material ↔ Vendor with price

What: Info Record = the agreement saying "Vendor X sells Material Y to Plant Z at price P." When you create a PR/PO, SAP auto-suggests the price from here. Optional but standard.

Action:

Run ME11
Vendor: MUGHAL21 · Material: RM-IRON-01 · Purch Org: PKLO · Plant: PK01 · Info Cat: Standard
Enter → General Data tab: Sort Term, Reminders, etc. (skip)
Purch Org Data 1: Net Price = 250000 · Currency = PKR · Validity From-To (e.g., today to 31.12.9999)
Save → Info Record # assigned (e.g., 5300000123)

Verify: SE16N → EINA (general info) + EINE (purch org details) — both populated.

🔄 Transaction Flow — The 5 Steps

Step 1. Purchase Requisition — ME51N

What: PR = internal request "I need this material." Originates from MRP, production, maintenance, or manual entry. Free of charge — no commitment to vendor yet.

Action:

Run ME51N
Doc Type: NB (Standard PR) · Header text optional
Line 1:
- Material: RM-IRON-01
- Quantity: 50 · UOM: TO
- Delivery Date: today + 14 days
- Plant: PK01 · Storage Location: RAWM
- Purchasing Group: RMT (auto from material)
Item Detail → Source of Supply tab: vendor MUGHAL21, Info Record auto-suggests price (250000/TO)
Save → PR # assigned (e.g., 10000123)

Tables updated: EBAN (PR header + item) + EBKN (account assignment, if used).

Step 2. Purchase Order — ME21N · 2 Flows (with PR vs without PR)

What: PO = legal commitment to vendor. Sent to vendor as printed/emailed document. Two ways to create it:

🎯 KEY POINT — If you already have a PR with Plant + Purch Org + Vendor + Material filled, DON'T re-enter them in PO! Use "Adopt PR" flow → all PR fields auto-copy to PO. You only verify + add PO-specific fields (Tax Code, exact Delivery Date).

✅ Flow A — Convert PR to PO (RECOMMENDED — auto-fills everything)

Use when: You completed Step 1 (PR created). All fields like Material, Plant, Purch Org, Vendor, Quantity, Net Price will auto-copy from PR. You DON'T re-enter them.

Run ME21N
Don't enter ANY fields yet — just click "Document Overview On" button (top-left, looks like 🗂️)
💡 Document Overview panel opens on the LEFT side of screen
In the Document Overview dropdown (left panel) → select "Purchase Requisitions"
Selection screen popup:
- Purchasing Group: RMT (or your PR's group)
- OR enter PR # directly: 10000123
- Click Execute (F8)
Your PR appears in left panel with all line items
Drag the PR line item (or use "Adopt" button) → drop on right side (PO area)
💡 Alternatives if drag-drop fails: (1) Expand PR with ▶ → right-click the ITEM line (not the PR header!) → "Adopt". (2) ⭐ MOST RELIABLE (this is what worked in our IDES): skip Document Overview entirely — in the PO item table, scroll RIGHT to the "Purchase Requisition" column → type the PR number there → Enter → all fields auto-copy. If the column is hidden: right-click any column header → Configure → show it.

✨ SAP auto-copies from PR to PO:

Field	Auto-copied from PR?	Source
Material	✅ YES	PR item
Plant	✅ YES	PR item
Storage Location	✅ YES	PR item
Quantity	✅ YES	PR item
Unit of Measure	✅ YES	PR item
Vendor	✅ YES (if Fixed Vendor in PR)	PR Source of Supply
Purch Org	✅ YES (if entered in PR Source of Supply)	PR Source of Supply
Purch Group	✅ YES	PR item
Net Price	✅ YES (from Info Record)	ME11 Info Record
Material Group	✅ YES	Material Master
Account Assignment Cat	✅ YES (if entered in PR)	PR item
Delivery Date	✅ YES (or recalculated)	PR + delivery time
Currency	✅ YES	Vendor LFM1
Doc Type	Defaults to `NB`	Personal Settings

You only need to VERIFY + add PO-specific fields:
- Tax Code: I0 (Input tax 0% — ⚠️ verified in our IDES; V0 did NOT exist! Press F4 to see YOUR system's codes. "I" prefix = Input tax for purchases, "O/A" = Output tax for sales) — usually blank in PR
- Header → Org Data tab: confirm Company Code PSPK (auto from Purch Org)
- Header → Delivery/Invoice tab: Payment Terms (auto from vendor), Incoterms (auto from vendor)
- Item → Confirmations tab: tick "Acknowledgment Reqd" if you want vendor to confirm acceptance
Click Check (yellow tick icon) → review messages → no errors → Save (Ctrl+S)
PO # assigned (e.g., 4500000123)
PR status now shows "PO created" — closed against this PO

✅ Result of Flow A: No duplicate data entry. PR-PO link maintained (EKPV table). Reporting via ME5A shows PR-to-PO conversion rate. Audit trail intact.

⚠️ Flow B — Create PO Direct (NO PR) — use only when no PR exists

Use when: Skip PR step (sometimes done for urgent buys, low-value purchases, or recurring buys with established vendor). All fields must be entered manually.

Run ME21N
Doc Type: NB (Standard PO)
Vendor: MUGHAL21 (Mughal Steel)
Header → Org Data tab (enter manually since no PR to inherit):
- Purch Org: PKLO
- Purch Group: RMT
- Company Code: PSPK (auto from Purch Org)
Item Overview — enter manually:
- Material: RM-IRON-01
- Quantity: 50 TO
- Net Price: 250000 (auto-fills if Info Record exists)
- Plant: PK01
- Storage Location: RAWM
- Delivery Date: planned date
Item Detail → Invoice tab: Tax Code I0 (Input 0% — F4 to check your system; V0 may not exist)
Check → Save → PO # assigned

⚠️ Caveat of Flow B: No requisitioner approval trail. No PR-PO link. Bypasses release strategy in some configs. Avoid unless specifically needed.

🆚 Quick Comparison — Flow A vs Flow B

Aspect	Flow A (from PR) ⭐	Flow B (direct PO)
Data re-entry	Minimal — just verify + add tax/payment terms	All fields manual
Time to create	~1 minute	~5-10 minutes
PR-PO link in EKPV	✅ Yes — full audit	❌ No
Requisitioner approval flow	✅ Yes (PR was approved)	⚠️ Depends on release strategy
Risk of typos	Low	High (manual)
Real-world frequency	~80% of POs	~20% (urgent, recurring)
When to use	Standard flow — always prefer this	Emergency, low-value, scheduled buys

Tables updated (after Save): EKKO (PO header) + EKPO (PO items) + EKET (delivery schedule) + EKPV (PR-to-PO link — Flow A only) + EKBE (PO history).

⚠️ No accounting entry yet — PO is a commitment, not a posting. Some companies enable "PO commitment" reporting which makes a memo entry, but no real G/L hit. Real FI hit comes at MIGO (Step 3).

🔧 Pro tip — Set Personal Settings for ME21N too

Just like ME51N (Step 1), set defaults in ME21N → Personal Setting button → Default Values:

Document Type: NB
Purchasing Org: PKLO
Purchasing Group: RMT
Plant: PK01
Storage Location: RAWM
Acct Assignment Cat: blank (or K if usually consumable)

This makes Flow B faster too (defaults pre-fill).

Step 3. Goods Receipt — MIGO with movement 101

What: Vendor delivers the iron ore. You confirm receipt and post it to inventory. FIRST accounting entry hits here.

⚠️ FIRST GR in a brand-new company code? Expect a chain of one-time config errors (ML not productive → T169P → VP tolerance → G/L not in CC → number range NR751). This is NORMAL — each is a 2-minute fix. Full plain-language walkthrough: Setup Guide → Step 1O (Material Ledger) + 1P (the 4 Gates) + the 9-Gate Gauntlet table. Fix all of them up front and MIGO posts first try.

Action:

Run MIGO
Transaction: Goods Receipt · Reference: Purchase Order · PO #: 4500000123
Movement Type: 101 (GR for PO into warehouse) — auto-filled
Header: Delivery Note # from vendor (any text e.g., "DN-MS-789"), Bill of Lading # optional, Posting Date = today
Item Overview tab: Confirm Quantity (50 TO), Storage Location (RAWM), Item OK checkbox ✓
Click Check → no errors → click Post (Ctrl+S)
Material Document # assigned (e.g., 5000000123) AND FI Document # auto-generated

Accounting entry posted automatically (via OBYC):

Posting Key	G/L Account	Description	Amount
89 (Inventory Dr)	`300000`	Raw Material Inventory (BSX rule for VKL 3000)	Dr 12,500,000
96 (GR/IR Cr)	`191100`	GR/IR Clearing (WRX rule)	Cr 12,500,000

Tables updated: MSEG (material doc items) + MKPF (material doc header) + BKPF/BSEG (FI doc) + MBEW (material valuation updated — stock qty + value).

Verify: Run MMBE (Stock Overview) for RM-IRON-01 → 50 TO unrestricted stock at PK01/RAWM.

Step 4. Invoice Receipt — MIRO

What: Vendor sends invoice; you verify it matches the PO + GR (3-way match: PO qty/price ↔ GR qty ↔ Invoice qty/price). Post → vendor liability created.

Action:

Run MIRO
Transaction: Invoice · Invoice Date: vendor's invoice date · Posting Date: today
Reference: vendor invoice # (e.g., "INV-MS-2025-456")
Amount: 12,500,000 PKR (gross)
Calculate Tax checkbox: ✓ (if tax applicable)
PO Reference tab: PO # = 4500000123 → enter
System pulls in the GR line → confirm Qty (50 TO), Net Price (250,000)
Balance shows 0.00 (gold light 🟢) → Post
Invoice doc # assigned (e.g., 5105600123)

Accounting entry:

Posting Key	G/L Account	Description	Amount
86 (GR/IR Dr)	`191100`	GR/IR Clearing (clears the credit from GR)	Dr 12,500,000
31 (Vendor Cr)	`160000`	Trade Payables (via vendor recon account)	Cr 12,500,000

The famous GR/IR clearing: After GR + IV, GR/IR account net = 0. If different, it means qty or price mismatch. GR/IR is a transit account — should always clear.

Tables updated: RBKP (invoice header) + RSEG (invoice items) + BKPF/BSEG (FI doc with vendor open item).

Step 5. Vendor Payment — F-53 (manual) or F110 (automatic)

What: Pay the vendor → clear the AP liability. Manual via F-53 (one-off), automatic via F110 (payment run for batch payments — real projects use this).

Action (F-53 manual):

Run F-53
Document Date / Posting Date: today · Company Code: PSPK · Currency: PKR
Bank Data: G/L account = 113100 (bank main account) · Business Area blank · Amount = 12,500,000
Open Item Selection: Vendor = MUGHAL21
Click Process Open Items → SAP lists vendor's open invoices
Select invoice 5105600123 → Amount Entered must equal Assigned → Post
Payment doc # assigned (e.g., 1500000123)

Accounting entry:

Posting Key	G/L Account	Description	Amount
25 (Vendor Dr)	`160000`	Trade Payables (clears the credit)	Dr 12,500,000
50 (Bank Cr)	`113100`	Bank Main Account	Cr 12,500,000

Tables updated: BKPF/BSEG (payment doc) + BSAK (vendor cleared items — invoice & payment matched).

Step 6. Trace the COMPLETE document flow — ME23N · FBL1N · FB03 (consultant skill!)

What: After the cycle completes, prove every link in the chain and that the vendor account is CLEAR. This is what auditors, FI teams, and clients ask you to do daily.

Method 1 — The PO History hub (⭐ start here)

ME23N (auto-opens your last PO) → click item → tab "Purchase Order History"
Every follow-on doc is listed: WE (GR material doc) + RE-L (invoice) with qty/value
Click any doc number to drill in · GR doc → Doc Info → FI Documents → accounting doc · Invoice → Follow-On Documents → its FI doc
PR link: item detail field Purchase Requisition (EKPO-BANFN) — or from the PR side: ME53N → Status tab shows the PO it became

Method 2 — FBL1N: prove vendor account is clear

FBL1N · Vendor MUGHAL21 · CC PSPK · radio "Cleared items" → Execute
Invoice (RE) + Payment (KZ) both show green ✓ and carry the SAME Clearing Document number (AUGBL) — SAP's proof they're matched and closed
Switch to radio "Open items" → list is EMPTY = vendor fully paid, account clear

Method 3 — Relationship Browser (the wow trick)

FB03 → any FI doc of the chain → menu Environment → Document Environment → Relationship Browser
SAP draws the whole document family tree — MM + FI + invoice docs, all clickable

🎓 Where the links live (interview gold)

Link	Table.Field
PO item → PR	`EKPO-BANFN`
PO → all follow-on docs (GR, IR…)	`EKBE` — the PO history table, one row per event
MM doc → FI doc	`BKPF-AWKEY` (FI doc stores the MM doc # as reference key)
Vendor open vs cleared items	`BSIK` (open) / `BSAK` (cleared)
The clearing "marriage certificate"	`AUGBL` (clearing doc) + `AUGDT` (date) stamped on BOTH items

💰 Complete Accounting Trail (T-account view)

G/L Account	GR (101)	IV (MIRO)	Payment (F-53)	Net
300000 Raw Mat Inventory	Dr 12,500,000	—	—	Dr 12,500,000
191100 GR/IR Clearing	Cr 12,500,000	Dr 12,500,000	—	0 ✓
160000 Trade Payables	—	Cr 12,500,000	Dr 12,500,000	0 ✓
113100 Bank	—	—	Cr 12,500,000	Cr 12,500,000

Net: Inventory ↑ 12.5M PKR · Bank ↓ 12.5M PKR · GR/IR clears to 0 (success indicator) · Vendor clears to 0 (paid).

🚨 Common Errors & Fixes

Step	Error	Root cause	Fix
MM01	"Valuation class 3000 not allowed for material type ROH"	OMSK config missing	OMSK → ROH → allow 3000-3999 range
ME21N	"Net price is 0.00"	No info record or price 0	Create info record (ME11) or enter price manually in PO line
ME21N	"Account assignment mandatory for material XX"	Material type not stockable (NLAG/UNBW)	For stock material, ensure type ROH/HALB/FERT; for non-stock, enter Acct Asgn K
MIGO	"Account determination for entry INT BSX VKL 3000 not possible"	OBYC missing	OBYC → BSX → add row for VKL 3000, G/L 300000
MIGO	"Posting period MM YYYY is not open"	OB52	Open period in OB52 for variant PSPK
MIGO	"Document number not in range 49"	FBN1 range 49 missing	FBN1 → CC PSPK → create range 49
MIRO	"Balance not zero"	Qty/price mismatch with PO	Check qty (GR vs invoice) and price (vendor invoice vs PO)
MIRO	"Tax code V1 does not exist"	FTXP missing	FTXP → create tax code V1 (PK Sales Tax 17%)
F-53	"No open items found"	Wrong vendor or invoice already paid	FBL1N → vendor → check open status

✅ Verification — How to confirm Scenario 1 worked

#	T-code	Check
1	ME53N	PR 10000123 status = Completed (converted to PO)
2	ME23N	PO 4500000123 status = Delivered + Invoiced
3	MB51	Mvt 101 entry for RM-IRON-01 at PK01/RAWM
4	MMBE	RM-IRON-01 → 50 TO unrestricted at PK01/RAWM (or less if consumed)
5	MIR4	Invoice 5105600123 status = Posted, balance 0
6	FBL1N	Vendor MUGHAL21 → no open items (cleared)
7	FAGLB03	G/L 191100 GR/IR → net 0 for this PO
8	FBL3N	G/L 300000 → debit of 12,500,000 visible

🎓 Interview-ready 30-sec answers from this scenario

Q: Walk me through the standard P2P cycle

PR (internal request, ME51N) → PO (commitment to vendor, ME21N, no FI hit) → GR (101, MIGO — inventory Dr, GR/IR Cr) → IV (MIRO — GR/IR Dr, vendor Cr; 3-way match) → Payment (F-53 or F110 — vendor Dr, bank Cr). GR/IR clears across GR + IV; if non-zero, qty or price mismatch.

Q: What's the difference between V and S price control?

V = Moving Average — material valuation updates with every GR at actual price. Used for raw materials where vendor price varies. S = Standard Price — fixed price set in master; any variance posts to a separate variance account. Used for finished goods (FERT) for stable costing.

Q: How does GR auto-determine the G/L account 300000?

Material's Valuation Class (3000 in Accounting view) + Movement Type (101) + Transaction Key (BSX for inventory) + Chart of Accounts (INT) → OBYC table lookup → G/L 300000. Pure config, no user input needed.

✅ Scenario 1 complete — full P2P cycle executed end-to-end

Return to Vendor — Quality Reject

FOUNDATION ★☆☆☆☆ ⏱️ ~1 hour MIGO (122 or 161) → MIRO (credit memo)

🇵🇰 Business Story

Of the 50 tons iron ore received from Mughal Steel in Scenario 1, 5 tons fail quality inspection — moisture content above spec. PakSteel raises a return to vendor. Mughal Steel issues a credit note for PKR 1,250,000. Two methods exist: Return Delivery (mvt 122) when invoice not yet received, OR Return PO with mvt 161 when invoice received and credit memo needed.

🎯 What you'll learn

Two return methods and when to use each (122 vs 161)
How return movements reverse the original FI entries
Vendor credit memo (Doc type KG) vs invoice (KR) — same MIRO, different sign
How to track returns reporting (MB51 with movement filter)

📋 Prerequisites

Scenario 1 completed (PO, GR, IV all done). Material RM-IRON-01 has stock.

🔄 Method A — Return Delivery (mvt 122) — when invoice not yet received

2A.1. Return delivery via MIGO mvt 122

When to use: GR done but MIRO not yet posted. You return the goods BEFORE invoice arrives. Vendor either reships or you reduce the future invoice.

Action:

Run MIGO
Transaction: Return Delivery · Reference: Material Document · Material Doc # from original GR (5000000123)
Movement Type auto-sets to 122
Reason for Movement: 0001 (Quality reject) — mandatory
Quantity: 5 TO (of original 50)
Storage Location: RAWM
Post → Material doc # assigned

Accounting entry (reverses GR for 5 TO):

Inventory (300000)	Cr 1,250,000
GR/IR (191100)	Dr 1,250,000

Net effect — depends on whether the invoice was already posted:

Timing	What happens to the 122's GR/IR debit	Money document needed?
Return BEFORE invoice (normal case for 122)	Nets against the original GR credit still sitting on GR/IR (12.5M Cr − 1.25M Dr = 11.25M Cr) → the later invoice for 45 TO clears it to zero. GR-Based IV proposes 45 automatically	❌ None — vendor just invoices 45
Return AFTER invoice	Original GR credit already consumed by the full invoice → the 1,250,000 debit dangles open, waiting for the vendor's credit memo (= the Pakistani "debit note") to clear it	✅ MIRO → Credit Memo 1,250,000 (see Method B step 2B.3)

💡 The 122 always posts identically (Inventory Cr / GR-IR Dr). What differs is whether the original GR credit is still there to absorb it. Also: the return reopens 5 TO as "on-order stock" — SAP expects a replacement delivery. If none is coming: ME22N → item → Delivery tab → "Delivery Completed" ✓ (or reduce PO qty to 45).

🔄 Method B — Return PO + mvt 161 — when invoice already received

2B.1. Create Return PO — ME21N with Returns flag

When to use: MIRO already posted; vendor needs to issue credit memo. Return PO formally documents the reverse transaction.

Action:

Run ME21N — a Return PO is a NORMAL PO + one tick. Same header as always (Standard PO, Purch Org, Group — Personal Settings fill them)
Vendor: MUGHAL21
Item: Material RM-IRON-01, Qty 5 TO, Plant PK01 · Net Price stays the ORIGINAL purchase price (it drives the credit memo value!) · Tax Code I0
⭐ The one new thing: tick the "Returns Item" checkbox — the small R column in the item grid (scroll right; also visible in Item Detail)
Save → Return PO #

2B.2. Goods Issue against return PO — MIGO mvt 161

Action:

Run /nMIGO (fresh screen)
Transaction: Goods Receipt · Reference: Purchase Order
⚠️ Top-right header movement field: keep/type 101 — NEVER type 161 there! Manually forcing 161 throws M7 873 "Movement type 161 is not allowed". The rule: 101 is what you TYPE, 161 is what the Returns flag MAKES
PO #: your Return PO → Enter → the ITEM line's Mvt column shows 161 by itself (derived from the R tick)
Header → Delivery Note: e.g. RET-MS-002 (your return challan # — mandatory in many systems, error M7 018)
Item → Where tab → Storage Location RAWM — a return ISSUES stock, SAP must know from which shelf (M7 018 "Enter Location" if empty)
Quantity 5 TO (Quantity tab if adjusting) · Item OK ✓ · Check → Post

🚨 If M7 873 persists with a correct setup: (1) ME23N → confirm the R tick was really saved on the PO item; (2) OMJJ → movement 161 → Allowed Transactions → must include MIGO (compare against 122's list, which works — note: MIGO_GR may not exist as a tcode in your S/4 release). Full diagnosis in the Troubleshooting encyclopedia.

Same accounting effect as mvt 122 (inventory Cr 1,250,000 / GR-IR Dr 1,250,000) — different in that it's tied to a return PO, which gives the credit memo something formal to reference.

2B.3. Credit Memo from vendor — MIRO doc type KG

Action:

Run MIRO
Transaction: Credit Memo (not Invoice)
Doc Type: KG (Vendor credit memo)
Reference: vendor's credit note # e.g., "CN-MS-2025-001"
Amount: 1,250,000 PKR
PO Reference: return PO 4500000125
Balance 0 → Post

Accounting: GR/IR Cr 1,250,000 / Vendor Dr 1,250,000 (reduces vendor liability — they owe you back).

✅ Verify Scenario 2

MB51 → filter Movement Type 122 or 161 → see return entries
MMBE → RM-IRON-01 → stock dropped from 50 to 45 TO
FBL1N → Vendor MUGHAL21 → debit balance of 1,250,000 (they owe you)
F-44 or F-58 to actually clear the credit (vendor refunds bank, or offset against next invoice)

💡 122 vs 161 — when to use which

Method	When	Vendor receives
Return Delivery (122)	Invoice NOT yet posted	Adjusted future invoice OR reship
Return PO + 161	Invoice ALREADY posted	Issues Credit Memo (KG) — formal paperwork

✅ Scenario 2 complete — return executed via 122 and/or 161

Goods Issue & Stock Transfers — Internal Movements

FOUNDATION ★☆☆☆☆ ⏱️ ~1 hour MIGO / MB1A / MB1B (201, 261, 311, 309)

🇵🇰 Business Story

Now that iron ore is in stock at PK01, PakSteel needs to:

Issue 30 TO to Production (consumption) — via mvt 261 to a production order, or mvt 201 to cost center if no PP order
Transfer 10 TO from RAWM to WIPS within same plant — internal storage location move (mvt 311)
Convert 5 TO of HALB-BILLET-01 from one material to another (mvt 309) — change item

🎯 What you'll learn

Movement types 201, 261, 311, 309 and what each does to inventory + FI
Consumption to cost center (CO touch — needs CO setup)
Storage location transfer (no FI, just inventory move)
Material-to-material transfer (rare but useful for grade reclassification)
OBYC role in determining offset G/L for consumption

🔄 Movement Type Cheat Sheet

Mvt	What	FI effect	OBYC key
201	GI to cost center (consumption)	Consumption Dr / Inventory Cr	GBB · VBR
202	Reverse 201 (return from cost ctr)	Inventory Dr / Consumption Cr	GBB · VBR
261	GI to production order	Consumption Dr / Inventory Cr	GBB · VBR
262	Reverse 261	Inventory Dr / Consumption Cr	GBB · VBR
311	Transfer SLoc → SLoc (same plant)	No FI (same valuation area)	—
301/303	Transfer Plant → Plant (one-step / two-step)	FI if cross-CC; none if same CC	GBB · UMB
309	Material → Material (reclassification)	Old Inventory Cr / New Inventory Dr	BSX (both)
561	Opening stock entry (initial upload)	Inventory Dr / Off-balance Cr	GBB · BSA
501	Receipt without PO (gift, sample)	Inventory Dr / Other revenue Cr	GBB · ZOB

3.1. Goods Issue to Cost Center — mvt 201 (needs CO setup)

What: Issue 5 TO of iron ore to Karachi Production cost center for testing/sampling. Goes to expense (consumption), hits the cost center.

Action:

Run MIGO (or MB1A)
Transaction: Goods Issue · Movement Type: 201
Plant PK01, Storage Location RAWM
Material: RM-IRON-01 · Quantity: 5 TO
Account Assignment tab → Cost Center: PKKHI-PROD
Post → Material doc # assigned

Accounting (auto via OBYC GBB-VBR):

Consumption Raw Mat (400000)	Dr 1,250,000	Cost Center: PKKHI-PROD
Inventory (300000)	Cr 1,250,000	—

CO posting: Cost Center PKKHI-PROD shows debit of 1,250,000 in S_ALR_87013611 cost center actual/plan report.

3.2. Goods Issue to Production Order — mvt 261 (requires PP order)

What: Issue 25 TO of iron ore to a production order making steel billets. Component consumption tied to PP order.

Prerequisite: A production order exists (CO01 or auto-created via MRP). For practice, skip this if PP not set up.

Action:

Run MIGO (or MB1A)
Transaction: Goods Issue · Movement Type: 261
Account Assignment: Order = production order # (e.g., 1000000023)
Material RM-IRON-01, Qty 25, Plant PK01, SLoc RAWM → Post

3.3. Storage Location Transfer — mvt 311 (no FI)

What: Move 10 TO of iron ore from RAWM (raw material warehouse) to WIPS (work-in-progress location) — both in plant PK01.

Action:

Run MIGO (or MB1B)
Transaction: Transfer Posting · Movement Type: 311
Source: Material RM-IRON-01, Plant PK01, SLoc RAWM
Destination: same Plant PK01, SLoc WIPS
Quantity: 10 TO · Post

FI effect: NONE. Same valuation area (plant-level), just changing physical location. Only MARD updated (stock per SLoc).

3.4. Material Reclassification — mvt 309 (one material → another)

When used: You discover 5 TO of HALB-BILLET-01 is actually different specification — convert to a new material code without physically moving stock. Useful for grade reclassification, batch error correction.

Action:

Run MIGO
Transaction: Transfer Posting · Movement Type: 309
Source Material: HALB-BILLET-01, Qty 5 TO, Plant PK01, SLoc WIPS
Destination Material: HALB-BILLET-02 (must exist!) — same plant + SLoc
Post

FI effect: Old material inventory Cr + new material inventory Dr (BSX both sides). If price differs → variance posts to gain/loss G/L.

✅ Verify Scenario 3

MB51 → filter by RM-IRON-01 → see 201, 261, 311 entries in chronological order
MMBE → stock per SLoc — RAWM lower, WIPS higher
S_ALR_87013611 → Cost Center PKKHI-PROD shows consumption debit
FBL3N → G/L 400000 (Consumption) shows debit; 300000 (Inventory) shows credit equal amount

✅ Scenario 3 complete — internal stock movements (201, 311, optionally 261, 309) executed

🔵 Tier 2: Account-Assigned Procurement

POs where the material doesn't go to stock — it goes directly to a cost object (cost center, asset, order). Requires CO setup — see Setup Guide Step 19 (Controlling Area & Cost Centers).

Service Procurement — Consulting Hours

INTERMEDIATE ★★☆☆☆ ⏱️ ~2 hours AC03 → ME21N (item D) → ML81N → MIRO

🇵🇰 Business Story

PakSteel hires Lucky Consulting (Pvt) Ltd for SAP implementation support — 120 consulting hours @ PKR 5,000/hour = PKR 600,000. Service is delivered weekly; PakSteel approves time sheets via Service Entry Sheet (SES). Cost hits the IT Department cost center (PKADM-IT).

🎯 What's different from stock procurement

No material master needed — use Service Master (AC03) or short text
Item Category D (Service) in PO — different flow from blank (standard stock)
No MIGO — use ML81N Service Entry Sheet instead
Cost goes directly to a cost center (no inventory) → CO must be set up
Account Assignment K mandatory
Two-step acceptance: SES creation + approval (release)

📋 Prerequisites

CO setup complete — Setup Guide Step 19 (Controlling Area + cost centers)
Cost Center PKADM-IT created in KS01
G/L 470000 (Consulting Expense) exists in INT chart, marked as Cost Element Cat = 1
Vendor VEN-LCK-CON (Lucky Consulting) created via BP with FLVN00/01/02 roles

📦 Master Data Setup

4.1. Create Service Master — AC03

What: Service Master = the "material" for services. Optional but reusable. Alternative is to type service description directly in PO each time.

Action:

Run AC03
Activity Number: SVC-CONSULT-01 · Service Category: SERV
Description: SAP Functional Consulting Hour
Base Unit: HR (Hour) · Valuation Class: 3200 (Services)
Material Group: 007 (Services)
Tax Indicator: relevant for services in PK (often 17%)
Purchasing Org Data: Purch Org PKLO, Purch Group SRV
Save

🔄 Transaction Flow

4.2. Service PO — ME21N with Item Category D

Action:

Run ME21N
Doc Type: NB · Vendor: VEN-LCK-CON
Header → Org Data: Purch Org PKLO · Purch Group SRV
Line 1:
- Item Category: D (Service)
- Account Assignment Category: K (Cost Center)
- Material: leave blank (use service master in line detail) OR enter SVC-CONSULT-01
- Plant: PK01
- Short Text: SAP MM Implementation Support
Click line → Service tab (bottom): Enter service line:
- Service No: SVC-CONSULT-01 (or short text)
- Quantity: 120 HR
- Gross Price: 5000 PKR/HR
- Cost Center: PKADM-IT
- G/L Account: 470000 (Consulting Expense)
Save → PO # assigned

Tables: EKKO + EKPO (item D) + ESLL (service lines) + ESLH (service header).

4.3. Service Entry Sheet — ML81N

What: Equivalent of GR for services. Records "service delivered." Vendor performs the work weekly; you create an SES for hours delivered.

Action:

Run ML81N
Click Create · enter PO # → Enter
SES line: pulls service from PO → enter Actual Quantity (e.g., 40 hours this week)
Header: External Number (e.g., timesheet ref), Period
Save (creates SES, status = "Created")
Click Accept (green tick) → status = "Accepted" → FI/CO posted

Accounting on Acceptance:

Consulting Expense (470000)	Dr 200,000	Cost Center: PKADM-IT
GR/IR Services (191200)	Cr 200,000	—

Repeat SES weekly until all 120 hours delivered.

4.4. Invoice Verification — MIRO

Same as Scenario 1's MIRO — reference PO, system pulls in accepted SES quantities, balance 0, post.

GR/IR Services (191200)	Dr 600,000
Vendor (160000 via VEN-LCK-CON)	Cr 600,000

🚨 Common Errors

Step	Error	Fix
ME21N	"Item category D not allowed for doc type NB"	OMG0 → allow item cat D for NB; or use service doc type FO
ME21N	"Cost center PKADM-IT not assigned"	KS01 → check valid-from date covers today
ML81N	"Service entry sheet not released"	Click Accept (green tick) — required before invoicing
MIRO	"Service-based invoice verification — no quantity"	SES must be accepted first; check Header → "Service-based IV" flag

✅ Verify Scenario 4

ML84 → list of SES for PO → all accepted
S_ALR_87013611 → Cost Center PKADM-IT → debit 600,000
FBL1N vendor cleared after F-53 payment

✅ Scenario 4 complete — Service PO + SES + IV cycle done

Consumable Direct Purchase — Office Supplies (NLAG)

INTERMEDIATE ★★☆☆☆ ⏱️ ~1.5 hours MM01 (NLAG) → ME21N (acct K) → MIGO → MIRO

🇵🇰 Business Story

PakSteel Finance Department orders 100 reams of A4 paper from local stationery supplier — PKR 800/ream = PKR 80,000. Material doesn't go to stock (NLAG = non-stock). GR posts directly to expense, tied to Finance cost center (PKADM-FIN).

🎯 NLAG vs ROH — the key difference

NLAG (Non-stock material) = no inventory tracking. No MBEW, no MARD. Each PO posts directly to expense at GR.
ROH = stocked, valued. Inventory account hit at GR; consumption posted later via separate GI.
Use NLAG for low-value items consumed immediately: office supplies, cleaning materials, small parts.
Account Assignment K (cost center) is mandatory on every NLAG PO.

📦 Master Data

5.1. Create NLAG Material — MM01

Action:

MM01 · Material OFFC-PAPER-01 · Industry M · Material Type NLAG
Views needed: Basic Data 1, Purchasing — no Accounting view (NLAG isn't valued)
Description: A4 Office Paper 80gsm 500 sheets · Base Unit: EA
Purch Group: OFC (or RMT)
Save

🔄 Transaction Flow

5.2. Direct PO with Account Assignment K — ME21N

ME21N · Vendor: any local stationer (e.g., create new BP)
Line 1:
- Account Assignment Category: K (Cost Center)
- Item Category: blank
- Material: OFFC-PAPER-01
- Quantity: 100 EA · Net Price: 800 PKR
- Plant: PK01
Item Detail → Account Assignment tab:
- Cost Center: PKADM-FIN
- G/L Account: 410000 (Office Supplies Expense) — auto-determined from material group or AAC
Save

5.3. GR with mvt 101 — posts directly to expense (NO inventory)

Key difference: Because material is NLAG + Acct K, GR doesn't hit inventory — it hits the expense G/L directly.

Accounting:

Office Supplies Expense (410000)	Dr 80,000	Cost Center: PKADM-FIN
GR/IR (191100)	Cr 80,000	—

No MMBE entry (no inventory). MB51 still shows the movement record.

5.4. MIRO — same as standard

Reference PO → balance 0 → Post. GR/IR Dr, Vendor Cr.

🚨 Common Errors

"Material OFFC-PAPER-01 is non-stock — Account Assignment required"	Add Acct K + cost center on PO line
"GBB VBR for VKL not found"	OBYC → GBB → VBR row missing for cost center consumption — add G/L 410000

✅ Scenario 5 complete — NLAG direct purchase with Acct K

Asset Procurement — New CNC Machine

INTERMEDIATE ★★★☆☆ ⏱️ ~2 hours AS01 → ME21N (acct A) → MIGO → MIRO → ABT1N

MM AM FI CO

⚙️ Prerequisite Setup

This scenario needs FI-AA (Asset Accounting) module activated — typically FI consultant work, not MM:

Asset Classes defined (e.g., 2000 Plant & Machinery)
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

🇵🇰 Business Story

PakSteel Karachi Factory purchases a CNC milling machine from Pak Machine Tools Ltd for PKR 4,500,000. Asset is capitalized in FI-AA module, depreciated over 10 years. May start as Asset Under Construction (AuC) during installation, then transferred to active asset after commissioning.

🎯 What's different — 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

📋 Prerequisites (FI-AA)

Asset Class exists (e.g., 2000 Plant & Machinery)
Depreciation Areas configured (01 Book, 15 Tax for Pakistan)
Account Determination for Asset Class (links to G/L 140000 Plant & Machinery)
Above is FI consultant territory; just ask "is asset class 2000 ready?" before starting

📦 Master Data

6.1. Create Asset Master — AS01

AS01 · Asset Class: 2000 · Company Code: PSPK
Description: CNC Milling Machine - Karachi Line 1
Cost Center: PKKHI-PROD · Plant: PK01
Time-dependent tab: Useful Life 10 years
Depreciation Areas tab: Depreciation Key LINK (straight-line) for area 01
Save → Asset # assigned (e.g., 200000123)

🔄 Transaction Flow

6.2. PO with Account Assignment A — ME21N

ME21N · Vendor: Pak Machine Tools BP
Line: Acct Asgn A · Material blank (use short text) · Short Text: CNC Milling Machine VMC-850
Quantity: 1 EA · Net Price: 4,500,000 PKR · Plant PK01
Account Assignment tab: Asset = 200000123 · G/L 140000 auto
Save

6.3. GR — capitalizes the asset

Accounting:

Plant & Machinery (140000)	Dr 4,500,000	Asset: 200000123
GR/IR (191100)	Cr 4,500,000	—

Asset value now 4.5M in FI-AA. Depreciation kicks in from capitalization date.

6.4. Optional — AuC route (when asset takes months to install)

Create AuC asset first (Class 4000) → procure → GR hits AuC
Once commissioned: AIAB distribute AuC costs → AIBU settle to final asset

6.5. MIRO + Payment — standard flow

Same as Scenario 1 from MIRO onwards.

🚨 Common Errors

"Asset class 2000 has not been created"	FI-AA setup needed — talk to FI consultant
"Account determination not possible (account assignment A)"	AO90 config missing — FI-AA
"Asset capitalization date not set"	AS02 → fill Capitalized On date

✅ Verify Scenario 6

AW01N Asset Explorer → asset 200000123 → 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

✅ Scenario 6 complete — Asset procured + capitalized + depreciation running

🟡 Tier 3: Multi-Plant Movements

Stock Transport Orders (STO) move material between plants. Intra-company STO is simple (same CC). Inter-company STO involves SD billing and cross-CC payment — the most complex flow in this tier.

Intra-Company STO — Karachi → Lahore

INTERMEDIATE ★★☆☆☆ ⏱️ ~1.5 hours ME21N (UB) → MIGO (351 or 641/101)

🇵🇰 Business Story

PakSteel Karachi (PK01) has surplus 20 TO of finished rebars (FERT-REBAR-01). Lahore plant (PK02) has demand. Both plants belong to the SAME company code PSPK. Move stock from Karachi to Lahore using STO. Two flavors: one-step (mvt 647) instant transfer, or two-step (mvt 641 → 101) with stock in transit.

🎯 What's different — STO vs simple transfer (311)

STO uses a PO document (Doc Type UB) — for tracking, approval, delivery
Cross-plant (PK01 → PK02), not just SLoc-to-SLoc
No invoice when intra-company (same CC, no AR/AP)
Delivery via SD optional (more enterprise; simple cases use direct mvt 351 without SD)
FI impact depends on whether plants share valuation area (usually plant-level → potential price-difference posting)

📋 Prerequisites

Both plants PK01 + PK02 assigned to same CC PSPK
Material FERT-REBAR-01 extended to BOTH plants (MM01 with plant view for each)
STO Doc Type UB active (delivered standard)
For SD-integrated route: shipping points + sales area assignments (skip for simple route)

🔄 Transaction Flow — Simple route (mvt 351 without delivery)

7.1. Create STO — ME21N with Doc Type UB

ME21N · Doc Type: UB (Stock Transport Order)
Supplying Plant: PK01 (header → Customer/Vendor tab if needed)
Line:
- Material FERT-REBAR-01 · Qty 20 TO
- Receiving Plant: PK02 (in the Plant field on line)
- Item Category: blank (standard)
- Storage Location at receiving: FNGD
Save → STO # (e.g., 4500000200)

7.2. Goods Movement — Method 1: One-step (647)

Stock leaves PK01 and arrives at PK02 instantly. No in-transit stock.

MIGO · Goods Issue · Reference: Purchase Order · STO #
Movement Type: 647 (auto)
Confirm qty + SLocs (RAWM out at PK01, FNGD in at PK02)
Post

FI: NONE if plant valuation prices are equal (same material code, same plant-level price). If price differs → variance to gain/loss G/L.

7.3. Goods Movement — Method 2: Two-step (641 → 101)

Stock leaves PK01 → in-transit → arrives at PK02 later (realistic for trucks taking 2 days).

Step A (issue from supplying plant): MIGO → Goods Issue → STO → mvt 641 → post (creates in-transit stock at PK02)
Step B (receipt at receiving plant): MIGO → Goods Receipt → STO → mvt 101 → post (clears in-transit, lands at FNGD)

Track in-transit: MMBE for FERT-REBAR-01 → "Stock in Transit" column shows qty between steps A and B.

✅ Verify Scenario 7

MMBE → FERT-REBAR-01 → 20 TO moved from PK01 to PK02
MB51 → mvt 351/641/647 entries
ME23N → STO 4500000200 → all items delivered
ME2O stock provided to vendor / stock transit overview

✅ Scenario 7 complete — Intra-company STO done

Inter-Company STO — PakSteel Karachi → PakSteel Dubai (PSPK → PSAE)

ADVANCED ★★★★☆ ⏱️ ~3 hours ME21N (NB) → VL10B → VF01 → MIGO → MIRO

MM SD FI

⚙️ Prerequisite Setup Required

This scenario needs SD module configuration (Sales Org, Distribution Channel, Division, Shipping Point, OBYA inter-co clearing). If not yet done in your IDES:

📖 Complete Setup Guide Step 16 (SD Setup for Inter-Co STO) first — 10 sub-steps (16A-16J)
🪂 Alternative: Skip this scenario and do Scenario 7 (Intra-Company STO) instead — same MM mechanics, no SD needed
👥 Or: Ask your SD consultant to do the setup for you

🇵🇰 Business Story

PakSteel Pakistan (PSPK, plant PK03 Karachi DC) sells 500 TO of TMT rebars to PakSteel UAE (PSAE, plant AE01 Dubai). Even though same parent company, PSAE is a separate legal entity (UAE LLC, AED currency). This requires actual SD billing + AP/AR clearing. Total: PKR 75,000,000 ≈ AED 1,000,000 at 75:1 rate.

🎯 What makes inter-company STO the most complex flow

Two CCs involved (PSPK + PSAE) → real AR (sender) + AP (receiver)
Currency conversion (PKR ↔ AED)
SD module used — outbound delivery + intercompany billing
Vendor master in receiving CC = supplying CC's "customer" linkage
Customer master in supplying CC = receiving CC's "vendor" linkage
Customs/import implications (Pakistan export, UAE import)

📋 Prerequisites — significant config

Setup	Where	Done in Setup Guide?
CC PSPK + PSAE configured	Step 1 + 2	✓
Plant PK03 + AE01 + assignments	Step 3 + 4	✓
Customer master in PSPK for PSAE (link)	BP role FLCU01	Step 14
Vendor master in PSAE for PSPK (link)	BP role FLVN01	Step 14
Plant↔Customer + Plant↔Vendor assignments	OMGN	Step 14
Sales area for supplying plant PK03	SD config (OVXG, etc.)	SD consultant
Shipping point assigned to PK03	OVL2	SD consultant
STO doc type for cross-CC: `NB`	OMGN customizing	SD/MM consultant
Intercompany Pricing Procedure (IV01)	SD config	SD consultant

🔄 Transaction Flow (high-level)

8.1. Receiving plant creates STO — ME21N doc type NB

PSAE creates a PO with PSPK's plant PK03 as "supplier" (Vendor = vendor master of PSPK linked via OMGN).

ME21N · Doc Type: NB · Vendor: vendor # representing PSPK (e.g., 1000099)
Org Data: Purch Org AELO (PSAE) · Purch Group RMT
Line: Material FERT-REBAR-01 · Qty 500 TO · Plant AE01 (receiving) · SLoc EXPT
Save

8.2. Supplying plant creates outbound delivery — VL10B or VL10G

SD takes over — PSPK's shipping point creates outbound delivery referencing the STO.

VL10B · selection: by Vendor → enter STO #
Select line → click Background
Delivery # generated (e.g., 80000123)

8.3. Post Goods Issue from delivery — VL02N

VL02N · delivery # · click Post Goods Issue (PGI)
Movement type 643 or 645 posted

Accounting at supplying CC PSPK:

Cost of Goods Sold (500000)	Dr	—
Inventory FERT (302000)	Cr	—

8.4. Intercompany Billing — VF01

VF01 · reference delivery 80000123
Billing type: IV (Intercompany Billing)
Save → Billing doc #

Accounting at supplying CC PSPK:

Customer (PSAE recv) (130000)	Dr 75,000,000	—
Intercompany Revenue (510000)	Cr 75,000,000	—

8.5. Receiving plant: GR — MIGO

PSAE receives the goods at AE01.

Accounting at receiving CC PSAE: (converted to AED)

Inventory FERT (300000)	Dr 1,000,000 AED
GR/IR (191100)	Cr 1,000,000 AED

8.6. Receiving plant: Invoice — MIRO

PSAE invoices itself against PSPK's billing doc (cross-CC AP/AR).

GR/IR (191100) at PSAE	Dr 1,000,000 AED
Vendor (PSPK supplier) (160000)	Cr 1,000,000 AED

Final settlement: Periodic inter-company netting via F.13 or treasury — AR in PSPK matched against AP in PSAE.

💡 Key insight

Inter-company STO = MM ↔ SD ↔ FI integration. As MM consultant you set up the receiving side; SD consultant handles delivery + billing; FI consultant handles cross-CC clearing. Real projects spend 2-4 weeks on this flow.

✅ Scenario 8 complete — Inter-company STO end-to-end (often skipped in IDES — review flow only)

🟠 Tier 4: Special Procurement Types

Non-standard procurement flows that don't follow the basic PR→PO→GR→IV pattern: subcontracting (BOM-driven), consignment (vendor stock at our site), pipeline (continuous flow), and third-party (drop-ship).

Subcontracting — Send Components, Receive Finished Goods

ADVANCED ★★★★☆ ⏱️ ~2.5 hours CS01 → ME21N (item L) → MIGO (541/543/101)

MM PP FI

⚙️ Prerequisite Setup (minimal)

This scenario uses BOM (PP master data) but does NOT need full PP module setup:

✅ You need: Just CS01 (Create BOM) — covered in this scenario step 9.1. No work centers or routings needed.
📖 Reference: Setup Guide Step 17B covers BOM creation in detail if you want to read more
⏩ Why subcon doesn't need full PP: The "production" is done by the SUBCONTRACTOR (external vendor), not your plant. So no PP order, no work center, just BOM mapping for components.

🇵🇰 Business Story

PakSteel doesn't have galvanizing capacity. They send steel billets to Pakistan Cables Ltd (subcontractor) who galvanizes them and returns finished galvanized rebars. PakSteel pays the subcontractor a service fee (PKR 500/TO). Components (billets) remain PakSteel's ownership while at vendor site.

🎯 What makes subcontracting unique

Item Category L (Subcontracting) on PO
BOM-driven — system knows what components to send based on the BOM (CS01)
Special Stock O — "stock provided to vendor" (your stock, at vendor's location)
Three movements: 541 send components, 543 consume at receipt, 101 receive finished product
Vendor PO line shows BOTH the finished product AND its components
Subcontractor's bill = service charge only (not material value)

📦 Master Data Setup

9.1. Create BOM — CS01 for the finished product

Create a single-level BOM showing what components produce 1 TO of galvanized rebar.

CS01 · Material: FERT-REBAR-GALV-01 (galvanized rebar — create as FERT first) · Plant PK01 · Usage 1 (Production)
Components:
- HALB-BILLET-01 (steel billet) — Qty 1 TO per 1 TO output
- Optional: ZN-COATING (zinc coating consumable) — Qty 0.05 TO
Save BOM

9.2. Maintain Subcontracting Info Record — ME11

ME11 · Vendor VEN-PCABLE · Material FERT-REBAR-GALV-01 · Purch Org PKLO · Plant PK01
Info Category: Subcontracting
Net Price: 500 PKR/TO (the service fee, not the material value)
Save

🔄 Transaction Flow

9.3. Create Subcontract PO — ME21N with Item Cat L

ME21N · Doc Type NB · Vendor VEN-PCABLE
Line: Item Category L (Subcontracting) · Material FERT-REBAR-GALV-01 · Qty 100 TO · Plant PK01
Press Enter → SAP auto-expands components from BOM (HALB-BILLET-01 × 100 TO)
Net Price line: 500 PKR/TO (service fee) · Save

9.4. Send components to subcontractor — mvt 541 (MB1B or MIGO)

Run MB1B · Mvt Type 541 (or use ME2O for monitor-based dispatch)
Vendor VEN-PCABLE · Material HALB-BILLET-01 · Qty 100 TO · Plant PK01 · SLoc WIPS
Post

FI effect: NONE (same valuation, just transfer to "stock at vendor"). Stock now visible in MMBE under "Special Stock O".

Monitor: ME2O shows stock provided to vendor.

9.5. Receive finished product — MIGO mvt 101 + auto 543

MIGO · Goods Receipt · Reference Purchase Order · STO PO #
Qty 100 TO of FERT-REBAR-GALV-01 · SLoc FNGD · Post

Two movements happen simultaneously:

Mvt	What	Accounting
101	Receive 100 TO galvanized rebar	Inventory Galv Rebar Dr / GR/IR Cr (service fee value)
543	Consume components at subcontractor	Component Consumption Dr / Stock Provided to Vendor Cr

Net FI: Galv rebar inventory increases by component value + service fee. Component value (billets) moves from "stock provided" to consumption.

9.6. Invoice for service fee — MIRO

Vendor invoices ONLY the service portion (100 TO × 500 = PKR 50,000).

MIRO normally → GR/IR Dr / Vendor Cr 50,000.

✅ Verify Scenario 9

ME2O → stock at vendor cleared
MMBE → FERT-REBAR-GALV-01 stock 100 TO at PK01/FNGD
MMBE → HALB-BILLET-01 → reduced by 100 TO from WIPS
Vendor cleared after F-53

✅ Scenario 9 complete — Subcontracting end-to-end

Consignment Procurement — Vendor Stock at Our Plant

ADVANCED ★★★★☆ ⏱️ ~2 hours ME11 (cons info) → MIGO (101-K/411-K) → MRKO

🇵🇰 Business Story

DG Cement places 2000 bags of cement at PakSteel's Karachi DC on consignment. Cement remains DG Cement's property; PakSteel only pays when they actually consume/withdraw from consignment stock. Pakistani textile and construction industries use this heavily for raw materials.

🎯 Consignment essentials

Special Stock K — "vendor consignment stock" at our location
Item Category K on PO (or special info record category)
No invoice at GR — only when consumed (mvt 411-K) or settled via MRKO
Liability only created at consumption — improves cash flow
Stock visible in MMBE under "Vendor Consignment" column

📦 Master Data

10.1. Create Consignment Info Record — ME11

ME11 · Vendor VEN-CONSIG (DG Cement) · Material HAWA-CEMENT-01 · Purch Org PKLO · Plant PK01
Info Category: Consignment (option 2 on selection screen)
Net Price: 650 PKR/bag · Validity from-to
Save

🔄 Transaction Flow

10.2. Receive consignment stock — MIGO mvt 101 with Special Stock K

MIGO · Goods Receipt · "Other" (no PO needed — info record is enough)
Mvt 101 · Material HAWA-CEMENT-01 · Qty 2000 BAG · Plant PK01 · SLoc GNRL
Special Stock Indicator: K (Vendor Consignment) · Vendor: VEN-CONSIG
Post

FI effect: NONE. No expense, no liability. Stock visible only as "vendor consignment" in MMBE.

10.3. Consume consignment stock — mvt 201-K (consumption with K)

MIGO · Goods Issue · Mvt 201 · Special Stock K · Vendor VEN-CONSIG
Material HAWA-CEMENT-01 · Qty 500 BAG · Cost Center: any (e.g., PKKHI-MAINT)
Post

NOW liability is created:

Consumption (410000)	Dr 325,000 (500 × 650)	Cost Ctr
Vendor Consignment Liability (160100)	Cr 325,000	—

10.4. Periodic settlement — MRKO

Monthly: settle consigment liability into a normal vendor invoice for payment.

MRKO · Company Code PSPK · Vendor VEN-CONSIG · Plant PK01
Settlement Period (this month)
Execute → creates an invoice doc → vendor liability moves from "consignment" to "AP"

Pay normally via F-53/F110.

✅ Verify

MMBE → HAWA-CEMENT-01 → "Vendor Consignment" column shows 1500 BAG remaining
MB54 → Consignment Stock report → see vendor's stock at our plant

✅ Scenario 10 complete — Consignment with MRKO settlement

Pipeline Material — Natural Gas Continuous Flow

INTERMEDIATE ★★★☆☆ ⏱️ ~1 hour MM01 (UNBW pipeline) → MB1A (201-P) → MRKO

🇵🇰 Business Story

Sui Southern Gas Co. (SSGC) supplies natural gas to PakSteel Karachi via pipeline — no PO, no GR. PakSteel records consumption monthly based on meter reading. Settlement via MRKO. Same model: electricity (K-Electric), water (KWSB).

🎯 Pipeline essentials

Special Stock P — "pipeline" — no physical stock tracked
Material type often UNBW (non-valuated) with Procurement Type "Pipeline"
No PO needed — info record alone defines vendor + price
Direct consumption via mvt 201 with Special Stock P
MRKO settles consumption into invoice

📦 Master Data

11.1. Pipeline-enabled Material + Pipeline Info Record

MM01 · Material UTIL-GAS-01 · Type UNBW (or ROH with Procurement Indicator P)
Purchasing view: Set Procurement Type indicator if needed
ME11 · Vendor VEN-SSGC · Material UTIL-GAS-01 · Info Category: Pipeline
Price: PKR 50/m³
Save

🔄 Transaction Flow (no PO!)

11.2. Record consumption — MB1A mvt 201 Special Stock P

MB1A · Mvt 201 · Special Stock P
Material UTIL-GAS-01 · Qty 50,000 m³ (this month's reading) · Cost Center PKKHI-PROD
Vendor: VEN-SSGC · Post

Posting: Consumption Dr / Pipeline Liability Cr.

11.3. Monthly Settlement — MRKO

Same as consignment — MRKO converts pipeline liability to vendor invoice for payment.

✅ Scenario 11 complete — Pipeline material consumption + MRKO

Third-Party Drop-Ship — Vendor Ships Direct to Customer

ADVANCED ★★★★☆ ⏱️ ~2.5 hours VA01 (item TAS) → ME21N auto → MIRO → VF01

MM SD FI

⚙️ Prerequisite Setup Required

This scenario needs SD module configuration (Sales Org, item category TAS, basic customer master):

📖 If SD not yet set up: complete Setup Guide Step 16 (sub-steps 16A-16I) — focus on Sales Org + Customer Master parts
👥 Or: Ask your SD consultant to provide a customer master + sales area for testing
🪂 Alternative: Skip for now and revisit when SD setup is complete

🇵🇰 Business Story

PakSteel sells 200 TO of rebar to a builder customer, but doesn't have stock. Instead, they arrange for vendor Aisha Steel Mills to ship directly to the builder's site. PakSteel never touches the goods — they just earn the margin between vendor cost and customer price.

🎯 Third-party essentials

Trigger: SD Sales Order with Item Category TAS (Third Party)
PR auto-created from SO
PO has Account Assignment X (sales order) — stock never enters our books
Vendor ships directly to customer; PakSteel just verifies invoice + bills customer
MIGO is STATISTICAL (no real stock movement)
Goods Receipt indicator on PO may be unchecked (skip GR entirely)

🔄 Transaction Flow

12.1. Sales Order — VA01 with item category TAS

VA01 · Order Type OR · Sales Org / Distribution Channel / Division of PSPK
Customer: builder BP · Material FERT-REBAR-01 · Qty 200 TO
Item Category: TAS (Third-party — Order)
Save → SO #
Behind the scenes: SAP creates a PR (NB-style) for the third-party PO

12.2. Convert PR to PO — ME21N (or auto if release strategy disabled)

ME21N · pull in the auto-created PR
Account Assignment: X (Sales Order) — Item Cat S (Third-party)
Vendor: VEN-AISHA · Save

12.3. Statistical GR (optional) — MIGO

If GR indicator on PO is on: post statistical GR just to mark "vendor confirmed shipment to customer." No stock impact.

12.4. Vendor invoice — MIRO

Standard MIRO. Posts to a "Third-party COGS" G/L → Vendor Cr.

12.5. Customer Billing — VF01

Bill the customer based on the SO. Customer Dr / Revenue Cr. Margin = Revenue − Third-party COGS.

✅ Scenario 12 complete — Third-party drop-ship cycle

🟣 Tier 5: Process Controls

The "rules" layer real businesses add on top of P2P: approval workflows (release strategies), automatic source selection (source list + quota), and long-term outline agreements (contracts + scheduling agreements).

Release Strategy — PO Approval Workflow

ADVANCED ★★★★☆ ⏱️ ~3 hours CT04 → CL02 → OMGS → OMGSCK → ME21N → ME29N

🇵🇰 Business Story

PakSteel implements PO approval policy:

PO < PKR 500,000 → Buyer auto-approves
PO PKR 500,000 – 5,000,000 → Department Head must approve
PO > PKR 5,000,000 → Department Head + CFO must approve

Until approved, PO can't be sent to vendor or used for GR.

🎯 Release Strategy — the 5 building blocks

Characteristic (CT04): WHAT triggers the strategy — total value, doc type, plant, material group, purch group
Class (CL02): Groups characteristics under class type 032 (PO release) or 009 (PR release)
Release Group (OMGS): A code (e.g., 02) grouping strategies for similar docs
Release Codes (OMGS): The approvers (e.g., D1 = Dept Head, F1 = CFO)
Release Strategy (OMGS): Combines class + codes + dependencies (precondition, simultaneous)

⚙️ Config Steps (PO Release for value-based approval)

13.1. Create Characteristic — CT04

CT04 · Characteristic: CEKKO_GNETW (total PO net value) — use this existing characteristic OR copy to Z_PO_VALUE
If creating new: Data type CURR, length 15.2, Table CEKKO, Field GNETW
Values tab: define value ranges (e.g., 0 – 500,000; 500,001 – 5,000,000; etc.)
Save

13.2. Create Class — CL02

CL02 · Class: Z_PSPK_PO_REL · Class Type: 032 (Release strategy for PO)
Description: PakSteel PO Release Class
Characteristics tab: Add CEKKO_GNETW (or your Z_ char)
Save

13.3. Release Group + Codes — OMGS (for PO)

OMGS · Edit Release Groups · New Entry: Group 02, Class Z_PSPK_PO_REL · Description "PakSteel POs"
Edit Release Codes: D1 (Dept Head), F1 (CFO) — link to user role/agent via SAP user authorization
Edit Release Indicators: 1 = blocked, 2 = released
Save

13.4. Release Strategies — OMGS

OMGS · Release Strategies · New Entries:
- Strategy S1: Class Z_PSPK_PO_REL · Codes D1 only · Value 500K-5M
- Strategy S2: Codes D1 + F1 simultaneous · Value 5M+
For each: Click Classification → set the characteristic value ranges
For S2: Release Prerequisites → F1 needs D1 first (sequential)
Save

🔄 Test Flow

13.5. Create PO and see release block

ME21N · create PO totaling PKR 2,000,000 (in S1 range)
Save → PO has status "Blocked for release"
You can't print/transmit the PO yet

13.6. Release the PO — ME29N (or ME28 bulk)

Login as Dept Head user (assigned to release code D1)
ME29N · PO # → click Release
PO status changes to "Released"
Now visible in vendor's view, GR allowed, etc.

💡 Workflow integration

SAP Workflow (SBWP) notifies the approver email when their release is pending. Use SBWP Business Workplace to see pending approvals.

✅ Scenario 13 complete — Release strategy configured + tested

Source Management Mastery — Source List, Quota, Block, Time-Dependent (8 sub-scenarios)

DEEP DIVE ★★★★☆ ⏱️ ~3-4 hours total ME01 · ME0M · MEQ1 · MEQ3 · MEQ4 · OMQM · MD03

🇵🇰 Business Story — Multiple Real Scenarios

PakSteel sources iron ore from multiple Pakistani vendors with different policies over time:

Strategic sole-source: Mughal Steel is sole approved supplier for RM-IRON-01 (premium grade)
Dual sourcing: Mughal + Aisha Steel both approved for RM-COAL-01 (risk mitigation)
Quota split: 60% Mughal, 40% Aisha by volume (per long-term agreement)
Seasonal switch: Buy from Mughal till 30-Jun (winter contract), switch to Aisha from 1-Jul (summer)
Quality block: Mughal failed last QC — block them for 30 days, buy only from Aisha temporarily
MRP automation: Production triggers MD03 → PR auto-created with right vendor based on Source List

This scenario teaches ALL these patterns step-by-step.

🎯 The Source Determination Priority Chain

When SAP processes a PR or PO with "Source Determination" active, it checks sources in this exact order:

Priority	Source	T-Code	What triggers it
1️⃣	Quota Arrangement	MEQ1	Allocates by % between approved vendors
2️⃣	Source List (Fixed)	ME01	Single vendor flagged "Fix ✓"
3️⃣	Outline Agreement	ME31K (Contract) / ME31L (Sched. Agr.)	If referenced in source list
4️⃣	Info Record	ME11	If only one info record exists for material+plant
5️⃣	Fall back	Manual	User must enter vendor

📊 Two Database Tables Behind All This

Table	What it stores	Key fields
`EORD`	Source list entries (current state)	MATNR + WERKS + LIFNR + EKORG + VDATU/BDATU (validity) + AUTET (MRP rel) + NOTKZ (block) + AGREEMENT
`EORDH`	Source list change history (audit log)	Same as EORD + change timestamp + user
`EQUK / EQUP`	Quota arrangement header / items	MATNR + WERKS + LIFNR + QUOTA
`EBAN`	Purchase requisition items	FLIEF (Fixed Vendor) + EKORG (Purch Org) populated from source determination

📦 Sub-Scenario 14A — Activate Source List Requirement

14A. Make Source List MANDATORY for material — MM02

Why: When "Source List" flag is ON in Purchasing view, SAP rejects POs/PRs to vendors NOT in the source list. This enforces approved-vendor policy.

Action:

MM02 → Material RM-IRON-01
Select view: Purchasing → Plant PK01
Find checkbox "Source list" (MARC-KORDB) → ✓ tick it
Save → Local Object

💡 Alternative: Set as default for ALL materials via OMS2 or OMSK (Material Type config — "Source List Required" flag at material type level).

Verify: SE16N → table MARC → MATNR RM-IRON-01 → field KORDB should = X.

📦 Sub-Scenario 14B — Single Fixed Source (Strategic Sole-Sourcing)

14B. Mughal Steel as SOLE approved vendor for RM-IRON-01 — ME01

Business case: Premium-grade iron ore has only ONE approved vendor (Mughal Steel) — quality contract signed. No alternatives allowed.

Action:

ME01
Material: RM-IRON-01 · Plant: PK01 → Enter

Fill row in table:

Field	Value	Meaning
Valid From	Today	Start of approval
Valid To	`31.12.9999`	Open-ended
Vendor	`MUGHAL21`	Approved supplier
POrg	`PKLO`	Pakistan local purch org
Fix ✓	✓ (CHECK)	⭐ Marks as FIXED source — auto-picked in PR/PO
MRP	`1`	Relevant for MRP auto-PR creation
Block	blank	Not blocked

Save → ✅ "Source list maintained successfully"

Effect: When you create PR with "Source Determination" ✓, SAP auto-picks MUGHAL21 — no manual entry needed.

📦 Sub-Scenario 14C — Multiple Approved Sources (No Fixed)

14C. Mughal + Aisha both approved, buyer chooses — ME01

Business case: For commodity-grade iron ore, multiple vendors are approved. Buyer picks based on current price/availability. No vendor is "preferred" — risk mitigation.

Action:

ME01 · Material RM-IRON-01 · Plant PK01

Add 2 rows:

Vendor	POrg	Fix	MRP	Valid From-To
`MUGHAL21`	`PKLO`	☐ (NOT fixed)	1	Today → 31.12.9999
`AISHA22`	`PKLO`	☐ (NOT fixed)	1	Today → 31.12.9999

Save

Effect in PR: When you tick Source Determination → SAP shows popup "Multiple sources found — choose" → buyer picks Mughal OR Aisha manually. POs to ANY other vendor will be REJECTED.

Use case in PakSteel: Commodity-grade materials where price flexibility matters more than supplier loyalty.

📦 Sub-Scenario 14D — Time-Dependent Source Switching

14D. Mughal till 30-Jun, Aisha from 1-Jul — ME01

Business case: PakSteel signed 6-month contracts. Mughal's contract ends 30-Jun. Aisha's contract starts 1-Jul. SAP should automatically switch vendor based on requirement date.

Action:

ME01 · Material RM-IRON-01 · Plant PK01

Fill table:

Valid From	Valid To	Vendor	POrg	Fix	MRP
`01.01.2026`	`30.06.2026`	`MUGHAL21`	`PKLO`	✓	1
`01.07.2026`	`31.12.2026`	`AISHA22`	`PKLO`	✓	1

Save → both periods saved with different Fixed vendors

Effect:

PR created with delivery date 15-Jun-2026 → auto-picks MUGHAL21
PR created with delivery date 15-Aug-2026 → auto-picks AISHA22
No manual intervention — SAP reads the date and picks right vendor

Real Pakistani use: Pre-monsoon vs post-monsoon vendor contracts, fiscal-year-based vendor rotation, seasonal pricing.

📦 Sub-Scenario 14E — Block a Source Temporarily

14E. Mughal blocked for QC issue — buy only from Aisha — ME01

Business case: Last shipment from Mughal Steel failed quality inspection (sulfur content too high). Block Mughal as source for 30 days while they investigate. Aisha continues as alternate.

Action:

ME01 · Material RM-IRON-01 · Plant PK01
Find row for MUGHAL21
Find column "Blk" (Block) → click ✓ to tick
Save

Vendor	Fix	MRP	Blk	Status
`MUGHAL21`	☐	0	✓ Blocked	Can't be picked
`AISHA22`	✓	1	☐	Active — auto-picked

Effect: PRs auto-pick AISHA22. POs to MUGHAL21 will be rejected with error 06401 — Source not allowed.

Unblock after QC clears: Untick Blk → Save. Mughal active again.

💡 Pro tip: Block is INSTANT. Time-dependent block? Use Valid To = block date (better audit trail than Blk flag).

📦 Sub-Scenario 14F — Quota Arrangement (% Split)

14F. 60% Mughal + 40% Aisha by volume — MEQ1

Business case: Long-term contract says 60% of iron ore volume goes to Mughal, 40% to Aisha (vendor relationship management). SAP auto-allocates this split.

Step 1 — Activate Quota Usage on material:

MM02 → RM-IRON-01 → Purchasing view → Plant PK01

Find field "Quota arr. usage" (MARC-USEQU) → enter value:

Value	Meaning
`1`	Quota applies to PRs
`2`	Quota applies to POs
`3`	Quota applies to scheduling agreements
`4`	Quota applies to ALL (PR + PO + sched agr) ⭐ recommended

Save

Step 2 — Maintain Quota Arrangement (MEQ1):

MEQ1 · Material RM-IRON-01 · Plant PK01
Validity Start: Today · Validity End: 31.12.9999

Fill quota items table:

P (Proc Type)	S (Special Stock)	Vendor	Quota Allocated	Quota Base Qty	Maximum Quantity
`F` (External Proc)	blank	`MUGHAL21`	`60`	0 (auto)	0 (unlimited)
`F`	blank	`AISHA22`	`40`	0	0

Save

Step 3 — Test:

ME51N → PR for 100 TO iron ore
SAP creates ITEM 10 for 60 TO from Mughal · ITEM 20 for 40 TO from Aisha (auto-split)
OR if "Quota Base Qty" is set per item, splits by base unit

Monitor quota: MEQ3 shows used/remaining quota per vendor. Useful for reporting.

Re-balance quota: If Mughal is at 80% used and Aisha at 20%, SAP biases future PRs to Aisha until rebalanced.

📦 Sub-Scenario 14G — Manual PR with Source Determination

14G. ME51N with auto-vendor selection — ME51N

Setup pre-req: Sub-scenarios 14A + 14B (or 14C/14F) completed.

Action:

ME51N
At top: tick checkbox "Source Determination" ✓
Add item: Material RM-IRON-01 · Qty 50 TO · Plant PK01 · SL RAWM · Delivery Date
Press Enter → SAP runs source determination logic

Possible outcomes:

Source List state	Behavior
Only 1 fixed source	✅ Auto-fills Fixed Vendor + Purch Org + Info Record
Multiple sources (no Fixed)	Popup: "Choose vendor" — buyer selects
Quota active	Splits items per quota %
No source list entry	Error: "No source of supply found"

Save → ✅ PR created with auto-source

💡 To make Source Determination tick the default, set in Personal Setting button at top of ME51N → Default Settings tab.

📦 Sub-Scenario 14H — MRP-Driven Auto-PR with Source List

14H. MD03 single-material MRP run creates PR with auto-vendor — MD03

Business case: Production needs 200 TO of iron ore for next month. Stock is 50 TO. MRP runs nightly → detects shortage → creates PR automatically. Source List determines which vendor.

Pre-req: Source List entry MUST have MRP column = 1 (not just Fix flag).

Action:

Pre-req: Material RM-IRON-01 has MRP type set (MM02 → MRP 1 view → MRP Type PD for stochastic, VB for reorder point, etc.)
Run MD03 · Material RM-IRON-01 · Plant PK01 · Processing Key NETCH · Create PR 1 (Always create PR)
Press Enter → MRP runs in foreground
Result: PR auto-created for shortfall qty
Check PR via MD04 · Material RM-IRON-01 · Plant PK01
You'll see new PR with Fixed Vendor pre-filled from Source List

Important — MRP rules:

MRP only considers source list rows with MRP indicator = 1
If MULTIPLE rows have MRP=1 → MRP picks first by sort, OR splits per Quota
If NO rows have MRP=1 → MRP creates PR WITHOUT vendor (buyer must add manually later)
Fix flag is IGNORED by MRP — only MRP indicator matters!

📦 Sub-Scenario 14I — Source List + Outline Agreement Reference

14I. Source List points to existing Contract — ME31K + ME01

Business case: Mughal Steel and PakSteel signed a 12-month value contract MK-0001 for ₨50 crore worth of iron ore. All POs to Mughal should reference this contract (consume from agreement value).

Action:

First create contract: ME31K · Doc Type MK · Vendor MUGHAL21 · Purch Org PKLO · Item: RM-IRON-01, target qty 200 TO, net price 250000 PKR
Note Contract Number (e.g., 4600000123)
ME01 · RM-IRON-01 · Plant PK01
Edit Mughal row → fill "Agreement" column = 4600000123 · "Item" column = 10
Save

Effect: Future POs to Mughal auto-reference contract → quantities count against contract → invoice verification validates against contract terms.

🔍 Verification — Check via Tables

How to verify Source List + Quota in database

SE16N → Table EORD · Filter MATNR = RM-IRON-01 + WERKS = PK01

Check fields:

Field	Meaning
LIFNR	Vendor #
EKORG	Purch Org
VDATU / BDATU	Valid From / To
AUTET	MRP relevant (1 = yes)
NOTKZ	Block indicator (X = blocked)
FLIFN	Fixed source indicator (X = fixed)
EBELN / EBELP	Linked contract # / item

For Quota: SE16N → Table EQUK (header) + EQUP (items)

⚠️ Common Errors + Fixes

Source List troubleshooting reference

Error	Cause	Fix
06401 — Source not allowed	PO vendor not in source list, but Source List flag is ON	Add vendor to ME01 OR untick "Source List" flag in MM02
06405 — Source list entry has been blocked	Trying to use blocked vendor	Untick Block in ME01 OR use different vendor
06424 — No source of supply found	No valid source list entry for date	Check ME01 Valid From/To covers PR delivery date
06010 — Vendor not extended to Purch Org	Source list has vendor but BP/LFM1 not maintained for that POrg	BP → add Vendor (Purchasing) role for that Purch Org
Quota not splitting	Quota Usage in MM02 is blank or wrong value	MM02 → Quota Arr Usage = `4` for all docs
MRP not picking from source list	MRP indicator on source list row not set to `1`	ME01 → MRP column = `1` for the desired vendor

🎓 Interview-Ready Q&A

Q: Difference between Info Record and Source List?

A: Info Record (ME11) stores PRICE + conditions for a material-vendor-purchorg combination. Source List (ME01) stores APPROVED VENDORS list for a material-plant combination. Info Record answers "at what price?" — Source List answers "from whom can I buy?". You can have many Info Records (one per vendor) but only one Source List per material+plant.

Q: Difference between Fix flag and MRP indicator in Source List?

A: Fix flag = "This vendor is the preferred source for manual PR/PO creation." Only ONE vendor can be Fixed per period. MRP indicator = "Use this vendor when MRP auto-creates PRs." Multiple vendors can have MRP=1 (then MRP uses quota or picks first). Critically: Fix flag is IGNORED by MRP. Only MRP indicator matters for automation.

Q: How does SAP decide source priority?

A: Priority chain: (1) Quota Arrangement — if active, allocates by %. (2) Source List with Fix flag — single auto-pick vendor. (3) Outline Agreement referenced in source list — uses contract terms. (4) Info Record — if no source list, single info record can default the vendor. (5) Manual — buyer enters vendor. This chain is configured via SPRO → MM → Purchasing → Source Determination.

Q: How would you implement "approve only ISO-certified vendors" policy?

A: Three-layer approach: (1) Source List per material — only add ISO-certified vendors via ME01. (2) Activate "Source List Required" flag on materials in MM02 → blocks POs to non-listed vendors. (3) For audit: build Z-report joining EORD + LFA1 + custom ISO certificate fields. SAP standard alone enforces the source list rule. Additional governance via release strategy + workflow approval.

Q: Can you block a vendor for ALL materials at once?

A: Yes — three ways: (1) Block at vendor master level (BP → Status Blocked for purchasing or specific Purch Org) — affects ALL materials immediately. (2) Mass update Source List via ME0M (Mass Maintain Source Lists) — set Blk ✓ for all material rows of that vendor. (3) Time-bound: change Valid To = today in all source list entries via SE16N table update or LSMW. Method 1 (vendor block) is most common; method 2 lets you keep vendor active for some materials but block for others.

Q: What is ME0M and when to use it?

A: ME0M = Mass Maintenance of Source Lists. Lets you create/change source list entries for MULTIPLE materials at once. Use cases: (1) Onboarding new vendor across 50 materials. (2) Blocking a vendor across all materials they supply. (3) Extending validity dates after contract renewal. (4) Bulk-loading source lists during data migration. Saves hours vs material-by-material ME01.

Q: Can MRP create PR if Source List has no Fixed vendor?

A: Yes — MRP doesn't use Fix flag. MRP uses MRP indicator (= 1). If only one source list row has MRP=1, MRP picks that vendor. If multiple have MRP=1 AND Quota Arrangement active, MRP splits per quota. If multiple have MRP=1 but NO quota → MRP picks first valid row (alphabetical/numerical sort). If NO rows have MRP=1 → MRP creates PR without vendor (buyer must add manually after).

Q: How do you audit "who approved Mughal Steel as a vendor for iron ore?"

A: Source List has change history in table EORDH (Source List Change History). Query: SE16N → EORDH → Material RM-IRON-01 + Vendor MUGHAL21 → see all changes with user ID + timestamp. Combine with FK02 (vendor master) change docs for full audit trail. For real compliance, integrate with workflow approval (e.g., Vendor Onboarding Workflow) so additions to source list require manager approval before save.

🇵🇰 Pakistani Business Scenarios

💡 Real-world Pakistani applications

Steel mills: Mughal + Aisha + International Steels — quota by capacity (20/30/50%)
Cement industry: Lucky Cement (sole for export), DG Khan (local) — time-dependent split by month
Textile: NTC Mills (cotton), Gul Ahmed (yarn) — separated by material, both fixed
FMCG: Engro Foods + Nestlé Pakistan + FrieslandCampina Engro — quota with seasonal rebalancing
Banking IT: TPS + NIFT + 1LINK — service vendors with strict source list enforcement
Oil & Gas: Schlumberger + Halliburton + WeatherFord — international + local quota with security clearance

✅ Scenario 14 complete — All 9 sub-scenarios (Source List + Quota + Block + Time + MRP + Contract)

📚 Sources: Verified against SAP Learning — Maintaining Source Lists + SAP Learning — Controlling Source Determination with Source Lists + SAP Community — Source List Deep Dive + SAP Community — MRP vs Fixed flag.

Outline Agreements — Contracts & Scheduling Agreements

INTERMEDIATE ★★★☆☆ ⏱️ ~2 hours ME31K (contract) → ME21N (release order) · ME31L (sch agr) → ME38 (sch lines)

🇵🇰 Business Story

PakSteel signs a 1-year contract with Mughal Steel for 1000 TO at PKR 250,000/TO. Throughout the year, they release smaller POs (release orders) against the contract — 100 TO this month, 80 TO next, etc. Contract guarantees price + capacity. Alternative: Scheduling Agreement with delivery schedule built-in (less paperwork per shipment).

🎯 Contract vs Scheduling Agreement

Aspect	Contract (ME31K)	Scheduling Agreement (ME31L)
What it is	Long-term price/qty agreement	Long-term delivery schedule
Release Order needed?	Yes (ME21N referencing contract)	No — delivery schedule embeds releases
Document Type	MK (quantity) or WK (value)	LP (with release docs) or LPA (without)
Use when	Volume guarantee + flexible scheduling	JIT, predictable cadence

🔄 Contract Flow

15.1. Create Quantity Contract — ME31K

ME31K · Agreement Type MK (Quantity Contract) · Vendor MUGHAL21 (Mughal)
Header: Validity From-To · Purch Org PKLO · Purch Group RMT
Line: Material RM-IRON-01 · Target Qty 1000 TO · Net Price 250,000/TO · Plant PK01
Save → Contract # (e.g., 4600000010)

15.2. Create Release Order — ME21N referencing contract

ME21N · Doc Type NB · Vendor MUGHAL21
Document Overview ON → My Contracts → drag contract line
Qty 100 TO (release portion) · system auto-fills price + plant from contract
Save → Release PO # · Contract released qty updated (now 100/1000 consumed)

Track contract usage: ME33K → display contract → release qty visible.

🔄 Scheduling Agreement Flow

15.3. Create Scheduling Agreement — ME31L

ME31L · Agreement Type LP · Vendor
Header validity · Line: Material · Target Qty 1000 TO · Price · Plant
Save → SA # (e.g., 5500000010)

15.4. Add Delivery Schedule — ME38

ME38 · SA # · select line · Delivery Schedule tab
Add rows: Date 15-Jan, Qty 100 · Date 15-Feb, Qty 100 · etc.
Save

System treats each schedule line as a "release" — GR/IV done against the SA + schedule line directly.

✅ Scenario 15 complete — Contract + Scheduling Agreement

🟪 Tier 6: Master Data Features

Industry-specific master data depth: batch management (pharma, food, steel grades), split valuation (origin/quality based pricing), QM integration (inspection workflow).

Batch Management — Steel Grade & Heat Number Tracking

ADVANCED ★★★★☆ ⏱️ ~2.5 hours OMCD → MSC1N → MIGO (w/ batch) → MMBE

🇵🇰 Business Story

Iron ore quality varies by batch — different sulfur/phosphorus content per shipment. PakSteel must track each batch (called "Heat Number" in steel industry) for traceability. If a customer rebar fails QC, they trace it back to which iron ore batch was used. Same applies in pharma (shelf life), food (production date), chemicals (purity).

🎯 Batch Management essentials

Activate batch mgmt on material (MM02 Purchasing view → "Batch Management" ✓)
Choose Batch Level in OMCD: Plant / Material / Client-wide
Batch can have characteristics (purity %, expiry date, manufacture date) via classification
FEFO (First Expired First Out) or FIFO picking via batch determination
Every stock movement asks for batch number — mandatory once activated

⚙️ Config

16.1. Set Batch Level — OMCD

OMCD · Select Batch Level: Material (batch unique per material across all plants — most common)
Activate Batch Status Mgmt (optional)
Save (this is system-wide and can't easily change later — careful!)

16.2. Activate Batch on Material — MM02

MM02 · RM-IRON-01 · Purchasing view → "Batch Management" ✓
Plant Storage Data view: optionally configure auto batch numbering, batch determination
Save

16.3. Optional — Batch Class & Characteristics (CT04/CL02 class type 023)

Create characteristics like SULFUR_PCT, PHOSPHORUS_PCT, HEAT_NUMBER. Group into class type 023 (Batch). Assign class to material's classification view. Now batch master holds these values.

🔄 Transaction Flow

16.4. Create Batch Master — MSC1N

MSC1N · Material RM-IRON-01 · Batch: HEAT-2025-001 · Plant PK01
Description, Manufacture Date, Vendor, Country of Origin
Characteristics tab: enter Sulfur % = 0.05, Phosphorus % = 0.04, Heat # = HT001
Save

16.5. GR with batch — MIGO

MIGO · GR · PO #
Line item now has Batch field — mandatory. Enter HEAT-2025-001 (or new batch)
If new batch, SAP prompts to create on the fly
Post

Stock per batch: MMBE now shows quantity per batch + total.

16.6. Batch Determination at GI — auto-pick FEFO/FIFO

Configure batch determination strategy (CU50 / MMB) — sort key = Expiry Date ASC → SAP auto-picks oldest batch first when issuing.

✅ Verify

MSC3N → display batch master + characteristics
MMBE → expand RM-IRON-01 → see per-batch stock
SE16N → MCHB (batch stock) + MCHA (batch master) → rows visible

✅ Scenario 16 complete — Batch management active + tested

Split Valuation — Same Material, Different Prices by Origin

ADVANCED ★★★★☆ ⏱️ ~2 hours OMWC → MM01 (val type) → MIGO

🇵🇰 Business Story

PakSteel buys steel scrap from local sources (PKR 80,000/TO) and imported (PKR 120,000/TO). SAME material code, but DIFFERENT valuation per origin. Need separate inventory value tracking. Split valuation lets one material code hold multiple valuations.

🎯 Split Valuation concepts

Valuation Category (e.g., H for Origin) — what dimension you split on
Valuation Types (e.g., LOCAL, IMPORT, USED, NEW) — the specific buckets within category
Material master extended with all valuation types
Every PO + GR + GI must specify valuation type
MBEW table has multiple rows — one per valuation type

⚙️ Config

17.1. Activate Split Valuation Category — OMWC

OMWC · Activate Split Valuation globally
Define Valuation Category H (Origin) — usually delivered standard
Define Valuation Types under H: LOCAL, IMPORT
Assign Cat H to Valuation Areas (plants PK01/PK02/PK03)
Save

17.2. Extend Material with Valuation Types — MM01

MM01 · Material SCRAP-STEEL-01 · Material Type ROH
Accounting view → Valuation Category: H
Now create per valuation type:
- Valuation Type: LOCAL · Moving Price: 80,000 PKR/TO
- Valuation Type: IMPORT · Moving Price: 120,000 PKR/TO
Header level: an "average" price for reporting

🔄 Test

17.3. PO + GR with valuation type

ME21N · Material SCRAP-STEEL-01 · enter Valuation Type field = LOCAL · Price 80,000
GR mvt 101 · system posts to LOCAL bucket of MBEW
Stock now: LOCAL 100 TO @ 80K, IMPORT 0 TO
Repeat with valuation type IMPORT

✅ Scenario 17 complete — Split valuation by origin

QM Integration — GR into Inspection Stock + Usage Decision

ADVANCED ★★★★☆ ⏱️ ~2 hours QA32 → MIGO (101 → quality stock) → QA11 (usage)

MM QM FI

⚙️ Prerequisite Setup Required

This scenario needs QM module activated (inspection setup, sampling, certificates). If your IDES doesn't have QM:

QM activation is typically done by QM consultant — basic activation in SPRO → QM → Basic Settings → Activate QM in MM
Material master must have QM view with Inspection Type 01 (GR Inspection) active
🪂 Alternative: Skip this scenario if QM not available; works without QM via standard GR mvt 101 to unrestricted stock

🇵🇰 Business Story

PakSteel inspects incoming iron ore for sulfur content. GR doesn't directly post to unrestricted stock — instead it lands in quality inspection stock. QC team tests, then makes a usage decision: Accept (mvt 321 → unrestricted) or Reject (mvt 122 → return to vendor).

🎯 QM essentials

Activate QM view in material (MM02 → QM view → Inspection Setup: Type 01 GR Inspection)
GR with QM auto-creates Inspection Lot + stock moves to "Quality Inspection" status
Inspector enters results in QE51N / QA32
Usage Decision (QA11) — Accept → mvt 321 (Q→unrestricted); Reject → mvt 122 (return)
Material can't be used until usage decision made

⚙️ Setup (high level)

18.1. Activate QM Inspection on Material

MM02 · RM-IRON-01 · Inspection Setup view
Inspection Type: 01 (Goods Receipt for Purchase Order)
Active ✓ · 100% inspection · Save

🔄 Test

18.2. GR creates Inspection Lot — MIGO

MIGO · GR · mvt 101 · post
Material shows in "Quality Inspection" stock (not Unrestricted)
Inspection Lot # auto-created

18.3. Record Results — QE51N

Enter measurement values (sulfur %, density, etc.) against the inspection lot.

18.4. Usage Decision — QA11

QA11 · Inspection Lot #
Usage Decision: Accept → Qty to Unrestricted = 50 TO · save → mvt 321
OR: Reject → Qty to Blocked/Return = 50 TO → mvt 122 auto-posted

✅ Verify

MMBE → see "Quality Inspection" + "Unrestricted" + "Blocked" columns change as you decide
QA32 → list of open inspection lots

✅ Scenario 18 complete — QM inspection + usage decision

🔴 Tier 7: Customization — What Makes You a CONSULTANT

The end-user runs transactions. The CONSULTANT configures the system. This tier is what real clients pay you for: custom material types for industry-specific items, custom document types for different process flows, custom pricing procedures, and output determination.

Custom Material Type — Halal-Certified Materials

EXPERT ★★★★★ ⏱️ ~2 hours OMS2 → OMSK → SNRO → MM01

🇵🇰 Business Story

PakSteel food-grade subsidiary needs to track Halal-certified materials separately from non-halal — for regulatory + religious compliance. Standard ROH/HALB/FERT don't capture this. Solution: create ZHAL (Halal-certified) material type that auto-blocks non-halal valuation classes, has its own number range, and unique field selection.

🎯 What "Custom Material Type" controls

Field selection — which fields are mandatory/optional/hidden for this material type
Valuation classes allowed — which OBYC G/L accounts get hit
Number range — separate numbering pool (e.g., HAL-xxxxxxx vs MAT-xxxxxxx)
Stock-keeping — is it stockable? Valuated?
Quantity / Value updating per plant or globally
Authorization group — who can create

⚙️ Config Steps

19.1. Copy standard ROH to ZHAL — OMS2

OMS2 · select ROH · Copy As → new type ZHAL
Description: Halal-Certified Raw Material
External Purchase Orders: + (allowed)
Internal Purchase Orders: +
Field selection group: 41 (or copy from ROH)
Authorization group: Z_HALAL
Number range group: ZH (define separately in next step)
Save

19.2. Assign Valuation Classes — OMSK

OMSK · Material Type ZHAL · allowed Valuation Classes
Add: 3050 (Halal Raw Materials) — a new valuation class
Save
Also configure OBYC for VKL 3050 if not already done

19.3. Define Number Range — SNRO Object MATERIALNR

SNRO · MATERIALNR · Number Ranges
Add Interval: ZH · From: HAL0000001 · To: HAL9999999 · External Y/N
OMS2 → ZHAL → link Number Range Group ZH
Save

🔄 Test

19.4. Create material with ZHAL — MM01

MM01 · Material: (blank, auto-assigned) · Industry M · Material Type ZHAL
System assigns HAL0000001
Fill views; Accounting → Valuation Class ONLY 3050 allowed (others blocked) ✓
Save

✅ Scenario 19 complete — Custom material type ZHAL working

Custom PO Document Type — Imports vs Local

EXPERT ★★★★★ ⏱️ ~2 hours OMEC → OMEB → SNRO (object EBELN)

🇵🇰 Business Story

PakSteel wants separate document types for Local POs (ZLOC) and Import POs (ZIMP). Reasons:

Different number ranges (Z-local 1xxxx, Z-import 9xxxx) for reporting
Import POs need additional fields (incoterms, port, BL #) mandatory
Different release strategies (import POs always need CFO approval)
Custom output forms (import has customs paperwork)

🎯 What "Custom Document Type" controls

Number range — separate pool per doc type
Allowed item categories (blank, K, L, S, etc.)
Field selection — mandatory/optional fields per doc type
Print/Output settings — different SmartForms per doc type
Release Strategy linkage — different approval per type
Authorization — who can create which doc type

⚙️ Config Steps

20.1. Define Document Type — OMEC (or SPRO path)

SPRO → MM → Purchasing → Purchase Order → Define Document Types
Copy NB → ZIMP (Import PO) · Description: PakSteel Import PO
Number Range Internal: ZI (define in next step)
Update group: leave standard
Field selection key: ZIMP (create separately if custom fields needed)
Allowed item categories: blank only (no subcon for imports)
Save

Repeat: copy NB → ZLOC.

20.2. Number Range — SNRO Object EBELN

SNRO · Object EBELN · Number Ranges
Add interval ZI: From 9000000000 to 9999999999 (imports)
Add interval ZL: From 1000000000 to 1999999999 (locals)
Link in OMEC: ZIMP → ZI, ZLOC → ZL

20.3. Field Selection — OMEB (for custom mandatory fields)

Define field selection key ZIMP with INCOTERMS, Country of Origin, LC Number, etc. as Required input.

🔄 Test

20.4. Create PO with ZIMP — ME21N

ME21N · Doc Type = ZIMP
Notice: Number from ZI range (e.g., 9000000001)
If field selection set, Incoterms/Port required to save

✅ Scenario 20 complete — Custom doc types ZIMP & ZLOC

Pricing Procedure — Custom Conditions (Discount, Freight, Tax)

EXPERT ★★★★★ ⏱️ ~3 hours M/06 (cond types) → M/08 (proc) → OMFO (schema determination)

🇵🇰 Business Story

PakSteel's PO price is rarely just "Gross Price". Real example:

Gross Price (PB00)	+ 250,000
Vendor Discount 3% (RA00)	− 7,500
Freight 2% (FRA1)	+ 4,850
Customs Duty 5% (custom Z_CUST)	+ 12,367 (planned)
17% Sales Tax (MWST)	+ 43,930
Effective Price/TO	303,647

Pricing Procedure orchestrates all these condition types.

🎯 Pricing Procedure essentials

Condition Types (M/06): each rule — PB00 gross, RA00 discount %, MWST tax, FRA1 freight
Access Sequence (M/07): WHERE SAP looks for price (info record, contract, manual)
Pricing Procedure (M/08): ORDERED list of condition types — what gets added/subtracted in what sequence
Schema Determination (OMFO): which procedure is used for which purch org schema group + vendor schema group

⚙️ Config Steps (focus: add custom condition Z_CUST for customs duty)

21.1. Create Condition Type Z_CUST — M/06

M/06 · Copy FRA1 → Z_CUST
Description: Customs Duty %
Condition Class: A (Discount/Surcharge) · Calculation Type: A (%) · Plus/Minus: A (positive)
Access Seq: (assign one if records via info record), or "Manual entry only"
Save

21.2. Add Z_CUST to Pricing Procedure — M/08

M/08 · Open standard procedure RM0000 (or copy to Z_PSPK) · Details
Add step (e.g., Step 35, Counter 10): Condition Type Z_CUST · From-To referencing subtotal where customs applies
Save

21.3. Procedure Determination — OMFO (Schema Determination) + supporting T-codes

Pricing procedure determination involves 4 related T-codes (all under SPRO → MM → Purchasing → Conditions → Define Price Determination Process → Define Schema Group / Schema Determination):

T-code	What it does
OMFN	Define Schema Group for Vendor
OMFM	Define Schema Group for Purchasing Organization
OMFP	Assign Schema Group to Purchasing Organization
OMFO	Schema Determination — combine Vendor Schema Group + Purch Org Schema Group → Pricing Procedure

Action:

Run OMFO
New Entries → combine Schema Group of Purch Org (PKLO's schema grp) + Schema Group of Vendor (PSPK Imports' schema grp) → Procedure Z_PSPK
Save

⚠️ Note: M/03 is for Access Sequences (sequences SAP follows to find a price), NOT for procedure determination. The earlier reference to M/03 here was incorrect; OMFO is the verified T-code for schema determination.

🔄 Test

21.4. Create PO + see new condition

ME21N → import vendor → line item conditions tab now shows Z_CUST as a row. Enter % → recalc updates total.

✅ Scenario 21 complete — Custom condition added to pricing procedure

Output Determination — Print/Email PO Form

INTERMEDIATE ★★★☆☆ ⏱️ ~2 hours NACE → MN04 (condition records) → ME9F

🇵🇰 Business Story

When a PO is created/changed, PakSteel needs to:

Print a hardcopy for vendor (signed + stamped, Pakistani business norm)
Email PDF to vendor's procurement contact
Send fax (some legacy vendors still use this)
For internal: post to a shared printer at procurement desk

Output Determination = SAP's framework for routing PO docs to printers/email/fax/EDI.

🎯 Output Determination essentials

Output Types (NACE): NEU (New PO print), MAHN (reminder), etc. Each = an output trigger
Access Sequence: where SAP looks for output condition records
Condition Records (MN04): per Purch Org + Vendor + Doc Type → "use medium 1 (printer)" or "5 (email)"
Procedure: ordered list of output types applicable to doc
Smart Form / Adobe Form: the actual PDF layout (developed in SE71 / SFP)

⚙️ Config Steps

22.1. Output Type Setup — NACE Application EF (Purchasing)

NACE · Application EF · Output Types
Default type NEU exists — review settings (Medium 1 = Print, 5 = Email/EDI)
Optional: copy to Z_NEU for custom logic

22.2. Maintain Condition Records — MN04

MN04 · Output Type NEU
Key combination: Doc Type + Purch Org + Vendor
Add row: NB · PKLO · MUGHAL21 → Medium 5 (Email) · Vendor's email · Time 3 (immediate)
Save

22.3. Process Output — ME9F

ME9F runs to dispatch pending output. Real systems run this as background job hourly.

✅ Scenario 22 complete — Output determination + email PO to vendor

🇵🇰 Tier 8: Pakistani Context — Local Fiscal Compliance

Two scenarios specific to Pakistan that you'll always encounter on PK projects: import procurement with Letter of Credit + customs, and Withholding Tax (WHT) on vendor payments per FBR rules.

Import Procurement — Foreign Vendor + LC + Customs

EXPERT ★★★★★ ⏱️ ~3 hours ME21N (ZIMP) → MIRO (planned delivery costs) → MIRO (customs)

🇵🇰 Business Story

PakSteel imports 100 TO of coking coal from Shanghai Steel Trade Co. (China). Invoice value: USD 50,000 = PKR 14,000,000 @ 280:1. Additional costs flow in:

Sea freight (Karachi port): USD 3,000
Marine insurance: 1.5% of CIF
Customs Duty: 5% on assessed value
Sales Tax: 17% on CIF + Customs
Letter of Credit (LC) opened via Habib Bank Ltd. as payment instrument

All costs must be capitalized into the inventory value of coal (not expensed). This is what makes imports complex.

🎯 Import Procurement essentials

Use Planned Delivery Costs on PO — freight, customs, insurance enter PO line so they capitalize at GR
Multiple currencies — vendor invoice in USD, books in PKR (exchange rate at PO date vs invoice date can differ → variance)
Multiple invoices per PO — main vendor (goods), customs broker (duty), forwarder (freight), insurance company
Each cost has its own G/L account but all roll up to inventory value at GR
LC is FI/Treasury domain — MM just records the PO terms (Incoterms FOB/CIF/DDP)

⚙️ Config Prerequisites

Foreign vendor BP created (VEN-IMPCH) with currency USD, country CN
Condition types defined for Freight (FRA1), Customs (Z_CUST from Sc 21), Insurance (INS1)
Pricing procedure includes these conditions
Exchange rates maintained — OB08 rate type M for USD ↔ PKR
OBYC entries for FRE (freight clearing), customs clearing G/L

🔄 Transaction Flow

23.1. Create Import PO — ME21N with planned delivery costs

ME21N · Doc Type ZIMP (or NB) · Vendor VEN-IMPCH
Header → Currency = USD · Exchange Rate: from OB08 (auto)
Header → Incoterms: CIF (Cost Insurance Freight) · Karachi Port
Line: Material RM-COAL-01 · Qty 100 TO · Net Price USD 500/TO · Plant PK01
Click line → Conditions tab:
- FRA1 (Freight): USD 30/TO planned
- INS1 (Insurance): 1.5% on goods+freight
- Z_CUST (Customs): 5% on CIF
For each delivery cost: enter Vendor of Freight Forwarder, Customs Broker, Insurance Co (these are separate vendors!)
Save

SAP commits planned costs — they'll capitalize at GR.

23.2. GR — capitalizes goods + planned costs

At GR, SAP capitalizes:

Inventory RM-COAL (300100)	Dr PKR 16,800,000	(goods + freight + insurance + customs all included)
GR/IR (191100) - Main	Cr 14,000,000	Main vendor
Freight Clearing (191500)	Cr 840,000	Forwarder
Insurance Clearing (191600)	Cr 252,000	Insurance Co
Customs Clearing (191700)	Cr 1,708,000	Customs broker

All 4 vendors will invoice separately — each MIRO clears its own GR/IR.

23.3. Goods Invoice — MIRO in USD

MIRO · Vendor VEN-IMPCH · Currency USD · Amount 50,000
SAP translates to PKR at invoice date exchange rate
If rate differs from PO/GR rate → posts variance to "Exchange Rate Difference" G/L

23.4. Planned Delivery Cost Invoices — MIRO (3 more)

MIRO → Transaction = "Planned Delivery Costs" (instead of Invoice)
Reference original PO · select freight forwarder vendor · enter freight invoice amount
Repeat for customs broker, insurance
Each clears its own delivery cost GR/IR

23.5. LC Settlement (FI side — outside MM)

FI consultant handles: Open LC against bank, debit margin from vendor, eventual payment via bank → vendor account cleared.

💡 Pakistani import specifics

FBR Customs General Order rates change annually — keep customs duty % updated in OB08 / condition records
Sales tax on imports @ 17% (or current FBR rate) charged at port; recoverable as input tax
WeBOC integration optional (Web-Based One Customs system) — some Pakistani implementations integrate via IDoc
GIDC (Gas Infrastructure Development Cess) applies to some imports

✅ Scenario 23 complete — Import procurement with multi-currency + planned costs

Withholding Tax — FBR Section 153 on Vendor Payments

ADVANCED ★★★★☆ ⏱️ ~1.5 hours FBKP → FK02 (WHT tab) → F-53 (auto-deducts)

🇵🇰 Business Story

Pakistani tax law (FBR Income Tax Ordinance Section 153) requires PakSteel to deduct income tax at source when paying vendors:

Goods: 4.5% for filers, 9% for non-filers
Services: 8% for filers, 16% for non-filers
Construction contracts: 7.5%/15%

When paying Mughal Steel PKR 1,000,000 (goods, filer), PakSteel pays only PKR 955,000 and remits PKR 45,000 to FBR on vendor's behalf. SAP must auto-calculate and post both legs.

🎯 Withholding Tax in SAP — two flavors

Classic WHT: Calculated at payment time only (F-53/F110). Older method.
Extended WHT (recommended): Calculated at invoice posting AND optionally at payment. Modern flexibility — what Pakistani implementations use.
SAP S/4 fully supports both; Extended is the default.

⚙️ Config Steps

24.1. Activate Extended WHT — FBKP / SPRO

SPRO → FI → FA Global Settings → Withholding Tax → Extended WHT
Define WHT Country: PK
Activate Extended WHT for CC PSPK

24.2. Define WHT Types & Codes

Define WHT Type: P1 (Pakistan Goods - Filer) · Country PK · Calc at Invoice
Define WHT Code: under P1 → Code 153G · Rate 4.5%
Repeat for:
- P2 / 153G-NF · 9% (Goods non-filer)
- P3 / 153S · 8% (Services filer)
- P4 / 153S-NF · 16% (Services non-filer)
Save

24.3. Assign WHT to Company Code

Assign WHT Types P1-P4 to CC PSPK with validity period.

24.4. Assign WHT G/L Accounts

WHT Payable to FBR Liability G/L: 160500 (or your CoA equivalent). Cleared monthly when remitting to FBR via challan.

24.5. Assign WHT to Vendor Master — FK02 or BP

BP / FK02 · Vendor MUGHAL21 (Mughal Steel — filer) · CC PSPK
Withholding Tax tab: Add WHT Type P1, Code 153G, Liable ✓
Save
For non-filer vendors, assign P2/153G-NF instead

🔄 Test

24.6. Post Invoice → WHT auto-calculated

MIRO · vendor MUGHAL21 · amount PKR 1,000,000 (Goods)
Withholding Tax tab shows: Base 1,000,000 · WHT 45,000 (4.5%)
Post

Accounting:

Inventory / GR/IR Dr	1,000,000
Vendor Cr	955,000
WHT Payable to FBR (160500) Cr	45,000

24.7. Pay Vendor — only Net 955,000 — F-53

F-53 selects vendor open item 955,000 (already net of WHT). Bank Cr 955,000.

24.8. Monthly WHT Remittance to FBR — manual JV

Manual FI posting (F-02): WHT Payable Dr / Bank Cr → clears WHT liability after challan deposit at NBP.

✅ Scenario 24 complete — WHT auto-deducted per FBR rules

🔗 Tier 9: MM Cross-Module Integration

Scenarios where MM intentionally hands off to OTHER SAP modules — Plant Maintenance (PM) for spare parts, Project System (PS) for capex projects. These show MM's role as a central enabler across the SAP suite.

MM ↔ PM Integration — Spare Parts for Maintenance Orders

ADVANCED ★★★★☆ ⏱️ ~2 hours IW31 → ME21N (acct F) → MIGO → IW32 (confirm)

MM PM FI CO

🇵🇰 Business Story

The Karachi Factory (PK01) has a critical CNC machine failure. Maintenance team creates a Maintenance Order (IW31) requesting a new bearing. The order generates a PR with account assignment F (Internal Order) — meaning the cost goes to the maintenance work order, not directly to a cost center. After repair, the maintenance order is settled to the affected production line cost center.

⚙️ Prerequisite Setup

This scenario needs PM module activated. If PM isn't set up in your IDES, you can:

Skip this scenario (PM is typically PM consultant work, not MM)
OR work with PM consultant to enable basic PM (work order types, notification types)
OR substitute with cost center accounting (Scenario 5 — Consumable Direct) — same MM mechanics, simpler account assignment

🎯 What this teaches

Account assignment F (Internal Order / PM Order) on PO line
PR triggered FROM PM module (not manually) — MRP-like external integration
Cost accumulation on maintenance order, then settled at month-end
Material Master ERSA type for spare parts
How MM consultant supports PM consultant in real projects

🔄 Transaction Flow

25.1. PM Maintenance Order — IW31

PM consultant / maintenance planner creates a maintenance order:

IW31 · Order Type: PM01 · Technical Object: CNC-PK01-MIL01 · Plant: PK01
Operations tab: Repair sequence
Components tab: Required spare part SP-BEARING-01, Qty 1 EA
Save → Maintenance Order # (e.g., 8000001234)
This auto-creates PR if component not in stock + Procurement Type external

MM consultant's role: Ensure spare part material master is created (MM01 ERSA) with Purchasing view + valuation class.

25.2. Convert PR to PO — ME21N with account assignment F

ME21N · pull in auto-created PR
Verify Account Assignment: F (Internal Order)
Order field shows the PM order # (8000001234)
G/L auto-determined (e.g., 410100 Maintenance Material Expense)
Save

Posting at GR: Material Cost Dr / GR-IR Cr — cost tagged to PM order, not cost center directly.

25.3. Goods Receipt — MIGO mvt 101

Standard GR. Cost flows to PM order via account assignment F.

Maintenance Expense (410100)	Dr 5,000	PM Order: 8000001234
GR/IR (191100)	Cr 5,000	—

25.4. Settle PM Order to Cost Center — KO88 (end of month)

PM/CO consultant runs KO88 to settle the maintenance order's accumulated cost to the receiver (cost center PKKHI-PROD).

KO88 · Order: 8000001234 · Settlement period
Settlement rule: 100% to cost center PKKHI-PROD
Execute → cost moves from order to cost center

💡 MM consultant's role in PM integration

You don't configure PM, but you DO:

Create spare part material masters (ERSA type, ITAS prevention via Source List, alternative vendors)
Maintain reorder points and safety stocks for critical spares
Set up procurement type "F" (external) on spare materials
Handle GR/IV for spare parts purchased via PM orders
Coordinate with PM team on consignment/safety stock arrangements

✅ Scenario 25 complete — MM-PM integration via maintenance order

MM ↔ PS Integration — Project-Based Procurement (WBS)

EXPERT ★★★★★ ⏱️ ~2.5 hours CJ20N (project) → ME21N (acct P) → MIGO → CJ88 (settle)

MM PS FI CO AM

🇵🇰 Business Story

PakSteel is building a new galvanizing plant extension at Karachi — a 6-month, PKR 50,000,000 capex project. PS module tracks the project via WBS (Work Breakdown Structure) elements. Each procurement (steel beams, electrical equipment, concrete) is tagged to a specific WBS element. At project completion, all costs settle to a fixed asset (Asset Under Construction → Final Asset).

⚙️ Prerequisite Setup

This scenario needs PS module + FI-AA (Asset Accounting) activated. Options:

Skip this scenario (PS is specialized — many companies don't use it)
Substitute with Scenario 6 (Asset Procurement direct, account assignment A) — simpler, similar MM mechanics
OR work with PS consultant to create a basic project + WBS for testing

What you need from PS team: Project definition + at least 1 WBS element (e.g., GALVAN-PRJ-001 with WBS GALV-001-CONST)

🎯 What this teaches

Account assignment P (Project / WBS) on PO line
WBS-based cost accumulation (different from cost center)
Asset Under Construction (AuC) handling for capex projects
Multi-step settlement: WBS → AuC → Final Asset
How MM enables long-running capex projects in SAP

🔄 Transaction Flow

26.1. PS Project + WBS — CJ20N

PS consultant creates the project structure (typically before MM gets involved):

CJ20N · Project Definition: GALVAN-PRJ-001 "Galvanizing Plant Extension"
WBS elements (project breakdown):
- GALV-001-CONST: Construction phase
- GALV-001-EQUIP: Equipment phase
- GALV-001-INST: Installation phase
Each WBS has cost element, account assignment, settlement rule (to AuC asset)
Save and release the project

26.2. Create PO with WBS Account Assignment — ME21N with acct P

ME21N · Vendor: Pak Steel Structures (or any vendor)
Line: Material "Structural Steel Beam I-200" · Qty 100 TO · Net Price 80,000 PKR/TO
Account Assignment Category: P (Project)
Account Assignment tab → WBS Element: GALV-001-CONST
G/L auto-determined for project consumables
Save → PO #

Result: When GR happens, cost goes to WBS GALV-001-CONST, not a cost center.

26.3. GR + MIRO — Standard, but cost tags to WBS

Same as regular P2P, just the cost accumulates on the WBS element.

Project Construction Expense (4500xx)	Dr 8,000,000	WBS: GALV-001-CONST
GR/IR (191100)	Cr 8,000,000	—

26.4. Settle WBS → Asset Under Construction (AuC) — CJ88

Periodically (monthly during project), PS/CO consultant settles WBS cost to AuC.

At project completion, AuC settles to final operational asset via AIBU.

💡 MM consultant's role in PS integration

You don't configure PS, but you DO:

Configure your PO doc types to ALLOW account assignment P
Create custom PO doc type for capex projects (ZCAP) — see Scenario 20
Ensure release strategy triggers Director/Board approval for PS-tagged POs
Coordinate with PS team on planned vs actual procurement timelines
Handle change orders to project-specific contracts

✅ Scenario 26 complete — MM-PS integration via WBS procurement

📚 Reference Tables

Quick-lookup tables you'll come back to throughout your MM career. Bookmark this section.

🎯 Movement Types — what each does

Mvt	What	Stock Effect	FI Effect
101	GR for PO (warehouse)	Unrestricted ↑	Inv Dr / GR/IR Cr
102	Reverse 101	Unrestricted ↓	Reverse 101
103	GR to Blocked Stock	Blocked ↑	Inv Dr (blocked) / GR/IR Cr
105	Release Blocked to Unrestricted	Block ↓, Unrestricted ↑	None
122	Return delivery to vendor	Unrestricted ↓	Reverse of 101
123	Reverse return (102 + 122)	Unrestricted ↑	Reverse 122
161	Return PO Goods Issue	Unrestricted ↓	Like 122 + PO link
201	GI to Cost Center	Unrestricted ↓	Consumption Dr / Inv Cr
202	Reverse 201	Unrestricted ↑	Reverse 201
261	GI to Production Order	Unrestricted ↓	WIP Dr / Inv Cr
262	Reverse 261	Unrestricted ↑	Reverse
301	Plant-to-Plant transfer 1-step	From ↓, To ↑	FI if cross-CC
303 / 305	Plant-to-Plant 2-step (issue / receipt)	Transit	FI if cross-CC
309	Material-to-Material reclass	One ↓, Other ↑	BSX both
311	SLoc-to-SLoc transfer (same plant)	SLoc shift	None
321	Quality Stock → Unrestricted	Q ↓, U ↑	None
322	Reverse 321	U ↓, Q ↑	None
350	Block stock from unrestricted	U ↓, Block ↑	None
351	GI for STO (one-step at issue)	From ↓, To Transit	None if same val area
501	Receipt w/o PO (free goods)	U ↑	Inv Dr / Other Income Cr
541	Components to subcontractor	U ↓, Provided ↑	None
543	Subcontractor consumes components	Provided ↓	Consumption Dr / Provided Cr
561	Opening balance entry	U ↑	Inv Dr / Opening Cr
641 / 645 / 647	STO movements (issue, intercompany, one-step)	Plant-to-plant	Varies by config
701 / 702	Physical inventory variance	Surplus / Shortage	Inv Dr/Cr / Gain-Loss

📄 Document Types — Standard PO & PR Types

Doc Type	Used For	Doc Category
`NB`	Standard PO (most common)	F (Purchase Order)
`UB`	Stock Transport Order (intra-company)	F
`FO`	Framework Order / Service-heavy POs	F
`RV`	Outline Agreement Release	F
`MK`	Quantity Contract (Outline Agreement)	K
`WK`	Value Contract	K
`LP`	Scheduling Agreement (with release docs)	L
`LPA`	Scheduling Agreement (without release docs)	L
`NB (PR)`	Standard Purchase Requisition	B
`RV (PR)`	Subcontracting PR (auto from production)	B
`KR / KG`	FI Vendor Invoice / Credit Memo (auto from MIRO)	—
`WE`	FI doc for Goods Receipt (auto from MIGO)	—
`WA`	FI doc for Goods Issue (auto from MIGO)	—

🔑 OBYC Transaction Keys — what each does

Key	What it determines	Mvt that triggers it
`BSX`	Inventory Posting (Material's stock G/L)	101 (GR), 309 (reclass), most posting movements
`WRX`	GR/IR Clearing (for PO-based GR)	101, 102
`FRE`	Freight Clearing (for delivery costs)	101 with freight conditions
`GBB`	Offsetting entry for stock posting (consumption, scrap, etc.)	201, 261, 561, 309, etc. — needs sub-key
`GBB → VBR`	Consumption (most common GBB)	201, 261
`GBB → BSA`	Initial stock entry	561
`GBB → ZOB`	Receipt without PO	501
`GBB → AUF`	GI for Order	261 (some configs)
`GBB → INV`	Inventory differences (physical count)	701, 702
`GBB → UMB`	Stock transfer (revaluation)	309, plant-to-plant if val diff
`PRD`	Price Differences (when V vs S, or invoice vs PO)	MIRO with variance
`UMB`	Revaluation / Gain-loss	Plant-to-plant transfer if val diff
`KDM`	Exchange Rate Difference (foreign curr POs)	MIRO when rates differ

🚨 Top 15 Errors and Fixes

Error	Cause	Fix
"Account determination for entry INT BSX VKL 3000 not possible"	OBYC missing	OBYC → BSX → add VKL 3000 → G/L 300000
"Posting period MM YYYY is not open"	OB52	OB52 → open current period for variant
"Document number not in range"	FBN1 missing	FBN1 → CC → create range
"No field status variant assigned"	OBY6	OBY6 → CC → fill FSV
"G/L account XXXX not created in CC"	FS00 → not extended	FS00 → extend to your CC
"Cost center XX does not exist"	KS01 missing or validity	KS03 → check; KS01 to create
"Tax code V1 does not exist in CC"	FTXP missing	FTXP → create tax code with %
"Source list missing"	Material has SL Required flag but no SL entries	ME01 → maintain SL OR remove flag via MM02
"Net price 0.00"	No info record / contract	ME11 → create info record OR enter manually
"Material doesn't exist in plant XX"	Plant view not extended	MM01 / MM50 → extend material to plant
"Balance not zero" (MIRO)	Qty or price mismatch	Verify qty vs GR + price vs PO
"Item category L not allowed for doc type NB"	OMG0 link	OMG0 → allow L for NB
"Valuation class XXXX not allowed for material type"	OMSK	OMSK → add allowed VKL
"Movement type XXX not allowed"	OMJJ assignment	OMJJ → enable mvt for material type
"PO not yet released"	Release strategy active	ME29N → release; or check approver

🎓 Key Tables Cheat Sheet

Table	What it stores
`MARA`	Material Master — general (client-level)
`MARC`	Material per Plant
`MBEW`	Material Valuation (per plant + valuation type)
`MARD`	Material Stock per SLoc
`MCHA`	Batch master
`MCHB`	Batch stock
`LFA1 / LFB1 / LFM1`	Vendor General / CC / Purch Org (deprecated by BP but still populated)
`BUT000`	BP General data
`EBAN`	PR header + items
`EKKO / EKPO`	PO header / items
`EKET`	PO delivery schedule
`EKBE`	PO history (GR + IV transactions)
`EINA / EINE`	Info record general / org-specific
`MKPF / MSEG`	Material doc header / items
`BKPF / BSEG`	FI doc header / items
`RBKP / RSEG`	Invoice header / items
`T001 / T001W / T001L / T001K`	CC / Plant / SLoc / Valuation Area
`T024 / T024E / T024W`	Purch Group / Purch Org / Plant assignment
`T030`	OBYC entries (account determination)
`T156`	Movement types
`NRIV`	Number range intervals
`TKA01 / CSKS`	CO Area / Cost Centers

🎉 You've completed the P2P journey — what's next?

Finishing all 24 scenarios = you've touched 95% of what an MM functional consultant does on real projects. Here's where to go from here:

🎯 Interview prep

Practice 30-60 second answers for each scenario. Use the "Interview-ready" boxes in Scenario 1 as a template. Common interview topics: P2P walk-through, release strategy, subcontracting, OBYC, batch mgmt, account assignment categories.

📚 Deepen specific topics

Check our Advanced Topics page for dedicated deep-dives on Batch Management, Release Strategies, and Subcontracting beyond what's in this scenarios guide.

🛠️ Real project simulation

Use Interactive Workflow to walk through a complete P2P state-tracked end-to-end. State persists in localStorage so you can pause and resume.

🔧 Configure your IDES

Reference back to Setup Guide as you build each scenario's config in IDES. Build muscle memory for the IMG paths.

P2P Cycle — 26 Real-World Scenarios (with Cross-Module Integration)

🎯 Why 26 scenarios (and not just one P2P walkthrough)?

🧭 How to use this page

🔗 MM doesn't live alone — Cross-Module Integration

🏷️ Module tags used throughout scenarios

📚 How prerequisite setup works in this guide

📋 The 26 scenarios at a glance

📊 Coverage analysis — what 26 scenarios give you

🎯 Module activation cheat sheet — when to ask Basis to activate

✅ Prerequisites — config you need before scenario 1

📦 Master Data Baseline — what we'll create & reuse

Materials (9 cover 90% of MM scenarios)

Vendors (Pakistani context — Business Partners)

⚙️ Controlling (CO) — needed from Scenario 4 onwards

🎯 Why an MM consultant must know CO basics (even if FI/CO configures it)

💡 Account Assignment Categories in MM (memorize these)

🟢 Tier 1: Foundation — start here

Stock Procurement — The Basic P2P Cycle

🇵🇰 Business Story

🎯 What you'll learn in this scenario

📋 Prerequisites

⚙️ New config needed for this scenario

📦 Master Data Setup

🔄 Transaction Flow — The 5 Steps

✅ Flow A — Convert PR to PO (RECOMMENDED — auto-fills everything)

⚠️ Flow B — Create PO Direct (NO PR) — use only when no PR exists

🆚 Quick Comparison — Flow A vs Flow B

🔧 Pro tip — Set Personal Settings for ME21N too

Method 1 — The PO History hub (⭐ start here)

Method 2 — FBL1N: prove vendor account is clear

Method 3 — Relationship Browser (the wow trick)

🎓 Where the links live (interview gold)

💰 Complete Accounting Trail (T-account view)

🚨 Common Errors & Fixes

✅ Verification — How to confirm Scenario 1 worked

🎓 Interview-ready 30-sec answers from this scenario

Return to Vendor — Quality Reject

🇵🇰 Business Story

🎯 What you'll learn

📋 Prerequisites

🔄 Method A — Return Delivery (mvt 122) — when invoice not yet received

🔄 Method B — Return PO + mvt 161 — when invoice already received

✅ Verify Scenario 2

💡 122 vs 161 — when to use which

Goods Issue & Stock Transfers — Internal Movements

🇵🇰 Business Story

🎯 What you'll learn

🔄 Movement Type Cheat Sheet

✅ Verify Scenario 3

🔵 Tier 2: Account-Assigned Procurement

Service Procurement — Consulting Hours

🇵🇰 Business Story

🎯 What's different from stock procurement

📋 Prerequisites

📦 Master Data Setup

🔄 Transaction Flow

🚨 Common Errors

✅ Verify Scenario 4

Consumable Direct Purchase — Office Supplies (NLAG)

🇵🇰 Business Story

🎯 NLAG vs ROH — the key difference

📦 Master Data

🔄 Transaction Flow

🚨 Common Errors

Asset Procurement — New CNC Machine

⚙️ Prerequisite Setup

🇵🇰 Business Story

🎯 What's different — Asset accounting touches FI-AA

📋 Prerequisites (FI-AA)

📦 Master Data

🔄 Transaction Flow

🚨 Common Errors

✅ Verify Scenario 6

🟡 Tier 3: Multi-Plant Movements

Intra-Company STO — Karachi → Lahore

🇵🇰 Business Story

🎯 What's different — STO vs simple transfer (311)

📋 Prerequisites

🔄 Transaction Flow — Simple route (mvt 351 without delivery)

✅ Verify Scenario 7