30-days Money-Back Guarantee
SAP MM- PR/PO Release strategy and Inventory Management in Materials Management
Updated on Sep, 2026
Office Productivity, SAP, SAP MM
Training 5 or more people ?
Get your team access to 10000+ top Tutorials Point courses anytime, anywhere.
The release procedure defines, how the document is going to release. The document can be PR, PO, Contract, Scheduled agreement, or RFQ. Here we study the purchase requisition.
Purchase requisition will be created by the respective stakeholders of their plant, if a request is created it will go to buyers Que to create purchase order and before that whoever is created the purchase requisition should approve, and after that respective manager should approve.
We can create an N number of approvers for the documents like PR, whereas an SAP MM consultant's it's their duty to maintain the release approvers.
We can maintain the release process for respective documents also.
Eg: we can maintain the release strategy for plant or material groups also.
we have 2 types of release procedures, defined below.
1. With Classification
2. Without Classification
1. With Classification:
We have 2 sub-terms in with classification.
Where we can release these documents at the Document header level or Item level as per our business requirement.
Header level contains PR, PO, Contract, Scheduled Agreement, RFQ
Item level contains PR.
2. Without Classification:
Without classification, we have only 1 type of release process
Flow-chart for the above 2 Classifications
With Classification--
PR, PO, Contract, SA, RFQ
Without Classification--
To maintain the release procedure for particular document types in SAP MM, we have communication tables/Structures for document types, mentioned below
Document type Communication table
PR, PO, CO, SA, RFQ CEKKO
In the above-mentioned communication, tables are used to know the details for respective document type field components.
We have a T-code to help to find the component for the respective field in the communication table, that is SE11, where we can only display the data (ABAP Data), it's mainly used to find the component for the document type with the help of the communication table.
Eg: CEBAN is used for PR, if we are maintaining the release procedure with respect to the plant than we need to find the respective component for the plant filed in PR.
So, go to SE11, and maintain the communication table as CEBAN if you are working for PR, or else you can maintain CEKKO, and CESSR for the remaining data field components.
As mentioned in the example, we have only one condition (Plant) to maintain the release strategy, if I would like to maintain the release strategy with a combination of conditions then we need to define it as mentioned below.
Note: Important Note: 1 condition = 1 Characteristic
2 Condition = 2 Characteristic
Note: To maintain the release strategy we need to follow the below steps.
Check out the detailed breakdown of what’s inside the course
Easy Learn SAP EWM/ MM, I would like to share and enhance my knowledge in this platform, Which will help many people to understand the configuration and concepts of SAP MM/EWM and even I think this is the platform to explore the knowledge.
My concept way of explanation and examples were different compared to anyone this makes me unique in teaching and everyone should learn and achieve their goals in their life.
Use your certificate to make a career change or to advance in your current career.
Become a valued member of Tutorials Point and enjoy unlimited access to our vast library of top-rated Video Courses
Master prominent technologies at full length and become a valued certified professional.