MM / P2Pintermediate

MM Purchase Order Part 3: Item Categories — Standard, Consignment, Subcontracting, Third-Party, Service and Limit

Key takeaway

Item categories change what a PO item does: standard (stock/consumption), K consignment (no value until withdrawal), L subcontracting (components provided), S third-party (supplier ships to customer), D service, B limit, U stock transfer — and their effects on GR, IV and postings.

Explanation

📌 KEY POINTS
✅ Standard: GR to stock or consumption, invoice expected.
✅ K consignment: supplier-owned stock, no value at GR; settlement after withdrawal.
✅ L subcontracting: components provided to supplier, GR of finished product consumes them.
✅ S third-party: supplier ships to customer; D service: service entry; B limit: value-only for unplanned needs; U: stock transfer.
⚠️ Using standard items for supplier-held consignment stock inflates inventory and payables.

━━━━━━━━━━━━━━━━━━━━
▶ WHERE WE ARE
Part 2 covered pricing. Now item categories.

━━━━━━━━━━━━━━━━━━━━
▶ 1. STANDARD

Stock material: GR to stock; account-assigned: consumption.

━━━━━━━━━━━━━━━━━━━━
▶ 2. CONSIGNMENT (K)

Special stock K; no price in PO item; liability at withdrawal.

━━━━━━━━━━━━━━━━━━━━
▶ 3. SUBCONTRACTING (L)

Components (BOM) sent via 541; GR 101 with 543 consumption.

━━━━━━━━━━━━━━━━━━━━
▶ 4. THIRD-PARTY (S), SERVICE (D), LIMIT (B)

S: account-assigned, delivery to customer.
D: service lines and service entry (or lean services).
B: expected/overall value limits, no GR required.

━━━━━━━━━━━━━━━━━━━━
▶ 5. STOCK TRANSFER (U)

Between plants; delivery and GR at receiving plant.

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

Create PO items with categories K and L.
Post GR for each; compare postings.

✅ CHECKPOINT: you can predict stock and accounting effects for each item category.

Code example

ABAP Code

===== STEP 1: examples =====K: consignment item → GR into special stock K (no value) → withdrawal 201K/261K → MRKO settlementL: subcontracting item with components → 541 transfer to supplier → GR 101 + 543 consumptionS: third-party with account assignment to sales orderB: limit item: overall limit 10,000, expected value 6,000, no GR ===== STEP 2: effects =====Standard stock: Dr stock Cr GR/IR | K: no value at GR | L: component consumption + finished stock

Real project scenario

A project used standard PO items for vendor-held consignment stock. Inventory and payables were overstated because goods were valued at GR. Switching to K items with consignment info records and MRKO settlement aligned stock ownership and liabilities.

Common mistakes

Standard items for consignment.
L items without components.
Limit items for regular materials.
Missing account assignment on S items.
Services as material items.

Best practices

Choose item category by ownership and flow.
Maintain special info records.
Use limits only for unplanned needs.
Train buyers per scenario.
Review postings.

Interview angle

Questions: "Which PO item categories exist?", "How does consignment differ from standard?", "When use limit items?"
Strong answer: standard, K, L, S, D, B, U with GR/IV/posting effects and appropriate use.

Practice this lesson

Quick check

1. Vendor-owned stock at your site was ordered with standard PO items. What is the correct item category?

2. Which item category is used when components are provided to a supplier who returns a finished product?

3. When is a limit item (B) appropriate?

Interview questions

1. A client on S/4HANA Public Cloud with EWM (embedded or decentralized) wants a custom field on the purchase order to trigger special putaway logic in EWM. How do you design this within Clean Core principles?

Answer it in your own words first, then compare.

2. What is a limit item in a purchase order and when would you use it instead of a standard line item with account assignment?

Answer it in your own words first, then compare.

Practice more with Interview AI →

Reference-verified: the steps are checked against official SAP documentation and tutorials, and object and field names in the sample code are checked for consistency. The code has not been compiled or run on an SAP system by ERPClimb. Syntax marked release-dependent varies by SAP release, so check it in your own system.