<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=""><div class="">Hello Richa,</div><div class=""><br class=""></div><div class="">it’s true that within the SAP Standard settings, there’s nothing pretty much going on, when a PO is rejected and - by the way - all this is the same with Purchase Requisitions, too: An information is sent to the PO creator and that’s it.</div><div class=""><br class=""></div><div class="">From a business-process point of view, I’ve also made the experience that the process is somewhat "not fully completed", as the PO keeps somewhat pending in the system, although a rejected PO</div><div class="">- cannot be printed</div><div class="">- cannot receive goods receipt</div><div class="">- and no invoice can be posted against a PO</div><div class="">Where the same applies to a PO which is not yet fully released. This all depends on the setting of the release status.</div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">At a larger implementation for the release procedure, I have designed the rejection process in the following way:</div><div class=""><br class=""></div><div class="">- The rejecting person creates a mandatory annotation. This can be done in one of the header texts (or a new header text), as already mentioned by Monique - or you can create a separate custom popup to enter some text (storing it in the header note).</div><div class="">- All previously involved approver receive also an information (not a work item), that a previously release PO was rejected</div><div class="">- The process goes back to the creator, … or to be exact: To the person that has triggered the new release procedure</div><div class="">- The creator chooses now between two alternatives: Changing the PO and send it back to approval - OR - Ending the process.</div><div class=""><br class=""></div><div class="">For that matter I’ve created a pair of new events:</div><div class="">- FinallyReleased</div><div class="">- FinallyRejected</div><div class=""><br class=""></div><div class="">The FinallyReleased event comes with the last "Released"-event that turns the PO to become released.</div><div class="">The FinallyRejected event comes with the decision of the PO-Creator to accept the rejection, which ends the process.</div><div class=""><br class=""></div><div class="">In any case, the Approval-Procedure and its workflow is coming back, once that status changes to be "in approval”, the SAP Transaction will always re-create the .ReleaseStepCreated-events, from which one can startup a new workflow instance.</div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">Also I usually design the Workflow on a larger implementation to process all release codes in one single Workflow-instance only, that incorporates the Rejection procedure as one of the Sub-Flows. This way it’s easier to transfer information / annotation and the flow information between the releasers and the creator. But that can be considered optional.</div><div class=""><br class=""></div><div class="">To design the rejection process, I’d advice to use the two standard event</div><div class="">.Rejection_Start</div><div class="">.Rejection_Stop</div><div class=""><br class=""></div><div class="">to start the rejection -subFlow.</div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">With the very best wishes</div><div class=""> Florin</div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div><br class=""><div><blockquote type="cite" class=""><div class="">Am 14.03.2015 um 20:01 schrieb Richa Gupta <<a href="mailto:richa.cse7@gmail.com" class="">richa.cse7@gmail.com</a>>:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">Hi Monique,<div class=""><br class=""></div><div class="">Yes, that would be really appreciated. </div><div class=""><br class=""></div><div class="">Regards,</div><div class="">Richa</div></div><div class="gmail_extra"><br class=""><div class="gmail_quote">On Sat, Mar 14, 2015 at 11:07 AM, Stephens, Monique S L <span dir="ltr" class=""><<a href="mailto:moniques@bcm.edu" target="_blank" class="">moniques@bcm.edu</a>></span> wrote:<br class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="auto" class="">
<div class="">Prior to implementing SRM, our PO's were routing through workflow for approvals. If it needed to be rejected, we had an additional step in the logic that the approver had to put a reason in the header notes. I would need to check with our programmer to
see how that was included in the workflow logic.</div>
<div class=""><br class="">
<br class="">
<div class="">Monique Stephens</div>
Sent from my iPhone
<div class=""> (Please ignore any typos)</div>
</div>
<div class=""><br class="">
On Mar 14, 2015, at 12:54 PM, Richa Gupta <<a href="mailto:richa.cse7@gmail.com" target="_blank" class="">richa.cse7@gmail.com</a>> wrote:<br class="">
<br class="">
</div>
<blockquote type="cite" class="">
<div class="">
<div dir="ltr" class="">Hi Goudham,
<div class=""><br class="">
</div>
<div class="">Yes, that I know. My question was more from business perspective. What a business should do when a PO is rejected or in other words, as SAP consultant what should we suggest them to do if a PO is rejected.</div>
<div class=""><br class="">
</div>
<div class="">Currently, they follow manual processes to handle this.</div>
<div class=""><br class="">
</div>
<div class="">Regards,</div>
<div class="">Richa</div>
</div>
<div class="gmail_extra"><br class="">
<div class="gmail_quote">On Sat, Mar 14, 2015 at 6:20 AM, Goudham Vel <span dir="ltr" class="">
<<a href="mailto:goudhamvel.88@gmail.com" target="_blank" class="">goudhamvel.88@gmail.com</a>></span> wrote:<br class="">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi Richa,
<div class=""><br class="">
</div>
<div class="">After po is rejected from workflow in table ekko field procstat will be set as value 08 </div>
<div class=""><br class="">
</div>
<div class="">Regards </div>
<div class="">Goudham
<div class="">
<div class=""><br class="">
<br class="">
On Saturday, March 14, 2015, Richa Gupta <<a href="mailto:richa.cse7@gmail.com" target="_blank" class="">richa.cse7@gmail.com</a>> wrote:<br class="">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr" class="">Hi Folks,
<div class=""><br class="">
</div>
<div class="">What is the best practice for a business in case of rejection of a purchase order?</div>
<div class="">Just to notify someone, or to take some specific actions.</div>
<div class=""><br class="">
</div>
<div class="">Reason behind asking this question is that our client has asked us what should they do from SAP perspective when a PO is rejected. Currently, they simply notify the buyer if a PO is rejected and that too manually using outlook.</div>
<div class=""><br class="">
</div>
<div class="">Thanks in Advance.</div>
<div class=""><br class="">
</div>
<div class="">Regards,</div>
<div class="">Richa</div>
<div class=""><br class="">
</div>
<div class=""><br class="">
</div>
</div>
</blockquote>
</div>
</div>
</div>
<span class=""><font color="#888888" class=""><br class="">
<br class="">
-- <br class="">
<div dir="ltr" class="">
<div class="">Regards</div>
<div class="">Goudham</div>
</div>
<br class="">
</font></span><br class="">
_______________________________________________<br class="">
SAP-WUG mailing list<br class="">
<a href="mailto:SAP-WUG@mit.edu" target="_blank" class="">SAP-WUG@mit.edu</a><br class="">
<a href="http://mailman.mit.edu/mailman/listinfo/sap-wug" target="_blank" class="">http://mailman.mit.edu/mailman/listinfo/sap-wug</a><br class="">
<br class="">
</blockquote>
</div>
<br class="">
</div>
</div>
</blockquote>
<blockquote type="cite" class="">
<div class=""><span class="">_______________________________________________</span><br class="">
<span class="">SAP-WUG mailing list</span><br class="">
<span class=""><a href="mailto:SAP-WUG@mit.edu" target="_blank" class="">SAP-WUG@mit.edu</a></span><br class="">
<span class=""><a href="http://mailman.mit.edu/mailman/listinfo/sap-wug" target="_blank" class="">http://mailman.mit.edu/mailman/listinfo/sap-wug</a></span><br class="">
</div>
</blockquote>
</div>
<br class="">_______________________________________________<br class="">
SAP-WUG mailing list<br class="">
<a href="mailto:SAP-WUG@mit.edu" class="">SAP-WUG@mit.edu</a><br class="">
<a href="http://mailman.mit.edu/mailman/listinfo/sap-wug" target="_blank" class="">http://mailman.mit.edu/mailman/listinfo/sap-wug</a><br class="">
<br class=""></blockquote></div><br class=""></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=""></body></html>