You need to quicky configure a simple multi-level (e.g. 3) release strategy for the Purchase Requisition based on Purchasing Group and PR Value with classification. The following steps drive you in the configuration:
1. Be aware of some Key terms:
- Release Codes – The different levels that the approval will go through.
- Release Groups – Grouping of strategies.
- Release Strategy – Unique, set of condition, sequence and levels of releases. Every line in diagram is a Strategy (so we have 3).
- Release Indicator / Status – The status of PR as it moves through the strategy. Example ‘Block’ (can’t create PO yet) or ‘Final Release’ (can create PO from PR)
2. With T-Code CL04 you define a new class (e.g. ZCLIENT_PR_RELEASE).
3. With T-Code CL04 you directly create the following new characteristics:
- Characteristic to identify the Purchasing Group (e.G. ZCLIENT_PGROUP), CHAR, 3 char, table name CEKKO, Field name EKGRP class type 32, multiple values
- Characteristic to identify the Value (e.G. ZCLIENT_VALUE), CHAR, 15 char, deciamal 2 char, template _____________,__ class type 32, multiple values, Interval allowed.
4. With SPRO > .. > Set Up Procedure with Classification
- Release Groups: create group 01, class ZCLIENT_PR_RELEASE, Description (Flag overall purchase requisition release if you want to release the entire value instead of the single items)
- Release Codes: create four release codes as follow
01 L1 1 CLIENT 1st Releaser
01 L2 1 CLIENT 2nd Releaser
01 L3 1 CLIENT 3rd Releaser - Release Indicator: define the following release indicators with relevant settings
A Released
R Rejected
X Not Released - Release Strategies: define one strategy for each code/level of release. For each strategy you enter the releasing steps required based on the value and PGroup and the relevant statuses. (e.g. L1, L2, L3 – Statuses X,X,X,A – Classification PGruop XXX, Value >= 10.000 EUR)
5. With SPRO > .. > Define document types you define whether the PR must be released either on item level or on document level.
Customer Service 