<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<style>
<!--
@font-face
        {font-family:Calibri}
@font-face
        {font-family:Tahoma}
@font-face
        {font-family:Andalus}
@font-face
        {font-family:"Arial Black"}
@font-face
        {font-family:Verdana}
p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0in;
        margin-bottom:.0001pt;
        font-size:12.0pt;
        font-family:"Times New Roman","serif"}
a:link, span.MsoHyperlink
        {color:blue;
        text-decoration:underline}
a:visited, span.MsoHyperlinkFollowed
        {color:purple;
        text-decoration:underline}
p
        {margin-right:0in;
        margin-left:0in;
        font-size:12.0pt;
        font-family:"Times New Roman","serif"}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
        {margin:0in;
        margin-bottom:.0001pt;
        font-size:8.0pt;
        font-family:"Tahoma","sans-serif"}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
        {margin-top:0in;
        margin-right:0in;
        margin-bottom:0in;
        margin-left:.5in;
        margin-bottom:.0001pt;
        font-size:12.0pt;
        font-family:"Times New Roman","serif"}
span.hoenzb
        {}
span.EmailStyle18
        {font-family:"Calibri","sans-serif";
        color:#1F497D}
span.EmailStyle20
        {font-family:"Calibri","sans-serif";
        color:#1F497D}
span.BalloonTextChar
        {font-family:"Tahoma","sans-serif"}
.MsoChpDefault
        {font-size:10.0pt}
@page WordSection1
        {margin:1.0in 1.0in 1.0in 1.0in}
div.WordSection1
        {}
ol
        {margin-bottom:0in}
ul
        {margin-bottom:0in}
-->
</style>
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt; font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:#1F497D">Julius,</span></p>
<p class="MsoNormal"><span style="font-size:11.0pt; font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:#1F497D">&nbsp;</span></p>
<p class="MsoNormal"><span style="font-size:11.0pt; font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:#1F497D">Not really a guru, but here is my $0.02&#8230;</span></p>
<p class="MsoNormal"><span style="font-size:11.0pt; font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:#1F497D">&nbsp;</span></p>
<p class="MsoNormal"><span style="font-size:11.0pt; font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:#1F497D">Your question as posed is more of a process question than a workflow question.&nbsp; There are a lot of dependencies that relate to the process that have to be
 answered before you decide on how to implement a solution.&nbsp; For example, what if the PO gets cancelled, what if the user really wants to add more quantity or value to the PR, what if the user needs another line item, etc&#8230; .&nbsp; There are a lot of consequences
 to just forcing a quick solution for all documents that really only solves a narrow range of conditions (that users might be complaining about).&nbsp; Having said that&#8230;</span></p>
<p class="MsoNormal"><span style="font-size:11.0pt; font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:#1F497D">&nbsp;</span></p>
<p class="MsoNormal"><span style="font-size:11.0pt; font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:#1F497D">Of course if you have already thought of all this and you have solid processes that support such a change, I can recommend a few of courses of action for
 you:</span></p>
<p class="MsoListParagraph" style="text-indent:-.25in"><span style="font-size:11.0pt; font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:#1F497D"><span style="">1.<span style="font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><span style="font-size:11.0pt; font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:#1F497D">There are customizing settings in MM-&gt; Purchasing-&gt;Purchase Requisitions-&gt;Define Screen layout at Document Level that can be used to force screen fields as
 hidden, display only, optional, or mandatory.&nbsp; These settings DO take into account the so-called &#8220;release indicator&#8221; given to released purchase requisitions and involve sets of &#8220;field selection keys&#8221;.&nbsp; You will have to read the documentation in SPRO as the
 use of these keys is bad-ugly to anyone not familiar with how they work (talk to your local purchasing consultant).</span></p>
<p class="MsoListParagraph" style="text-indent:-.25in"><span style="font-size:11.0pt; font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:#1F497D"><span style="">2.<span style="font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><span style="font-size:11.0pt; font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:#1F497D">A user exit / BAdI for ME52, ME52N, or any other transaction can be used to force whatever you want into place (talk to your local ABAPer)</span></p>
<p class="MsoListParagraph" style="text-indent:-.25in"><span style="font-size:11.0pt; font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:#1F497D"><span style="">3.<span style="font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><span style="font-size:11.0pt; font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:#1F497D">A quick and dirty would be to modify the workflow to look at say, field EBAN-EBELN for a PO value and not start the workflow if it finds one.&nbsp; Use the workflow
 log and transaction SWETYPV to find the event / workflow linkage and of course SWDD / PFTC / etc&#8230; to modify the tasks and workflow to suite your needs.</span></p>
<p class="MsoNormal"><span style="font-size:11.0pt; font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:#1F497D">&nbsp;</span></p>
<p class="MsoNormal"><span style="font-size:11.0pt; font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:#1F497D">I hope that helps.&nbsp; We have had similar problems over the years, but due to a variety of reasons, the only action we ever took was to train the help desk
 on the proper response to the users who are having problems ;-)</span></p>
<p class="MsoNormal"><span style="font-size:11.0pt; font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:#1F497D">&nbsp;</span></p>
<div>
<p class="MsoNormal"><b><span style="font-size:13.5pt; font-family:&quot;Arial Black&quot;,&quot;sans-serif&quot;; color:olive">Michael McLey</span></b><b><span style="font-size:11.0pt; font-family:&quot;Arial Black&quot;,&quot;sans-serif&quot;; color:olive">&nbsp;</span></b><span style="font-size:11.0pt; font-family:&quot;Arial Black&quot;,&quot;sans-serif&quot;; color:olive"><br>
MBUSI - IT Parts &amp; Administration </span><span style="font-size:10.0pt; font-family:&quot;Arial Black&quot;,&quot;sans-serif&quot;; color:olive"><br>
Mercedes-Benz US International, Inc.</span><span style="font-size:11.0pt; font-family:&quot;Arial Black&quot;,&quot;sans-serif&quot;; color:olive">&nbsp;</span><span style="font-size:10.0pt; font-family:&quot;Arial Black&quot;,&quot;sans-serif&quot;; color:olive"><br>
1 Mercedes Drive</span><span style="font-size:11.0pt; font-family:&quot;Arial Black&quot;,&quot;sans-serif&quot;; color:olive">&nbsp;</span><span style="font-size:10.0pt; font-family:&quot;Arial Black&quot;,&quot;sans-serif&quot;; color:olive"><br>
Vance, AL 35490</span><span style="font-size:11.0pt; font-family:&quot;Arial Black&quot;,&quot;sans-serif&quot;; color:olive">&nbsp;</span><span style="font-size:10.0pt; font-family:&quot;Arial Black&quot;,&quot;sans-serif&quot;; color:olive"><br>
PHONE: &nbsp;(205) 462 - 5239</span><span style="font-size:11.0pt; font-family:&quot;Arial Black&quot;,&quot;sans-serif&quot;; color:olive">&nbsp;</span><span style="font-size:10.0pt; font-family:&quot;Arial Black&quot;,&quot;sans-serif&quot;; color:olive"><br>
EMAIL: &nbsp; </span><span style="font-size:11.0pt; font-family:&quot;Arial Black&quot;,&quot;sans-serif&quot;; color:#1F497D"><a href="mailto:michael.mcley@daimler.com"><span style="font-size:10.0pt">michael.mcley@daimler.com</span></a></span><span style="font-size:11.0pt; font-family:&quot;Arial Black&quot;,&quot;sans-serif&quot;; color:olive">&nbsp;
 &nbsp;</span><span style="font-size:11.0pt; font-family:&quot;Arial Black&quot;,&quot;sans-serif&quot;; color:#1F497D"><br>
<br>
</span></p>
</div>
<p class="MsoNormal"><span style="font-size:11.0pt; font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:#1F497D">&nbsp;</span></p>
<div>
<div style="border:none; border-top:solid #B5C4DF 1.0pt; padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:10.0pt; font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style="font-size:10.0pt; font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> sap-wug-bounces@mit.edu [mailto:sap-wug-bounces@mit.edu]
<b>On Behalf Of </b>Julius Morifi<br>
<b>Sent:</b> Tuesday, February 25, 2014 7:06 AM<br>
<b>To:</b> SAP Workflow Users' Group<br>
<b>Subject:</b> RE: [Privileged] Enhance sap class with custom event</span></p>
</div>
</div>
<p class="MsoNormal">&nbsp;</p>
<p class="MsoNormal"><span lang="EN-ZA" style="font-size:11.0pt; font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:#1F497D">Hi Gurus!</span></p>
<p class="MsoNormal"><span lang="EN-ZA" style="font-size:11.0pt; font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:#1F497D">I need help or advice on the following. When a PR has been created and released, automatic PO get created and then goods is receipted. My issues
 is </span></p>
<p class="MsoNormal"><span lang="EN-ZA" style="font-size:11.0pt; font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:#1F497D">That I need to Gray out( non-editable) the valuation price on the PR. My user keep changing this price and this triggers the release strategy&nbsp;
 again and</span></p>
<p class="MsoNormal"><span lang="EN-ZA" style="font-size:11.0pt; font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:#1F497D">It irritates the releaser since the pr was previously done.</span></p>
<p class="MsoNormal"><span lang="EN-ZA" style="font-size:11.0pt; font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:#1F497D">&nbsp;</span></p>
<p class="MsoNormal"><span lang="EN-ZA" style="font-size:11.0pt; font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:#1F497D">Please HELP.</span></p>
<p class="MsoNormal"><span lang="EN-ZA" style="font-size:11.0pt; font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:#1F497D">&nbsp;</span></p>
<p class="MsoNormal"><span lang="EN-ZA" style="font-size:11.0pt; font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:#1F497D">Regards,</span></p>
<p class="MsoNormal"><span lang="EN-ZA" style="font-size:11.0pt; font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:#1F497D">Julius.</span></p>
<p class="MsoNormal"><span lang="EN-ZA" style="font-size:11.0pt; font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:#1F497D">&nbsp;</span></p>
<div style="border:none; border-top:solid #B5C4DF 1.0pt; padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:10.0pt; font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style="font-size:10.0pt; font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">
<a href="mailto:sap-wug-bounces@mit.edu">sap-wug-bounces@mit.edu</a> [<a href="mailto:sap-wug-bounces@mit.edu">mailto:sap-wug-bounces@mit.edu</a>]
<b>On Behalf Of </b>Srinivas Reddy<br>
<b>Sent:</b> 25 February 2014 02:23 PM<br>
<b>To:</b> SAP Workflow Users' Group<br>
<b>Subject:</b> Re: Enhance sap class with custom event</span></p>
</div>
<p class="MsoNormal"><span lang="EN-ZA">&nbsp;</span></p>
<div>
<p class="MsoNormal"><span lang="EN-ZA">Hi Claus,</span></p>
<div>
<p class="MsoNormal"><span lang="EN-ZA">&nbsp;</span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-ZA">Why not inheritance? &nbsp;</span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-ZA">Create a Z class and assign the standard class&nbsp;</span><span lang="EN-ZA" style="font-size:10.0pt; font-family:&quot;Verdana&quot;,&quot;sans-serif&quot;">IHC_CL_UTIL_WORKFLOW as super class to the Z class. Create your event in the Z class.&nbsp;</span><span lang="EN-ZA"></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-ZA" style="font-size:10.0pt; font-family:&quot;Verdana&quot;,&quot;sans-serif&quot;">Any specific reason you want to do this by enhancing the standard class?</span><span lang="EN-ZA"></span></p>
</div>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span lang="EN-ZA">&nbsp;</span></p>
<div>
<p class="MsoNormal"><span lang="EN-ZA">On Thu, Feb 20, 2014 at 4:07 PM, Claus Lücking &lt;<a href="mailto:wug@lucking.dk" target="_blank">wug@lucking.dk</a>&gt; wrote:</span></p>
<div>
<div>
<p class="MsoNormal" style=""><span lang="DA" style="font-size:10.0pt; font-family:&quot;Verdana&quot;,&quot;sans-serif&quot;">Hi,</span><span lang="DA"></span></p>
<p class="MsoNormal" style=""><span lang="DA" style="font-size:10.0pt; font-family:&quot;Verdana&quot;,&quot;sans-serif&quot;">&nbsp;</span><span lang="DA"></span></p>
<p class="MsoNormal" style=""><span style="font-size:10.0pt; font-family:&quot;Verdana&quot;,&quot;sans-serif&quot;">I would like to enhance a SAP standard workflow class (IHC_CL_UTIL_WORKFLOW) with a new custom event. This goes well, but the event does not get status active and
 thus when I raise the event an exception occurs &#8216;Event CREATED does not exist&#8217;.</span><span lang="DA"></span></p>
<p class="MsoNormal" style=""><span style="font-size:10.0pt; font-family:&quot;Verdana&quot;,&quot;sans-serif&quot;">&nbsp;</span><span lang="DA"></span></p>
<p class="MsoNormal" style=""><span style="font-size:10.0pt; font-family:&quot;Verdana&quot;,&quot;sans-serif&quot;">Is&#8217;nt it possible to enhance a standard class in this way? &#8211; or where do I set the event as active in the class/enhancement?</span><span lang="DA"></span></p>
<p class="MsoNormal" style=""><span style="font-size:10.0pt; font-family:&quot;Verdana&quot;,&quot;sans-serif&quot;">&nbsp;</span><span lang="DA"></span></p>
<p class="MsoNormal" style=""><span style="font-size:10.0pt; font-family:&quot;Verdana&quot;,&quot;sans-serif&quot;">Thanks,</span><span lang="DA"></span></p>
<p class="MsoNormal" style=""><span style="font-size:10.0pt; font-family:&quot;Verdana&quot;,&quot;sans-serif&quot;; color:#888888">&nbsp;</span><span lang="DA" style="color:#888888"></span></p>
<p class="MsoNormal" style=""><span style="font-size:10.0pt; font-family:&quot;Verdana&quot;,&quot;sans-serif&quot;; color:#888888">Claus.</span><span lang="DA" style="color:#888888"></span></p>
</div>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span lang="EN-ZA"><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></span></p>
</div>
<p class="MsoNormal"><span lang="EN-ZA"><br>
<br clear="all">
</span></p>
<div>
<p class="MsoNormal"><span lang="EN-ZA">&nbsp;</span></p>
</div>
<p class="MsoNormal"><span lang="EN-ZA">-- </span></p>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span lang="EN-ZA">Thanks and Regards<br>
Srini..<br>
SAP Technical Consultant</span></p>
</div>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span lang="EN-ZA">&nbsp;</span></p>
<p><span lang="EN-ZA" style="font-size:8.0pt; font-family:&quot;Verdana&quot;,&quot;sans-serif&quot;; color:black">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 (&#8220;Barloworld&#8221;) 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.
</span></p>
<p><b><span lang="EN-ZA" style="font-size:8.0pt; font-family:&quot;Verdana&quot;,&quot;sans-serif&quot;; color:black">Barloworld Equipment - 8 Values: Safety &#43; Integrity &#43; Uncompromising Customer Service &#43; Long Term Customer Relationships &#43; Passion For Our Brands &#43; Professionalism
 &#43; Effective Communication &#43; Winning Through Team Work. </span></b><span lang="EN-ZA" style="font-size:8.0pt; font-family:&quot;Verdana&quot;,&quot;sans-serif&quot;; color:black"></span></p>
<p class="MsoNormal"><span lang="EN-ZA"><br>
<br>
<span style="color:white">itevomcid</span> </span></p>
</div>
<table cellpadding="0" cellspacing="0" border="0">
<font face="sans-serif, Arial, Helvetica" size="-1" color="#808080"><br>
If you are not the addressee, please inform us immediately that you have received this e-mail by mistake, and delete it. We thank you for your support.<br>
<br>
</font>
</table>
</body>
</html>