MM / P2Padvanced

MM Release Strategy Part 2: Migrating Classic Release Strategy to Flexible Workflow

Key takeaway

Move from classic release to S/4HANA flexible workflow: analysing existing strategies, simplifying approval policy, mapping characteristics to workflow conditions and codes to agents, activation per document type, handling open documents at cutover, and testing.

Explanation

📌 KEY POINTS
✅ Analyse strategies: characteristics used, value bands, approvers, real approval patterns.
✅ Map characteristics to flexible workflow start conditions and release codes to steps with agents.
✅ Activate flexible workflow per document type; classic release must not stay active for the same type.
✅ Open documents in approval need a cutover plan (approve before switch or re-trigger).
⚠️ One-to-one copying of dozens of strategies wastes the chance to simplify.

━━━━━━━━━━━━━━━━━━━━
▶ WHERE WE ARE
Part 1 covered classic release. Now migration.

━━━━━━━━━━━━━━━━━━━━
▶ 1. ANALYSIS

Strategies, classification values, codes, users; usage statistics.

━━━━━━━━━━━━━━━━━━━━
▶ 2. POLICY SIMPLIFICATION

Few value bands, role-based approvers, auto-approval below threshold.

━━━━━━━━━━━━━━━━━━━━
▶ 3. MAPPING

Characteristics → conditions; codes → steps and agents.

━━━━━━━━━━━━━━━━━━━━
▶ 4. ACTIVATION AND CUTOVER

Per document type; handle documents in approval.

━━━━━━━━━━━━━━━━━━━━
▶ 5. TESTING AND TRAINING

Threshold tests, substitutes, My Inbox usage.

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

Export strategies and approver lists.
Agree new policy.
Configure workflows and activate for one document type.
Test and roll out.

✅ CHECKPOINT: approval coverage is equal or better with far fewer rules.

Code example

ABAP Code

===== STEP 1: mapping example =====Classic: 24 strategies (value bands × plants × doc types) | codes per personFlexible: 4 workflows: <10k auto | 10–100k: step purchasing group lead | >100k: + finance director | category capex: + asset manager ===== STEP 2: activation =====Activate flexible workflow for PO document type NB (SPRO > MM > Purchasing > Purchase Order > Flexible Workflow)Remove release strategy relevance for NB ===== STEP 3: cutover =====Approve open POs before switch or re-trigger workflow after activation

Real project scenario

A rollout enabled flexible workflow but left classic release strategies active for the same document types. Some POs followed both logics and got stuck. The team deactivated classic release for switched types, re-triggered affected POs and added a coexistence check to the transport checklist.

Common mistakes

Leaving both active.
1:1 mapping.
No plan for open documents.
Person-based agents.
Insufficient testing.

Best practices

Simplify policy first.
Switch per document type.
Plan cutover for open items.
Use role-based agents.
Test thresholds and substitutes.

Interview angle

Questions: "How do you migrate release strategies to flexible workflow?", "What happens to open POs?", "Can both run together?"
Strong answer: analysis, simplification, mapping to conditions/agents, per-type activation, cutover of open documents, testing.

Practice this lesson

Quick check

1. Contract release orders for a global services contract are failing with document type incompatibility errors after a document type restriction change. How would you diagnose and resolve this? Choose the response that best aligns with the expected SAP approach.

2. How would you configure release strategy and workflow integration for external services procurement so that both the service purchase order and its subsequent service entry sheet are subject to appropriate approval before invoice posting? Choose the response that best aligns with the expected SAP approach.

3. You are designing a global release strategy architecture spanning multiple purchasing document types (PR, PO, contract, scheduling agreement) across regions with different approval hierarchies. What architectural considerations determine whether to use a single shared classification structure or separate strategies per document type? Choose the response that best aligns with the expected SAP approach.

Interview questions

1. In a Central Procurement (S/4HANA hub) landscape, a requester in a connected ECC backend raises a requisition for external services, which is centrally sourced and converted into a PO in the hub. The backend business team asks why the release strategy triggered in the hub differs from what they expect based on the backend's approval hierarchy. How would you explain this and what would you check?

Answer it in your own words first, then compare.

2. You are designing a global release strategy architecture spanning multiple purchasing document types (PR, PO, contract, scheduling agreement) across regions with different approval hierarchies. What architectural considerations determine whether to use a single shared classification structure or separate strategies per document type?