Quick Answer — Release Strategy Not Triggering
- A release strategy does not trigger when the document's values do not match any configured strategy's classification. SAP reads specific fields from the purchasing document and compares them to the values set in OMGS — one mismatch and no strategy fires.
- The five causes are: classification values in OMGS don't match the document; characteristics in CT04 reference wrong fields; class in CL02 not correctly assigned; release group not assigned to the document type; or changeability settings reset the status unexpectedly.
- The diagnostic sequence is: OMGS → CT04 → CL02. Check the release group assignment first, then the characteristic field references, then the class assignment and classification values.
- After fixing configuration, re-save the document to trigger re-determination of the release strategy. SAP determines the strategy at save time — refreshing the screen is not enough.
- This applies to both POs and PRs — the configuration is separate (OMGS for POs, different SPRO node for PRs) but the diagnostic logic is identical.
Symptoms you may see:
No Release Strategy tab visible on the PO header in ME23N
No Release button appearing in ME21N or ME22N
"Release strategy could not be determined" in the message log
PO saves without any approval requirement (no strategy = no approval gate)
Release tab present but only some release codes offered (partial match)
Diagnose before you change config. Compare the PO's actual values (from ME23N) against the strategy's classification values in OMGS before touching anything. One mismatch found in 5 minutes beats 30 minutes of trial-and-error config changes.
The release group is the first gate. If no release group covers the PO document type, SAP does not even begin determination. Check this in OMGS first — it eliminates one of the five causes immediately.
CT04 characteristic field references are the hardest to spot. A characteristic pointing to the wrong field in CEKKO reads blank — and blank never matches. The config looks complete from OMGS; the break is one level deeper.
Re-save the document after fixing config. SAP determines the release strategy at save time. Refreshing the screen or pressing Enter is not enough — you must trigger a save in ME22N to get the updated determination.
Transport config changes — never change directly in production. OMGS, CT04, and CL02 changes are client-dependent configuration. Test in DEV, transport to QA, transport to PRD. A misconfigured strategy can silently allow POs to bypass approval.
How SAP Release Strategy Determination Works
When you save a purchase order in ME21N, SAP does not just store the data — it runs a release strategy determination routine. It reads a set of values from the document (the total net value, the document type, the purchasing organisation, the purchasing group, the plant) and compares them against the classification values you have set up in the release strategy configuration.
This determination uses SAP's classification system. The values SAP reads come from a communication structure — CEKKO for purchase orders and CEBAN for purchase requisitions. These are not the actual database tables where POs are stored; they are temporary in-memory structures that SAP populates at save time specifically for release strategy determination. Your characteristics in CT04 must point to the right field in the right structure — otherwise SAP reads a blank and nothing matches.
Plain English explanation. Imagine the release strategy as a set of rules: "Any PO worth more than CA$10,000, from purchasing organisation ORCA, document type NB, must be approved by two managers." SAP checks your PO against those rules when you save it. If the PO is worth CA$9,999.99, or uses purchasing org ORCC instead of ORCA, or is document type UB instead of NB — the rules don't match, no approval is required, and the PO saves without a Release tab. That is the bug. The fix is always in the rules — either the rules are wrong (OMGS), or the way SAP reads the values to check against the rules is wrong (CT04, CL02).
The Determination Chain — Where Each Break Causes the Error
| Component | Transaction | What It Does | Break Causes |
|---|---|---|---|
| Release Group | OMGS | Assigns document types (e.g. NB) to the release procedure and links the class type (032 for PO) | No strategy fires at all |
| Release Strategy | OMGS | Defines which release codes are required and the classification values that trigger this specific strategy | Wrong or no strategy selected |
| Characteristics | CT04 | Defines how SAP reads each value — which field (GNETWR, BSART, EKORG) from which structure (CEKKO) | SAP reads blank/wrong value |
| Class | CL02 | Groups the characteristics together (class type 032) and is assigned to the release group | Strategy not linked to group |
| Classification Values | OMGS | The actual values (e.g. value range 10000–99999, doc type NB) that a document must match to trigger this strategy | Document value outside range |
| Changeability | OMGS | Controls whether changing the PO after release resets the approval status | Unexpected release reset |
5 Root Causes of Release Strategy Not Triggering
Work through these causes in order. Start with the release group (cause 1) because it is the most common and the quickest to check. Only move to CT04 and CL02 if the release group setup looks correct.
Do not skip the diagnostic step. Jumping straight to making changes in OMGS without confirming which cause applies often creates new problems. Take 10 minutes to compare the PO's actual values (from ME23N header) against the classification values in OMGS before touching any configuration. Transport implications: changes in OMGS, CT04, and CL02 in a production system require a transport request — test in a development client first.
Step-by-Step: Diagnosing and Fixing the Error
Follow this sequence exactly. Each step either confirms the component is working or identifies the break point. Stop at the first break — fix it, re-test, and confirm before moving to the next step.
Common mismatches: value just below the lower threshold; document type code has a typo; purchasing org is correct but the characteristic uses an AND condition that also requires the purchasing group to match and that field is wrong. Fix each mismatch in OMGS classification.
• Value characteristic: Table = CEKKO, Field = GNETWR
• Document type: Table = CEKKO, Field = BSART
• Purchasing org: Table = CEKKO, Field = EKORG
• Purchasing group: Table = CEKKO, Field = EKGRP
If any Table or Field is blank or wrong, SAP reads nothing for that characteristic and classification fails. Update and save. Changes to characteristics in CT04 require a transport in production systems.
Check the result in ME23N — the Release Strategy tab should now be visible at the header. If it is, the fix is confirmed. If not, return to step 2 and re-check — the most common remaining cause is a classification value that still does not match.
Transport reminder for production systems: Changes in OMGS, CT04, and CL02 are client-dependent configuration changes. In a three-system landscape (DEV → QA → PRD), you must make the fix in DEV, transport it to QA for testing, and then transport to PRD. Never make release strategy changes directly in production — a misconfigured strategy can allow POs above your approval threshold to bypass approval entirely.
Changeability — Why Your Release Resets After a PO Change
A separate but related issue: the release strategy triggered correctly, the PO was approved — and then someone changed the quantity or delivery date, and suddenly the PO is back to awaiting release. This is controlled by the changeability setting in OMGS.
- 0 — Not changeable: once released, the PO cannot be changed at all. Strictest setting — rarely used in practice.
- 1 — Changeable, no new release needed: any change is allowed, release status is preserved. Least secure — a value increase after approval bypasses re-approval.
- 2 — Changeable, new release if value increases: changes that increase the total value above the strategy threshold reset the release. Value decreases and non-value changes are allowed.
- 3 — Always new release if changed: any change to the PO resets all release codes. Most common in audit-sensitive environments.
- For most organisations: option 2 (new release if value increases) balances control with practicality — minor admin changes don't need re-approval.
- For SOX or audit-intensive environments: option 3 (always new release) — any change requires full re-approval.
- For framework orders with fixed prices: option 1 can be acceptable if the agreement is already audited.
- For low-risk categories with single approvers: option 2 is standard.
The most dangerous setting is option 1 with a high-value release threshold. It means an approver can release a CA$50,000 PO, and a buyer can then increase the value to CA$500,000 with no further approval. This is a common SAP audit finding. If your organisation has SOX obligations or internal audit requirements, use option 2 or 3.
Related SAP MM Errors and Guides
Once the release strategy triggers and the PO is approved, the next step is goods receipt — where a different set of errors can appear. These guides cover the most common ones in sequence.
SAP Release Strategy Not Triggering — 21 Questions Answered
A SAP release strategy does not trigger when the document's characteristic values do not match any configured release strategy. The five most common causes are: (1) the classification values in OMGS do not match the actual values in the PO (total value, document type, purchasing org, group); (2) characteristics in CT04 reference the wrong communication structure or field; (3) the release group is not assigned to the PO document type; (4) the class in CL02 uses the wrong class type or missing characteristics; (5) the document was previously released and changeability settings prevent re-determination.
A release strategy is SAP's approval workflow for purchase orders and purchase requisitions. It determines who must approve a document before it can proceed. The strategy is assigned automatically based on the document's values — total value, document type, purchasing org — matched against classification rules configured in OMGS. When a strategy is found, a Release tab appears and the document waits for the configured approvers to release it using their release codes (via ME28 for POs, ME54N for PRs).
Release strategy with classification (configured in OMGS for POs) uses SAP's classification system — characteristics, classes, and values — to determine which strategy applies. This is the standard and most flexible approach. Release strategy without classification uses simpler value-based rules without the full classification framework, typically for PRs in older configurations. Mixing the two approaches — applying a classification strategy to a document type that expects the non-classification approach — causes strategies not to trigger. For modern S/4HANA implementations, use classification for both POs and PRs.
OMGS is the SAP configuration transaction for the release procedure for purchase orders with classification. Menu path: SPRO > Materials Management > Purchasing > Purchase Order > Release Procedure for Purchase Orders > Define Release Procedure with Classification. In OMGS you define: release groups (which document types the procedure covers), release codes (who approves), release indicators (post-release status), release prerequisites (which codes approve in what order), changeability (what happens when the PO is changed after release), and the classification values that trigger each strategy.
CEKKO is the communication structure for purchase orders — it holds the values SAP reads at save time for release strategy determination: GNETWR (total net value), BSART (document type), EKORG (purchasing org), EKGRP (purchasing group), WERKS (plant), KNTTP (account assignment). CEBAN is the equivalent structure for purchase requisitions. Characteristics in CT04 must reference the correct field in CEKKO (for PO) or CEBAN (for PR). A wrong structure reference causes SAP to read blank values — and blank never matches any classification value.
In ME23N, go to the header and check the Release Strategy tab if it exists. To see raw values: from the PO header in ME23N, note the total net value (sum all lines), document type, purchasing org, purchasing group, and plant. These are the values CEKKO is populated with at save time. Compare them exactly against the classification values in OMGS. Even a one-unit difference in total value, or a one-character difference in a code field, will prevent the strategy from triggering.
GNETWR is the field in communication structure CEKKO that holds the total net value of a purchase order — the sum of all line items before tax. When you configure a value-based release strategy (trigger for POs above CA$10,000), the value characteristic in CT04 must reference Table CEKKO and Field GNETWR. If the characteristic points to a different field or a different structure, SAP reads zero or blank for the value, and the strategy never triggers regardless of the PO's actual total value.
This means the strategy is correctly configured but one or more values on the specific PO fall outside the classification rules. Common scenarios: a new purchasing group was created but not added to the strategy's classification; a PO uses document type UB (stock transport order) which is not covered by any release group; the total value is just below the lower threshold; or the plant on the PO was not included in the plant characteristic values. Compare a PO that triggers correctly with one that does not — the difference in their values reveals the gap in the classification.
A release group is the top-level grouping in the OMGS release strategy configuration. It defines which document types (e.g. NB for standard PO, FO for framework order) are subject to the release procedure, and links the classification class type (032 for PO). If no release group covers a document type, no strategy will ever trigger for POs of that type — SAP does not even begin determination. A release group can contain multiple strategies — one for low-value POs (one approver) and one for high-value POs (two approvers).
A release code is the identifier for an individual approver role — for example, code 01 for a purchasing manager, 02 for a finance controller. Each release code is assigned to one or more SAP user IDs via the user master (SU01) or through authorisation objects. A user can only release documents using the code assigned to their user ID. ME28 (Release Purchase Orders) is the bulk release transaction for POs; ME54N handles individual PR release.
Individual: open the PO in ME23N, go to the Release Strategy tab, and click Release. You can only release with the code assigned to your user ID. Bulk release: use ME28 — enter selection criteria, execute, select the POs requiring your release code, and click Release in one step. For purchase requisitions, the equivalent is ME54 (single) or ME55 (mass). After all required release codes approve, the release indicator changes to fully released and the PO can proceed to goods receipt.
This depends on the changeability setting in OMGS: 0 — not changeable (PO locked after release); 1 — changeable, no new release (any change allowed, status preserved); 2 — new release if value increases (only a value increase above the threshold resets approval); 3 — always new release if changed (any change resets all release codes). Most organisations use option 2 or 3. If the release is resetting unexpectedly after minor changes, check which option is set on the strategy in OMGS.
Yes — but PR release is configured separately. PR release: SPRO > Materials Management > Purchasing > Purchase Requisition > Release Procedure > Procedure with Classification (class type 033, communication structure CEBAN). PO release: OMGS (class type 032, structure CEKKO). Many organisations implement both — PRs are approved by requestors' line managers before a buyer converts them to POs, then POs are approved by purchasing managers. Each uses its own characteristics, classes, and release groups.
Class type 032 is the SAP classification class type used specifically for purchase order release strategies. Class type 033 is for purchase requisitions. When you create the class in CL02 that will be linked to your PO release group in OMGS, the class must be type 032. Using type 033 for a PO release will cause the strategy to never trigger — SAP looks for a class type 032 class and finds nothing. The class type is set on the first screen of CL02 and cannot be changed after creation.
Go to CT04 and open the characteristic. On the Basic Data tab, find the Additional Data section. Check: Table Name = CEKKO (for PO characteristics) and Field Name = the exact field name (GNETWR for value, BSART for document type, EKORG for purchasing org, EKGRP for purchasing group, WERKS for plant). If either field is blank or points to a different structure, SAP reads a blank value for that characteristic during determination. Update and save in CT04, then re-test by saving the PO in ME22N.
This message appears when SAP finds a release group that covers the document type (so it begins determination) but cannot find any strategy within that group whose classification values match the document. It is different from a document having no release group at all (in which case no message appears). Fix: open OMGS, check all strategies within the relevant release group, and compare their classification values to the document's actual values. The document's values must match at least one strategy exactly.
Yes — but only with the authorisation object M_EINK_FRG (Release of Purchasing Documents) with activity 02. This allows bypassing the release procedure entirely and is typically given only to system administrators for emergency situations. In normal operations, bypassing the release is a controls failure and a common SAP audit finding. If your organisation has SOX or internal audit obligations, bypass access should be tightly restricted and all uses logged.
ME28 is the SAP transaction for releasing purchase orders in bulk. You enter selection criteria — purchasing org, purchasing group, document type, value range, creation date — and the system lists all POs that require your release code. Select and release in one step. It is the standard daily tool for purchasing managers who approve multiple POs. For individual release, ME23N (display PO > Release Strategy tab > Release) is more practical. ME54 (single) and ME55 (mass) are the PR equivalents.
Yes — the configuration (OMGS, CT04, CL02) and determination logic are identical between ECC and S/4HANA. Communication structures CEKKO and CEBAN are unchanged. Transactions ME28, ME54, ME55, ME23N, and ME53N work the same way. Some release-related screens appear with Fiori-style layouts in the S/4HANA Fiori launchpad, but the backend configuration and release determination are identical. Existing ECC release strategies migrate to S/4HANA with no rework.
Yes — VoiSAP's SAP MM training covers the full procure-to-pay cycle including purchasing configuration: info records, source lists, release strategies (OMGS, CT04, CL02 setup), account determination (OBYC), and invoice verification — all on a live SAP S/4HANA system. Book a free demo to discuss your background and the fastest path to your first SAP MM role.
After making config changes in OMGS, CT04, or CL02, go to ME22N and open a PO that was not triggering the strategy. Make a minor change (or add a note in the header text) and save. Then open the same PO in ME23N and check for a Release Strategy tab at the header level. If it appears, the strategy is now being determined correctly. If it does not appear, the classification values still do not match — use the Analysis button in the Conditions tab or check OMGS again. Always test on a PO whose values you have already verified against the strategy's classification.
On a Real System, Not a Simulation.
Book a free demo class with Gourav. See a live SAP S/4HANA system, ask your questions, and find out whether VoiSAP's training fits your background and goals.