202
MODULE TOPICExplore the capabilities that make P2P work

PROCURE TO PAY · STRUCTURE

How is a purchase order put together?

A purchase order is not one flat record. Organizational context, shared header data, item-specific behavior, account assignments, delivery schedules, and control indicators work together to make the supplier commitment executable.

PROCESS ROLE

Structure separates shared commitment from item-specific execution

Company code, purchasing organization, and document type establish the purchasing context. Supplier and commercial terms are largely shared at header level, while each item can carry a different material or service, plant, quantity, price, delivery schedule, account assignment, and follow-on behavior.

Conceptual purchase order structure showing document type, purchasing organization, company code, supplier, purchase order, line items, material, receiving plant, account assignment, indicators, inventory, cost object, and asset.
Original Purchase Order Structure conceptual model © Benedict Yong. Reproduced with permission.The ERP Atlas model below extends this foundation by separating organizational context, header, item, schedule and account-assignment detail, and follow-on evidence for SAP S/4HANA.

DOCUMENT MODEL

One order, four connected data levels

Read downward. Put a value at the highest level where it remains true, then use item and execution detail for controlled differences.

CONTEXT

Organization and document type

Company code, purchasing organization, purchasing group, plant responsibility, and PO type establish who buys, for whom, and under which processing rules.

HEADER

Shared supplier commitment

Supplier, currency, payment terms, incoterms, document date, approval, and output context normally apply across the purchase order.

ITEM

Material or service behavior

Material or service, quantity, plant, item category, price, tax, and account-assignment category can differ by line.

EXECUTION DETAIL

Schedules, assignments, and indicators

Delivery dates and quantities, cost-object distribution, goods-receipt and invoice indicators, tolerances, confirmations, and completion status govern what can follow.

OPERATIONAL FLOW

What happens in SAP

Read the sequence as one connected business event, not as isolated transactions.

01FRAME

Establish the purchasing context

Organization, document type, supplier, and reference documents establish the eligible master data, number range, field behavior, and approval context.

02STRUCTURE

Build header and item commitment

Shared terms sit at header level while each item records its own object, quantity, price, plant, category, and accounting intent.

03CONTROL

Determine follow-on behavior

Schedules, account assignment, goods-receipt and invoice indicators, tolerances, and confirmation control determine receipt, valuation, matching, and completion.

04FOLLOW ON

Create referenced evidence

Goods receipts, service entries, supplier invoices, accounting documents, changes, and reversals retain the PO and item reference.

DESIGN & CONTROL

What shapes the result

These controls work together; a locally correct setting can still produce the wrong end-to-end outcome.

Header-level control

Document type, supplier, purchasing organization, company code, currency, payment terms, approval, and output establish the shared commitment and communication.

Item and account-assignment control

Item category, material or service, plant, quantity, price, tax, account-assignment category, G/L account, and cost object define what is purchased and where value belongs.

Schedule and indicator control

Delivery schedules, confirmations, GR required, GR-based invoice verification, non-valuated receipt, delivery-complete, final-invoice, and tolerances shape successor documents and status.

DIAGNOSTIC EVIDENCE

Diagnose at the level where the result was determined

A header, item, account-assignment, or schedule issue can produce the same blocked outcome, but the cause and owner are different.

HEADER

PO type, supplier, organization, company code, currency, terms, overall approval, output, change version, and header status.

ITEM & ASSIGNMENT

Material or service, plant, item category, quantity, conditions, tax, account-assignment category, G/L account, cost object, and distribution.

EXECUTION DETAIL

Delivery schedule, confirmation, receipt and invoice indicators, tolerances, purchasing history, open quantity and value, and completion status.

PROJECT MOMENT

One supplier, two items, different accounting

A supplier receives one PO containing ten stock-managed motors and one calibration service. The header shares supplier and commercial terms, while the motor item receives into inventory and the service item carries a cost-center assignment and requires accepted service evidence before invoicing.

  • Shared terms belong at header
  • Each item behavior is explainable
  • Accounting destination is explicit
  • Follow-on indicators match the evidence
Technical referencesSAP Help — Purchase Orders
CONTINUE THE PATHContinue to P2P 303

See how demand, sourcing, commitment, receipt alternatives, invoice matching, accounting entries, payment, and clearing connect.

Open practitioner map