Training by Studyuuu for SAP MM

Training by Studyuuu for SAP MM
Training by Studyuuu for SAP MM

Sunday, 16 June 2019

Release Procedure for Purchase requisition(PR)-SAP MM




Release procedure for Purchase requisition

For Videos Explanation, please go to YouTube and Subscribe -  Studyuuu  SAPMM


Release procedure defines, how the document is going to release. The document can be PR, PO, Contract, Scheduled agreement, RFQ. Here we study about the purchase requisition.
Purchase requisition will be created by the respective stake holders of there plant, if a request is created it will go to buyers Que to create purchase order and before that who ever is created purchase requisition he should approve and after that respective manager should approve.
We can create an N number of approvers for the documents like PR, where as an SAP MM consultant its 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 group 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 in 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 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/Structure 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 component.
We have 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), its mainly used to find the component for the document type with the help of communication table.

Eg: CEBAN is used for PR, if we are maintaining the release procedure with respect to plant than we need to find the respective component for the plant filed in PR.
So, go to SE11, maintain the communication table as CEBAN if you are working for PR or else you can maintain CEKKO, 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 combination of conditions then we need to define as mentioned below.

Note: Important Note: 1 condition = 1 Characteristic
                                    2 Condition =  2 Characteristic

Note: Maintaining the release strategy we need to follow the below steps.

1.     Edit Characteristic
2.     Edit Class

3.     Setup procedure with classification
1.     Release Groups
2.     Release Codes
3.     Release indicator
4.     Release strategies
1.     Release prerequisites
2.     Release statues
3.     Classification

Path to go to above release procedure (OLME)

SPRO--
            IMG--
                        Materials Management--
                                                            Purchasing--
                                                                        Purchase requisition--
                                                                                       Release procedure--
                                                                                                             With Classification—


Practicing:

Now will maintain the release procedure with respect to purchase group and Item category.
Follow the steps as mentioned above:

Edit Characteristic:
Where 1 condition is equal to 1 characteristic
We have 2 conditions here (purchase group and Item category), so we need to maintain 2 characteristics in the path I mentioned above.
OLME-With Classification

Characteristics: M1(Enter M1 and check whether its maintained already or not by clicking specs icon), if not created already then click on create icon next to the spec.
Here we should maintain the field components (Purchase group and item cat from SE11)
Go to additional data and maintain the table name as: CEBAN
Go to SE11 and take the field components by selecting the Purchase group and item cat.
P.group-EKGRP
Item cat-PSTYP
Now in this characteristic, we need to maintain either P.group filed component or Item cat component, because we mentioned above 1 condition =1 characteristics.
Maintain field name as: PSTYP

Now create an another characteristics for P.group

M2(Enter M2 and check whether its maintained already or not by clicking specs icon), if not created already then click on create icon next to the spec.
Here we should maintain the field components (Purchase group and item cat from SE11)
Go to additional data and maintain the table name as: CEBAN
Go to SE11 and take the field components by selecting the Purchase group and item cat.
P.group-EKGRP
Item cat-PSTYP
Now in this characteristic, we need to maintain either P.group filed component or Item cat component, because we mentioned above 1 condition =1 characteristics.
Maintain field name as: EKGRP

Note: Now we maintained the two characteristics that we want to use for release strategy.

Edit Classes:

Here we should define the class for characteristics, where we maintained 2 characteristics and we cannot maintain all characteristics directly to release strategy.
We need to define a class and we need to link all the characteristics in that class, so that in the next steps we can use class instead of all characteristics.
Go to Edit Class-
Class-M3
Class type-Release strategy
Click on create icon
Maintain the description as “Something relevant like this is for PR to convert to PO”
Go to characteristics-maintain the both Char numbers we created above.
M1
M2
Save

Select “setup procedure with classification

Here we need to do some functions like-release groups, release codes, release indicator, release strategies.

Select-Release group:

We need to maintain a new group in release group and we need to assign the class to this release group
M4 (Newley created group) assigned to M3(Class we defined)
Save

Release Codes

Maintain the release codes.
Group we maintained is M4-code is CR and maintain the description.
Here if we want two approvers then we need to maintain 2 column’s M4 and next to maintain CR-creator and MN-Manager and maintain the description as same.
M4-CR
M4-MN

Release Indicator

Maintain new entries, where we need to maintain the Block and release fields here
B-Block
R-Release

Release Strategy

Maintain release group what we maintained-M3 and release strategy number as 10.
Release codes-Mention
CR
MN
Select Prerequisites—
Select the last tab and continue—

Select release statuses---
Select the last tab as R-so that once we get all approvals PR will allow to create PO.
Select Classification
Item cat-Z
P.group-000
Maintain few values for the fields we defined for release strategy.
Now create the PR with above combination, we will see a new tab in the item level…. Release strategy
Go to ME54N and open the PR and release the PR to create PO.
















                       









2 comments:

  1. kindly explain release procedure for contracts and SA

    ReplyDelete
  2. Just u need to select the characteristics as document type and net price , which are common fields for contract and PO

    ReplyDelete

Featured post

What is IDOC? Explanation for Interview Purpose

What is IDOC? Explanation for Interview Purpose: Overview Explanation for Interview purpose Question: What is IDOC ? IDOC i...

Popular Posts