Download as docx, pdf, or txt
Download as docx, pdf, or txt
You are on page 1of 7

RELEASE STRATEGY

- Release strategy is a process of giving permission to the Purchasing documents for the
further processing.
- Release strategy defines approval process for Purchasing Documents
- Release strategy van be done in two ways
1) With classification – We can release Purchasing document at Item as well at header
level.
2) Without classification – We can release purchasing document only at Item level
- Purchase requisition can be released at Header as we as at item level.
- PO, Scheduling agreements & contracts can only released at Header level only.

- To view Communication table TCODE is SE11.


- Tables for Release strategy
PO – CEKKO, CEKPO
PR – CEBAN, CEBKN

PATH – SPRO – IMG – Materials management – (PO/Contracts/Purchase requisition) – Setup


release strategy
STEPS
1) Edit characteristics
2) Edit class
3) Define Release procedure
A) Release group
B) Release codes
C) Release indicators
D) Release strategies
TEST CASE
Apply release strategy if total net value of PO is greater than 100000 INR.
1) First we have to enter TCODE OLME

From OLME we have to select Purchase Order and under that we have to select
Release procedure for purchase order.

Under the release procedure for purchase order we have to select edit
characteristics

In edit characteristics we have to enter a short key and description for that key
In additional data tab, we have to enter table name & field name

Next step is Edit Class,


Here we have to enter a short key for class and we have to enter a class type
For Release Strategy Class Type is always ‘032’
In characteristics tab we have to assign a characteristic which we have created.

Next step is Define release procedure, under that first step is to create release
group, so we have to enter a key for rel. group & we have to enter a class.

Next step is to define release codes, here we have to enter the codes i.e.
authorities with who’s permission we want to release a document.

(Max 8 levels we can create in release code)

Next step is to define release indicators, These indicators will explain the status
of the document i.e. whether it is released or blocked
After defining release codes next step is to define release strategy, from here we
have to select create new one.
Then we have to enter Release group & we have to enter short key and
description of Release strategy.
Then we have to add the release codes.

After adding rel. codes we have to select release procedure

From here we can decide the sequence of authority through which we want to
release the document.
Next step is release statuses

From here we can configure the condition to release the document i.e. if
Document is released by only one of the Release code then what should happen
and if document is released by total release codes then what should happen i.e.
whether document should get released or not.

Next step is classification,


Here we have to put the value for which release strategy will get applied.
E.g. I am applying release strategy for the PO only when total net value is more
than 100000 rupees, then I have to enter >100000.

In this way we can configure release strategy for PO.

To release PO TCODE is ME29N.


For next session
- Purchasing group, plant, PO creation date, company code, p.org.
- 3-4 new Release codes.
- Invoice verification (Credit note, debit note, subsequent credit)
- Service procurement

You might also like