Purchase Order Master Reference — Every PO Field Explained

📍 Quick Navigation

PO Concepts & Lifecycle
PO Document Types (NB, UB, FO, MK, WK)
PO Header Fields (Top Section)
PO Header Tabs (11 tabs)
PO Item Overview Fields
PO Item Detail Tabs (13 tabs)
Item Categories (Standard, K, L, B, D, S, T)
Account Assignment Categories (K, A, F, P, N, C, E, Q, M, X, U)
Tax Codes in PO
Pricing & Conditions
Common Errors & Fixes (20+)
PO-Related Configuration T-codes
PO Database Tables
T-Code Cheat Sheet
Interview Q&A (25+)
Pakistani Context Examples

🎯 Purchase Order — Concepts & Lifecycle

📖 What is a Purchase Order?

Definition: A Purchase Order (PO) is a legally binding commercial document issued by the buyer to a vendor, committing to purchase specified goods/services at agreed prices, quantities, and delivery terms.

In SAP: PO is created via ME21N and stored in tables EKKO (header) + EKPO (items). Once saved, it's the legal source document for vendor billing.

▶ Try it live: P2P Database Explorer — run a full Procure-to-Pay cycle and watch all the backend tables fill row-by-row.

PO Lifecycle in SAP

Stage	T-Code	Status	Tables Updated	FI Impact
1. Created (Saved)	ME21N	Open	EKKO, EKPO, EKET	None (commitment only)
2. Released (Approved)	ME29N	Released	EKKO-FRGKE	None
3. Sent to Vendor (Output)	ME9F	Printed/EDI sent	NAST	None
4. Goods Received	MIGO (101)	Partial/Full delivery	MSEG, MKPF, MBEW	Inventory Dr / GR-IR Cr
5. Invoice Received	MIRO	Invoiced	RBKP, RSEG, BKPF, BSEG	GR-IR Dr / Vendor Cr
6. Payment Made	F-53 or F110	Paid	BKPF, BSEG, BSAK	Vendor Dr / Bank Cr
7. Closed	Auto	Final	EKKO-LOEKZ	None

📄 PO Document Types — When to Use Each

SAP ships with 11+ standard PO document types. Configured via OMEC. Each has its own number range, field selection, and item categories allowed.

NB Standard PO

Most common (~80% of POs). Used for stock procurement, services, consumables, capex — anything bought from a vendor. Default if not specified.

Pakistani example: Mughal Steel iron ore order, Aisha Steel coal order, Lucky Cement HAWA purchase.

UB Stock Transport Order (Intra-Company)

Plant-to-plant transfer WITHIN same Company Code. No external vendor — supplying plant is treated as "internal vendor." Free of cost (no AP posting).

Pakistani example: Steel scrap transferred from PK01 Karachi Factory to PK03 Karachi DC for distribution.

UB Stock Transport Order (Cross-CC)

Stock transfer across Company Codes (different legal entities). Uses delivery + billing (SD). Inter-company invoice generated.

Pakistani example: Finished goods from PSPK (Pakistan) to PSAE (UAE) for re-export.

FO Framework Order / Limit Order

Open value-based PO for recurring services or supplies. Vendor delivers/invoices over time until budget exhausted. No specific quantity or delivery date.

Pakistani example: Annual maintenance contract (AMC) with TCS Logistics, security services from a contractor.

MK Quantity Contract

Outline Agreement — commits to buying X tons of material over Y months at fixed price. Released via individual call-off POs (RV doc type).

Pakistani example: 1000-ton iron ore contract with Mughal Steel for 12 months @ 250,000 PKR/ton.

WK Value Contract

Similar to MK but committed by VALUE not quantity. Useful when prices fluctuate but budget is fixed.

Pakistani example: 50-crore PKR steel scrap contract — buy whatever you can until value exhausted.

LP Scheduling Agreement (with release docs)

Long-term agreement with periodic delivery schedules. Vendor delivers per agreed schedule. Each call-off generates a "release order" doc.

Pakistani example: Monthly cement delivery from Lucky Cement per fixed schedule.

LPA Scheduling Agreement (without release docs)

Same as LP but no separate release docs — schedule lines themselves are the calls.

Use case: Simpler scheduling. Less audit trail.

RV Outline Agreement Release Order

The actual PO created against a contract (MK/WK). References the contract → counts against target qty/value.

🔧 Document Type Configuration (OMEC)

Setting	Where	Purpose
Doc Type code (4 chars)	OMEC header	Unique identifier
Number Range	OMEC + SNRO	Internal/external range, range #
Field Selection Key	OMEB	Which fields are mandatory/optional/hidden
Item Categories Allowed	OMEC item config	K (consignment), L (subcon), S (third-party), etc.
Release Strategy	SPRO → Release Procedure	Required approval workflow
Output Determination	NACE	How PO is sent to vendor (print/email/EDI)

📝 PO Header Fields — Top Section (Above Tabs)

These appear at the very top of ME21N screen, above all tabs. Mandatory unless noted.

Document Type EKKO-BSART MANDATORY

Purpose: Defines PO type (NB/UB/FO/MK/etc.). Drives number range, field selection, item categories allowed, release strategy.

How to fill: Defaults to NB (Standard). Override via dropdown.

Where stored: EKKO-BSART

Changeable after save: No (changes require recreation).

Supplier (Vendor) EKKO-LIFNR MANDATORY

Purpose: The vendor you're buying from. Pulls vendor master data (address, payment terms, currency, incoterms).

How to fill: Enter vendor number (e.g., MUGHAL21) or F4 to search.

Validation: Vendor must be (a) created via BP, (b) extended to the Purch Org (LFM1), (c) not blocked.

Changeable after save: No (would change entire commitment context).

Doc Date EKKO-BEDAT AUTO

Purpose: The date the PO was created. Used for reporting and aging.

How to fill: Defaults to today. Editable but rarely changed.

Difference from Posting Date: Doc Date = when PO created. Posting Date = when financial impact happens (typically at MIGO/MIRO).

Purchasing Organization EKKO-EKORG MANDATORY

Purpose: The legal/organizational entity that negotiates with the vendor and owns the PO.

How to fill: Auto-fills from Plant (via OMKI) OR Personal Settings default OR enter manually.

Validation: Must be assigned to the Plant (OX17) AND to the vendor (LFM1).

Where: Org. Data tab — auto-fills to header.

Purchasing Group EKKO-EKGRP MANDATORY

