MM / P2Pintermediate

MM Flexible Workflow Part 2: Architecture and Supported Purchasing Scenarios

Key takeaway

How flexible workflow is built: scenario definitions per business object, workflow templates, BRF+-based condition evaluation, agent rules, integration with My Inbox and notifications — and which purchasing documents support it (requisitions, orders, contracts, scheduling agreements, RFQs, quotations, service entry sheets, supplier invoices per release).

Explanation

📌 KEY POINTS
✅ Each supported business object has a flexible workflow scenario delivered by SAP.
✅ Workflow definitions (created in Fiori) sit on top of scenarios: conditions, steps, agents.
✅ Supported purchasing documents include requisitions, orders, contracts, scheduling agreements and more (check release).
✅ Technical prerequisites: workflow runtime configured, event linkages active, My Inbox set up.
⚠️ Missing workflow runtime setup makes all workflows fail silently.

━━━━━━━━━━━━━━━━━━━━
▶ WHERE WE ARE
Part 1 introduced the concept. Now architecture and scope.

━━━━━━━━━━━━━━━━━━━━
▶ 1. SCENARIOS

SAP-delivered per object (PR, PO, contract, scheduling agreement, RFQ, quotation, invoice…).

━━━━━━━━━━━━━━━━━━━━
▶ 2. DEFINITIONS

Business-created: conditions, steps, agents, order of workflows.

━━━━━━━━━━━━━━━━━━━━
▶ 3. RUNTIME

Workflow engine, event linkage, background user.

━━━━━━━━━━━━━━━━━━━━
▶ 4. APPROVER EXPERIENCE

My Inbox, notifications, mobile.

━━━━━━━━━━━━━━━━━━━━
▶ 5. EXTENSIBILITY

Custom conditions and agent rules via BAdIs (per release), clean core.

━━━━━━━━━━━━━━━━━━━━
▶ STEP BY STEP

Check workflow runtime setup.
List scenarios available for your release.
Define which documents need approval.

✅ CHECKPOINT: every approval-relevant document has a scenario and definition owner.

Code example

ABAP Code

===== STEP 1: prerequisites =====Workflow runtime customizing (e.g. SWU3 / automatic workflow customizing) | event linkages active | My Inbox roles ===== STEP 2: scope examples =====Purchase requisition | purchase order | central contracts | scheduling agreements | RFQ | supplier quotation | service entry sheet | supplier invoice (per release) ===== STEP 3: extensibility =====Custom conditions/agent rules via released BAdIs; avoid modifications

Real project scenario

After go-live, no PO workflows started although definitions were active. Workflow runtime customizing had not been executed in production. Running the runtime setup, activating event linkages and adding them to the cutover checklist fixed approvals within hours.

Common mistakes

Skipping runtime setup.
Assuming all documents are supported.
Custom code instead of released BAdIs.
No notification setup.
No owner per scenario.

Best practices

Include runtime setup in cutover.
Check scope per release.
Use released extension points.
Configure notifications.
Assign scenario owners.

Interview angle

Questions: "Which documents support flexible workflow?", "What are the technical prerequisites?", "How is it extended?"
Strong answer: scenarios per object, business definitions, runtime and event linkage, My Inbox, BAdI-based extensibility.

Practice this lesson

Quick check

1. Which of the following is NOT a purchasing document type for which SAP delivers a standard Flexible Workflow approval scenario?

2. In SAP Flexible Workflow for purchasing documents, which technology is primarily used to define approval conditions (e.g., value thresholds) without requiring custom ABAP development?

3. Which technical prerequisite must be completed for any flexible workflow to start?

Interview questions

1. In an SAP Ariba Buying integration where purchase requisitions require flexible approval workflows before PO creation in S/4HANA, what governance controls must the solution architect design to prevent duplicate or unauthorized PO creation?

Answer it in your own words first, then compare.

2. A global rollout uses MDG for vendor master governance feeding S/4HANA, and Flexible Workflow-driven PO output (email with PDF) intermittently fails only for newly created vendors replicated from MDG. Approvals work fine, but output determination silently skips. What is your troubleshooting approach?

Answer it in your own words first, then compare.

Practice more with Interview AI →

Reference-verified: the steps are checked against official SAP documentation and tutorials, and object and field names in the sample code are checked for consistency. The code has not been compiled or run on an SAP system by ERPClimb. Syntax marked release-dependent varies by SAP release, so check it in your own system.