Error fixSAP ECC / S/4HANAMM Purchasing / Release Strategy

PO Not Released in SAP: Release Strategy, ME28 and ME29N Fixes

Error
po not released in sap

Also searched as

  • sap mm order workflow
  • purchase order release strategy not working SAP
  • ME29N release button greyed out
  • PO stuck waiting for release SAP

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.

Applies to: SAP ECC 6.0 and S/4HANA on-premise, classification-based PO release strategy. Release procedure with workflow or without.

How to find out why a PO is not released

  1. 1Open 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.
  2. 2If 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.
  3. 3Confirm 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.
  4. 4Try 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.
  5. 5If 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.
  6. 6Check 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.
  7. 7Verify the strategy actually exists and is complete in Customizing: classification values, release codes, release prerequisites and release statuses.
  8. 8After 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.

How the release strategy decides

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

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.

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

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

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.

Try it here, free

SAP Release Strategy Design Template

Open full tool

Fill-in design document for a classic SAP release procedure: groups, codes, characteristics, approval levels and test cases.

Common 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.

How an ERP-grounded AI assistant handles this

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.

See ERPray

Frequently asked questions

Why is the release button greyed out in ME29N?

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?

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?

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?

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.

Related

How-to

SAP ME21N: why the release strategy is not determined on a purchase order

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.

How-to

SAP PO Report by Creator: Transactions and EKKO-ERNAM

To list SAP purchase orders by who created them, run ME2N or ME80FN and filter on Created By (EKKO-ERNAM), using dynamic selections when the field is not on the selection screen. For a quick raw list, read table EKKO in SE16N with ERNAM set to the user ID. Save the selection as a variant so buyers and managers can rerun it.

How-to

SAP open purchase orders report: ME2N, ME2M, ME2L and the underlying tables

Use ME2N for a flexible open PO list, ME2M by material and ME2L by vendor, with the selection parameter Still to be delivered. The open quantity is the scheduled quantity in EKET minus goods received in EKBE, excluding deleted and delivery-completed items. For custom reports, read EKKO, EKPO, EKET and EKBE.

Error fix

SAP M7 021: Deficit of SL Stock Quantity

M7 021 fires during a goods issue, delivery, or confirmation when SAP checks the unrestricted-use (SL) stock for the exact plant, storage location and batch combination and finds less than what you are trying to post out. Fix the entry (batch, storage location, quantity) first; only enable negative stock or downgrade the message to a warning if the business genuinely needs to post ahead of a receipt.

Error fix

SAP IDoc Status 51: Application Document Not Posted

Status 51 tells you the IDoc reached the application layer and failed to post, but the status text itself is not the error - the real cause sits in the status record's long text or the linked application log. Fix the underlying data or configuration, then reprocess the IDoc through BD87 rather than editing the status.

Error fix

SAP Short Dump TIME_OUT: Maximum Runtime Exceeded

A TIME_OUT runtime error means a dialog (or RFC) work process ran longer than the maximum allowed runtime, controlled by profile parameter rdisp/max_wprun_time (600 seconds by default). The fix is almost always to move the long-running work to background processing or tune the underlying program, not to raise the timeout.

AI for ERP

AI for SAP S/4HANA, Running On-Prem or in Your Private Cloud

Run AI on SAP S/4HANA without sending ERP data to a public API. On-prem and private-cloud architecture, CDS views, OData, and honest deployment trade-offs.

AI for ERP

Get AI Value From SAP ECC Now, and Use It to De-Risk the Move to S/4HANA

SAP ECC 6.0 mainstream maintenance ends in 2027. Add AI value on ECC now, using its existing BAPIs and IDocs, and use it to de-risk the S/4HANA migration.

Stuck on SAP ECC / S/4HANA?

Talk to engineers who work inside SAP ECC / S/4HANA every week, and who build private AI that answers these questions from your own ERP data.

Talk to an ERP engineerBrowse ERP Help
All ERP Help articles

Keep exploring

Free tools

ERP fixes and how-tos

Integrations

TermsSAP ME21N (Create Purchase Order)