<html><head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 12 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
p.MsoTitle, li.MsoTitle, div.MsoTitle
{mso-style-priority:10;
mso-style-link:"Title Char";
margin-top:0cm;
margin-right:0cm;
margin-bottom:15.0pt;
margin-left:0cm;
border:none;
padding:0cm;
font-size:26.0pt;
font-family:"Cambria","serif";
color:#17365D;
letter-spacing:.25pt;}
p.MsoTitleCxSpFirst, li.MsoTitleCxSpFirst, div.MsoTitleCxSpFirst
{mso-style-priority:10;
mso-style-link:"Title Char";
mso-style-type:export-only;
margin:0cm;
margin-bottom:.0001pt;
border:none;
padding:0cm;
font-size:26.0pt;
font-family:"Cambria","serif";
color:#17365D;
letter-spacing:.25pt;}
p.MsoTitleCxSpMiddle, li.MsoTitleCxSpMiddle, div.MsoTitleCxSpMiddle
{mso-style-priority:10;
mso-style-link:"Title Char";
mso-style-type:export-only;
margin:0cm;
margin-bottom:.0001pt;
border:none;
padding:0cm;
font-size:26.0pt;
font-family:"Cambria","serif";
color:#17365D;
letter-spacing:.25pt;}
p.MsoTitleCxSpLast, li.MsoTitleCxSpLast, div.MsoTitleCxSpLast
{mso-style-priority:10;
mso-style-link:"Title Char";
mso-style-type:export-only;
margin-top:0cm;
margin-right:0cm;
margin-bottom:15.0pt;
margin-left:0cm;
border:none;
padding:0cm;
font-size:26.0pt;
font-family:"Cambria","serif";
color:#17365D;
letter-spacing:.25pt;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoNoSpacing, li.MsoNoSpacing, div.MsoNoSpacing
{mso-style-priority:1;
margin:0cm;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Times New Roman","serif";}
span.TitleChar
{mso-style-name:"Title Char";
mso-style-priority:10;
mso-style-link:Title;
font-family:"Cambria","serif";
color:#17365D;
letter-spacing:.25pt;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<style type="text/css">
.style1 {font-family: "Times New Roman";}
</style></head><body lang="EN-ZA" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Hi Mark,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Wow! Very interesting. I am not certain of your conditions but I assume you want to perform an Automation of PR release via WF-batch.You did not specify the
type of Pr you want to automate.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">I am assuming that the Pr is released entirely not at an item level.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">My suggestion is that, get a concern approval first ,so that someone can be accountable for such .<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Secondly , you may omit the decision step in your workflow and replace it with an email notification once FW –batch has approved a Pr.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">You can specify the period also . I am not sure what will happen when SoD is being violated based on amounts of each Pr<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal"><b><span style="font-size:8.0pt;font-family:"Arial","sans-serif";color:#1F497D"><o:p> </o:p></span></b></p>
<p class="MsoNormal"><b><span style="font-size:8.0pt;font-family:"Arial","sans-serif";color:#1F497D">Julius Morifi<o:p></o:p></span></b></p>
<p class="MsoNormal"><b><span style="font-size:8.0pt;font-family:"Arial","sans-serif";color:#1F497D">SAP Technical Administrator-Workflow<o:p></o:p></span></b></p>
<p class="MsoNormal"><b><span style="font-size:6.0pt;font-family:"Arial","sans-serif";color:#1F497D">Barloworld Equipment
<o:p></o:p></span></b></p>
<p class="MsoNormal"><b><span style="font-size:6.0pt;font-family:"Arial","sans-serif";color:#1F497D">a division of Barloworld South Aftrica (Pty) Ltd<o:p></o:p></span></b></p>
<p class="MsoNormal"><span style="font-size:6.0pt;font-family:"Arial","sans-serif";color:#1F497D">Electron Avenue Extention Isando<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:6.0pt;font-family:"Arial","sans-serif";color:#1F497D">PO Box 11 Isando 1600 South Africa<o:p></o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:6.0pt;font-family:"Arial","sans-serif";color:#1F497D">Telephone</span></b><span style="font-size:6.0pt;font-family:"Arial","sans-serif";color:#1F497D"> +27 (11) 9290556<o:p></o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:6.0pt;font-family:"Arial","sans-serif";color:#1F497D">Mobile</span></b><span style="font-size:6.0pt;font-family:"Arial","sans-serif";color:#1F497D"> +27 798906900<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><a href="mailto:fmosololi@barloworld-equipment.com"><span style="font-size:6.0pt;font-family:"Arial","sans-serif"">jmorifi@barloworld-equipment.com</span></a></span><span style="font-size:6.0pt;font-family:"Arial","sans-serif";color:#1F497D"><o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> sap-wug-bounces@mit.edu [mailto:sap-wug-bounces@mit.edu]
<b>On Behalf Of </b>Mark Pyc<br>
<b>Sent:</b> 16 August 2016 11:38 PM<br>
<b>To:</b> SAP Workflow Users' Group<br>
<b>Subject:</b> Re: PR Release WF - GRC ME54N<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">Whaaaaat?!?? For real??<o:p></o:p></p>
</div>
<div id="AppleMailSignature">
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div id="AppleMailSignature">
<p class="MsoNormal">Just when I thought WUG was dead it delivers some gold!<o:p></o:p></p>
</div>
<div id="AppleMailSignature">
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div id="AppleMailSignature">
<p class="MsoNormal">My memory isn't great but I don't remember having any problems using background release of PR by WF-BATCH based on user decision approval. I'm all for user decision, system update. It's the only practical way to ensure true instance level
SoD. That's certainly the standard I've set at my current govt client and 2.5 years in we're about to introduce PRs (it's all been Carts so far). <o:p></o:p></p>
</div>
<div id="AppleMailSignature">
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div id="AppleMailSignature">
<p class="MsoNormal">If anyone does know of issues of background release I'd love details. I don't intend to hack around them, I'll be bitching to SAP to get them resolved. Luckily on this project we have their attention and can get things fixed. <br>
<br>
Many thanks!<o:p></o:p></p>
</div>
<div id="AppleMailSignature">
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div id="AppleMailSignature">
<p class="MsoNormal">Have fun,<o:p></o:p></p>
</div>
<div id="AppleMailSignature">
<p class="MsoNormal">Mark<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
On 17 Aug 2016, at 3:35 AM, Bill C <<a href="mailto:billtcraig@gmail.com">billtcraig@gmail.com</a>> wrote:<o:p></o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<div>
<div>
<div>
<div>
<div>
<p class="MsoNormal">Jeffrey,<o:p></o:p></p>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt">I was on a project that did not want users to access ME54N. After about a year of my life and many issues they decided to allow users access. The problems we faced were not so much the simple release of the
PR but rather all the integration into FM budgetary ledger etc. It seems that the simple release from the business object BUS2105 does not invoke any of these integration points. One step I added was executing program RFFMRP34N to create the follow on documents
etc., then trying to figure out how and who should review and handle any errors...the list goes on and on.
<o:p></o:p></p>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt">My advice, and I understand that it is not always easy, would be to convince them there is a reason the standard workflow uses ME54N. I would certainly try Florin's approach rather than trying to work around
ME54N.<o:p></o:p></p>
</div>
<p class="MsoNormal">Thanks,<o:p></o:p></p>
</div>
<p class="MsoNormal">Bill Craig <o:p></o:p></p>
<div>
<div>
<div>
<div>
<div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">On Tue, Aug 16, 2016 at 12:01 PM, <<a href="mailto:sap-wug-request@mit.edu" target="_blank">sap-wug-request@mit.edu</a>> wrote:<o:p></o:p></p>
<p class="MsoNormal">Send SAP-WUG mailing list submissions to<br>
<a href="mailto:sap-wug@mit.edu">sap-wug@mit.edu</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="http://mailman.mit.edu/mailman/listinfo/sap-wug" target="_blank">
http://mailman.mit.edu/mailman/listinfo/sap-wug</a><br>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:sap-wug-request@mit.edu">sap-wug-request@mit.edu</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:sap-wug-owner@mit.edu">sap-wug-owner@mit.edu</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of SAP-WUG digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. PR Release WF - GRC ME54N (Jeffrey A. Rappaport)<br>
2. Re: PR Release WF - GRC ME54N (Florin Wach (SI))<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Tue, 16 Aug 2016 09:43:55 -0400<br>
From: "Jeffrey A. Rappaport" <<a href="mailto:Jeff@business-workflow.com">Jeff@Business-Workflow.com</a>><br>
Subject: PR Release WF - GRC ME54N<br>
To: "SWUG \(SAP\)" <<a href="mailto:SAP-WUG@mit.edu">SAP-WUG@mit.edu</a>><br>
Message-ID: <470D0CB4BF7448E4A6EA169CDB3512E4@jrapp123><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
Hey WUG?ers,<br>
<br>
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?<br>
<br>
Thanx for your feedback,<br>
<br>
Jeffrey A. Rappaport<br>
Business Workflow Inc.<br>
Voice: <a href="tel:%2B1%20%28561%29%20508-2555">+1 (561) 508-2555</a><br>
Fax: <a href="tel:%2B1%20%28866%29%20301-7666">+1 (866) 301-7666</a><br>
Email: <a href="mailto:Jeff@business-workflow.com">Jeff@Business-Workflow.com</a><br>
Web: <a href="http://www.Business-Workflow.com" target="_blank">www.Business-Workflow.com</a><br>
Link: <a href="http://www.linkedin.com/in/businessworkflow" target="_blank">www.linkedin.com/in/businessworkflow</a><br>
<br>
<br>
<br>
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.<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <a href="http://mailman.mit.edu/pipermail/sap-wug/attachments/20160816/3c138b1a/attachment-0001.html" target="_blank">
http://mailman.mit.edu/pipermail/sap-wug/attachments/20160816/3c138b1a/attachment-0001.html</a><br>
<br>
------------------------------<br>
<br>
Message: 2<br>
Date: Tue, 16 Aug 2016 16:08:33 +0200<br>
From: "Florin Wach (SI)" <<a href="mailto:florin.wach@systems-integration.net">florin.wach@systems-integration.net</a>><br>
Subject: Re: PR Release WF - GRC ME54N<br>
To: "SAP Workflow Users' Group" <<a href="mailto:sap-wug@mit.edu">sap-wug@mit.edu</a>><br>
Message-ID:<br>
<<a href="mailto:6D971557-D407-4C76-9995-DA3288B728D5@systems-integration.net">6D971557-D407-4C76-9995-DA3288B728D5@systems-integration.net</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
? what the heck :-) ? or hack :-)<br>
<br>
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.<br>
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.<br>
<br>
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?.<br>
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 ;-)<br>
<br>
<br>
Other option: Get a screen user exit or BADI during post that prevents the requisition from beeing changed, other than the release codes.<br>
<br>
<br>
<br>
<br>
Mit freundlichen Gruessen / With kind regards<br>
Florin Wach<br>
Senior Workflow Engineer<br>
Systems-Integration<br>
<br>
--------------------------------------------------<br>
<a href="http://www.systems-integration.net" target="_blank">http://www.systems-integration.net</a> <<a href="http://www.systems-integration.net/" target="_blank">http://www.systems-integration.net/</a>><br>
> Am 16.08.2016 um 15:43 schrieb Jeffrey A. Rappaport <<a href="mailto:Jeff@business-workflow.com">Jeff@Business-Workflow.com</a>>:<br>
><br>
> Hey WUG?ers,<br>
><br>
> 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?<br>
><br>
> Thanx for your feedback,<br>
><br>
> Jeffrey A. Rappaport<br>
> Business Workflow Inc.<br>
> Voice: <a href="tel:%2B1%20%28561%29%20508-2555">+1 (561) 508-2555</a><br>
> Fax: <a href="tel:%2B1%20%28866%29%20301-7666">+1 (866) 301-7666</a><br>
> Email: <a href="mailto:Jeff@business-workflow.com">Jeff@Business-Workflow.com</a> <mailto:<a href="mailto:Jeff@Business-Workflow.com">Jeff@Business-Workflow.com</a>><br>
> Web: <a href="http://www.Business-Workflow.com" target="_blank">www.Business-Workflow.com</a> <<a href="http://www.business-workflow.com/" target="_blank">http://www.business-workflow.com/</a>><br>
> Link: <a href="http://www.linkedin.com/in/businessworkflow" target="_blank">www.linkedin.com/in/businessworkflow</a> <<a href="http://www.linkedin.com/in/businessworkflow" target="_blank">http://www.linkedin.com/in/businessworkflow</a>><br>
><br>
><br>
><br>
> 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.<br>
> _______________________________________________<br>
> SAP-WUG mailing list<br>
> <a href="mailto:SAP-WUG@mit.edu">SAP-WUG@mit.edu</a><br>
> <a href="http://mailman.mit.edu/mailman/listinfo/sap-wug" target="_blank">http://mailman.mit.edu/mailman/listinfo/sap-wug</a><br>
<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <a href="http://mailman.mit.edu/pipermail/sap-wug/attachments/20160816/2b1375b8/attachment-0001.html" target="_blank">
http://mailman.mit.edu/pipermail/sap-wug/attachments/20160816/2b1375b8/attachment-0001.html</a><br>
<br>
------------------------------<br>
<br>
_______________________________________________<br>
SAP-WUG mailing list<br>
<a href="mailto:SAP-WUG@mit.edu">SAP-WUG@mit.edu</a><br>
<a href="http://mailman.mit.edu/mailman/listinfo/sap-wug" target="_blank">http://mailman.mit.edu/mailman/listinfo/sap-wug</a><br>
<br>
<br>
End of SAP-WUG Digest, Vol 138, Issue 1<br>
***************************************<o:p></o:p></p>
</div>
<p class="MsoNormal"><br>
<br clear="all">
<o:p></o:p></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</blockquote>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal">_______________________________________________<br>
SAP-WUG mailing list<br>
<a href="mailto:SAP-WUG@mit.edu">SAP-WUG@mit.edu</a><br>
<a href="http://mailman.mit.edu/mailman/listinfo/sap-wug">http://mailman.mit.edu/mailman/listinfo/sap-wug</a><o:p></o:p></p>
</div>
</blockquote>
</div>
<br /><br />
<p style="font-family: Verdana; font-size:8pt; color:black;">
This e-mail transmission may contain confidential information, which is the property of Barloworld Equipment a division of Barloworld South Africa (Pty) Ltd (“Barloworld Equipment”). No person, other than the recipient (so indicated by the sender) may use or disclose the contents of this message, links or attachments thereto, to any person. The information in this email, links or attachments thereto is intended for the attention and use of the recipient only – if you are not the intended recipient any use, disclosure, copying or distribution thereof or the taking of any action in reliance thereon is strictly prohibited. Should you have received this e-mail in error, kindly notify the sender immediately by return e-mail and delete the original message.
<br /><br />
The provisions of Sections 11,12, and 13 of the Electronic Communications and Transactions Act, 25 of 2002, in so far as e-contracting is concerned are expressly excluded and contracted out of by Barloworld South Africa (Pty) Ltd (“Barloworld”) and, unless clearly stated to the contrary in the body of the data message or electronic communication no data message or electronic communication will be recognised as having legal contractual status as per the aforementioned provisions under any circumstances. All contracts concluded by Barloworld, its Business Units, Divisions and Subsidiaries will only be legally binding and recognised once reduced to physical writing and physically signed by a duly authorised representative of Barloworld.
All other provisions of the Electronic Communications and Transactions Act, 25 of 2002 are accepted.
<br /><br />
<br />
Although Barloworld Equipment has taken all reasonable precautions to ensure that this e-mail is virus free, Barloworld Equipment does not accept any liability for any damage caused by any virus transmitted by this email.
<br />
<br />
</p><p style="font-family: Verdana; font-size:8pt; color:black;">
<b>
Barloworld Equipment - Integrity + Commitment + Excellence + Teamwork + Sustainability
</b></p>
<br /><br />
<font color="white">itevomcid</font>
<p></p>
</body></html>