PROCURE TO PAY · DETERMINE
How do conditions, confirmations, workflow, and output shape a purchase order?
A valid supplier and material do not fully explain a purchase order. SAP must determine commercial value, expected supplier responses, approval authority, and the controlled communication sent outside the company.
PROCESS ROLE
Four mechanisms turn a PO into a governed commitment
The purchasing condition technique builds price and planned costs. Confirmation control defines expected supplier evidence. Workflow controls authority and restart behavior. Output management determines what is sent, to whom, through which channel, and when.
DETERMINATION MODEL
Four decisions before execution
Read left to right. Each mechanism has different master data, configuration, status, and troubleshooting evidence.
Condition technique
Calculation schema, condition types, access sequences, condition tables, schema groups, info records, contracts, and condition records build the effective purchase value.
Confirmation control
Confirmation categories and control keys define whether acknowledgements, shipping notifications, inbound deliveries, dates, and quantities are expected or relevant.
Workflow or release
Flexible workflow or an approved classic release strategy determines approvers, thresholds, sequence, restart, rejection, and evidence.
Output determination
S/4HANA Output Parameter Determination or classic message control selects output type, receiver, channel, form, language, dispatch time, and processing status.
OPERATIONAL FLOW
What happens in SAP
Read the sequence as one connected business event, not as isolated transactions.
Determine the calculation schema
Supplier and purchasing-organization schema groups select the purchasing calculation schema; condition types then search eligible records through their access sequences.
Define expected supplier evidence
Purchasing value keys, reminders, confirmation categories, and confirmation-control keys establish which dates, quantities, acknowledgements, or inbound deliveries matter.
Select one authority model
Configure flexible workflow for the target S/4HANA scope or retain a deliberately approved classic release strategy; never blend their assumptions.
Determine and process output
Choose the release-appropriate output framework, determine recipient and channel, generate the form or message, dispatch it, and retain processing evidence.
DESIGN & CONTROL
What shapes the result
These controls work together; a locally correct setting can still produce the wrong end-to-end outcome.
Purchasing conditions
M/08 calculation schemas, M/06 condition types, access sequences, schema groups and determination, pricing dates, scales, freight, taxes, condition records, and manual-condition policy explain the net and effective price.
Confirmations and tolerances
Purchasing value keys, reminder days, confirmation categories, confirmation-control keys, inbound-delivery relevance, date and quantity checks, and GR tolerance align the supplier promise with execution.
Release and output boundary
Flexible workflow and classic release are alternatives with different configuration and runtime evidence. OPD/BRF+ output and NACE/MN04 message control are likewise release-dependent branches.
DIAGNOSTIC EVIDENCE
Trace the mechanism that produced the PO result
A wrong price, missing acknowledgement, repeated approval, or failed output has a different determination chain.
Schema groups, calculation schema, condition type, access sequence, accessed condition record, validity, scales, currency, pricing date, manual changes, and planned delivery costs.
Purchasing value key, confirmation-control key, expected categories, acknowledgement and inbound-delivery status, active workflow, start conditions, recipients, decisions, and restart.
Framework, output type, receiver, channel, form template, language, dispatch time, application log, generated content, send result, and change output.
PROJECT MOMENT
The PO is approved but the supplier receives the wrong value
A contract price is valid, but a manual condition and planned freight change the effective value. The buyer traces the calculation schema and condition origin, confirms the approval restart policy, then verifies the correct output request and form before reissuing the commitment.
- Price source is traceable
- Supplier response is defined
- Authority matches final value
- Output content and status agree
See how demand, sourcing, commitment, receipt alternatives, invoice matching, accounting entries, payment, and clearing connect.