on 06-05-2008 7:08 AM
Hi Experts,
I have a background step in my workflow , when iam testing this workflow from SWUS the workflow is getting stopped at this background step the workflow is not going forward to next step. the workflow log shows ' task started in background'
moreover i did't find any errors in the log for the same.and i checked SM37 there the relevent job is finished. please advice what canbe the problem?
Thanks & Regards,
Sarath.
HI Sarath ,
Just change yuor task from BAckgroung to foreground. Insert a break point in the code of the function module used in the task and execute your workflow.
Coz you cant debug a background task , you will never come to know wht is happening inside .
By debugging get the problem in the code , rectify it and change the task again to the background .
Hope this will help.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Sarath,
check your settings in SWU3.check whether background job settings been executed(in green) properly.
thanks
Ashok
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Sarath!
Can you please give us some more information on the task/method name where the workflow is getting stopped? Will it be possible for you to execute the method via SWO1 by instantiating the object? In that way, we can find out if the method genuinely is going into error when you execute it separately.
Let us know if you need any further help.
Regards,
Anwar.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Debug your method by providing the parameters that are passed from the Workflow to the method in SWO1 and analyse accordingly from Wflow Log and ST22.
Thanks
Arghadip
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Sarath,
if the method in your background step has a runtime error it will look like the workflow just stopped, it will not get the status: ERROR. The main workflow will have a message though: "Execution interupted". There can be many causes for this, some will end up as ABAP dumps, so you can check there. Also just try to run the method in the foreground with the same parameters as passed in the workflow and see what happens.
Hope this helps,
Gert.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Sarath K,
Always be careful when your using background task.
Since your executing it in SWUS there is no problem, but when your workflow development goes to production it will cause major effects.
Coming to the point, If this is going to be case, Check for the binding between
Workflow-->task
task>method and Method>task
Task--workflow.
Thanks and Regards
Balaji K.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
83 | |
10 | |
10 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.