Purchase Requisition Workflow

Jerry.Martinek jerry.martinek at shawbiz.ca
Fri Oct 7 23:16:04 EDT 2005


Hi Vineet,

How/where did you switch ther release strategies? Our functional consultant
is not quite sure where to do this as it's not obvious to him from looking
at the available functionality in the IMG.

Thanks,
Jerry
  -----Original Message-----
  From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu]On Behalf Of
Vineet.Mehta at mbusi.daimlerchrysler.com
  Sent: Friday, October 07, 2005 7:02 AM
  To: sap-wug at mit.edu
  Subject: Re: Purchase Requisition Workflow



  He is partially correct. The release strategy it self is looking for the
release at the level it was rejected. Therefore, at that time the
Requisitioner or someone else has to do something with the requisition
(Change it).
  Now comes the workflow part, unless the requisition is "significantly
changed" the Event for ReleaseStep will not be raised.
  We have a release strategy which is an exact duplicate of the main one.
Since, the workflow is not smart enough, to know which level the Requisition
needs to be, we start over with a new strategy. Thus any "significant
change" essentially causes a new release strategy to be looked at (Lets say
one is X1 other one is Z1 with same release steps).

  There are other ways to handle this also.


  Regards / Mit freundlichen Grüßen
  Vineet Mehta
  Mercedes-Benz U.S. International, Inc
  Phone: 205-462-5482


       jerry.martinek at shawbiz.ca
        Sent by: sap-wug-bounces at mit.edu
        10/07/2005 08:46 AM
        Please respond to sap-wug


                To:        sap-wug at mit.edu
                cc:
                Subject:        Purchase Requisition Workflow



  Hi,

  We are trying to implement a one step purchase requisition workflow using
  BUS2009.

  Once the requisition is changed after it's been rejected, no events are
  being raised to trigger the restart of the subsequent approval process.
Our
  functional consultant is telling me that there is nothing he can do in the
  release strategy setup and supposedly according to him it's a workflow
  problem because the changed requisition is assigned the correct release
  strategy.

  Can someone please explain what needs to be set (config/ABAP/workflow) to
  restart the approval workflow for a changed requisition?

  Thanks,
  Jerry Martinek

  _______________________________________________
  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/20051007/29b23f72/attachment.htm


More information about the SAP-WUG mailing list