What should be done if a PO is rejected!!!

Tue Mar 17 12:32:53 EDT 2015

Hi Florin,

I got that point of yours. Thanks again for your guidance. I will have a
word with business and will share it how they decided to handle the same. :)

Regards,
Richa

On Tue, Mar 17, 2015 at 3:35 AM, Florin Wach <
florin.wach at systems-integration.net> wrote:

>  Hi Richa,
>
>
> 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.
>
> 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 :-)
>
>
> Mit freundlichen Gruessen / With kind regards
> Florin Wach
> Senior Workflow Engineer
> SAP Certified Development Associate for Workflow
>
> --------------------------------------------------
> http://www.systems-integration.net
>
>
>  Richa Gupta <richa.cse7 at gmail.com> hat am 15. März 2015 um 21:45
> geschrieben:
>
> Hi Florin,
>
>  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.
>
>  Could you please throw some more light on it so that I can discuss it
> with my client.
>
>  Thanks again for your guidance.
>
>  Warm Regards
>  Richa
>
> On Sunday, March 15, 2015, Florin Wach (SI) <
> florin.wach at systems-integration.net> wrote:
>
>  Hi Richa,
>
>  in such a case, create an Ask-For-Information scenario within the
> Workflow, if you want to design that process within.
>
>  You could use one of the wonderful
>  custom BaDI's to include such features into the ME29n. I wasn't yet in
> the need to do so.
>
>  Florin
>
>
>  Mit freundlichen Gruessen / With kind regards
>  Florin Wach
>  Senior Workflow Engineer
>  Systems-Integration
>
>  --------------------------------------------------
>  http://www.systems-integration.net
>
> Am 15.03.2015 um 19:57 schrieb Richa Gupta < richa.cse7 at gmail.com>:
>
>   Hi Florin,
>
>  Thank you very much for your detailed email.
>
>  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.
>
>  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.
>
>
>  Regards,
>  Richa
>
> On Sunday, March 15, 2015, Florin Wach (SI) <
> florin.wach at systems-integration.net> wrote:
>
>  Hello Richa,
>
>  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.
>
>  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
>  - cannot be printed
>  - cannot receive goods receipt
>  - and no invoice can be posted against a PO
>  Where the same applies to a PO which is not yet fully released. This all
> depends on the setting of the release status.
>
>
>  At a larger implementation for the release procedure, I have designed
> the rejection process in the following way:
>
>  - 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).
>  - All previously involved approver receive also an information (not a
> work item), that a previously release PO was rejected
>  - The process goes back to the creator, ... or to be exact: To the person
> that has triggered the new release procedure
>  - The creator chooses now between two alternatives: Changing the PO and
> send it back to approval - OR - Ending the process.
>
>  For that matter I’ve created a pair of new events:
>  - FinallyReleased
>  - FinallyRejected
>
>  The FinallyReleased event comes with the last "Released"-event that
> turns the PO to become released.
>  The FinallyRejected event comes with the decision of the PO-Creator to
> accept the rejection, which ends the process.
>
>  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.
>
>
>  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.
>
>  To design the rejection process, I’d advice to use the two standard
> event
>  .Rejection_Start
>  .Rejection_Stop
>
>  to start the rejection -subFlow.
>
>
>  With the very best wishes
>  Florin
>
>
>
>
>
>   Am 14.03.2015 um 20:01 schrieb Richa Gupta < richa.cse7 at gmail.com>:
>
>  Hi Monique,
>
>  Yes, that would be really appreciated.
>
>  Regards,
>  Richa
>
>  On Sat, Mar 14, 2015 at 11:07 AM, Stephens, Monique S L <
> moniques at bcm.edu> wrote:
>
>  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.
>
>
>  Monique Stephens
> Sent from my iPhone
> (Please ignore any typos)
>
> On Mar 14, 2015, at 12:54 PM, Richa Gupta < richa.cse7 at gmail.com> wrote:
>
>   Hi Goudham,
>
>  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.
>
>  Currently, they follow manual processes to handle this.
>
>  Regards,
>  Richa
>
>  On Sat, Mar 14, 2015 at 6:20 AM, Goudham Vel < goudhamvel.88 at gmail.com>
> wrote:
>
> Hi Richa,
>
>  After po is rejected from workflow in table ekko field procstat will be
> set as value 08
>
>  Regards
>  Goudham
>
>
> On Saturday, March 14, 2015, Richa Gupta < richa.cse7 at gmail.com> wrote:
>
>  Hi Folks,
>
>  What is the best practice for a business in case of rejection of a
> purchase order?
>  Just to notify someone, or to take some specific actions.
>
>  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.
>
>  Thanks in Advance.
>
>  Regards,
>  Richa
>
>
>
>
> --
>  Regards
>  Goudham
>
>
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
>
>
>    _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
>
>
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
>
>
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
>
>
>     _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
>
>  _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
>
>
>
>
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20150317/8b76eb60/attachment-0001.htm