Customer

SAP Product Support Webinar

Release Strategy (MM-PUR-GF-REL)
Lorraine Donnelly, Brian King
March 14, 2017
 Customer

Identify and resolve common issues in Release

Strategies for Purchasing Documents
 Agenda
1. Brief overview of Release Strategy in Requisition/ Purchase Order documents.

2. Customizing setup.

3. Demo.

4. Checklist to detect and solve Release Strategy issues.

5. Frequently Asked Questions.

6. Relevant KBA’s and Notes.

© 2016 SAP SE or an SAP affiliate company. All rights reserved. Customer 3

Release Strategies

Approve REQ (RELEASE)

© 2016 SAP SE or an SAP affiliate company. All rights reserved. Customer 4

 Release
Group

Release
Class
Code

Release
Strategy

Characteristics Release
Indicator
Release
Strategy

© 2016 SAP SE or an SAP affiliate company. All rights reserved. Customer 5

Configuration of Release strategy

SPRO: Materials Management->Purchasing->Purchase Order/Purchase Requisition->Release Procedure for

Purchase order

 Edit Characteristic(Transaction CT04)

 Edit Class(Transaction CL02) ,Class type 032

 Define Release Strategy for Purchase Order

 Release Groups
 Release Codes
 Release Indicator
 Release Strategies

© 2016 SAP SE or an SAP affiliate company. All rights reserved. Customer 6

 Purchase Requisition
Type of Release

Item Release check Overall Release

Item class Overall class

CLASS CLASS

FRG_EBAN_ITEM FRG_EBAN

Characteristic Characteristic

CEBAN-GSWRT CEBAN-GFWRT

Customizing setting
Release group: Flag ‘OverReqRel’ (V_T16FG-FRGFG)
Document type Flag ‘OverReqRel’ (V_T161-GSFRG)
MUST BE SET/NOT SET DEPENDING ON TYPE OF RELEASE

© 2016 SAP SE or an SAP affiliate company. All rights reserved. Customer 7

DEMO
CHARACTERISTICS/ CLASS

Characteristic view Class view

© 2016 SAP SE or an SAP affiliate company. All rights reserved. Customer 9

Release strategy

Scenario 1

Values in PO subject to release strategy

Order type LNB
Purchasing group 001

Material group 01

Total net order value <500.00, >500.00 Euro

Purchasing Document Category F

© 2016 SAP SE or an SAP affiliate company. All rights reserved. Customer 10

Release strategy DL LD is not triggered for PO 4500036257

Scenario 2

Values in PO subject to release strategy

Order type NB
Purchasing group 001
Material group 01,02,03
Total net order value €3900.00
Purchasing Document Category F

© 2016 SAP SE or an SAP affiliate company. All rights reserved. Customer 11

Checklist
Characteristic Checks

The release procedure for purchasing documents is carried out on header level. For this, the following values are
aggregated from the items on header level:
* item value
* plant
* material group
The plant is only aggregated on header level if all items contain the same plant. If more than one alternative plant exists, ' ' is
aggregated on header level. A release strategy is then searched for with this value.
Of course, a corresponding strategy is only found if the value ' ' was maintained for the characteristic 'Value' as an object
value.

Maintain blank characteristic in CT04.

Cost center/material numbers/version number

The characteristics must be entered as they are specified on the database, that is, the item category must be entered in the
internal format, for example (value 0-9), values must be entered with leading zeros.

Item category
In case the item category is used as a characteristic, check that the customer uses the internal format defined in customizing.

© 2016 SAP SE or an SAP affiliate company. All rights reserved. Customer 13

Enhancement M06B0002 (REQ), M06E0004(PO)
CALL CUSTOMER-FUNCTION '004'
Purchase Requisitions EXPORTING
i_ceban = ceban
IMPORTING
e_ceban = ceban
EXIT_SAPLEBND_001 TABLES
E_CEBAN= I_CEBAN c_eban = t_geban_new
EXIT_SAPLEBND_004 c_ebkn = t_gebkn_new.
IF ceban EQ *ceban. ---------------breakpoint to see the values of CEBAN after
the user exit
EXIT.

Purchase orders ENDIF.

Remark:
The user exist used for overall release is EXIT_SAPLEBND_004.

Program MM06EF0S_STRATEGIE_CEKKO:
if sy-subrc eq 0 and not l_active is initial.
EXIT_SAPLEBND_002 E_CEKKO = I_CEKKO call function 'EXIT_SAPLEBND_002'
exporting
i_cekko = cekko
it_bekpo = pot[]

Following user fields are available in CEKKO/CEBAN it_beket = ett[]

it_ekknu = knt[]
USRC1, USRC2 importing
e_cekko = cekko.
USRN1, USRN2
endif. ---------------breakpoint to see the values of CEKKO after the user exit

© 2016 SAP SE or an SAP affiliate company. All rights reserved. Customer 14

Release strategy LH LD is not triggered for PO 4500036225

Scenario 3

Values in PO subject to release strategy

Order type NB
Purchasing group 001
Material group 01,02
Total net order value €750
Purchasing Document Category F

© 2016 SAP SE or an SAP affiliate company. All rights reserved. Customer 15

Check is user exit active

Check transaction CMOD, enter project name

Transaction SE37
Enter function module, EXIT_SAPLEBND_002 (Purchase Orders)
EXIT_SAPLEBND_004 (item Requisition)
EXIT_SAPLEBND_001 (overall Requisition)

Transaction SE38, Program :MM06EF0S_STRATEGIE_CEKKO

Set breakpoint

CALL FUNCTION 'MODX_FUNCTION_ACTIVE_CHECK'

IF sy-subrc EQ 0 AND NOT l_active IS INITIAL.

© 2016 SAP SE or an SAP affiliate company. All rights reserved. Customer 16

Steps to determine why release strategy is not triggered
1. Go into transaction CL30N and enter the values of the document and click on the button ‘find in initial class’. If you do not get
a result, check the customizing if there is a release strategy which matches the values of the document.

2. If more than one release strategy is determined

3. If you get exactly one result, it is an indicator that the customizing was defined correctly. Then check:

4. Characteristic checklist, all values entered correctly

5. Is there a userexit activated (see note 365604 for the user exit name)? If yes, check if it contains the magic line (for
purchase requisition: ‘E_CEBAN = I_CEBAN’, for purchase order ‘E_CEKKO = I_CEKKO’).

© 2016 SAP SE or an SAP affiliate company. All rights reserved. Customer 17

Frequently Asked Questions

Deletion of Release strategy

• See note 365604, point 5
Report RCCLZUOB
When running the report, make use of the following parameters:
Class Type 032
Object Table KSSK
Delete X
• Please refer to KBA 2417519

Changes to Release strategy

• Please refer to KBA 1635346

Multiple currencies in Release strategy

• Please refer to KBA 1739381

Version Management
• Please refer to KBA 1961482
1961585

Missing release strategy tab for PO on hold

• Please refer to KBA 1981241
© 2016 SAP SE or an SAP affiliate company. All rights reserved. Customer 18
Function modules/BAPI

Requisitions
ME_REL_GENERAL_STRATEGY_EBAN
ME_REL_STRATEGY_REQUISITION

Purchase Orders
ME_REL_STRATEGIE_EKKO
MM06EF0S_STRATEGIE_CEKKO
CLSC_SELECT_OBJECTS (How many release strategies are found)

BAPI’S
BAPI_PO_RELEASE
BAPO_PO_RESET_RELEASE
BAPI_PO_GETRELINFO

Authorisation object M_EINK_FRG

© 2016 SAP SE or an SAP affiliate company. All rights reserved. Customer 19

Q&A
Thank you