<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">… what the heck :-) … or hack :-)<div class=""><br class=""></div><div class="">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.</div><div class="">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.</div><div class=""><br class=""></div><div class="">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”.</div><div class="">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 ;-)</div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">Other option: Get a screen user exit or BADI during post that prevents the requisition from beeing changed, other than the release codes.</div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""><div class="">
<div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class="">Mit freundlichen Gruessen / With kind regards <br class=""> Florin Wach <br class=""> Senior Workflow Engineer<br class=""> Systems-Integration <br class=""><br class="">--------------------------------------------------<br class=""><a href="http://www.systems-integration.net" class="">http://www.systems-integration.net</a></div></div></div>
</div>
<br class=""><div><blockquote type="cite" class=""><div class="">Am 16.08.2016 um 15:43 schrieb Jeffrey A. Rappaport <<a href="mailto:Jeff@business-workflow.com" class="">Jeff@Business-Workflow.com</a>>:</div><br class="Apple-interchange-newline"><div class="">
<div dir="ltr" class="">
<div dir="ltr" class="">
<div style="FONT-SIZE: 10pt; FONT-FAMILY: 'Book Antiqua'; COLOR: #0000ff" class="">
<div class="">Hey WUG’ers,</div>
<div class=""> </div>
<div class=""> 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?</div>
<div class=""> </div>
<div class="">Thanx for your feedback,</div>
<div class=""> </div>
<div style="FONT-SIZE: 10pt; FONT-FAMILY: 'Book Antiqua'; COLOR: #0000ff" class="">Jeffrey A.
Rappaport<br class="">Business Workflow Inc. <br class="">Voice: +1 (561)
508-2555<br class="">Fax: +1 (866) 301-7666 <br class="">Email: <a href="mailto:Jeff@Business-Workflow.com" class="">Jeff@Business-Workflow.com</a><br class="">Web:
<a href="http://www.business-workflow.com/" class="">www.Business-Workflow.com</a><br class="">Link:
<a href="http://www.linkedin.com/in/businessworkflow" class="">www.linkedin.com/in/businessworkflow</a><br class=""><br class=""><br class=""><br class=""><em class="">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.</em></div></div></div></div>
_______________________________________________<br class="">SAP-WUG mailing list<br class=""><a href="mailto:SAP-WUG@mit.edu" class="">SAP-WUG@mit.edu</a><br class="">http://mailman.mit.edu/mailman/listinfo/sap-wug<br class=""></div></blockquote></div><br class=""></div></body></html>