Purpose: The team/buyer responsible for this PO. Used for workload assignment and reporting.

How to fill: Auto-defaults from material master (Purchasing view) OR Personal Settings OR enter manually.

Examples (Pakistani): RMT (Raw Materials Trading), PKG (Packaging), MRO (Maintenance/Repair/Ops), ITS (IT & Services), SRV (Services), CPX (Capex), URG (Urgent).

Company Code EKKO-BUKRS AUTO

Purpose: The legal financial entity for accounting impact. Determines G/L postings at MIGO/MIRO.

How to fill: Auto-derived from Purchasing Organization (via OX01 assignment).

Where stored: EKKO-BUKRS

Note: If Purch Org is cross-company (no OX01 assignment), CC determined per item from Plant's CC (OX18).

📑 PO Header Tabs — All 11 Tabs Explained

After saving header, ME21N shows multiple tabs. Each tab groups related header-level fields.

📅 Delivery/Invoice Tab

Payment, currency, exchange rate, GR/IV behavior.

Field	Code	Required?	Source	Purpose
Payment Terms	EKKO-ZTERM	Required	Vendor LFM1	When invoice due + cash discount. e.g., `0003` = 14d 2%/30d net
Payment in (days)	EKKO-ZBD1T	Auto	From ZTERM	Discount tier 1 days
Currency	EKKO-WAERS	Required	Vendor LFM1	Order currency (PKR, USD, AED)
Exchange Rate	EKKO-WKURS	Auto if foreign	OB08 (daily rates)	Conversion to CC currency
Fixed Exch.Rate	EKKO-KUFIX	Optional	Manual	If checked → freeze the rate
GR Message	EKPO-WEBRE	Optional	Manual	Send confirmation to vendor at GR
Goods Receipt	EKPO-WEPOS	Required	Doc type config	Is GR required? (tick if stock material)
Invoice Receipt	EKPO-REPOS	Required	Doc type config	Is IR required?
GR-Based IV	EKPO-WEBRE	Optional	Vendor master	Invoice based on GR qty (recommended)

💰 Conditions Tab (Header Level)

Header-level pricing conditions (freight, discounts, taxes that apply to whole PO).

Field	Purpose
Pricing Procedure	Determined via M/06 → calc schema (e.g., RM0000)
Net Value (Header)	Sum of all item values + header conditions
Header Freight	If freight applies to whole PO (e.g., FRC1 freight condition)
Header Discounts	Cross-item discounts (e.g., 5% for order above 1 cr)

📝 Texts Tab

Free-text fields for PO notes, terms, special instructions.

Text ID	Purpose
F01 Header Text	General notes — printed on PO output
F02 Header Note	Internal note (not printed)
F03 Pricing Type	Pricing instructions
F04 Terms of Delivery	Delivery instructions
F05 Terms of Payment	Payment instructions (e.g., LC details)

🏠 Address Tab

Delivery address for the PO. Defaults to plant address.

Override use case: Drop-ship to customer site (not plant), or to specific project site (construction).

📞 Communication Tab

Phone, email, fax for vendor contact during this PO. Inherits from vendor master.

👥 Partners Tab

Defines who plays which role for THIS PO. Examples:

Partner Function	Purpose
LF — Supplier	Who you order from (main vendor)
BA — Ordering Address	Where to send PO (e.g., regional office)
RS — Invoice Issuer	Who sends invoice (may differ from goods supplier)
WL — Goods Supplier	Who actually ships (sub-supplier)
ZP — Forwarding Agent	Logistics handler

📊 Additional Data Tab

Custom Z-fields, supplementary info, attachments, references.

🏢 Org Data Tab

Purchasing Organization, Purchasing Group, Company Code — these auto-fill but can be reviewed here.

🔓 Status Tab

Shows release status, document statistics, processing status.

Field	Meaning
Released?	Yes/No — based on release strategy
Ordered Value	Total PO value
Statistics: Delivered	How much GR'd so far
Statistics: Invoiced	How much MIRO'd so far

💳 Payment Processing Tab

House Bank, Payment Method, Payment Block.

Field	Purpose
House Bank	Which bank account to pay from (HBL, MCB, UBL)
Payment Method	How to pay (T=Transfer, C=Cheque, B=Bank, E=Electronic)
Payment Block	Block payment until released (e.g., quality hold)

🚢 Incoterms Tab

International commercial terms — who bears freight/risk/customs.

Code	Meaning	Pakistani Use
EXW	Ex Works — buyer picks up	Rare for imports
FOB	Free On Board — vendor ships to port	Standard for local steel
CFR	Cost & Freight — vendor pays shipping	Common for imports
CIF	Cost, Insurance, Freight — full vendor responsibility	Premium imports
DDP	Delivered Duty Paid — door delivery	Convenience purchases

📋 PO Item Overview Fields — The Item Table

Each PO has one or more items (lines). The item table shows multiple fields per row.

Column	Code	Required?	Purpose
S (Selected)	—	Auto	Selection checkbox
Item Number (Itm)	EKPO-EBELP	Auto	Auto-incrementing (10, 20, 30...)
A (Acct Asgn Cat)	EKPO-KNTTP	Conditional	K, A, F, P, etc. (blank = inventory)
I (Item Category)	EKPO-PSTYP	Conditional	blank=Standard, K, L, B, D, S, T
Material	EKPO-MATNR	Conditional	Material number (if stock item)
Short Text	EKPO-TXZ01	Required	Description (auto-fills from material)
PO Quantity	EKPO-MENGE	Required	Quantity to buy
OUn (Order Unit)	EKPO-MEINS	Required	Unit (TO, KG, PC, M)
C (Compl Goods)	EKPO-ELIKZ	Optional	"Delivery completed" indicator
Deliv. Date	EKET-EINDT	Required	Expected delivery date
Net Price	EKPO-NETPR	Required	Price per unit (defaults from Info Record)
Curr. (Currency)	EKKO-WAERS	Auto	From header
Per	EKPO-PEINH	Required	Price unit (e.g., 1 = per 1 ton)
OPU (Order Price Unit)	EKPO-BPRME	Auto	Pricing unit (usually = OUn)
Matl Group	EKPO-MATKL	Auto	From material master
Plant	EKPO-WERKS	Required	Receiving plant
Stor. Location	EKPO-LGORT	Conditional	SLoc for stock receipt
Tax Code	EKPO-MWSKZ	Conditional	I0, V0, V1 (input tax)
Purchase Requisition	EKPO-BANFN	Optional	Link to PR if PO from PR
PR Item	EKPO-BNFPO	Auto	PR item # linked
Tracking Number	EKPO-BEDNR	Optional	External tracking ref
Info Record	EKPO-INFNR	Auto	Linked info record
Returns	EKPO-RETPO	Optional	Mark as returns PO
Free Indicator	EKPO-UMSON	Optional	Free goods (no payment)

