Prepared by:

Sudhakar A L
EAS – SAP Practice
Sudhakar.lakshmegowda@wipro.com

© Wipro Limited, 2002, All Rights Reserved.

This document is proprietary to Wipro Technologies, a division of Wipro Limited.
You may not modify, copy, reproduce, republish, upload, post, transmit or distribute any
material from this document, in any form or by any means, nor may you modify or create
derivative works based on the text of any file, or any part thereof for public, private or
commercial use, without prior written permission from Wipro Limited.
 Implementing Release Strategy in SAP

Introduction

This document gives an insight on

 What information is required to set up release strategy?
 How to segregate the required data for setting up new release strategy?
 What all configurations are required to be set up in SAP to enable release
strategy for Purchase order?

Business Scenario

ABC Company is into Manufacturing and Trading.

 Currently it purchases Raw materials for its internal consumption for
manufacturing.
 It also purchases materials from its vendors for its go-going trading
business.
 It wants to control the material purchases done for trading and
manufacturing separately. Hence it has identified the persons who are
responsible for purchasing as well as for approving the purchases.
 It has given authorization for each personal to approve for certain value of
purchase.

Wipro Technologies Confidential Page 2 of 8

Organisation Structure - Business

Purchase Department – Trading

GM – Trading Purchases

Manager – Trading Purchases

Sr. Executive – Trading Purchases

Buyer - 1 Buyer - 2 Buyer - 3

Purchase Department – Manufacturing

GM – Manufacturing Purchases

Manager - Manufacturing Purchases

Sr. Executive – Manufacturing Purchases

Buyer - 4 Buyer - 5 Buyer - 6

Wipro Technologies Confidential Page 3 of 8

Organisational Structure in SAP

Purchase Organisation for Trading

Purchase Organisation Trading

Purchase Group - 1
TRAD
Purchase Group - 2

Purchase Group - 3

Plant - 1000

Storage Storage
Location Location
0001 0002

Purchase Organisation for Manufacturing

Purchase Organisation
Purchase Group - 4
Manufacturing - MANF
Purchase Group - 5

Purchase Group - 6

Plant - 2000

Storage Storage
Location Location
0003 0004

Wipro Technologies Confidential Page 4 of 8

 Configuration in SAP

In this scenario we are trying to implement release strategy for each Purchase
organisation based on Purchase value and Plant used in purchase Orders.

Collect the data as below for implementing Release strategy

Release SAP User ID

Purchase Document Release Release
Plants Value Limit Level / to be
Organisation Type Group Strategy
Code assigned
TRAD 1000 NB > 0.01 - 10000.00 INR 50 L1 R1 User1
      > 1000.01 - 100000.00 INR 50 L2 R2 User2
      > 100000.01 INR 50 L3 R3 User3
MANF 2000 NB > 0.01 - 10000.00 INR 51 L1 R1 User4
      > 1000.01 - 100000.00 INR 51 L2 R2 User5
      > 100000.01 INR 51 L3 R3 User6

Characteristics

We need to create 4 characteristics and maintain all respective organisation units

as characteristics values (refer the table above)
1. PO_PURCHASE_ORG
2. PO_PLANT
3. PO_ORDER_TYPE
4. PO_VALUE_LIMIT

Class

 We can use the existing Class PO_RELEASE and Class Type = 032

 In class PO_RELEASE we need to maintain all the characteristics on

which we need to control the release of PO.

 In the scenario given we need to implement release strategy for trading

separately and manufacturing separately. For Trading and manufacturing
we have the same control setup hence we can use the existing class.

Wipro Technologies Confidential Page 5 of 8

Release Procedure setup for Purchase Orders - OMGS

Release Groups

 Since there are two purchase departments operated by different group of

peoples we need to create two Release Groups.

 There are there levels of release application for each purchasing cycle.
Hence we need to create 3 release strategies in SAP.

Release codes

There are three persons nominated in purchase department for authorizing the
purchases done. Hence three release cods are created in Sap. Since Roles can
be reusable we have created only 3 release codes R1, R2, R2 with generic Role
Names Like
R1 – Executive
R2 – Manager
R3 – General Manager

Release Strategy

At each release group and release strategy combination we need to maintain the
respective SAP organisation unit value for which the release strategy should be
application along with the value limit applicable for releasing PO’s.

Wipro Technologies Confidential Page 6 of 8

Release Pre-requisites

In release strategy we need to maintain the pre-requisite for releasing the

purchase order

 If value range is within Level-1

Only R1 release is applicable

 If value range is within Level-2

First R1 should release
Then R2 should release
Or
We can setup in such a way that, if R2 releases the Purchase Orders then
the entire order is released in total.

 If value range is within Level-3

The same thing applies in case of Level3 also.
First R1 should release
Then R2 should release
Then Subsequently R3 should release
Or
We can setup in such a way that, if R3 alone or R3 along with R1 or R3
along with R2 can release the Purchase Orders in total.

Wipro Technologies Confidential Page 7 of 8

 SAP Transactions

Slno Transaction Description Key Fields Values

1. CT04 Create Class Characteristic Name Maintain all
allowed values
Characteristic Value
2. CL02 Change Class Class number PO_RELEASE

Class type Maintain

characteristics
Characteristic Name created in step1
3. OMGS Release Procedure Setup the following Values are given
-Purchasing Documents Release Group in the table
Release Codes discussed above
Release Indicator
Release Strategy
4. ME21N Create Purchase Order
5. ME22N Change Purchase Order Check for
release strategy
picked up
6. ME28 Release Purchase
Documents

*****

Note:

Refer Document Titled Instructions for Configuring Release procedure with

Classification on Wipro Knet which is a good note for beginners on release
procedure configuration.

Wipro Technologies Confidential Page 8 of 8