<div>Thanks for the response Shai!</div>
<div> </div>
<div>B certainly sounds interesting but I can't seem to figure it out. This exit seems more to control which documents are controlled by Release proceedures or not rather than controlling whether a given document is released or not. From the doco and examples I can find the idea is that you include one of the user fields (USRC1 for example) in the classification defintion of the release strategy and within the exit you can control this field. If the field is set the PO is subject to Release, otherwise it isn't which isn't the same as resetting the release code.
</div>
<div> </div>
<div>There is also a field CEKKO-PDUMMY which is part of a structure defined as 'PO release for User Exit', but I'm not sure how this is supposed to be used. Putting an 'X' in it in the exit didn't do much.</div>
<div> </div>
<div>I hope I'm just missing the point and this exit can help. Are you able to provide me any further clarification.</div>
<div> </div>
<div>Many thanks,</div>
<div>Mark <br><br> </div>
<div><span class="gmail_quote">On 8/9/06, <b class="gmail_sendername">Shai Eyal</b> <<a href="mailto:shaie@team.co.il">shaie@team.co.il</a>> wrote:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Dear Mark,<br><br>Basicly, your requirement does not concern the workflow - you wish to<br>reset the release strategy due to non-significant change. For the best
<br>of my knowledge, there are two options:<br>A. Make this change significant (reduce the %changeable).<br>B. Use exit EXIT_SAPLEBND_002 to reset the release strategy due to<br>non-significant change. Reseting the release strategy will trigger event
<br>ReleaseStepCreated and from there you know to carry on.<br><br>OK ?<br><br><br>Regards,<br>Shai Eyal<br><br>------------------------------<br><br>Message: 5<br>Date: Wed, 9 Aug 2006 13:55:08 +0100<br>From: "Mark Pyc" <
<a href="mailto:mark.pyc@gmail.com">mark.pyc@gmail.com</a>><br>Subject: Determining PO Rel Code to allow Reset on Non-Significant<br> Change<br>To: WUG <<a href="mailto:sap-wug@mit.edu">sap-wug@mit.edu</a>>
<br>Message-ID:<br> <<a href="mailto:23f0a78a0608090555y5b28a9ffh2eb0df036597fc2c@mail.gmail.com">23f0a78a0608090555y5b28a9ffh2eb0df036597fc2c@mail.gmail.com</a>><br>Content-Type: text/plain; charset="iso-8859-1"
<br><br>G'day all,<br><br>I appreciate this is more of just a coding issue than WF exactly, but<br>I'll<br>try all the same. ECC 5.0<br><br>How can you determine the Release Code for a PO when a non-significant<br>change has occured. To be able to call
BUS2012.ResetRelease you must be<br>able<br>to pass the Release Code, but I can't see how this can easily be<br>determined.<br>I'm in fact amazed at how uneasy it seems.<br><br>When dealing with Significant Changes the event passes you the Rel Code
<br>so<br>there is no need to think about it.<br><br>When certain non-Significant changes occur to an already released PO,<br>the<br>desire is to reset the release and go through approvals. The problem is<br>finding the needed Release Code.
<br><br>Many thanks,<br>Mark<br>-------------- next part --------------<br>An HTML attachment was scrubbed...<br>URL:<br><a href="http://mailman.mit.edu/pipermail/sap-wug/attachments/20060809/c5f86a5b/a">http://mailman.mit.edu/pipermail/sap-wug/attachments/20060809/c5f86a5b/a
</a><br>ttachment.htm<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">
http://mailman.mit.edu/mailman/listinfo/sap-wug</a><br><br><br>End of SAP-WUG Digest, Vol 21, Issue 38<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">http://mailman.mit.edu/mailman/listinfo/sap-wug</a><br></blockquote></div><br>