MM Purchase Requisition Part 1: The Purchase Requisition Lifecycle, Item Data and Account Assignment
The purchase requisition is the internal request to procure. Learn how PRs are created (manually, by MRP, from sales orders or projects), the key item data, document types, item categories and account assignment categories, and the PR lifecycle from creation to conversion and closing.
What this complete series covers
Learn Purchase Requisition in a clear, practical sequence — from the basic idea to real project use, troubleshooting, and interview-ready understanding.
- Who it is for
- Best for SAP consultants, developers, and learners who want a practical understanding of Purchase Requisition.
- Prerequisites
- Basic SAP S/4HANA navigation and an understanding of the business process are helpful. Configuration or transaction steps require suitable access to a practice or project system.
- Final outcome
- By the end, you should be able to explain Purchase Requisition clearly, follow the main end-to-end flow, apply it in a project scenario, and troubleshoot the most common issues.
- Part 1: MM Purchase Requisition Part 1: The Purchase Requisition Lifecycle, Item Data and Account Assignment
Understand the purchase requisition as an internal demand document whose item category, material/service data, plant, quantity, delivery date, account assignment, source and approv
- Part 2: MM Purchase Requisition Part 2: Source Determination for PRs — Source Lists, Quotas and Info Records
Understand how SAP determines candidate and preferred sources for requisitions using valid source lists, purchasing info records, outline agreements, quota arrangements, and planni
- Part 3: MM Purchase Requisition Part 3: MRP-Generated vs Manually Created Requisitions
Distinguish requisitions created from planning from manually entered demand so source determination, dates, quantities, exception analysis, and planner/buyer responsibilities are interpreted correctly.
- Part 4: MM Purchase Requisition Part 4: PR Approval — Classic Release Procedure vs Flexible Workflow
Compare classic PR release procedures with S/4HANA Flexible Workflow, including item-wise versus overall approval, business conditions, recipients, My Inbox, and migration/coexistence decisions.
- Part 5: MM Purchase Requisition Part 5: Converting PRs to POs and Troubleshooting Exceptions
Troubleshoot PR-to-PO conversion by checking release status, source, supplier/purchasing organization, document and item categories, quantities/dates, account assignment, master da
System and release assumptions: Examples focus on SAP S/4HANA. Exact apps, transaction codes, configuration paths, and field names can vary by release and deployment model.
Explanation
📌 KEY POINTS
✅ A PR is an internal request; it does not go to suppliers and has no financial posting.
✅ PRs come from users (ME51N, self-service), MRP, sales orders (third-party/individual PO), projects and maintenance orders.
✅ Item category (standard, consignment, subcontracting, third-party, service) and account assignment category (cost center K, order F, asset A, project P…) drive what happens next.
✅ Lifecycle: created → (released) → assigned source → converted to PO → closed.
⚠️ Stock material PRs without account assignment are valuated at GR; consumables need account assignment.
━━━━━━━━━━━━━━━━━━━━
▶ WHAT THIS SERIES COVERS
Part 1: PR lifecycle, item data and account assignment
Part 2: Source determination for PRs
Part 3: MRP-generated vs manual PRs
Part 4: PR approval: classic release vs flexible workflow
Part 5: Converting PRs to POs and troubleshooting exceptions
━━━━━━━━━━━━━━━━━━━━
▶ 1. CREATION
- Manual (ME51N / Fiori self-service), MRP, SD, PS, PM.
- Document type NB standard (controls number range, item categories allowed, field selection).
━━━━━━━━━━━━━━━━━━━━
▶ 2. ITEM DATA
- Material or text item, quantity, delivery date, plant, storage location, purchasing group, desired supplier.
━━━━━━━━━━━━━━━━━━━━
▶ 3. ITEM CATEGORIES
- Standard, K consignment, L subcontracting, S third-party, D service.
━━━━━━━━━━━━━━━━━━━━
▶ 4. ACCOUNT ASSIGNMENT
- K cost center, F order, A asset, P project, M/E sales order (per config).
- Determines consumption posting at GR/IV.
━━━━━━━━━━━━━━━━━━━━
▶ 5. LIFECYCLE
- Release (if strategy), source assignment, conversion to PO, processing status, closing/deletion.
━━━━━━━━━━━━━━━━━━━━
▶ STEP BY STEP
- Create a PR for a stock material and one for a consumable with cost center.
- Check processing status.
- Convert one to a PO.
✅ CHECKPOINT: you can tell for any PR where it came from, what it will post and whether it is converted.
Code example
===== STEP 1: create =====ME51N: document type NB | item: material R-100, qty 100, delivery date, plant 1000, purchasing group 001Consumable: text item "Printer toner", account assignment K cost center 4100, material group 01 ===== STEP 2: categories =====Item category: blank standard | K consignment | L subcontracting | S third-party | D serviceAccount assignment: K cost center | F order | A asset | P project (WBS) ===== STEP 3: follow-up =====ME53N processing status → ME21N with reference / ME59N automatic / Fiori Manage Purchase RequisitionsReal project scenario
A company let users create consumable PRs without account assignment. GRs posted to stock accounts for items that were never stocked, and inventory held phantom office supplies. Making account assignment mandatory for non-stock material groups and using self-service catalogs fixed postings.
Common mistakes
- Consumables without account assignment.
- Free-text items instead of materials for regular buys.
- Missing purchasing group.
- Wrong item category.
- Never closing old PRs.
Best practices
- Use catalogs/materials for regular items.
- Enforce account assignment for non-stock.
- Default purchasing groups.
- Close obsolete PRs regularly.
- Report PR aging.
Interview angle
Questions: "What is a purchase requisition?", "What are item and account assignment categories?", "How are PRs created?"
Strong answer: internal request without posting, sources (manual/MRP/SD/PS/PM), document type, item categories, account assignment categories, lifecycle to PO.
Practice this lesson
Quick check
1. A user orders office supplies without a material master. What must the PR contain so the GR posts correctly?
2. Which statement about a purchase requisition is correct?
3. Which item category is used in a PR for a subcontracting requirement?
Interview questions
1. Explain the purchase requisition lifecycle and how item and account assignment categories influence later postings.
Answer it in your own words first, then compare.
2. As solution architect, how would you design purchase requisition document types to support both self-service (employee) requisitions and centralized strategic sourcing requisitions across a multi-country S/4HANA rollout, considering downstream FI-AP posting consistency?
Answer it in your own words first, then compare.
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.
More lessons in this topic
- MM Purchase Requisition Part 2: Source Determination for PRs — Source Lists, Quotas and Info Records
- MM Purchase Requisition Part 3: MRP-Generated vs Manually Created Requisitions
- MM Purchase Requisition Part 4: PR Approval — Classic Release Procedure vs Flexible Workflow
- MM Purchase Requisition Part 5: Converting PRs to POs and Troubleshooting Exceptions
Interview questions on this topic
Related SAP topics
- S/4HANA MM Transformation, Ariba, Migration, Public Cloud and Architecture
- Invoice Verification, GR/IR, Integration and Production Support
- Procurement and End-to-End Procure-to-Pay
- Inventory Management, Valuation, Material Ledger and Account Determination
- MM Foundation, Enterprise Structure and Master Data
- Enterprise Structure