AW: SAP Rel. 4.6B and background tasks in workflows

[Dart, Jocelyn]

Hi Eivind,
When a background task runs the agent is the workflow system user, WF-BATCH.
You will not see this in Goto>Agents>Selected Agents as you do with dialog users.
 
You will see WF-BATCH has been used to execute the background task in
the technical view of the workflow log
and the technical view of the work item and in a few other selected places.
 
The workflow system user is taken from the userid in the
WORKFLOW_LOCAL_xxx (xxx is your client number)RFC destination that was set up
using transaction SWU3.
 
So firstly check that the RFC destination in SWU3 is correctly defined and
pointing to the correct user, i.e. WF-BATCH. Please do not use any other userid (not even WF_BATCH).
 
Secondly from SWU3 start the verification workflow that sends a work item
to you.  Go to the inbox, execute it and choose "execute immediately".
You should then receive two mails - one from yourself, and the other from
the workflow system user.
If that much is working ok there is nothing wrong with WF-BATCH the problem
is with your particular background task.
 
If for some reason the coding in the method beneath a background task requires
user input, then the task will start but never complete - i.e. stays in status
STARTED.  You will usually see an error message about why the task could not be completed appearing
in transaction SM58 against the WF-BATCH user.
 
So - use the above to figure out if the problem is really with WF-BATCH, or whether
it's something to do with your method.  If it's only something to do with your
method then you need to fix your method coding so that it truly can be run in background.
 
Regards,
        Jocelyn Dart
Consultant (SRM, EBP, Workflow)
and co-author of the book
"Practical Workflow for SAP"
SAP Australia
email: jocelyn.dart at sap.com
phone: +61 412 390 267
fax:   +61 2 9935 4880
 
 
 
 
 
-----Original Message-----
From: Eivind Bustnes [mailto:EBU at edbgruppen.dk]
Sent: Tuesday, 27 August 2002 6:33 PM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: AW: SAP Rel. 4.6B and background tasks in workflows
 
 
Hi again,
 
I have now checked the systemlog, and the WF-BATCH. The user have SAP_ALL
and SAP_NEW and the systemlog does not contain any entries about this.
 
I have the same problem with all background task in my workflows. (I'm
using e.g. WS1000051 FIPP release procedure standard template). Here the
tasks that should determin the responible costcenter person does not find
any agent when the task runs as a background task, but it find it if I
unmark the background flag on the taskdefinition. This was just an example,
I have problems with all my background tasks.
 
Regars Eivind
 
 
 
 
                    "Becker Stephan (extern)"
                    <Stephan.Becker.ext at mchw.s       To:     SAP-WUG at MITVMA.MIT.EDU
                    iemens.de>                       cc:
                    Sent by: SAP Workflow            Subject:     AW: SAP Rel. 4.6B and background tasks in workflows
                    <Owner-SAP-WUG at MITVMA.MIT.
                    EDU>
 
 
                    26-08-2002 14:06
                    Please respond to SAP
                    Workflow Users' Group
 
 
 
 
 
 
Eivind, this doesn't sound like a bug. Are you doing a batch input or
something else that could trigger screen processing? Have a look at the
system log for the time you're running it as background, you might find
something there.
Hth,
Stephan
 
-----Urspr|ngliche Nachricht-----
Von: Eivind Bustnes [mailto:EBU at edbgruppen.dk]
Gesendet: Montag, 26. August 2002 13:59
An: SAP-WUG at MITVMA.MIT.EDU
Betreff: SAP Rel. 4.6B and background tasks in workflows
 
 
Hi,
 
I have a 4.6B system, where I have made some extentions to a objecttype
(FIPP, BUS2012 etc.). I have made my own methods which I link to a task in
a workflow.
 
The problem is that I want to run the task as a background task, and when I
do this it seems that the system doesen't read the method. If i run the
task in the foreground instead the method is read and the task is working.
When i do this in a 4.6C system everything is OK. To me this seems like a
bug in the system, but I can't find any OSS notes describing the problem.
 
Have anyone experienced the same problems or have someone a suggestion to
what I should do?
 
Best Regards Eivind Bustnes