# PO Not Released in SAP: Release Strategy, ME28 and ME29N Fixes > Source: https://netray.co/erp-help/po-not-released-in-sap-release-strategy-me28-me29n-fix > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: ERP Help ## Short answer A purchase order that stays unreleased almost always has a release strategy that is assigned but cannot advance: the release code is not given to the approver, the prior release step is still open, the approver or workflow agent does not exist, or a change reset the strategy. Check the Release Strategy tab in ME23N, then fix the code assignment, the workflow, or the value that triggered the strategy. ## Kind error ## System sap ## Erp SAP ECC / S/4HANA ## Module MM Purchasing / Release Strategy ## Query po not released in sap ## Alternate Queries - sap mm order workflow - purchase order release strategy not working SAP - ME29N release button greyed out - PO stuck waiting for release SAP ## Applies To SAP ECC 6.0 and S/4HANA on-premise, classification-based PO release strategy. Release procedure with workflow or without. ## Steps ### How to find out why a PO is not released **Items:** Open the PO in ME23N or ME29N and go to the Release Strategy tab (header). Note the release group, strategy, the codes and which are already set. If the status says release not completed, see which code is next. Releases normally happen in order, so a later approver cannot release before an earlier one. Confirm the approver has the release code. In ME29N the Release button is only active for users whose authorisation object (M_EINK_FRG) contains the release group and code. Try ME29N (individual) or ME28 (collective release by code) as the approver. If the PO does not appear in ME28, the user's code or group is wrong, or the PO is not at that step. If the release is via workflow, check the approver's inbox (SBWP) and the workflow log from the PO. A missing agent assignment leaves the work item with no recipient. Check whether the PO was changed. A change to value or other characteristics can reset the release strategy so it must be released again, or it may drop to a different strategy. Verify the strategy actually exists and is complete in Customizing: classification values, release codes, release prerequisites and release statuses. After the fix, release in ME29N and check that the PO status turns released, then check that follow-on documents (goods receipt, output) are no longer blocked. ## Sections ### How the release strategy decides **Body:** The release strategy is determined from classification characteristics of the PO header, most often the total net order value, the purchasing group, the document type and the plant. A strategy defines release codes, the order they must be applied in (the prerequisites) and what status results. Until the last required code is set, the PO is blocked for output and goods receipt. If the PO was saved without a strategy because none matched, it is not blocked at all. The opposite problem, a strategy that exists but cannot advance, is what this page covers. The existing article on strategy not being determined covers the reverse case. ### The usual causes **Body:** Release code not assigned to the user or authorisation role is the most common cause: the approver sees the PO but the Release button is greyed out, or ME28 returns no documents. Next is a wrong sequence, where code 02 is waiting on code 01 that nobody has released. A missing workflow approver gives a similar picture when release is routed through workflow. The PO sits in a work item that has no valid agent, for example because the approver left the company or the organisational assignment (position or job) is empty. Finally, a value change after release resets the strategy, so a PO that was released yesterday looks unreleased today. **Code:** ME23N > Header > Release Strategy tab ME29N Release purchase order (individual) ME28 Release purchase orders (collective, by release code) SBWP Business Workplace (approver inbox) SU53 Authorisation check after a failed release ### Workflow release versus manual release **Body:** With workflow, release can trigger a work item to the approver via the release strategy's organisational data. This uses standard workflow tasks that depend on the workflow customizing being complete. If SWU3 shows an incomplete configuration, items may not be created at all. Without workflow, approvers simply use ME28 or ME29N. For a small team this is simpler and easier to troubleshoot, but it needs someone to watch for POs waiting. A short list report on EKKO filtered on the release status fields (FRGKE, FRGZU) gives that backlog. ### Do not bypass the strategy **Body:** It is tempting to change the release indicator in the table to get the PO moving. Do not. It skips the audit trail and can break the strategy history. Fix the code assignment or the workflow, and release properly so the change documents record who approved. ## Pitfalls - Fixing the symptom in the table instead of assigning the release code to the right approver. - Ignoring prerequisite release codes so a later approver cannot act. - Changing PO value after release and not expecting a reset. - Workflow items sent to a role or position with no holder. - Testing only with a super user, hiding the authorisation gap the real approver has. ## Ai Angle An assistant grounded in SAP can look at an unreleased PO, read its release group, strategy and codes, compare them with the approver's authorisation and workflow assignment, and say which step is stuck and who must act. On-prem it runs read-only against your system with the model on your own GPUs; release itself stays a human approval. ## Faq ### Why is the release button greyed out in ME29N? **Answer:** Usually the user lacks authorisation for the release group and code (object M_EINK_FRG), or an earlier code in the sequence has not been set. Check SU53 after the attempt and the Release Strategy tab to see which code is next. ### What is the difference between ME28 and ME29N? **Answer:** ME29N releases one purchase order at a time, ME28 lists all POs waiting for a given release code and lets the approver release many. Both depend on the same release code authorisation. ME28 is the quicker choice for a daily approval run. ### Why did a released PO become unreleased? **Answer:** A change to something that feeds the strategy, typically the order value or a changed item, can reset the release so it must be approved again. This is controlled by the release strategy's change settings in Customizing. ### How do I find all POs waiting for release? **Answer:** Run ME28 for the relevant release code and group, or read EKKO in SE16N and filter on the release indicator fields. The list shows documents blocked and, with the strategy and code, who needs to act. ## Search terms po not released in sap, sap mm order workflow, sap po release strategy, me29n release, me28 release purchase orders, purchase order release code sap, sap po approval workflow, release strategy not working sap --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json