Understanding the Release Strategy in SAP MM

What Is Release Strategy In Sap Mm

Release strategy in SAP MM refers to the process of controlling and managing the release of purchase requisitions, purchase orders, and other procurement documents within an organization. It involves setting up rules and criteria that determine when a document can be released for further processing or approval. This strategy helps organizations maintain control over their procurement processes, ensuring that purchases are authorized based on predefined conditions such as value limits, specific departments or individuals responsible for approval, or any other relevant factors. By implementing a release strategy in SAP MM, businesses can streamline their procurement workflows and ensure compliance with internal policies and regulations.

Release strategy

There are various strategies available for different scenarios. For instance, you can establish a release strategy that relies on the type of document or important details related to purchasing such as the organization or group involved.

In many instances, the release strategy commonly employed revolves around the monetary worth of the procurement document.

Defining a Release Strategy

First, we need to establish a release strategy that will only prompt for manual approval when the value of purchasing documents exceeds 100 Euros. For instance, if we have a purchase order worth 50 Euros, it will be automatically approved and can proceed without any further release requirements. However, if the purchase order surpasses the threshold of 100 Euros, it will necessitate a manual release before proceeding with processing.

In order to achieve this, it is necessary to define a specific attribute in the system.

In the CT04 transaction, we have the option to define the NETVALUE characteristic. Its value should exceed 100 Euros.

In the second step, we assign the purchase document value field CEKKO-GNETW to a characteristic on the additional data tab.

Step 3) It is also necessary to designate a category that contains the attribute.

To achieve this, you can use the CL02 transaction code. In order to create a class in SAP MM, certain information needs to be provided such as the class name, class type, description and status, validity period, and same classification.

Step 4 involves assigning a specific characteristic to a class. In this case, we will assign the characteristic NETVALUE to a class named REL_PUR.

Step 5) The next set of actions should be performed in the customization process.

Once the strategy has been established, it is prepared and ready to be tested in the live system.

In the sixth step, we observe that our purchase order is generated with a total amount exceeding 100 Euros. If we were to create a purchase order for an amount lower than 100 Euros, it would be automatically approved without any further action required.

1. The presence of these two statuses signifies that our purchase order is undergoing a release process, which requires approval before any further actions can be taken. On the other hand, if the status is Blocked, it means that the purchase order has not been released yet.

You might be interested:  Creating a Namespace in SAP

2. The amount in question is 24,000 Euros, exceeding the threshold of 100 Euros.

Currently, we possess a purchase order that requires authorization (approval) in order to be considered valid for subsequent actions.

What is the highest level of release strategy in SAP MM?

To configure these release strategies in SAP, companies need to define criteria based on which approvals will be triggered at each level. These criteria could include factors like monetary value thresholds, material categories, vendor ratings, or any other relevant parameters specific to their business requirements.

Furthermore, regular monitoring and evaluation of these release strategies are crucial for maintaining efficiency in procurement processes. Companies should periodically review whether all defined levels are still necessary or if changes need to be made based on evolving business requirements.

Purchase Order Release in SAP MM

To initiate the release of the procurement document, we have the option to utilize t-code ME28 in SAP MM.

1. Carry out the transaction code.

2. Input the necessary release code (required) and release group (optional).

3. Preferences – maintain default settings as shown on the screen below.

5. Execute the command.

In the following screen, we will be able to view the purchase orders that have been chosen based on our specified criteria.

Select the desired purchase order by clicking on it, and then proceed to click on the release button.

The purchase order has been marked as released, indicating a change in its status.

Step 3) You can see in the ME23N or ME22N transaction that our purchase order has altered statuses. “Release completed” and ” Released” statuses are now shown in the PO header data.

The process flow remains consistent for all types of purchase documents, such as purchase requisitions and quotations.

How to showcase the release strategy in SAP MM?

To begin with, it is important to create release groups in order to categorize and organize them. These release groups can be assigned a specific class, such as REL_PUR for our case. By assigning a class to each release group, it becomes easier to manage and track different types of releases.

In addition to creating release groups and codes, it is essential to establish clear release indicators. These indicators serve as status markers for each individual release. For instance, using numbers like 1-Blocked or 2-Released helps convey whether a particular release is currently on hold or has been successfully deployed.

Furthermore, developing a comprehensive release strategy is crucial for effective project management. A well-defined strategy outlines the steps involved in releasing software updates or new features while considering factors like testing processes and deployment timelines. It ensures that all necessary actions are taken systematically before making any releases public.

Lastly, when implementing a specific release strategy, it is important to assign appropriate release groups and codes accordingly. This ensures that the right set of releases are included within each strategy based on their classification and purpose.

Practical advice:


Make sure that there is consistency in naming conventions when assigning code names or numbers so that they can be easily understood by everyone involved.

For instance: Use simple terms like “Blocked” instead of complex jargon while defining indicators.


Regularly review and update your release strategy to adapt to changing project requirements or industry standards.

For example: If you notice that certain releases consistently face delays, consider revising the strategy to address these issues proactively.

You might be interested:  Sap Basis Training Institute In Hyderabad

Release Cancellation in SAP MM

