Phase 10 — Release Strategy
🎯 In plain words
❓ Why it matters
Every real client wants spend controls — nobody lets staff buy unlimited amounts with no oversight. So almost every project configures release strategies, which makes this a classic configuration interview topic. If you can design and explain an approval matrix, you sound like a real consultant.
🧠 Key concepts you must know
1. It's built on Classification
A release strategy decides "which approval path applies" by looking at the document's data — and it reads that data through Classification:
- Characteristics (CT04) — the fields you trigger on, e.g. order value, plant, purchasing group, material group.
- Class (CL02) — a bundle of those characteristics. The class type for release is 032.
Think of the characteristics as the questions ("how much? which plant?") and the strategy as the answer ("then these people must approve").
2. The four building blocks
- Release group — a container that ties your strategies to a class.
- Release code — represents a person/role who approves (e.g. Manager, Director).
- Release strategy — the rule: "for this combination of values, these codes must release, in this order."
- Release prerequisites — the sequence: e.g. the Director can only approve after the Manager has.
3. With vs without classification
- Without classification — only available for PRs, and only item-by-item by simple value. Limited and largely legacy.
- With classification — flexible, can trigger on many fields, works for both PRs and POs. This is what real projects use.
4. PR release vs PO release
- PR release — approve the request to buy (can be at item or overall level).
- PO release — approve the actual order before it goes to the vendor (always at overall/header level). PO release requires classification.
5. Designing the approval matrix
This is the skill interviewers probe. You map thresholds → approvers:
- Value-based: < $1k auto, $1k–$50k Manager, > $50k Manager + Director.
- Plant-based: different approvers per plant/site.
- Material-group-based: e.g. IT purchases route to the IT lead.
Check a document's release status anytime in ME29N (and release it there too).
🛠️ Do it now — practise alongside
Don't just read — go build the workflow in your IDES. It only clicks once you've watched a document get blocked and released:
Scenario 13 — Release Strategy Advanced page — release detailsThen build a 3-level approval: small value = auto, mid value = Manager, large value = Director — and prove the Director can only release after the Manager. Watch the status flip in ME29N.
🔗 Connects to
- Phase 4 — Purchasing (PR/PO): release strategy sits on top of the PRs and POs you already create — a blocked PO can't be sent until released.
- Phase 1 — Enterprise Structure: your org levels (plant, purchasing group) are exactly the fields that drive the approval matrix.
🎓 Cert focus & quick recall
C_TS452 Purchasing area. Expect questions on the four building blocks, class type 032, and PR vs PO release differences.
Which class type is used for PO release?
Class type 032 (release strategy). You define the class in CL02 using characteristics from CT04.
What's the difference between a characteristic and a class?
A characteristic is one trigger field (e.g. order value or plant). A class bundles several characteristics together so a release group can read them.
Release code vs release strategy — what's each?
A release code represents one approver/role who signs off. A release strategy is the rule that says which codes must release (and in what order) for a given combination of values.
What causes a re-release?
Changing the document in a way that affects the strategy — typically increasing the value (or changing a field the characteristics read) past a threshold resets the release, so it must be approved again.
✅ You're ready to move on when…
- You can name the four building blocks (group, code, strategy, prerequisite) and what each does.
- You've built a working multi-level approval and watched a PO get blocked then released in ME29N.
- You can explain PR vs PO release and why PO release needs classification.