# SAP MM Approval Process: Release Strategies, Workflow and Fiori > Source: https://netray.co/erp-help/sap-mm-approval-process > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: ERP Help ## Short answer SAP MM approval is built on release strategies: rules that block a purchase requisition (PR) or purchase order (PO) until the right people release it with release codes. Strategies are configured with classification characteristics and can be released in ME28 or ME29N, through workflow, or in Fiori approval apps. In S/4HANA there are also flexible workflows for PRs. ## Kind how-to ## System sap ## Erp SAP ECC / S/4HANA ## Module MM / Purchasing Release Procedure and Workflow ## Query sap mm approval process ## Alternate Queries - purchase order approval process in sap - purchase requisition release strategy sap - sap po approval workflow fiori - how to configure release strategy for purchase order ## Applies To SAP ECC 6.0 and S/4HANA on-premise. Fiori app names vary by release. The classic release procedure is identical in both. ## Steps ### How to configure a PO release strategy **Items:** - Decide the approval rule: for example POs above 10,000 in plant 1000 for document type NB need the department head, and above 50,000 also the finance director. - Create the characteristics in CT04 using the communication structure CEKKO (for PO header fields such as GNETW net order value, BSART document type, WERKS plant, EKGRP purchasing group). For PRs, use CEBAN (item level). - Create a class in CL02 with class type 032 and assign the characteristics. - In IMG go to Materials Management, Purchasing, Purchase Order (or Purchase Requisition), Release Procedure, Procedure with Classification. Define release groups, release codes, release indicators and release strategies (transaction OMGSCK is the combined entry). - For each strategy set the release codes needed, the release prerequisites (which code must release before which) and the release statuses. - Open the classification of each strategy (the Classification button) and enter the characteristic values that make the strategy apply, for example GNETW 10,000 to 50,000. - Assign users to release codes through authorization object M_EINK_FRG (and the release code and group values). - Test: create a PO in ME21N, save, check the Release strategy tab in ME23N, and release in ME29N (single) or ME28 (collective). ## Sections ### PR versus PO release **Body:** A PR release strategy is item level by default (collective release in ME55, individual in ME54N). A PO strategy is header level (ME28 collective, ME29N individual) and uses the PO header fields. A PR can also be released as an overall document in classification setup, but most customers release per item because items may have different cost centers or amounts. If the PO is created from a released PR, the PO still needs its own release if the PO rules apply. Many sites release both at different thresholds: PR for budget approval, PO for commitment approval. ### Workflow and Fiori approval **Body:** Release can be delivered to the approver's inbox with SAP Business Workflow (the standard release workflow is attached to the release codes) so people do not need to open ME28. The approver sees a work item and releases from there. In Fiori, approval apps such as Approve Purchase Orders and Approve Purchase Requisitions (names depend on the release) work on top of the same release strategies. In S/4HANA, flexible workflow can be configured for PRs with conditions and approvers without classification. For POs most sites still use classic release strategies. ### Test cases to run before go-live **Body:** Test each strategy boundary: a PO of 9,999, 10,000, 10,001 and 50,001. Test each document type, each plant, a PO changed after release (does it reset?) and a PO with multiple items of different values. Test the negative cases: a user without the release code authorization tries to release, a user releases at the wrong step order, the release is reset, and the PO is changed with a value change above tolerance. Also test printing and goods receipt on a blocked PO to confirm what is blocked. ## Pitfalls - Overlapping strategies where two match the same PO; the first match wins and the other is ignored. - Not assigning release codes to users through authorization, so nobody can release. - Using the PO net value as a characteristic but expecting changes after release to re-trigger; check the changeability settings of the strategy. - Forgetting that PR and PO need separate classes and strategies. - Putting the same document type in a catch all strategy that hides the specific one. ## Ai Angle Approvers lose hours to 'what is waiting for me and why'. An assistant grounded in SAP data (ERPray, read-only, role-aware, can run on-prem) can list open release items per approver, the strategy and the amount, and show who is blocking a PO. It does not release anything; release stays with the person holding the release code. ## Faq ### How does the PO approval process work in SAP MM? **Answer:** A release strategy checks the PO against rules (value, plant, document type, purchasing group). If it matches, the PO is blocked until one or more release codes release it. Users release in ME28 or ME29N, or through workflow and Fiori. ### What is the difference between ME28 and ME29N? **Answer:** ME28 is collective release: a list of POs to release at once. ME29N releases one PO at a time and shows the document. PRs use ME55 for collective release and ME54N for individual release. ### Can I do approval without classification? **Answer:** In S/4HANA you can configure flexible workflow for purchase requisitions and some other documents without classification. For purchase orders, the classic release strategy with classification remains the main approach. ### Which authorization object controls release? **Answer:** M_EINK_FRG checks the release group and release code. A user needs the right release group and code in their role to release a document, in addition to the usual purchasing authorizations. ## Search terms sap mm approval process, sap po approval process, sap purchase requisition approval, sap release strategy configuration, sap me28 me29n release, sap release procedure with classification, sap po approval workflow, sap fiori approve purchase orders, sap me54n me55 release pr, sap m_eink_frg --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json