HELP, serious problem! , starting wf explicitly in user exit

[Becker, Stephan]

Set parameter DO_COMMIT of SWW_WI_START to blank.
 
-----Mensaje original-----
De: Sunni sunni [mailto:sunnilondon at hotmail.com]
Enviado el: 09 December 2003 19:22
Para: SAP-WUG at MITVMA.MIT.EDU
Asunto: HELP, serious problem! , starting wf explicitly in user exit
 
Hi all
 
Thought I'd finished my development only, but hit by serious setback.
I've written a function module that triggers a workflow explicitly by
calling
sww_wi_start.  Created a workflow to be called by it and pass it the
necessary parameters in a user exit.
 
Problem is that within sww_wi_start, there is a 'commit work' so user exit
falls over as you can't have a commit work in a user exit!!
 
How do I get around this, any suggestions will be greatly appreciated, this
is a showstopper.
 
Thanks...
Sunni
 
 
>From: "Brice, Andrew" <Andrew.Brice at AirservicesAustralia.com>
>Reply-To: SAP Workflow Users' Group <SAP-WUG at MITVMA.MIT.EDU>
>To: SAP-WUG at MITVMA.MIT.EDU
>Subject: Re: Worklfow stops at background task in a single client
>Date: Mon, 8 Dec 2003 09:05:10 +1100
>
>Sunni
>
>Check your customising transaction SWU3.
>The workflow RFC connection is client specific.
>
>Regards
>
>Andrew Brice
>Airservices Australia
>
>-----Original Message-----
>From: Sunni sunni [mailto:sunnilondon at hotmail.com]
>Sent: Saturday, 6 December 2003 1:06 AM
>To: SAP-WUG at MITVMA.MIT.EDU
>Subject: Worklfow stops at background task in a single client
>
>Hi all,
>
>I have a very strange problem.
>I am working in a multi client environment.  Workflow changes made in
>master
>development client 100 are picked up in client 200.  The strange thing
>is
>that in client 100 my workflow suddenly stops on a task which calls a
>background method, and hangs there.  The workflow log states, background
>method started, but never completes.
>
>In client 200 the same workflow is fine.  The strange thing is that the
>development isnot client specific so it should work in both clients the
>same.
>
>I have tried running SWU_OBUF, I've tried re-activating the workflow,
>I've
>tried reactivating the object being called in the hanging task, I've
>tested
>the object method in SWO1 & its fine in both clients; .....
>
>So I'm all out of ideas, can anyone suggest what may be causing this??
>
>Many thanks
>Sunni
>
>_________________________________________________________________
>Find a cheaper internet access deal - choose one to suit you.
>http://www.msn.co.uk/internetaccess
 
_________________________________________________________________
Use MSN Messenger to send music and pics to your friends
http://www.msn.co.uk/messenger