Guides / SAP & ERP

SAP business process diagrams: O2C, P2P & R2R flowcharts for S/4HANA

An SAP business process diagram visualizes how a financial or operational flow — Order-to-Cash (O2C), Procure-to-Pay (P2P), Record-to-Report (R2R) — runs through S/4HANA. The diagram captures every transaction code, document type, user role, and control point that auditors, implementers, and operators need to reference.

Order-to-Cash (O2C) in S/4HANA

The standard O2C flow in S/4HANA touches Sales (SD), Distribution (LE/WM), Finance (FI), and Controlling (CO). The diagram captures:

  1. Inquiry & quotation (VA11 / VA21)
  2. Sales order (VA01) — credit check, ATP, pricing
  3. Delivery (VL01N) — picking, packing
  4. Goods issue — automatic FI posting
  5. Billing (VF01) — invoice generation
  6. Accounts receivable posting (automatic from billing)
  7. Cash application (F-28 or lockbox automation)

Each transaction is a labeled box in the swimlane diagram, mapped to its responsible role and the SAP module that owns it.

Procure-to-Pay (P2P) process flow

P2P touches Materials Management (MM) and Finance (FI):

  1. Purchase requisition (ME51N)
  2. Source determination & RFQ (optional)
  3. Purchase order (ME21N) with release strategy
  4. Goods receipt (MIGO) — three-way match begins
  5. Invoice receipt (MIRO) — three-way match completes
  6. Payment run (F110)

Mark the three-way match (PO + GR + IR) as a key SOX control on the diagram. Block GR / IR mismatches need an exception path drawn.

Record-to-Report (R2R) close cycle

R2R is the financial close — typically 5–10 business days, fully diagrammed by day:

  1. Sub-ledger close (AR, AP, AA)
  2. Accruals & provisions (manual JEs with approval workflow)
  3. Intercompany reconciliation (ICR)
  4. Foreign currency revaluation (FAGL_FCV)
  5. Allocations & assessments (CO-OM)
  6. General ledger close
  7. Consolidation (Group Reporting or BPC)
  8. Disclosure & analytics

Manual journal entries should be flagged distinctly — they're the highest-risk step in the close from a controls perspective.

BPMN 2.0 for SAP implementations

Many SAP partners (Capgemini, Accenture, Deloitte) use BPMN 2.0 for blueprint documentation. BPMN's strength is precise event/gateway semantics; its weakness is the learning curve for operators. A pragmatic middle ground: use BPMN for the design phase (handed to the SI team) and swimlane flowcharts for the operate phase (used by business users and auditors).

Signavio vs. manual mapping

SAP Signavio is the official process mining and modeling platform — strong for large transformations because it mines actual transaction data and surfaces process variants. The downside is licensing cost and ramp-up time. For SMB customers and simpler SOX documentation needs, spreadsheet-driven swimlane tools like Querychart deliver comparable diagram quality without the platform overhead.

Worked example: vendor invoice flow

A SOX-grade vendor invoice flow inside SAP includes:

  1. Invoice received (paper, EDI, or e-invoice portal)
  2. Invoice posted in MIRO — automatic three-way match attempt
  3. Decision: match successful? — if no, parked for resolution (MIR4)
  4. Resolution: GR correction, PO change, or invoice query to vendor
  5. Released for payment (workflow approval if blocked)
  6. Payment run F110

Key controls: PO release strategy (preventive), three-way match (preventive), payment proposal review (detective), exception aging report (detective).

Frequently asked questions

What's the best way to document SAP processes for SOX?

Map each in-scope process as a swimlane flowchart with transaction codes, document types, and SOX control IDs on every key-control box. Pair it with a narrative and risk-and-control matrix that uses identical control IDs. Auditors should be able to read the flowchart and the RCM side by side without translation.

Do I need to redraw process diagrams when moving from ECC to S/4HANA?

Yes. S/4HANA collapses several ECC transactions (the universal journal merges FI and CO posting; MIGO/MIRO logic changed; new Fiori tile workflows replace some classic transactions). The to-be process diagram becomes a deliverable of the migration project, often the longest-lived artifact from the implementation.

BPMN vs. flowchart for SAP documentation?

BPMN is precise but takes training to read. Flowcharts and swimlane diagrams are accessible to anyone. A practical compromise: BPMN for implementation blueprints (audience: SI consultants) and swimlane flowcharts for operate-phase documentation (audience: users, auditors, support teams).

How granular should an SAP process diagram be?

One process per diagram (O2C, P2P, R2R, etc.) at 15–30 boxes — granular enough to show every key control and every transaction code, but not so granular that you're documenting individual field-level steps. Sub-diagrams handle the detail when needed (e.g., 'Credit management' as a sub-diagram of O2C).

Can I generate SAP process diagrams from a spreadsheet?

Yes. Querychart accepts a structured spreadsheet — one row per step with columns for SAP T-code, role, document type, control ID, decision outcome — and renders the swimlane diagram automatically. Updating a transaction code or control owner is a single-cell edit, and the diagram refreshes without redrawing.

Can I generate these diagrams from a spreadsheet?

Yes. Querychart turns a structured spreadsheet (one row per step, with role, action, and decision columns) into a connected swimlane flowchart automatically. When the process changes, you edit the row and the diagram updates — no manual redrawing.

Generate your SAP process flowchart from a spreadsheet in Querychart →