Purchase Req - Multiple Release codes
Stephane Bailleul
bailleuls at numericable.fr
Mon Aug 20 15:21:05 EDT 2007
Hi Prashanthi,
If you are using a custom workflow containing the logic of the workflow and
not following the MM customizing then you should create two event
PR Created and PR significantly change (where you define when you want the
PR change to be submitted to workflow)
Also dont forget to put a waiting event in order to stop workflow instance
already started if a significant change has been done
I hope this help
Cheers
Stephane
De : sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] De la part de
Prasad, Prashanthi
Envoyé : lundi 20 août 2007 18:52
À : sap-wug at mit.edu
Objet : Purchase Req - Multiple Release codes
Hello MIT Friends,
I have an issue with my Purchase requsition workflow. The only triggering
event for this workflow is 'Releasestepcreated'. Everything was working
great until now just because we had only one releasecode At ONE TIME. But
now they have come up with the idea that suppose if the Release code is
greaterr than release codeR5(250,000 to 500,000), the config has been
changed in such a way that for example, 3 release codes will appear in the
'Release Strategy' tab R5, R6 and R7. Before R7 was the only release code
and when he approves it, thats it. But now before R7 approves it, the
workflow should first go to R5 and he has to hit the Release button and save
it and then it has to go the next release code 'R6' and then after he
releases it, the workflow should go to R7. I have taken care of all these
logic.
Now the problem I am facing is the 'ReleaseStepCreated' event is being
triggered 3 time when the purchase req is created. How do I restrict this
event to be triggered just once at anytime?
Any help is greatly appreciated.
Thanks,
Prashanthi Prasad
SAP ABAP/Workflow
CITGO Petroleum Corporation
pprasad at citgo.com
832-486-4899
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20070820/0a258d55/attachment.htm
More information about the SAP-WUG
mailing list