Background Task performed by id other than WF-BATCH

[Dale Davis]

Thanks Jocelyn:
 
  I was aware of that for dialog steps but never thought it applied to
background steps as well.
 
Regards
Dale Davis Jones
IBM / SAP Certified
Senior SAP Workflow & PP Consultant - SAP Practice
 
IBM Global Services
Phone: 919-543-7678
               T/L 8-441-7678
  Internet Address: DKDAVIS at US.IBM.COM
 
.......You can never discover new oceans unless you have the courage to
lose sight of the shore..........
 
 
"Dart, Jocelyn" <jocelyn.dart at sap.com>@MITVMA.MIT.EDU> on 08/23/2002
12:06:15 AM
 
Please respond to "SAP Workflow Users' Group" <SAP-WUG at MITVMA.MIT.EDU>
 
Sent by:    SAP Workflow <Owner-SAP-WUG at MITVMA.MIT.EDU>
 
 
To:    SAP-WUG at MITVMA.MIT.EDU
cc:
Subject:    Re: Background Task performed by id other than WF-BATCH
 
 
 
Hi Dale,
Whenever a workflow is started directly via a user id
or a dialog step is completed, in case
the same user has to perform the next dialog step the
workflow manager runs any subsequent steps under that same
user id until it hits another background step or dialog step
for someone else.
 
This is controlled by the "advance with dialog"
flag in the step definition so try turning that off and that should
fix it.
 
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: Dale Davis [mailto:dkdavis at us.ibm.com]
Sent: Friday, 23 August 2002 12:26 AM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Background Task performed by id other than WF-BATCH
 
 
Hi All:
 
I have recently run into an unusual scenario where background tasks are
being performed by a CPIC background id instead of WF-BATCH. This is for a
custom workflow that we have created in R/3 that  validates data in inbound
IDOCs from another SAP system before allowing the idocs to post. The
workflow is started by a link to the process code associated with the
partner profile of the sending system.
 
This is the only workflow where this occurs in a system where we have about
100  custom workflows running . The main difference between this workflow
and the others is that there is no break between the background id that
starts the workflow and a series of background steps that occur.
The only dialog steps that occur are as a result of exception handling .
 
The problem with having the ALE CPIC id do background steps is two-fold.
 
1. The workflow team does not own that id so we  have little control of the
authorizations and its settings. As a result  we have already encountered
one authorization problem with the internet sendmail function which we have
resolved by now enabling the CPIC id to send internet mail.
2. It is quite confusing to administrators and users looking at the
workitem logs to see a CPIC id as the id completing the background steps
instead of WF-BATCH.
3. There are timezone issues related to the set up of the CPIC id vs the
WF-BATCH id.,
 
 
I have validated that the workflow local  RFC destination is still set up
with reference to WF-BATCH and that all related customizing is accurate.
 
Any advice from SAP on why this is occuring and what can be done to resolve
it would be appreciated.
 
 
Regards,
Dale Davis Jones
IBM / SAP Certified
Senior SAP Workflow & PP Consultant - SAP Practice
 
IBM Global Services
Phone: 919-543-7678
               T/L 8-441-7678
  Internet Address: DKDAVIS at US.IBM.COM
 
.......You can never discover new oceans unless you have the courage to
lose sight of the shore..........