Quartz 4

Purchase_Order

2 min read

Purchase Order

What is this?

A Purchase Order (PO) is a formal document sent from a company to a supplier requesting goods or services.

It specifies:

  • What to buy
  • How much
  • At what price
  • When to deliver

In SAP S/4HANA, this is the central procurement document.

Why it exists?

The PO exists to:

  • Formalize a purchase agreement
  • Ensure supplier accountability
  • Trigger downstream processes (GR, Invoice, Payment)

Without a PO: → Procurement becomes uncontrolled
→ Finance loses traceability

Structure

A Purchase Order has two main levels:

1. Header (overall info)

  • Supplier (Business Partner)
  • Company Code
  • Purchasing Organization
  • Payment terms

2. Item (line-level info)

  • Material / Service
  • Quantity
  • Price
  • Delivery date
  • Plant

Each PO can have multiple items.

Key Organizational Context

A PO is NOT standalone.

It is controlled by:

Purchasing Organization

  • Responsible for procurement activities
  • Negotiates terms with suppliers :contentReference[oaicite:0]{index=0}

Company Code

  • Financial entity

Plant

  • Where goods are delivered

In Oracle

Typical representation:

  • Purchase Order tables
  • Line items stored separately
  • Less tightly coupled with downstream processes

Key issue: → Often treated as static data

In S/4HANA

  • PO is part of a process chain
  • Directly linked to:
    • Goods Receipt
    • Invoice Verification
    • Accounting entries

System enforces: → PO → GR → Invoice consistency

SAP treats PO as:

an instruction to a supplier to deliver goods/services at defined terms :contentReference[oaicite:1]{index=1}

Mapping Logic

→ PO_Mapping

Core idea:

  • Oracle PO → SAP PO (but stricter structure)
  • Missing context (org units, BP) must be derived

Process Impact

Used in:

→ P2P_Procure_to_Pay

Specifically:

  • Trigger for Goods Receipt
  • Reference for Invoice Verification
  • Basis for payment

Without valid PO: → No GR
→ No Invoice
→ No Payment

Validation

→ Transactional_Validation

Critical checks:

  • Supplier exists as BP
  • Material exists
  • Org structure valid (Plant, Company Code)
  • Price & quantity consistency

Common Issues

→ Material_Issues

Typical failures:

  1. Missing Purchasing Organization
  2. Incorrect supplier mapping
  3. Invalid plant assignment
  4. Price mismatches
  5. Unit of measure inconsistencies

Key Takeaway

A Purchase Order is NOT just a record.

It is: → A legally and operationally binding instruction

If your PO is wrong: → Every downstream step fails (GR, Invoice, Payment)

And SAP will not quietly accept bad data like Oracle sometimes does.

Backlinks