🗂️ PO Item Detail Tabs — All 13 Tabs Explained

Click an item row → bottom area shows multiple tabs with deeper item-level fields.

1️⃣ Material Data Tab

Material identification fields, manufacturer info.

Field	Purpose
Material	Material number (RM-IRON-01)
Material Description	Auto from MARA
Manufacturer Part Number (MPN)	Vendor's catalog number
Vendor Material Number	How vendor codes the material
Revision Level	For engineering change tracking

2️⃣ Quantities/Dates Tab

All quantities, prices, schedule lines.

Field	Purpose
PO Quantity	Order quantity
Delivery Date	Expected delivery
Statistics: Delivered Qty	How much GR'd so far
Statistics: Open Qty	Quantity yet to receive
Schedule Lines	Multiple delivery dates (partial deliveries)

3️⃣ Valuation Tab

Material valuation context — price control, valuation class.

Field	Purpose
Price Control	V (Moving Avg) or S (Standard) — from material master
Valuation Class	e.g., 3000 (Raw Materials)
Moving Avg Price	Current MAP from MBEW
Standard Price	Current SP from MBEW

4️⃣ Conditions Tab (Item Level)

Pricing breakdown for this item. The big one. Shows gross price, discounts, freight, taxes.

Condition Type	Purpose
PBXX / P000	Gross price (base price)
RA00 / RA01	% discount
RB00 / RB01	Absolute discount
ZB00 / ZB01	Surcharge
FRA1 / FRA2 / FRB1	Freight (% / per unit / absolute)
JEXC / JEXT	Customs duty (for imports)
NAVS	Non-deductible tax

5️⃣ Account Assignment Tab

Critical for non-stock items. Where the financial impact goes (cost center, asset, project).

Fields visible depend on Account Assignment Category (see below).

If Acct Asgn Cat is...	Required Fields
`K` Cost Center	G/L Account + Cost Center
`A` Asset	G/L Account + Asset Number + Sub-number
`F` Internal Order	G/L Account + Order Number
`P` Project (WBS)	G/L Account + WBS Element
`N` Network	G/L Account + Network + Activity

6️⃣ Source of Supply Tab

Where the source determination logic shows. Fixed Vendor, Info Record, Source List entries, Outline Agreements.

Field	Purpose
Fixed Vendor	Locked-in vendor for this PR/PO
Info Record	Active info record (price source)
Agreement / Item	Reference outline agreement if applicable
Source List Active	Indicates if Source List required
Assign Source	Button to run source determination

7️⃣ Confirmations Tab

Vendor confirmations — order acknowledgment, shipping notification, delivery confirmation.

Confirmation Type	Purpose
AB Order Acknowledgment	Vendor confirms accepting PO
LA Shipping Notification	Vendor confirms ship date + qty
LB Rough Goods Receipt	Pre-receipt advice
Acknowledge. Required	Checkbox — block if not confirmed

8️⃣ Texts Tab (Item Level)

Free-text fields specific to this item.

9️⃣ Delivery Address Tab

Override default plant address with specific delivery address (drop-ship, project site).

🔟 Notes Tab

Long-text item notes.

1️⃣1️⃣ Status Tab

Item-specific status (delivery, invoice, returns, blocked).

1️⃣2️⃣ Purchase Order History Tab

Only after MIGO/MIRO posted. Shows all goods movements and invoices linked to this item.

Doc Type	Meaning
WE	Goods Receipt
RE-L	Invoice Receipt
WE-L	Reversed GR
RE	Final Invoice

1️⃣3️⃣ Customer Data Tab (Third-Party Only)

For third-party drop-ship (Item Cat S). Customer info from Sales Order.

🏷️ Item Categories — When to Use Which

Item Category controls procurement type. Configured via OMEC.

Code	Name	Stock Update?	Material Required?	GR Required?	IR Required?	Use Case
(blank)	Standard	✅ Yes	✅ Yes	✅ Yes	✅ Yes	Standard stock procurement (most POs)
`K`	Consignment	⚠️ Special	✅ Yes	✅ Yes	❌ No (MRKO settles)	Vendor owns stock until consumed
`L`	Subcontracting	✅ Yes (FG)	✅ Yes	✅ Yes	✅ Yes	Send components, receive finished goods
`B`	Limit	❌ No	❌ No	❌ No (or limit)	✅ Yes (within limit)	Framework orders (FO doc type)
`D`	Service	❌ No	❌ No	⚠️ ML81N entry sheet	✅ Yes	Service procurement
`S`	Third-Party	❌ No	✅ Yes	⚠️ Optional	✅ Yes	Drop-ship from vendor to customer
`T`	Text	❌ No	❌ No	❌ No	❌ No	Pure text line — for notes/instructions
`P`	Pipeline	⚠️ Special	✅ Yes	❌ No	❌ No (MRKO)	Pipeline materials (gas/water)
`U`	Stock Transfer	✅ Yes	✅ Yes	✅ Yes	❌ No (intra)	STO (UB doc type)

💡 Item Category × Doc Type matrix

Not all item categories are allowed in all doc types. Example:

NB (Standard PO) allows: blank, K, L, B, D, S, T
UB (STO) allows only: U
FO (Framework) allows only: B, D
MK (Quantity Contract) allows: blank, K, L, M, W

Configured in OMEC → Item Categories per Document Type.

💼 Account Assignment Categories — Where Money Goes

For items NOT going to inventory, Account Assignment Category determines the cost object. Configured via SPRO → MM → Purchasing → Account Assignment.

