WF-BATCH

[workflow99@aol.com]

Are you stripping off the first two characters of  WF_initiator before moving it to your user id field? The first two positions being object type (US for user). If not, the system may not recognize the value as a valid user and may be using the sy-uname.
 
Best Regards,
Ramki Maley,
WF Developer - USCBP.

 
 
-----Original Message-----
From: Josie Henriques <jhenriques_procwork at timbrasil.com.br>
To: SAP Workflow Users' Group <sap-wug at mit.edu>
Sent: Tue, 8 Nov 2005 18:06:18 -0200
Subject: RE: WF-BATCH


   
 Hi Ramki,
 
I'm sure that the WF_initiator is not WF-BATCH. And I've tested just the BAPI and it's recording the right user. But not when I use the Workflow. L
 
Josie Henriques



From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf Of workflow99 at aol.com
Sent: terça-feira, 8 de novembro de 2005 17:47
To: sap-wug at mit.edu
Subject: Re: WF-BATCH
 
Josie,
 
First make sure that the WF_initiator (event creator) is not WF_BATCH user.  
I know of at least one BAPI which has user id as a parameter but ignores the value supplied and uses sy-uname instead. So test the BAPI independently by passing a value other than your user id  in the uname parameter and check if it does use the supplied value. If it does not, you can request SAP to correct the problem.
 
Best Regards,
Ramki Maley.
 
 


_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug

Attached Image: container_workitem.JPG 
[Image removed] 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20051108/18e895a3/attachment.htm