Purchase Requisition Workflow

[Flavio Oliveira]

Jerry:

I do not remember if I've used any exit, but I think not... to generate the 
event, you just need to configure the change documents.

I agree with you that would be better to create a new custom event.

Regards,
Flávio.


>From: "Jerry.Martinek" <jerry.martinek at shawbiz.ca>
>Reply-To: "SAP Workflow Users' Group" <sap-wug at mit.edu>
>To: "'SAP Workflow Users' Group'" <sap-wug at mit.edu>
>Subject: RE: Purchase Requisition Workflow
>Date: Mon, 10 Oct 2005 09:47:16 -0700
>
>Hi Flavio,
>
>Thank you for the response which I hope I understand.
>
>I forgot to mention that we're running 4.6C and wanting to do the document
>level (BUS2105) release and not the item level one.
>
>You mentioned that you've done this before, did you activate MEREQ001 -
>EXIT_SAPLMEREQ_004 or EXIT_SAPLMEREQ_006? Also did you create a new custom
>event or did you reuse one of the existing events for this? I'm thinking
>that you'd want to create a separate custom event.
>
>Thanks,
>Jerry
>
>-----Original Message-----
>From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu]On Behalf
>Of Flavio Oliveira
>Sent: Monday, October 10, 2005 8:19 AM
>To: sap-wug at mit.edu
>Subject: RE: Purchase Requisition Workflow
>
>
>This will be more dificult...
>
>You will have to raise an event when the requisition is changed (Change
>Documents BANF).
>
>Either you put a Fork on your workflow with an Wait for Event step or 
>create
>a new asynchronous method to change the requisition.
>
>If the requisition is changed outside workflow, the Workitem will continue
>(because of the event) and everything is fine again.
>
>What make this a little had to do is that the object associated with the
>BANF object is BUS2105 (requisition) and not BUS2009 (requisition item), 
>but
>you can handle this with a couple of function modules.
>
>Flávio.
>
> >From: "Jerry.Martinek" <jerry.martinek at shawbiz.ca>
> >Reply-To: "SAP Workflow Users' Group" <sap-wug at mit.edu>
> >To: "'SAP Workflow Users' Group'" <sap-wug at mit.edu>
> >Subject: RE: Purchase Requisition Workflow
> >Date: Mon, 10 Oct 2005 07:30:45 -0700
> >
> >Hi Flavio,
> >
> >How do you deal with the scenario where the requisition is changed 
>outside
> >of the workflow after it's rejected?
> >
> >Thanks,
> >Jerry
> >
> >-----Original Message-----
> >From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu]On Behalf
> >Of Flavio Oliveira
> >Sent: Monday, October 10, 2005 4:24 AM
> >To: sap-wug at mit.edu
> >Subject: RE: Purchase Requisition Workflow
> >
> >
> >It is quite simple, Jerry:
> >
> >1- Before the task to change the requisition (that was rejected), you 
>have
> >to store the release strategy on a container element.
> >
> >2- After the user changes the requisition, you check the old release
> >strategy (stored on the container) with the new one (from the object
> >itself).
> >
> >3- If they are diferent, you do not have to do anything. The event will 
>be
> >raised by the standard aplication. If they are the same, you will have to
> >start the event manualy (just use the step "Event Create").
> >
> >I've used this before and it work just fine!!
> >
> >If you have any other questions, please let me know.
> >
> >Regards,
> >Flávio.
> >
> >
> > >From: "Jerry.Martinek" <jerry.martinek at shawbiz.ca>
> > >Reply-To: "SAP Workflow Users' Group" <sap-wug at mit.edu>
> > >To: "'SAP Workflow Users' Group'" <sap-wug at mit.edu>
> > >Subject: RE: Purchase Requisition Workflow
> > >Date: Fri, 07 Oct 2005 20:19:41 -0700
> > >
> > >Hi Flavio,
> > >
> > >I'm not sure I understand your second option. Would you be willing to
> > >provide some additional information?
> > >
> > >Thanks,
> > >Jerry
> > >
> > >-----Original Message-----
> > >From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu]On Behalf
> > >Of Flavio Oliveira
> > >Sent: Friday, October 07, 2005 7:02 AM
> > >To: sap-wug at mit.edu
> > >Subject: RE: Purchase Requisition Workflow
> > >
> > >
> > >Jerry:
> > >
> > >This problem happens when, after the modification, the release strategy
> > >remains the same. If the release strategy is different, it works fine.
> > >
> > >You have two options:
> > >1- Open an Oss message asking SAP to fix the bug (when I was on 3.0F,
> >they
> > >promisse to solve this in a future release).
> > >
> > >2- Copy the standard workflow and raise the event by yourself when the
> > >requisition was changed after the rejection and the release strategy is
> >the
> > >same.
> > >
> > >Regards,
> > >Flavio
> > >
> > >
> > > >From: "Jerry.Martinek" <jerry.martinek at shawbiz.ca>
> > > >Reply-To: "SAP Workflow Users' Group" <sap-wug at mit.edu>
> > > >To: sap-wug at mit.edu
> > > >Subject: Purchase Requisition Workflow
> > > >Date: Fri, 07 Oct 2005 06:46:07 -0700
> > > >
> > > >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
> > >
> > >
> > >_______________________________________________
> > >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