In order to make changes to a document that has already been released, the first step is to reverse the release of the purchasing document.

You have the option to perform this action within the ME28 transaction itself. Simply select the Cancel release checkbox and proceed with executing the transaction.

In the second step, a list of purchase documents that can be cancelled will be displayed.

1. Select the suitable document.

2. Click on the button to revoke the release.

If the release strategy in SAP MM does not permit reversals, it is not possible to cancel a release. This configuration is determined by the settings applied to the release indicator and release strategy levels.

You can test a release strategy used by the purchasing document by clicking the ” Release Strategy ” button on the above screen. You can also simulate the strategy output with Simulate release button.

Release Strategy in SAP MM is a process that is followed for purchase orders. It involves a set of procedures and steps that need to be undertaken in order to release the purchase order for further processing. This strategy ensures that the purchase order goes through the necessary approvals and authorizations before it can be executed.

The meaning of release code in SAP MM

Each level of approval is assigned a specific release code that corresponds to the responsible person or department. Once an individual with the appropriate authorization enters their release code into the system for a particular document, it signifies their approval and allows the document to move forward in the procurement process.

Understanding SAP MM Release Simulation

In SAP MM, the release strategy plays a crucial role in determining the approval process for external purchasing documents and purchase requisitions. By assigning a specific release code to a document, you can simulate its release status and understand how it will be processed further once released.

By using this functionality, organizations can streamline their purchasing processes, improve efficiency, and maintain control over expenditures. The ability to simulate different release scenarios enables users to make informed decisions regarding document processing based on factors such as budget availability or vendor preferences.

P.S. Simulating release statuses in SAP MM is an essential tool for effective procurement management. It empowers businesses to optimize their approval workflows while ensuring compliance with internal policies and regulations.

The significance of release strategy in SAP MM

The release strategy in SAP MM plays a crucial role in determining the approval process for purchase requisitions. It is a set of guidelines that outlines the necessary steps and individuals involved in approving a complete purchase requisition or its individual items. The strategy includes specific release codes that must be assigned to ensure proper authorization, as well as the sequence in which these approvals need to be obtained.

In order to initiate the release strategy, a complete purchase requisition or an item within it needs to go through various levels of approval. Each level corresponds to a specific release code, indicating the responsible person or department who has authority over granting approval. These release codes are typically assigned based on factors such as monetary value, material type, vendor selection criteria, or any other relevant parameters defined by the organization.

The sequence of approvals is also an essential aspect of the release strategy. It determines the order in which different stakeholders review and authorize each step of the procurement process. This ensures that all necessary checks and balances are followed before proceeding with purchasing activities.

You might be interested:  Different perspectives in SAP ABAP

The number of effective release strategies in SAP

The SAP Standard system has a limitation of allowing only 8 levels of release codes. In the context of Purchase Requisitions (PR), there are two types of Release Procedures available. The first type is called “With Classification,” which enables item-level release specifically for PRs. On the other hand, the second type is known as “Without Classification,” which allows header/document level release for various documents such as Request for Quotation (RFQ), Purchase Order (PO), Contract, and Scheduling.

In the case of PRs with classification, each individual item within a PR can undergo a separate release process based on specific criteria or conditions set by an organization. This means that different items in a single PR may require different levels of approval before they can be further processed.

On the contrary, when it comes to documents like RFQs, POs, contracts, and scheduling agreements, the release procedure operates at a higher level – namely at the header or document level rather than focusing on individual line items. This implies that all items within these documents will follow one common approval process instead of having separate approvals for each item.

Overall, understanding these two types of Release Procedures in SAP MM helps organizations streamline their procurement processes by ensuring proper authorization and control over purchasing activities while adhering to their specific business requirements

Changing a release strategy: How is it done?

In the context of SAP MM, release strategy refers to a set of steps and criteria that need to be fulfilled in order for a purchase requisition or purchase order to be approved. The release strategy determines who has the authority to approve or reject these documents based on various factors such as value, department, vendor, etc.

To remove the release prerequisites in SAP MM, certain actions need to be taken. Firstly, any existing release status needs to be eliminated. Additionally, any classification values that have been set should also be removed. Furthermore, it is necessary to delete all release strategies associated with the document. This includes removing the release indicator as well as deleting any assigned release codes and groups.

By following these steps effectively within SAP MM system configuration settings, organizations can streamline their approval processes and ensure that only authorized personnel are able to review and authorize purchase requisitions or purchase orders.

It is important for businesses using SAP MM in India to understand how release strategies work and how they can customize them according to their specific requirements. By implementing an efficient release strategy process within their procurement operations, companies can enhance control over purchasing activities while ensuring compliance with internal policies and regulations governing approvals at different levels within the organization hierarchy.

Deleting a release strategy in SAP MM: How can it be done?

Reassigning the deleted assignment of Release group, Release code, and Release strategy in SPRO can be done by moving the request to PRD. Once in PRD, it is important to assign the classification if it does not appear. Additionally, deleting the Release strategy in CL24N should be done in PRD as well. After completing these steps, all assignments should be deleted again in Dev before moving the request to PRD.