Skip to Content

Release Strategy: Restrict lower users to revoke PO after the complete release by superior

Dear Friends,


I would like to share with you all a scenario which I’ve come across in ‘PO Release Strategy’, and the requirement has been met by introducing a small enhancement.


Note: There was no solution in ‘Standard SAP’ (confirmed by SAP), thus achieved the requirement thru enhancement


The Scenario:


Example: PO Release Strategy is configured for 3 level as explained below;


1st Level:      L2 – Local Purchase Manager

2nd Level:     L3 –  Finance Manager

3rd Level:      GM – General Manager (Final/Highest Level)


For the above stated release strategy the standard SAP has provided an option to the 1st and 2nd (L2 – Local Purchase Manager & Finance Manager) level approvers to revoke the purchase order, which is released completely by 3rd level (General Manager). Few business advises to restrict this functionality, as they expect the functionality should be like once the PO gets released by General Manager (final approver), neither Finance Manager nor Local Purchase Manager should have the authorization to revoke the PO, until the General Manager revokes it.

Solution:

Restricted the release authorization at the role level for the transaction code ME29N, by doing screen enhancement. Since the requirement is not achievable in standard sap (confirmed by SAP).


Steps:

  1. Go to transaction code ME29N–> enter purchase order number, which is waiting for release–> enter /h (debug mode) in command bar–> then click on ‘Release Strategy’ tab in PO header–>it would take you to the program ‘SAPLMERELVI–> find out for the ‘Include – lmerelvici1–>double click on the include and then go to method ‘HOTSPOT_CLICK–> write the restriction logic for the desired roles as shown in below logic.

Transaction Code: ME29N

Program Name: SAPLMERELVI

Include Program: LMERELVICI1 

In Method: HOTSPOT_CLICK

Method.png

Method2.png


Fucnctional Logic:

  1. Once we go to the transaction ME29N to release the PO, the program would check for the PO release status (Structure: MEPO_REL_GENERAL- FRGKX≠ R or (Just for reference: EKKO-FRGRL=X))–> if the PO is not completely released (FRGKX ≠ R) skip the process–>  if the PO is released completely (FRGKX = R or (Ref: EKKO-FRGRL= ‘ ’)) go to table AGR_USERS (list of users) and check for the role–> if the user has role: ‘GM:GENERAL_MANAGER‘, allow the user to revoke the PO–> if he doesn’t has the given role, display an error message as ‘You are not Authorized to revoke the Release Strategy, until final level revokes the PO

Design.png


ABAP Code:

IF sy-tcode = ‘ME29N’.
TYPES:
BEGIN OF ty_agr_users,
agr_name
TYPE agr_users-agr_name,
uname
TYPE agr_users-uname,
END OF ty_agr_users.

DATA : lv_user TYPE sy-uname,
it_agr
TYPE TABLE OF ty_agr_users,
wa_agr
TYPE ty_agr_users.

if MEPO_REL_GENERAL-FRGKX = ‘R’.

lv_user = sy-uname.
SELECT
agr_name
uname
FROM agr_users
INTO TABLE it_agr
WHERE uname = lv_user.

READ TABLE it_agr INTO wa_agr WITH KEY agr_name = ‘GM:GENERAL_MANAGER’.
IF sy-subrc <> 0.
MESSAGE ‘You are not Authorized to revoke the Release Strategy, until the final level revokes the PO’ TYPE ‘I’ .
EXIT.
ENDIF.
ENDIF.
clear : lv_user,it_agr,wa_agr.
ENDIF.


Result:

Local Purchase Manager is trying to revoke a purchase order, which has already released by Finance Manager & General Manager, but system is throwing an error message, as expected.

Error.png     

Hope this document is clear for you and helps you in your current or future project(s) .

Thank you for reading the document .

Narayana N

34 Comments
You must be Logged on to comment or reply to a post.