Purchase Order

Lessons in this topic

• MM Purchase Order Part 1: Purchase Order Anatomy — Header, Item, Schedule Lines and Account AssignmentThe purchase order is the legal request to a supplier. Learn its structure — header (supplier, purchasing org, currency, payment terms), items (material, quantity, price, plant), schedule lines (delivery dates), account assignment — document types, and how to create POs manually or from requisitions.
• MM Purchase Order Part 2: PO Pricing — Conditions, Info Records and Calculation SchemaHow PO prices are determined: condition technique in purchasing, calculation schema (e.g. RM0000) determined by schema groups, condition types for gross price, discounts, freight and surcharges, info record and contract conditions, price units, and common price errors.
• MM Purchase Order Part 3: Item Categories — Standard, Consignment, Subcontracting, Third-Party, Service and LimitItem 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.
• MM Purchase Order Part 4: Follow-On Processing — Confirmations, Goods Receipt and Invoice ReceiptWhat happens after the PO is sent: order acknowledgments and shipping notifications (confirmation control), goods receipt with tolerances, invoice receipt with GR-based IV, PO history, delivery completed and final invoice indicators, and how open quantities are managed.
• MM Purchase Order Part 5: Approval, Output, Change Control and TroubleshootingControl and communicate POs: release strategies or flexible workflow for approvals, output to suppliers (print, email, EDI) in classic NAST or S/4HANA output management, change management with version management and change documents, and troubleshooting when POs are blocked, not sent or wrong.

Interview questions covered

• How does the purchasing document type influence output determination for purchase orders?
• You are migrating purchase order and output configuration data as part of an S/4HANA transformation, and the target landscape uses SAP BTP Integration Suite for supplier-facing output distribution instead of classic EDI middleware. What migration objects and integration design considerations must you address?
• A client on S/4HANA Public Cloud wants purchase order output (print/email/PDF) to be automatically triggered and routed through a supplier collaboration channel via Central Procurement. What output management approach and constraints should you explain given the Public Cloud restrictions on classic output configuration?
• As part of an S/4HANA transformation, output management for purchase orders must be migrated from classic NAST-based forms to a BRF+/Adobe Forms setup integrated with SAP BTP Integration Suite for supplier delivery. What key design decisions must be made?
• In an S/4HANA Public Cloud implementation following clean core principles, output for sales-order-driven procurement (e.g., third-party PO triggered from SD) fails intermittently, and the team wants to avoid a core modification fix. How would you troubleshoot and resolve this within clean core constraints?
• As an architect, how would you evaluate whether limit items should be permitted on a given purchase order document type, and what governance and document type design decisions mitigate the risk of uncontrolled spend?
• In S/4HANA Public Cloud, which Fiori app do procurement teams use to monitor the integration status of purchase orders sent to a connected FI/accounting backend or supplier system, and what does it show?
• What is a limit item in a purchase order and when would you use it instead of a standard line item with account assignment?
• What document type considerations apply when creating a returns purchase order for a vendor return in SAP MM, and how does this differ from a standard purchase order document type?
• What is the functional difference between a value contract and a quantity contract in SAP MM, and how do release orders reference them?
• A client with Central Procurement hub wants purchase order output (email/print) triggered consistently whether the sourcing PO originates from a connected S/4HANA on-premise back end or a Public Cloud back end. What output management approach and design considerations apply?
• You are designing the open PO migration approach for an S/4HANA Public Cloud rollout where EWM-managed warehouses are involved. What migration objects and sequencing considerations are critical for open POs that have partial goods receipts already posted in the legacy system?
• 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?
• Walk through the end-to-end process and document type considerations for handling a vendor return that requires both a returns purchase order and financial reversal of an already-settled invoice.
• A vendor's purchase order output was transmitted via EDI (message type ORDERS) but never reached the vendor due to an interface failure, and goods are needed urgently. Walk through the fallback and reissue process to get the PO to the vendor without creating a duplicate order.
• During hypercare, SD-triggered third-party sales order processing is generating purchase requisitions whose output-triggered vendor confirmations are not being sent, even though the PO output configuration tested fine before go-live. What extensibility and troubleshooting steps would you take?
• During an S/4HANA Public Cloud go-live, several thousand open purchase orders linked to production orders (PP) must be migrated with partially delivered quantities and pending goods receipts. What migration strategy would you design to preserve PP-MM linkage and prevent duplicate postings post go-live?
• During a P2P migration using Migration Cockpit, output determination for purchase orders (forms/emails) is not working correctly after cutover even though PO data migrated successfully. What is the likely cause and how would you resolve it?
• Design a purchase order output architecture for a multi-country S/4HANA rollout where legal requirements mandate different PO document layouts and delivery channels (email, EDI, print) per country, while maintaining a single global output determination strategy.
• Explain the structure of a purchase order and which master data provide its defaults.

Related topics

Interview questions on this topic

• SAP MM / P2P Purchase Order interview questions
• SAP MM / P2P interview questions