# SAP ME21N: why the release strategy is not determined on a purchase order > Source: https://netray.co/erp-help/sap-me21n-release-strategy-not-determined-po-not-blocked > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: ERP Help ## Short answer When a purchase order saves without a release strategy, no strategy in the release group matched the PO's characteristic values. Compare the PO header values (value, document type, purchasing group, plant) against the value ranges in the strategy classification (CL24N), and check that the release group and code are active for the PO document type. ## Kind how-to ## System sap ## Erp SAP ECC / S/4HANA ## Module MM Purchasing / Release Procedure ## Query SAP ME21N purchase order release strategy not determined, PO saved without release ## Alternate Queries - SAP release strategy not triggered ME21N - SAP PO release strategy not found class 032 CEKKO - why is my purchase order not going for approval in SAP ## Applies To SAP ECC 6.0 and S/4HANA on-premise, classic release procedure for POs (not the flexible workflow approval in Fiori) ## Steps ### Debug why no strategy is assigned **Items:** Open the PO in ME23N and go to Header > Release strategy tab. If it is empty and the PO is not blocked, the strategy was never determined. Note the net value, document type, purchasing group, plant and account assignment category. In SPRO go to Materials Management > Purchasing > Purchase Order > Release Procedure for Purchase Orders > Set Up Procedure with Classification, and check that the release group (for example 01) is assigned to the PO object, and that the release indicator and strategy exist. In CL20N, display class type 032 and the release class for your group. Check that the characteristics (for example CEKKO-GNETW, CEKKO-BSART, CEKKO-EKGRP, CEKKO-WERKS) are assigned and that each has a value range covering your PO. In CL24N, open the release strategy and look at the Classification screen. Every characteristic that has values on the strategy must match the PO. A characteristic with no values on the strategy acts as a wildcard. Check the currency. GNETW is compared in the characteristic's currency, usually the company code or a fixed one, and a PO in another currency is converted at the rate for the document date. If the PO already exists, change a value and re-save, or use ME28 or ME29N to see whether a strategy appears. Strategy determination reruns when relevant fields change, not on every save. Transport the corrected classification, because release strategies are customizing plus classification data, and classification changes need their own transport or manual replication in each client. ## Sections ### How determination actually works **Body:** The classic release procedure builds a communication structure, CEKKO for the PO header, and fills it from the document when you save in ME21N. SAP then looks through the release strategies in the release group for the one whose classification values all match the CEKKO fields. If exactly one matches, its release group and strategy are written to EKKO (fields FRGGR and FRGSX). If none match, nothing is written and the PO behaves as released. Each strategy is stored in table T16FS, the release codes in T16FC, and the prerequisites between codes in T16FV. The characteristic values for the strategy sit in the classification system, not in T16FS, which is why a customizing screen can look perfect while determination still fails. Because the match is an AND across characteristics, the most common cause is a value range that is slightly off: a PO of exactly 10,000.00 against a strategy that covers 10,000.01 to 50,000.00, or a document type NB against a strategy that lists only FO. **Code:** - -- Header release data on the PO - SELECT EBELN, BSART, EKGRP, FRGGR, FRGSX, FRGKE, FRGZU, FRGRL - FROM EKKO WHERE EBELN = '4500001234'; ### Value range gaps and overlaps **Body:** Two strategies in the same group that both match produce a determination conflict, and SAP picks neither or the one it finds first depending on release. Gaps are the opposite problem: no strategy covers the PO. Review all strategies in the group side by side and make the ranges contiguous, with the upper bound of one just below the lower bound of the next. For value characteristics, use the same decimals and currency across strategies. Mixing a range defined in USD with one defined in EUR is a frequent source of confusing behaviour after a company code restructure. If you want a PO to need no approval under a threshold, create an explicit strategy with no release codes or rely on the gap, but document the choice. A gap by accident and a gap by design look identical in the system. ### Fields that trigger a re-determination **Body:** Not every change reruns determination. Changing the net value, the document type or the purchasing group typically does. Editing text or delivery dates does not. If a user lowered the value after the PO was released, the existing release state is reset and the PO goes through the strategy again. For items, SAP also supports the item-level procedure for purchase requisitions through class 032 with the CEBAN structure, which is a different customizing node. Check you are editing the PO node and not the requisition node, because both live under Purchasing and have similar names. ### Authorizations and release codes **Body:** A strategy that is determined but has nobody who can release it looks like a stuck PO, not a missing strategy. Release codes are protected by authorization object M_EINK_FRG with the group and code. Verify with SU53 or the authorization trace in ST01 that approvers hold the right code, and that the prerequisite codes in the strategy are released first. ## Pitfalls - Editing the strategy in customizing but forgetting the classification values in CL24N, which is where the matching happens. - Overlapping value ranges across strategies in one release group, producing no determination or the wrong one. - Testing with a PO in a different currency than the characteristic and assuming the number you see is the number compared. - Transporting customizing but not the classification data, so the strategy works in development and fails in test. - Expecting a changed strategy to apply to existing POs automatically. Existing documents keep their strategy until a relevant field changes. ## Ai Angle An assistant grounded in your SAP system can take a PO number, read the EKKO header and the CEKKO-relevant values, then walk the strategies in T16FS and their classification ranges to say which characteristic fails to match and by how much. ERPray reads this data read-only and shows the query it used, so the buyer or key user sees the evidence. Fixing the classification stays a human change under your normal transport process. ## Faq ### Why does my PO save as released when I expect an approval? **Answer:** Because no release strategy matched the PO's values, SAP writes no release group and treats the PO as released. Compare the header net value, document type, purchasing group and plant against the ranges in the strategy classification in CL24N. A single characteristic outside the range is enough to prevent determination. ### Where is the release strategy stored? **Answer:** The strategy master is in table T16FS and the release codes in T16FC, but the characteristic values used for matching live in the classification system under class type 032. On a PO, the assigned group and strategy are stored in EKKO fields FRGGR and FRGSX. ### Does the release strategy rerun when I change the PO? **Answer:** It reruns when a field relevant to the communication structure changes, such as net value, document type or purchasing group. Changing a text or a delivery date does not trigger it. You can force a check by changing a relevant value and saving, or by using ME28 on the document. ### Can I use Fiori approval instead of the classic release procedure? **Answer:** In S/4HANA, flexible workflow approval for purchase orders is available as an alternative to the classic procedure. It is configured differently and the two should not be mixed on the same document type. If you already have a working classic setup, there is rarely a reason to migrate it just for the interface. ## Search terms SAP release strategy not determined, ME21N release strategy, SAP class 032 CEKKO, SAP PO release strategy CL24N, T16FS release strategy table, SAP purchase order approval not triggered, SAP release group release code, ME28 mass release --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json