PR/PO Release strategy and Inventory Management Course in SAP MM

SAP MM- PR/PO Release Strategy and Inventory Management in Materials Management

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.

Release procedure:

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.

1. Header Level

2. Item Level

Header Level:

Header level contains PR, PO, Contract, Scheduled Agreement, RFQ

Item Level:

Item level contains PR.

2. Without Classification:

Without classification, we have only 1 type of release process

            1. Item Level

Flow-chart for the above 2 Classifications

Release procedure--

            With Classification--

                        Header            ---                                                        Item--

                            PR, PO, Contract, SA, RFQ            

                                      PR       

Release procedure--

            Without Classification--

                                    Item--

                                                PR

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-                                          CEBAN

PR, PO, CO, SA, RFQ           CEKKO

SES                                          CESSR

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.