Explained full process of release strategy from the scrath

Question

Accepted Answer

The release strategy is a process in SAP MM that determines the approval process for purchasing documents.

Release strategy is defined based on certain criteria such as document type, purchasing organization, and value.
The release strategy is configured in the system using release groups, release codes, and release indicators.
Once a purchasing document is created, it goes through a series of release steps based on the defined release strategy.
Each release step can have multiple release codes assigned to it, and the document can be released by any of the assigned release codes.
The release codes can be assigned to specific users or user groups.
During the release process, the system checks if the document meets the criteria for each release step and if the required release code has been assigned.
If the document meets the criteria and the required release code is assigned, it moves to the next release step.
If the document doesn't meet the criteria or the required release code is not assigned, it remains in the current release step.
Once the document reaches the final release step, it is considered fully released and can proceed with further processing.
The release strategy can be customized to fit the specific approval process requirements of an organization.

Accepted Answer

The Release strategy for purchase order in SAP MM defines the approval process for purchase requisitions or external purchasing documents.

Accepted Answer

Release procedure: 
Purposes: Its used for PO approval generally, To Monitor the PO, Business Unit wise.
For the requirement PO which is an external doc , need to be approval by L1,L2, L3 Approval.
SAP Release strategy is the solution. This can be achieved by below steps.
CEKKO-Communication table for PO Release strategy.
In SAP we have a run time structure with name CEKKO (Communication Release Strategy Determination Purch. Document) which provides all the possible list of fields using which a release strategy can be configured.
Configuration:
Define characteristic-
 CT04 SPRO-MM-PUR-PO-RELESE PROCE. FOR PO-EDIT CHAR.
In characteristic We can have the parameters like Pur. Org EKORG, doc type BSART  , net PO value GNETW, currency ect.. for which PO should go for approval.
Define class  – BP
Grouping the characteristic into Class CL02 SPRO-MM-PUR-PO-RELESE PROCE. FOR PO-EDIT CLASS.
Class type 032 is mandatory 
Define Release strategy  
SPRO-MM-PUR-RELEASE PROCEDURE FOR PO-DEFINE RELEASE PROCEDURE
1.	Release Group- its created BP, multiple are created for in case multiple approver are required.
2.	Release Code 01,02,03 This are approver of PO ie.. L1,L2,L3 
3.	Release strategy ( A. Release pre-request B. Release status C. Release classification D.  Release simulation classification.)
Pre-Request shows sequence of approver 
In release status, its defined if PO status ie.. Blocked or released.
In Release classification CLASS/RELEASE GROUP/CLASSIFFICATION synchronization can be seen. 
If addition values are allowed at character creation then values can be added hear.
4.	Work Flow- hear with help of ABAP WF is maintained or 
Release code/description/ User ID are maintained and Authorization need to be provided for ME28 T-code.

Explained full process of release strategy from the scrath

Top TCS SAP MM Consultant interview questions & answers

Popular interview questions of SAP MM Consultant

Top HR questions asked in TCS SAP MM Consultant