This document provides an overview of the PO Release process in SAP MM. It defines key terms like release strategy, release group, and release code. A release strategy specifies the approval process and sequence for purchase requisitions. Release groups allow multiple use of the same release strategy. Individuals approve documents by entering their release code, which assigns a release indicator showing the document's status. The input transaction in ME29N is used for individual releases.

1. TRF-SURE-EU TRG Manual (PO Release) – 011 Rev. 00
Page 1 of 5
!" " # $ % $ & '(( )''
End User Training Manual
for
SAP MM – Material Management
Process Name: PO Release process
Process No: PO Release
Control Copy No: PO Release/01
*+ * $
Doc Version Description Prepared by Date Reviewed by Approved by
00 Draft Srinivas .T 25/12/2009

2. TRF-SURE-EU TRG Manual (PO Release) – 011 Rev. 00
Page 2 of 5
Use
You use this component if you wish to set up approval procedures for purchase requisitions or other
purchasing documents. Under such a procedure, if a purchase requisition or external purchasing
document fulfils certain conditions (e.g. the total order value exceeds $10,000), it has to be approved
(by the cost centre manager, for instance) before it can be processed further. This process of
approving (clearing, or giving the "green light" to) a proposed item of expenditure is replicated in the
SAP System by the "release procedure".
It is sensible to define separate release procedures for different groups of materials for which different
departments are responsible, and to define separate procedures for investment goods and
consumption goods.
Features
Each person involved in the release procedure effects release (signifies approval) via a release
transaction, using his or her release code. Once effected, a release can also be cancelled with the
same code (that is to say, the original status is reinstated).
Release Strategy
Definition
The release strategy defines the approval process for purchase requisitions or external purchasing
documents. The strategy specifies the release codes necessary and the sequence in which releases
have to be affected. You can define a maximum of eight release codes.
Release group-Contains one or more release strategies.
Use
This permits the multiple usage of the same release strategy key.
Example
Release group 01 is defined for purchase requisitions and release group 02 for purchase orders. You
can define release strategy S3 for both purchase requisitions and purchase orders.
Release indicator
Indicates the release status of a purchasing document
When you have approved a purchasing document with your release code, a release indicator is
assigned to the document. The release indicator determines how the document may be processed
further (for example, whether a requisition may be converted into a PO or whether the release point is
required to approve the document).

3. TRF-SURE-EU TRG Manual (PO Release) – 011 Rev. 00
Page 3 of 5
Release code
Specifies the release code with which you can process a purchase requisition item, an entire
requisition, or an entire purchasing document within the relevant release strategy.
Note: ME28-Collective release
Input Transaction in the command tool bar (ME29N-Individual release)
Click on the Release strategy tab in the Header details area
1. Enter release code.
2. Select PO and click release strategy. to release the requisition
3. Release status changes to released.

4. TRF-SURE-EU TRG Manual (PO Release) – 011 Rev. 00
Page 4 of 5
Finally Save.

5. TRF-SURE-EU TRG Manual (PO Release) – 011 Rev. 00
Page 5 of 5