Code	Name	Required Fields	GR Effect	Use Case
(blank)	Inventory	None (auto from material)	Stock ↑, G/L from OBYC	Standard stock procurement
`A`	Asset	Asset # + Sub#	Direct to asset (capitalized)	Machinery, vehicles, IT equipment
`F`	Internal Order	Order #	Direct to CO order	Marketing campaigns, R&D
`K`	Cost Center	Cost Center + G/L	Consumption to cost center	Office supplies, MRO, services
`N`	Network	Network + Activity	Direct to PS network	Project network costs
`P`	Project (WBS)	WBS Element	Direct to project WBS	Construction projects, IT implementations
`C`	Sales Order	Sales Order #	For SO consumption	MTO production materials
`E`	Sales Order w/ Stock	SO # + Stock segment	Stock for SO use	Customer-specific MTO stock
`Q`	Project Stock	WBS Element	Stock for project	Project-segregated inventory
`M`	Indiv w/o KD-CGS	Sales Order #	Customer-individual	Highly customized MTO
`U`	Unknown	None (TBD later)	Hold until assigned	Open-ended POs (FO)
`X`	Multiple	List of multiple assignments	Distribute across cost objects	Cost split (e.g., 50% A, 50% B)
`T`	Returns to Vendor	None special	Returns posting	Quality reject returns

🇵🇰 Pakistani Examples

Office supplies (stationery): Acct Cat = K, Cost Center = Admin
New CNC machine for factory: Acct Cat = A, Asset = AS-CNC-001
Construction of new warehouse: Acct Cat = P, WBS = WBS-WH-2026
Marketing campaign for Eid: Acct Cat = F, Internal Order = MKT-EID-2026
Iron ore (stock): Acct Cat = blank (Inventory) — material RM-IRON-01

💸 Tax Codes in PO

Tax Code drives input tax calculation in MIRO. Configured via FTXP.

Code	Prefix Meaning	Purpose	Rate (Standard IDES)
`I0`	I = Input Tax	Zero-rated input tax (no tax) — use for non-taxable purchases	0%
`I1`	I = Input Tax	Standard input tax	varies by country
`V0`	V = Vendor / Output (in some configs)	Zero-rated	0%
`V1`	V = Vendor / Output	Standard rate (varies — 17% in Pak default IDES, 19% EU)	varies

🇵🇰 Pakistani Tax Codes (to configure via FTXP)

Code	Purpose	Rate
`PIN0`	Pakistan Input Zero	0%
`PIN1`	Pakistan General Sales Tax (input)	17%
`PWHT`	Pakistan Withholding Tax (input)	1-5%
`PCST`	Pakistan Sales Tax — Sindh (provincial)	13%
`PWHS`	Withholding Sales Tax	4.5%

These need configuration in FTXP per company code. Most Pakistani projects implement these.

💵 Pricing & Conditions in PO

Pricing Procedure Determination

SAP determines which pricing procedure (calc schema) to apply based on:

Factor	Source
Schema Group: Vendor	Vendor master LFM1
Schema Group: Purch Org	OMFR config
Calc Schema	Determined by combo via OMFO (Schema Determination)

Standard Pricing Procedure: RM0000

Default for purchase procurement. Configured via M/08.

Step	Cond Type	Purpose
10	PBXX / P000	Gross Price
20	RA00	Discount % from net
30	—	Subtotal: Net Price
40	FRA1	Freight %
50	FRB1	Freight (Absolute)
60	FRC1	Freight (per Unit)
70	—	Subtotal: Net + Freight
80	NAVS	Non-deductible Tax
90	—	Effective Price

Where Net Price comes from (Priority Chain)

Info Record (ME11) — first priority, has master price for material+vendor+POrg
Outline Agreement (contract) — if PO references contract
Last PO price — if "Info Update" was unticked
Manual entry — if no above source

🚨 Common PO Errors & Fixes (25+ scenarios)

ME062 — Account assignment mandatory for material

Cause: Material has no Accounting view OR Material Type "Value Update" not active in OMS2.

Fix: (1) MM02 → Material → Accounting 1 view → fill Valuation Class + Price Control + Price. (2) OMS2 → Material Type → Quantity/Value Updating → check Value Update for plant.

M8 215 — Maintain tolerance limits for tolerance key PE (CoCode XXX)

Cause: Tolerance Key PE not configured for the Company Code (new CC issue).

