ME54N — Individual Release of Purchase Requisition

ME54N releases a purchase requisition that carries a release indicator, meaning it cannot be converted to an RFQ or purchase order until one or more approval codes have been given. The structural fact that drives most confusion is that release strategy can be configured at header level or at item level. Header-level release approves the entire requisition in one action once all codes sign off. Item-level release means each item carries its own release status, so releasing item 10 does nothing for item 20, and a requisition can sit half-released indefinitely if nobody checks every line. ME54N displays whichever mode is configured, along with the characteristic values SAP used to determine the strategy in the first place, which is the first thing to inspect when a requisition unexpectedly requires or skips approval.

ME54N is reached for whenever a purchase requisition has been created or changed and its release status shows as incomplete, blocking conversion to a purchase order. It sits between requisition creation (ME51N/ME52N) and sourcing: procurement cannot act on the requisition until release is complete. For releasing many requisitions at once, ME55 (collective release) is the better tool; ME54N is for a single document a buyer or approver has been pointed at directly, often from an error message during PO creation that says the requisition is not released. On systems where SAP Business Workflow drives approvals, most day-to-day releasing happens through the workflow inbox or a Fiori approval app, and ME54N becomes the fallback for manual release or for investigating why a workflow item never appeared.

Run SE16 on EBAN filtered by the requisition number (BANFN) and item (BNFPO). Check the release indicator and release status fields for that item: an incomplete status confirms outstanding approval, and comparing header-level versus item-level entries confirms whether the strategy is configured per item. Cross-check the characteristic-relevant fields on the same record (value fields, plant, material group, purchasing group) against the release strategy customizing to see whether the combination actually maps to a strategy at all; a requisition with no strategy assigned will show no release requirement even though the business expects one.

The release logic and underlying data structures for purchase requisition release are unchanged between ECC and S/4HANA; ME54N still exists and works the same way. What changes is the front end: S/4HANA offers a Fiori app for approving purchase requisitions (commonly reached through 'My Inbox' style approval apps) which most managers use instead of the SAP GUI transaction. ME54N remains the tool consultants and buyers use to inspect or force a release directly, and it is the natural place to check status when a Fiori approval seems to have gone nowhere.

Functional MM/procurement consultants own the release strategy configuration itself: which characteristics determine a strategy, which codes are required, and in what sequence. Basis or security teams own assignment of release code authorization to individual users. A good handover includes the requisition number, its current release status per item, the characteristic values driving strategy determination, and confirmation of which release code the affected user is trying to exercise.

ME55 covers the same release logic applied to a worklist of requisitions rather than one at a time, useful once the single-document behavior in ME54N is understood. ME52N and ME53N are where the characteristic-driving fields (value, plant, purchasing group) get changed or inspected, which is usually the first place to look when a strategy determination looks wrong. ME2L pulls open, unreleased requisitions by vendor or material, useful for building a worklist of stuck approvals rather than chasing one document at a time.