<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
</head><body>
<p>Hi Richa,<br /></p>
<p><br /></p>
<p>the Ask-For-Information scenario is a personal invention ... so to say :-)  ... I'd suggest that you go ahead with a normal release procedure first, and then make an estimation for that implementation, telling the customer that it's not within the SAP Standard.<br /></p>
<p>It depends hardly on the business, if they really need such a solution and sometimes the tag along with what they got for quite a while :-)<br /></p>
<p><br /></p>
<p class="io-ox-signature">Mit freundlichen Gruessen / With kind regards<br /> Florin Wach<br /> Senior Workflow Engineer<br /> SAP Certified Development Associate for Workflow<br /><br />--------------------------------------------------<br />http://www.systems-integration.net</p>
<p><br /></p>
<blockquote type="cite">
Richa Gupta <richa.cse7@gmail.com> hat am 15. März 2015 um 21:45 geschrieben:
<br />
<br />Hi Florin,
<div>
<br />
</div>
<div>
Ask for information scenario is sounding wonderful to me but unfortunately I was infact am not aware of it. Is it just whole customized scenario that needs to be designes or is there anything standard related to this.
</div>
<div>
<br />
</div>
<div>
Could you please throw some more light on it so that I can discuss it with my client.
</div>
<div>
<br />
</div>
<div>
Thanks again for your guidance.
</div>
<div>
<br />
</div>
<div>
Warm Regards
</div>
<div>
Richa
<br />
<br />On Sunday, March 15, 2015, Florin Wach (SI) <
<a href="mailto:florin.wach@systems-integration.net">florin.wach@systems-integration.net</a>> wrote:
<br />
<blockquote>
<div dir="auto">
<div>
Hi Richa,
</div>
<div>
<br />
</div>
<div>
in such a case, create an Ask-For-Information scenario within the Workflow, if you want to design that process within.
</div>
<div>
<br />
</div>
<div>
You could use one of the wonderful
</div>
<div>
custom BaDI's to include such features into the ME29n. I wasn't yet in the need to do so.
</div>
<div>
<br />
</div>
<div>
Florin
</div>
<div>
<br />
<br />
<div>
Mit freundlichen Gruessen / With kind regards
</div>
<div>
Florin Wach
</div>
<div>
Senior Workflow Engineer
</div>
<div>
Systems-Integration
</div>
<div>
<br />
</div>
<div>
--------------------------------------------------
</div>
<div>
<a target="_blank" href="http://www.systems-integration.net">http://www.systems-integration.net</a>
<br />
</div>
</div>
<div>
<br />Am 15.03.2015 um 19:57 schrieb Richa Gupta <
<a target="_blank">richa.cse7@gmail.com</a>>:
<br />
<br />
</div>
<blockquote type="cite">
<div>
Hi Florin,
<div>
<br />
</div>
<div>
Thank you very much for your detailed email.
</div>
<div>
<br />
</div>
<div>
There is another scenario where approver may reject PO just to get some clarification from the creator. In that case creator will not be required to make any changes in PO but just to send an email to approver providing him the required clarification.
</div>
<div>
<br />
</div>
<div>
Now here as mailing the clarification is a manual process, how can we recognize that when the aproval needs to be cancelled and sent back again for the approval.
</div>
<div>
<br />
</div>
<div>
<br />
</div>
<div>
Regards,
</div>
<div>
Richa
</div>
<div>
<br />On Sunday, March 15, 2015, Florin Wach (SI) <
<a target="_blank">florin.wach@systems-integration.net</a>> wrote:
<br />
<blockquote>
<div style="word-wrap: break-word;">
<div>
Hello Richa,
</div>
<div>
<br />
</div>
<div>
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>
<br />
</div>
<div>
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>
- cannot be printed
</div>
<div>
- cannot receive goods receipt
</div>
<div>
- and no invoice can be posted against a PO
</div>
<div>
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>
<br />
</div>
<div>
<br />
</div>
<div>
At a larger implementation for the release procedure, I have designed the rejection process in the following way:
</div>
<div>
<br />
</div>
<div>
- 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>
- All previously involved approver receive also an information (not a work item), that a previously release PO was rejected
</div>
<div>
- The process goes back to the creator, ... or to be exact: To the person that has triggered the new release procedure
</div>
<div>
- The creator chooses now between two alternatives: Changing the PO and send it back to approval - OR - Ending the process.
</div>
<div>
<br />
</div>
<div>
For that matter I’ve created a pair of new events:
</div>
<div>
- FinallyReleased
</div>
<div>
- FinallyRejected
</div>
<div>
<br />
</div>
<div>
The FinallyReleased event comes with the last "Released"-event that turns the PO to become released.
</div>
<div>
The FinallyRejected event comes with the decision of the PO-Creator to accept the rejection, which ends the process.
</div>
<div>
<br />
</div>
<div>
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>
<br />
</div>
<div>
<br />
</div>
<div>
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>
<br />
</div>
<div>
To design the rejection process, I’d advice to use the two standard event
</div>
<div>
.Rejection_Start
</div>
<div>
.Rejection_Stop
</div>
<div>
<br />
</div>
<div>
to start the rejection -subFlow.
</div>
<div>
<br />
</div>
<div>
<br />
</div>
<div>
With the very best wishes
</div>
<div>
Florin
</div>
<div>
<br />
</div>
<div>
<br />
</div>
<div>
<br />
</div>
<div>
<br />
</div>
<br />
<div>
<blockquote type="cite">
<div>
Am 14.03.2015 um 20:01 schrieb Richa Gupta <
<a>richa.cse7@gmail.com</a>>:
</div>
<br />
<div>
<div dir="ltr">
Hi Monique,
<div>
<br />
</div>
<div>
Yes, that would be really appreciated.
</div>
<div>
<br />
</div>
<div>
Regards,
</div>
<div>
Richa
</div>
</div>
<div class="gmail_extra">
<br />
<div class="gmail_quote">
On Sat, Mar 14, 2015 at 11:07 AM, Stephens, Monique S L <
<a>moniques@bcm.edu</a>> wrote:
<br />
<blockquote>
<div dir="auto">
<div>
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>
<br />
<br />
<div>
Monique Stephens
</div>Sent from my iPhone
<div>
(Please ignore any typos)
</div>
</div>
<div>
<br /> On Mar 14, 2015, at 12:54 PM, Richa Gupta <
<a>richa.cse7@gmail.com</a>> wrote:
<br />
<br />
</div>
<blockquote type="cite">
<div>
<div dir="ltr">
Hi Goudham,
<div>
<br />
</div>
<div>
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>
<br />
</div>
<div>
Currently, they follow manual processes to handle this.
</div>
<div>
<br />
</div>
<div>
Regards,
</div>
<div>
Richa
</div>
</div>
<div class="gmail_extra">
<br />
<div class="gmail_quote">
On Sat, Mar 14, 2015 at 6:20 AM, Goudham Vel <
<a>goudhamvel.88@gmail.com</a>> wrote:
<br />
<blockquote>
Hi Richa,
<div>
<br />
</div>
<div>
After po is rejected from workflow in table ekko field procstat will be set as value 08
</div>
<div>
<br />
</div>
<div>
Regards
</div>
<div>
Goudham
<div>
<div>
<br />
<br /> On Saturday, March 14, 2015, Richa Gupta <
<a>richa.cse7@gmail.com</a>> wrote:
<br />
<blockquote>
<div dir="ltr">
Hi Folks,
<div>
<br />
</div>
<div>
What is the best practice for a business in case of rejection of a purchase order?
</div>
<div>
Just to notify someone, or to take some specific actions.
</div>
<div>
<br />
</div>
<div>
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>
<br />
</div>
<div>
Thanks in Advance.
</div>
<div>
<br />
</div>
<div>
Regards,
</div>
<div>
Richa
</div>
<div>
<br />
</div>
<div>
<br />
</div>
</div>
</blockquote>
</div>
</div>
</div>
<span style="color: #888888;"><span style="color: #888888;"><br /> <br /> -- <br /></span></span>
<div dir="ltr">
<div>
Regards
</div>
<div>
Goudham
</div>
</div>
<span style="color: #888888;"><br /> </span>
<br /> _______________________________________________
<br /> SAP-WUG mailing list
<br />
<a>SAP-WUG@mit.edu</a>
<br />
<a target="_blank" href="http://mailman.mit.edu/mailman/listinfo/sap-wug">http://mailman.mit.edu/mailman/listinfo/sap-wug</a>
<br />
<br />
</blockquote>
</div>
<br />
</div>
</div>
</blockquote>
<blockquote type="cite">
<div>
_______________________________________________
<br /> SAP-WUG mailing list
<br />
<a>SAP-WUG@mit.edu</a>
<br />
<a target="_blank" href="http://mailman.mit.edu/mailman/listinfo/sap-wug">http://mailman.mit.edu/mailman/listinfo/sap-wug</a>
<br />
</div>
</blockquote>
</div>
<br />_______________________________________________
<br /> SAP-WUG mailing list
<br />
<a>SAP-WUG@mit.edu</a>
<br />
<a target="_blank" href="http://mailman.mit.edu/mailman/listinfo/sap-wug">http://mailman.mit.edu/mailman/listinfo/sap-wug</a>
<br />
<br />
</blockquote>
</div>
<br />
</div>_______________________________________________
<br />SAP-WUG mailing list
<br />
<a>SAP-WUG@mit.edu</a>
<br />
<a target="_blank" href="http://mailman.mit.edu/mailman/listinfo/sap-wug">http://mailman.mit.edu/mailman/listinfo/sap-wug</a>
<br />
</div>
</blockquote>
</div>
<br />
</div>
</blockquote>
</div>
</div>
</blockquote>
<blockquote type="cite">
<div>
_______________________________________________
<br />SAP-WUG mailing list
<br />
<a target="_blank">SAP-WUG@mit.edu</a>
<br />
<a target="_blank" href="http://mailman.mit.edu/mailman/listinfo/sap-wug">http://mailman.mit.edu/mailman/listinfo/sap-wug</a>
<br />
</div>
</blockquote>
</div>
</blockquote>
</div>_______________________________________________
<br />SAP-WUG mailing list
<br />SAP-WUG@mit.edu
<br />http://mailman.mit.edu/mailman/listinfo/sap-wug
<br />
</blockquote>
<p><br /> </p>
</body></html>