Fix: SPRO → MM → Purchasing → Purchase Order → Set Tolerance Limits for Price Variance → New Entries → PE + CC + limits. (Don't use OMR6 — PE not in its F4 list.)

M8 462 — Maintain tolerance limits for PP

Cause: Invoice tolerance PP not configured.

Fix: OMR6 → New Entries → PP + CC + limits.

06 105 — Plant XXXX not assigned to Purch Org YYYY

Cause: Missing OX17 assignment.

Fix: Run OX17, add Purch Org → Plant row.

06 010 — Vendor not extended to Purch Org

Cause: Vendor LFM1 (Purchasing data) missing for the Purch Org.

Fix: BP transaction → switch role to "Vendor (Purchasing)" → add Purch Org + currency + terms.

06 401 — Source not allowed (Source List required)

Cause: Material has "Source List Required" flag ON but vendor not in source list.

Fix: (1) ME01 → add vendor to source list, OR (2) MM02 → Purchasing view → untick "Source List".

06 424 — No source of supply found

Cause: No valid source list entry covers PO delivery date.

Fix: ME01 → check Valid From/To dates cover the PO date.

ME083 — Net price is 0

Cause: No info record exists or net price not entered.

Fix: (1) ME11 → create info record with price, OR (2) Manually enter price in PO item line.

06 207 — Output determination not configured

Cause: NACE/MN04 not set up for PO type.

Fix: (1) NACE → EF (Purchasing) → maintain condition records. (2) Or ignore — yellow warning, PO saves.

ME017 — Reminder days defined in vendor master

Cause: Vendor master has reminder days set. Informational only.

Fix: Ignore (yellow warning). Vendor reminders will trigger via ME92F batch.

06 005 — Realistic delivery date

Cause: Entered delivery date earlier than calculated (today + Planned Delivery Time + GR Processing).

Fix: (1) Ignore (warning only), OR (2) Adjust delivery date, OR (3) Reduce Planned Delivery Time in vendor LFM1.

06 116 — Currency not maintained for vendor + Purch Org

Cause: Vendor LFM1 currency missing.

Fix: BP → Vendor (Purchasing) → set Order Currency.

06 121 — Vendor blocked for Purchasing

Cause: Vendor has block flag set.

Fix: BP → check Status/Block → remove block. Or use different vendor.

M7 432 — Posting period not open

Cause: MM period not open via OMSY (or FI via OB52).

Fix: OMSY → set current period for the CC. OB52 → check FI periods.

BU 134 — BP can't be used as vendor in this Purch Org

Cause: CVI sync issue — BP exists but LFM1 not created.

Fix: BP → add Vendor (Purchasing) role → Purch Org → save (CVI auto-creates LFM1).

ME 083 — Net price is zero

Cause: Info Record price is 0 or expired.

Fix: ME12 → update Info Record price and validity dates.

00 055 — Release strategy not found

Cause: Release strategy configured but classification missing.

Fix: SPRO → Release Procedure for PO → check Class/Characteristic config (CT04/CL02).

06 217 — Net price varies by more than X%

Cause: Net Price varies beyond PE tolerance.

Fix: (1) Adjust price to within tolerance. (2) Or update tolerance limits in SPRO PO Price Variance config.

06 122 — Material XXXX not maintained for plant YYYY

Cause: Material exists but no plant-specific view (MARC).

Fix: MM01 → extend material → select Purchasing + Plant Data/Storage views → plant key → save.

FA 766 — Asset master record incomplete

Cause: Acct Cat A used but Asset master is incomplete.

Fix: AS02 → complete the asset master record.

KI 235 — Cost center not assigned to G/L account

Cause: Acct Cat K used with G/L that's not allowed for that cost center.

Fix: KS02 → assign cost center to G/L → OR use different G/L account.

M8 521 — Tax code not entered

Cause: Tax Code mandatory but not entered.

Fix: Enter I0 (zero tax) or appropriate tax code in Invoice tab.

06 113 — Net price not within tolerance to last PO

Cause: Price differs from last PO by more than tolerance.

Fix: Verify price is correct → ignore warning or adjust to match.

M8 138 — Account assignment differs from PO

Cause: MIRO invoice has different acct assignment than PO.

Fix: Match invoice to PO assignment OR change at MIRO level (if allowed).

06 110 — Goods receipt-based invoice verification active

Cause: GR-Based IV ticked but no GR yet.

Fix: Post GR first via MIGO before MIRO.

⚙️ All PO-Related Configuration T-codes

T-Code	Purpose	SPRO Path
OMEC	PO Document Types definition	MM → Purchasing → Purchase Order → Define Document Types
OMEB	PO Field Selection per doc type	MM → Purchasing → Purchase Order → Define Field Selection
SNRO	Number Ranges for documents	via OMEC linkage
OMR6	Invoice tolerance limits (PP, BD, DQ, VP, etc.)	MM → LIV → Set Tolerance Limits
SPRO PO Tolerance	PO Price Variance tolerance (PE, SE)	MM → Purchasing → Purchase Order → Set Tolerance Limits for Price Variance
OMC0	GR tolerance limits (B1, B2, VP)	MM → Inv Mgmt → Goods Receipt → Set Tolerance Limits
OMRM	Message control (Error → Warning)	MM → LIV → Define System Messages
OMS2	Material Type config (incl. value update)	Logistics General → Material Master → Material Types
OMSK	Valuation Class definition	FA → Materials Mgmt → Valuation
OBYC	Automatic Account Determination	MM → Valuation and Account Assignment → Account Determination
M/06	Condition Types (pricing)	MM → Purchasing → Conditions → Condition Types
M/08	Calculation Schema (pricing procedure)	MM → Purchasing → Conditions → Calculation Schema
OMFO	Schema Determination (vendor + purch org)	MM → Purchasing → Conditions → Schema Determination
NACE	Output Determination (print/email PO)	Cross-Application → NAST → Output
MN04	PO Output Condition Records	Logistics → MM → Master Data → Messages → PO → MN04
CT04	Classification Characteristics (for release strategy)	Cross-Application → Classification
CL02	Classification Class	Cross-Application → Classification
SPRO Release Procedure	Release strategy for PO	MM → Purchasing → Purchase Order → Release Procedure
OMD9	Special Procurement Keys	Production → Master Data → Special Procurement Types
OMKI	Standard Purch Org per Plant	Enterprise Structure → Assignment → MM → Assign Standard Purch Org to Plant
OX17	Assign Purch Org to Plant	Enterprise Structure → Assignment → MM
OX01	Assign Purch Org to Company Code	Enterprise Structure → Assignment → MM
FTXP	Tax Codes	FI → Global Settings → Tax on Sales/Purchases

🗃️ PO Database Tables

Table	Content	Key Fields
`EKKO`	PO Header	EBELN (PO #), BSART (Doc Type), LIFNR (Vendor), EKORG, EKGRP, BUKRS, WAERS
`EKPO`	PO Items	EBELN, EBELP (Item), MATNR, MENGE, NETPR, WERKS, LGORT
`EKET`	PO Delivery Schedule	EBELN, EBELP, EINDT (Delivery Date), MENGE
`EKPV`	Shipping Data for PO	EBELN, KZAZU (Shipping)
`EKKN`	Account Assignment per PO Item	EBELN, EBELP, KOSTL (Cost Ctr), ANLN1 (Asset), AUFNR (Order), PS_PSP_PNR (WBS)
`EKBE`	PO History (GR, IR, etc.)	EBELN, EBELP, VGABE (Trans Type), BEWTP (Doc Type WE/RE)
`EKBES`	PO History — Tax	EBELN, EBELP, tax data
`EKBZ`	PO History — Charges	EBELN, EBELP, planned costs
`EKES`	Vendor Confirmations	EBELN, EBELP, EBTYP (Conf Type)
`EKKI`	Item-level Conditions	EBELN, EBELP, condition records
`KONV / KONP`	Condition Values / Records	KNUMV (Condition Doc), KSCHL (Cond Type)
`EBAN`	Purchase Requisitions (linked)	BANFN (PR #), referenced from EKPO-BANFN
`NAST`	Output / Messages	OBJKY (PO #), KAPPL (EF for PO), KSCHL (Output Type)

🎯 PO T-Code Cheat Sheet

Daily-Use Transactions

T-Code	Purpose
ME21N	Create PO ⭐
ME22N	Change PO ⭐
ME23N	Display PO ⭐
ME29N	Release/Approve PO
ME9F	Print/Output PO
ME54N	Release PR (precursor to PO)
ME57	Assign and Process PR (convert to PO)
ME58	Ordering from Assigned PRs
ME59N	Auto-create POs from PRs ⭐

PO Reporting

T-Code	Purpose
ME2L	POs by Vendor
ME2M	POs by Material
ME2N	POs by PO Number
ME2K	POs by Account Assignment
ME2W	POs by Supplying Plant
ME80FN	General Analysis of Purch Documents
ME81N	Analysis of Order Values

PO Document History

T-Code	Purpose
ME23N	Display PO + history
ME92F	Monitor/Process Order Acknowledgments
MIR4	Display Invoice
MIGO	Display Material Doc (GR linked to PO)

🎓 Interview-Ready Q&A (25+ Questions)

Q1: What's the difference between PR and PO?

A: PR (Purchase Requisition) is an INTERNAL request — a department asks Purchasing to buy something. No commitment to any vendor. Created via ME51N. PO (Purchase Order) is the EXTERNAL legal commitment to a specific vendor at agreed price. Created via ME21N (often from PR). PR doesn't post anything to FI; PO is a commitment (still no FI hit until GR).

Q2: Explain 3-way match in MM.

A: 3-way match validates 3 documents before paying vendor: (1) PO — what you ordered/committed. (2) GR — what you received. (3) Invoice — what vendor charged. SAP checks quantities and prices match across all 3. If invoice qty > GR qty → MIRO blocks. If invoice price > PO price beyond PP tolerance → invoice blocked. Prevents overpayment and ensures vendor delivered what was ordered.

Q3: What's the difference between Item Category and Account Assignment Category?

A: Item Category defines what TYPE of procurement (Standard, Consignment K, Subcontracting L, Service D, Third-Party S). Account Assignment Category defines WHERE the financial impact goes (Cost Center K, Asset A, Project P, Order F, blank=Inventory). They're independent — e.g., Standard PO item (blank Item Cat) can be Cost Center assigned (K Acct Cat) for non-stock office supplies.

Q4: What happens at PO save? Are FI entries generated?

A: PO save updates EKKO + EKPO + EKET (header, items, schedule). Optionally EKKN (account assignment), EKPV (link to PR). NO FI entries — PO is just a commitment, not a posting. Some companies enable "commitment management" for budget reporting which makes memo entries, but no real G/L hits. First FI hit is at MIGO (GR): Inventory Dr / GR-IR Cr.

Q5: How does SAP determine pricing in PO?

A: Priority chain: (1) Outline Agreement reference (highest). (2) Info Record (ME11) for material+vendor+POrg. (3) Last PO price (if Info Update was unticked). (4) Manual entry. Pricing procedure (calc schema RM0000) determined by Vendor Schema Group + Purch Org Schema Group via OMFO. Schema processes conditions in sequence: Gross Price → Discounts → Subtotal Net → Freight → Subtotal Net+Freight → Tax → Effective Price.

Q6: What is GR-Based IV and when to use it?

A: GR-Based Invoice Verification flag means invoice qty is validated against GR qty (not PO qty). Use when: (1) Multiple deliveries per PO line. (2) Quantity variances expected between PO and actual receipt. (3) Strict 3-way match required. Don't use for: (1) Single-shot full deliveries. (2) Services where GR doesn't apply. Flag set in vendor master LFM1 OR PO item.

Q7: How would you implement multi-level PO approval?

A: Use Release Strategy: (1) Define Characteristics via CT04 (e.g., Net Order Value, Purch Group, Material Group). (2) Create Class via CL02 of class type 032 (Purchasing). (3) Assign characteristics to class. (4) Configure Release Strategy in SPRO with Release Codes (00, 01, 02 for different approver levels). (5) Define release prerequisites (sequential or parallel). (6) Workflow integration via SBWP for notifications. Real example: POs under 5 lac auto-released, 5-50 lac need Manager (RC 01), 50 lac+ need Director (RC 02). Implemented via release strategy + workflow.

Q8: What's the difference between Contract (MK) and Scheduling Agreement (LP)?

A: Both are Outline Agreements but different mechanics: Contract (MK/WK) = commits qty or value over time. Need separate Release Orders (RV) for each delivery. Vendor delivers when called. Scheduling Agreement (LP/LPA) = commits with pre-defined delivery schedule. Vendor delivers automatically per schedule without separate orders. Use Contract when timing flexible, Scheduling when timing fixed (e.g., monthly cement deliveries from Lucky Cement).

Q9: How is Tax Code determined in PO?

A: Tax Code on PO line determined by: (1) Material Master (MARC-MWSKZ default). (2) Info Record. (3) Vendor master default. (4) Manual entry. Then in MIRO, the same code drives tax calculation via FTXP rules. For Pakistan: configure I0 (zero), I1 (17% GST input), various provincial codes via FTXP per company code.

Q10: What is PE tolerance and when is it triggered?

A: PE = Price Variance Purchasing tolerance. Triggered at PO save (ME21N) when net price varies from material's moving average price beyond defined limits. Configured via SPRO IMG → MM → Purchasing → Purchase Order → Set Tolerance Limits for Price Variance. NOT in OMR6 (which is for Invoice tolerances). Common setup error in new CCs — fix by configuring PE for the CC or using OMRM to change message severity.

Q11: When would you create PO without PR?

A: Several scenarios: (1) Urgent purchases — no time for PR cycle. (2) Recurring buys with established vendor. (3) Low-value purchases under threshold. (4) Replenishment based on consumption (not formal request). (5) MRP-driven (system creates PR auto, but some configs skip to PO). Drawback: no PR-PO link in EKPV, no requisitioner approval trail, may bypass release strategy. Recommend 80%+ POs come from PR for governance.

Q12: Explain Source List vs Info Record.

A: Info Record (ME11) stores PRICE for material+vendor+POrg combo. Can have many — one per vendor. Answers "at what price?". Source List (ME01) stores list of APPROVED VENDORS for material+plant. Marks Fixed Source for auto-selection. Answers "from whom can I buy?". Source List drives Source Determination in PR/PO. Info Record provides the price.

Q13: What is "Subcontracting" item category L?

A: Item Cat L = Subcontracting. You send raw materials (components) to vendor, vendor manufactures, returns finished goods. SAP tracks: (1) Components consumed (movement 543). (2) FG received (movement 101). (3) Provided stock at vendor (movement 541). Requires BOM (CS01) for the FG defining component materials. Common in Pakistani textile, leather, electronics assembly.

Q14: How does Consignment (K) differ from Standard procurement?

A: Consignment K = vendor stores goods at YOUR plant but owns them. You don't pay until you CONSUME. Movements: GR 101-K (consignment stock — owned by vendor), Withdrawal 411-K (transfer to your stock OR consumption). Settlement via MRKO (creates invoice for consumed qty). No traditional MIRO. Vendor still owns unconsumed stock — can be recalled. Common for spare parts, pharmaceutical inventory.

Q15: What is Output Determination and how to set it up?

A: Output Determination = how PO is COMMUNICATED to vendor (print, email, fax, EDI, ALE). Configured via NACE (master) → Application EF (Purchasing) → Output Types (NEU=default print). Condition Records via MN04 define WHEN each output triggers. SAP Form (SAPscript/Smart Form) defines APPEARANCE. Output processed via ME9F. Without this, PO saves but no document sent — manual workaround needed.

Q16: How would you handle PO for foreign vendor (import)?

A: Multiple steps: (1) Vendor master in foreign currency (USD/EUR/CNY). (2) Tax Code I0 (no Pakistani tax on import — customs handles). (3) Incoterms (CIF or FOB). (4) Customs duty as planned costs in PO conditions (JEXC/JADC for India, similar for Pakistan). (5) LC payment terms (custom — LC30/LC60). (6) Inbound delivery via VL10B for tracking. (7) GR with customs and freight as planned costs. (8) Invoice verification of vendor invoice + separate customs invoice via MIRO. Pakistan-specific: WeBOC integration for customs declarations.

Q17: What's the difference between Purchase Org assigned to CC vs Cross-Company?

A: Assigned to CC (via OX01): Purch Org buys for plants of ONE specific Company Code. Common pattern (PKLO for PSPK only). Cross-Company (no OX01): Purch Org assigned to no CC. Can buy for plants of ANY CC (PKLO buying for both PSPK and PSAE). Used for global/regional procurement. Drawback: When buying for plant in different CC than Purch Org's, may need intercompany handling for invoicing.

Q18: What is GR Processing Time?

A: Time between physical goods arrival and stock being available for use. Includes unloading, quality inspection, system posting. Set in Material Master MRP 2 view (GR Processing Time field, days). Used in: (1) Lead time calculations. (2) Realistic delivery date checks in PO. (3) MRP date calculations. Typical values: 1-3 days for normal materials, 5-10 days for QM-inspected materials.

Q19: How does Cash Discount work in MM?

A: Defined in Payment Terms (e.g., 0003 = 14d 2%/30d net). If invoice paid within 14 days → 2% discount auto-calculated by SAP at F-53/F110. Discount G/L (Cash Discount Received) configured via OBXU. Posting: Invoice 100 → if paid in 14d → Vendor Dr 98 / Cash Discount Cr 2 / Bank Cr 98. Significant savings — 2% on 1 crore = 2 lac PKR per order. Real CFO motivation.

Q20: How do you delete/cancel a PO?

A: SAP doesn't allow true deletion (audit trail). Options: (1) Block (ME22N → Set Block) — PO can't be used but stays. (2) Mark for Deletion (ME22N → mark item with Delete flag) — PO archived eventually. (3) If no GR/IR yet — can be deleted via ME22N. (4) If GR/IR posted — must reverse those first (MIGO 102, MR8M). After PO closed (fully delivered + paid), it's archived but never truly deleted.

Q21: What is "Confirmation Control Key"?

A: Controls what vendor confirmations are expected for the PO item — Order Acknowledgment, Shipping Notification, Rough GR. Defined in Vendor master (LFM1) or PO item. Common keys: blank (no confirmations), 0001 (order ack required), 0002 (ship notification), 9999 (all confirmations). Without confirmation, GR may be blocked depending on config.

Q22: Explain Net Price vs Effective Price.

A: Net Price (EKPO-NETPR) = base price + discounts/surcharges from condition types up to step 30 in RM0000. Effective Price (EKPO-EFFWR / KOMV-EFFWR) = includes freight, customs, all costs up to step 90. Net Price is what vendor charges. Effective Price is what material actually costs you (used for valuation). Important: Inventory at GR uses Effective Price (not Net) — captures total acquisition cost.

Q23: Where do I configure validity period for Info Records?

A: Info Record (ME11) has Validity period at the Conditions level (price), not the header. Each condition record (PB00 gross price, RA00 discount) has Valid From and Valid To. Multiple price periods possible (e.g., Q1 price 250000, Q2 price 260000). SAP picks active condition based on PO delivery date. Useful for contract-based pricing changes.

Q24: What is "Standard Purchasing Organization" used for?

A: The DEFAULT Purch Org for a plant (configured via OMKI, stored in T001W-EKORG). Auto-fills in: (1) STO creation. (2) Pipeline material consumption. (3) Consignment settlement. (4) MRP-generated PRs. Critical for automated transactions where no user input is possible. Different from many-to-many assignment (OX17/T024W) which defines POSSIBLE assignments — Standard is the DEFAULT.

Q25: How do you handle PO change after Invoice Receipt?

A: After MIRO posted, PO field changes limited: (1) Cannot reduce qty/value below already invoiced. (2) Can extend qty/value with new line items. (3) Cannot change vendor or Purch Org (would invalidate invoice). (4) Cannot change Acct Assignment Cat. Approach: Either (a) Add new line for extras, (b) Reverse invoice (MR8M) → change PO → re-invoice. Best practice: catch issues at PO or GR stage, not after IR.

Q26: What is "Info Update" checkbox in PO?

A: When ticked (default), saving PO updates Info Record with current PO price (creates new info record if none exists). Untick if PO has special one-time pricing that shouldn't become the new standard. Common: ticked for regular vendors, unticked for spot purchases or one-time deals.

Q27: How does MM-FI integration work at PO save?

A: PO save itself doesn't create FI entries. But it sets up the chain: (1) EKKO-EKPO created with reference to G/L accounts via Material Valuation Class → OBYC BSX. (2) At MIGO 101: Inventory G/L from BSX, GR-IR from WRX. (3) At MIRO: GR-IR cleared, Vendor AP from vendor recon account. So FI accounts ARE pre-determined at PO save, but actual postings happen at GR/IR. This is why Material Master accounting view + OBYC + tolerances must be set BEFORE first PO.

🇵🇰 Pakistani Business Context Examples

Example 1: Mughal Steel Iron Ore Order

Vendor: MUGHAL21 (Mughal Steel Industries Pvt Ltd, Karachi)
Material: RM-IRON-01 (Iron Ore Lump Grade A 50-100mm)
Doc Type: NB (Standard PO)
Plant: PK01 (Karachi Factory)
Purch Org: PKLO (Pakistan Local)
Purch Group: RMT (Raw Materials Trading)
Quantity: 50 tons
Net Price: 250,000 PKR/ton
Currency: PKR
Incoterms: FOB Karachi
Payment Terms: 0003 (14d 2%/30d net)
Tax Code: I0 (no tax for now; later configure PIN1 for 17% GST)

Example 2: New CNC Machine for Production (Asset)

Vendor: Foreign vendor (Japan)
Material: ASSET-CNC-001 (capex item)
Doc Type: NB
Plant: PK01
Acct Assignment Cat: A (Asset)
Asset Number: 100001 (from AS01)
Currency: USD
Incoterms: CIF Karachi Port
Payment Terms: LC60 (60 days LC)
Customs Duty: planned as PO condition

Example 3: Office Supplies (Cost Center)

Vendor: Local stationery shop
Item: text only (no material master)
Doc Type: NB
Acct Assignment Cat: K (Cost Center)
Cost Center: 1000 (Admin)
G/L Account: 470000 (Office Supplies Expense)
Currency: PKR
Payment Terms: 0001 (Immediate)

Example 4: Subcontracting (Steel cutting)

Vendor: Cutting service provider
FG Material: SEMIFG-PLATE-CUT (cut steel plates)
Component (sent): RM-PLATE-RAW (raw plates)
Item Category: L (Subcontracting)
BOM: required (CS01) — defines RM-PLATE-RAW → SEMIFG-PLATE-CUT
Plant: PK01
Movements: 541 (send RM), 543 (RM consumed), 101 (receive FG)

Example 5: Inter-Company STO (PSPK → PSAE)

Doc Type: NB (with vendor = receiving plant's customer master)
Supplying Plant: PK01 (PSPK)
Receiving Plant: AE01 (PSAE — UAE)
Material: FG-PIPE-001
Inter-company invoice via SD (VF01)
FI: Inter-company posting via OBYA

📝 Final Verification Checklist Before First PO

Check	How to verify
Company Code exists	OX02 → check CC
Plant created and assigned to CC	OX10 + OX18
Purch Org created and assigned to Plant + CC	OX08 + OX17 + OX01
Standard Purch Org for Plant	OMKI
Material exists with all views	MM03 → check Basic, Plant, Storage, Purchasing, Accounting
Vendor (BP) exists with Purchasing role	BP → vendor → confirm Vendor (Purchasing) role for Purch Org
Info Record exists with price	ME13 → check material+vendor+POrg
Source List (if required)	ME03 → check material+plant
OBYC configured (BSX, WRX, GBB, PRD)	OBYC → verify rules for valuation class
Tolerance Keys (PE, PP, BD, DQ) configured	SPRO PO Price Variance + OMR6
MM Period open (OMSY)	OMSY → check current period
FI Period open (OB52)	OB52 → check current period
Tax Codes (I0, V0) exist	FTXP → check

📚 Sources: Verified against help.sap.com (S/4HANA) · learning.sap.com · saponlinetutorials.com · community.sap.com

🛒 Purchase Order Master Reference

📍 Quick Navigation

🎯 Purchase Order — Concepts & Lifecycle

📖 What is a Purchase Order?

PO Lifecycle in SAP

📄 PO Document Types — When to Use Each

NB Standard PO

UB Stock Transport Order (Intra-Company)

UB Stock Transport Order (Cross-CC)

FO Framework Order / Limit Order

MK Quantity Contract

WK Value Contract

LP Scheduling Agreement (with release docs)

LPA Scheduling Agreement (without release docs)

RV Outline Agreement Release Order

🔧 Document Type Configuration (OMEC)

📝 PO Header Fields — Top Section (Above Tabs)

Document Type EKKO-BSART MANDATORY

Supplier (Vendor) EKKO-LIFNR MANDATORY

Doc Date EKKO-BEDAT AUTO

Purchasing Organization EKKO-EKORG MANDATORY

Purchasing Group EKKO-EKGRP MANDATORY

Company Code EKKO-BUKRS AUTO

📑 PO Header Tabs — All 11 Tabs Explained

📅 Delivery/Invoice Tab

💰 Conditions Tab (Header Level)

📝 Texts Tab

🏠 Address Tab

📞 Communication Tab

👥 Partners Tab

📊 Additional Data Tab

🏢 Org Data Tab

🔓 Status Tab

💳 Payment Processing Tab

🚢 Incoterms Tab

📋 PO Item Overview Fields — The Item Table

🗂️ PO Item Detail Tabs — All 13 Tabs Explained

1️⃣ Material Data Tab

2️⃣ Quantities/Dates Tab

3️⃣ Valuation Tab

4️⃣ Conditions Tab (Item Level)

5️⃣ Account Assignment Tab

6️⃣ Source of Supply Tab

7️⃣ Confirmations Tab

8️⃣ Texts Tab (Item Level)

9️⃣ Delivery Address Tab

🔟 Notes Tab

1️⃣1️⃣ Status Tab

1️⃣2️⃣ Purchase Order History Tab

1️⃣3️⃣ Customer Data Tab (Third-Party Only)

🏷️ Item Categories — When to Use Which

💡 Item Category × Doc Type matrix

💼 Account Assignment Categories — Where Money Goes

🇵🇰 Pakistani Examples

💸 Tax Codes in PO

🇵🇰 Pakistani Tax Codes (to configure via FTXP)

💵 Pricing & Conditions in PO

Pricing Procedure Determination

Standard Pricing Procedure: RM0000

Where Net Price comes from (Priority Chain)

🚨 Common PO Errors & Fixes (25+ scenarios)

ME062 — Account assignment mandatory for material

M8 215 — Maintain tolerance limits for tolerance key PE (CoCode XXX)

M8 462 — Maintain tolerance limits for PP

06 105 — Plant XXXX not assigned to Purch Org YYYY

06 010 — Vendor not extended to Purch Org

06 401 — Source not allowed (Source List required)

06 424 — No source of supply found

ME083 — Net price is 0

06 207 — Output determination not configured

ME017 — Reminder days defined in vendor master

06 005 — Realistic delivery date

06 116 — Currency not maintained for vendor + Purch Org

06 121 — Vendor blocked for Purchasing

M7 432 — Posting period not open

BU 134 — BP can't be used as vendor in this Purch Org

ME 083 — Net price is zero

00 055 — Release strategy not found

06 217 — Net price varies by more than X%

06 122 — Material XXXX not maintained for plant YYYY