<HTML><HEAD>
<META content="text/html; charset=utf-8" http-equiv=Content-Type>
<META name=GENERATOR content="MSHTML 8.00.7601.18305"></HEAD>
<BODY style="MARGIN: 4px 4px 1px; FONT: 10pt Segoe UI">
<DIV>Mike,</DIV>
<DIV> </DIV>
<DIV>Thanks. I'll check that out. For now, if I put a 1 minute wait under Requested Start for the first task, it switches all subsequent workitems to WF-BATCH.</DIV>
<DIV> </DIV>
<DIV>Regards</DIV>
<DIV> </DIV>
<DIV>Claude<BR><BR>>>> Mike Pokraka <wug@workflowconnections.com> 2014/02/27 10:26 AM >>><BR>Hi Claude, <BR><BR>Does it also do this if you start it manually in the SAPGUI? The behaviour is by design, though my memory is a bit foggy on exactly where or how to control it. If you scroll to the right you will see it is running under WF-BATCH in column 'user context'.<BR>Have a play with the advance in dialog settings. Failing that, last resort big hammer approach is to force an RFC call by putting a background task in between.<BR><BR>Regards, <BR>Mike<BR><BR>On 21 Feb 2014, at 12:22, "Claude Bourque" <claude.bourque@rcmp-grc.gc.ca> wrote:<BR><BR>Hello everyone,<BR><BR>I haven't posted anything in at least 2 years so here it goes.<BR><BR>I've been asked to support a new WebDynpro App that starts a workflow, the WDA app uses Function Module ARCHIV_PROCESS_FAXINPUT to start WF.<BR><BR>Only problem is that this FM uses sy-uname as the creator.<BR><BR>As seen in the attached document, if I go to the Portal and start the process, I'm listed as the WF Initiator but the strange thing is that I'm also the creator of ALL tasks including all background tasks.<BR><BR>Here's a text snapshot of part of the log to show that. Full screenshot is in the included attachment.<BR><BR>Claude Bourque Execution started automatically 2014/02/21 07:05:45<BR>Claude Bourque Background work item created 2014/02/21 07:05:45<BR>Claude Bourque Work Item Processing Complete 2014/02/21 07:05:45<BR>Claude Bourque Result Processing 2014/02/21 07:05:45<BR><BR>We didn't noticed this until this week when I was asked to add an email step and the email comes from the user that start the process NOT WF-BATCH.<BR><BR>All the steps after approval return to "normal" and WF-BATCH creates and completed the background work items again.<BR><BR>A solution would be to have the WDA application be launched with WF-BATCH as the user but security is NOT crazy about that idea.<BR><BR>Any ideas/suggestions?<BR><BR>Thanks.<BR><BR>Regards<BR><BR>Claude<BR><Background workitem dilemma.docx><BR>_______________________________________________<BR>SAP-WUG mailing list<BR>SAP-WUG@mit.edu<BR><A href="http://mailman.mit.edu/mailman/listinfo/sap-wug">http://mailman.mit.edu/mailman/listinfo/sap-wug</A><BR><BR>_______________________________________________<BR>SAP-WUG mailing list<BR>SAP-WUG@mit.edu<BR><A href="http://mailman.mit.edu/mailman/listinfo/sap-wug">http://mailman.mit.edu/mailman/listinfo/sap-wug</A><BR></DIV></BODY></HTML>