PR Release WF - GRC ME54N

[Florin Wach (SI)]

… what the heck :-) … or hack :-)

Well, in a way yes and no: Normally the releasers, which are involved during the process are cost center owners, project managers or similar … so they usually can ALSO create or change manual requisitions for the own duties.
During the release transaction, the ME54N allows for changes within certain limitations (e.g. change of total value) and otherwise the release procedure will be reset.

However, your requirement might be somewhat easy to achieve via customizing, when you change the release indicator that you’re using DURING the approval, and modify the setting to “No change possible”.
This way, the requisition cannot be changed, while it’s in approval. If someone needs to make a change, the releases need to be reset … somehow… you got to try that out ;-)


Other option: Get a screen user exit or BADI during post that prevents the requisition from beeing changed, other than the release codes.




Mit freundlichen Gruessen / With kind regards 
  Florin Wach 
  Senior Workflow Engineer
  Systems-Integration 

--------------------------------------------------
http://www.systems-integration.net <http://www.systems-integration.net/>
> Am 16.08.2016 um 15:43 schrieb Jeffrey A. Rappaport <Jeff at Business-Workflow.com>:
> 
> Hey WUG’ers,
>  
>   Has anyone had any Clients out there that wound up restricting their Users from having access to both ME51N/ME52N with ME54N, due to real tight GRC ‘Segregation of Duties’ outcomes? And ended up having to redesign the entire PR Release WF process due to no one having access to ME54N?
>  
> Thanx for your feedback,
>  
> Jeffrey A. Rappaport
> Business Workflow Inc. 
> Voice: +1 (561) 508-2555
> Fax:    +1 (866) 301-7666 
> Email: Jeff at Business-Workflow.com <mailto:Jeff at Business-Workflow.com>
> Web: www.Business-Workflow.com <http://www.business-workflow.com/>
> Link: www.linkedin.com/in/businessworkflow <http://www.linkedin.com/in/businessworkflow>
> 
> 
> 
> The information contained in this message may be privileged, confidential and protected from disclosure. If the Reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error and would like to be removed from any future mailings from this Sender, please hit 'Reply' to this email with "REMOVE" in the Subject line.
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20160816/2b1375b8/attachment.html