Workflows for releasing purchase documents!
Márton Zsolt
Zsolt.Marton at t-systems.co.hu
Tue Jan 25 12:17:16 EST 2005
Hi Mark!
Thanks for your quick answer.
To answer at your question: they start directly using a generated transaction code.
Why? - the answer is simple: they creating and releasing purchase documents procedure is a little bit difficult. The person, who will release or cancel the document is not the same with who can modify the requisition or the order - accordingly, the new workflow is started when the release is canceled, but the requisition is still the same, it wasn't modified yet.
Regards
Zsolt
-----Original Message-----
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf Of Mark Pyc
Sent: Tuesday, January 25, 2005 5:38 PM
To: sap-wug at mit.edu
Subject: RE: Workflows for releasing purchase documents!
G'day Zsolt,
How are they manually retriggering?? Do they raise an event or start
directly?
If they don't use the event then you simply need to filter the event on
subsequent raises. Easy enough with a check function looking for existing WF
instances - if any exist, don't start another one.
The usual story, a bit more info will help.
Have fun,
Mark
PS I'm not asking any 'Why' questions here, I'm assuming you've already done
that.
From: Márton Zsolt <Zsolt.Marton at t-systems.co.hu>
Reply-To: "SAP Workflow Users' Group" <sap-wug at mit.edu>
To: "SAP Workflow Users' Group" <sap-wug at mit.edu>
Subject: Workflows for releasing purchase documents!
Date: Tue, 25 Jan 2005 16:46:02 +0100
Hi all!
One of our customers - they are using standard workflows for releasing
purchase documents for a long time - request is to change the workflows in
a such a way, that workflow is started automatically only at the first time,
when the release step is created; when the document is created. That is to
say, they don't want to restart the workflow when the release step is
canceled. In that case they want to start manually. Does anybody know a good
solution to this problem?
The problem is not how to start manually the workflow (they are already
using this), but how to not start when the release is canceled.
My idea is, to create a new starting event, but in that situation, my
workflow will run just once, because at the second level the workflow is not
triggered, the release step is not created.
Any idea is welcome
Regards
Zsolt
_______________________________________________
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
More information about the SAP-WUG
mailing list