LUW and workflow

Gavin West sapworkflow at blueyonder.co.uk
Sat Jun 22 06:53:48 EDT 2002


Hi Monique,
 
We have this problem as well. The problem we found was that if the user is
locked while they are still working in the sytem, for example while they are
working in the system, someone else tries to log on as them and locks them.
When the user tries to do anything in workflow while they are locked the RFC
cannot log on as the user is locked and then you get the error "You are not
authorized to logon to the target system" in SM58 log.
 
We have not found a way around this except to report the relevant user as
they are giving there log-in to other people to use as well. The best way
would be to throw them out of SAP when they start a new transaction and they
have been locked, but have not found a way of doing this yet. We are also on
40B.
 
Hope this helps.
 
Regards
Gavin West
 
-----Original Message-----
From: SAP Workflow [mailto:Owner-SAP-WUG at MITVMA.MIT.EDU]On Behalf Of
Stephens, Monique S L
Sent: Friday, June 21, 2002 22:15
To: SAP-WUG at MITVMA.MIT.EDU
Subject: LUW and workflow
 
 
We are on version 4.0B.  A particular user seems to be having a recurring
problem with her documents not getting routed via workflow.  When I try and
pull up the workflow log, "no work items linked" message appears.
 
I have been able to find the documents via SWUD (tRFC).  The following is
shown on the screen:
 
Function module: SWW_WI_CREATE_VIA_EVENT
Target system:  WORKFLOW_LOCAL
Status Text: You are not authorized to logon to the target system
Program: RSM13000
 
This does not happen for all documents.  But, it seems to happen to several
documents in a day.  I am able to fix the problem by executing LUW via tRFC.
What is LUW and how is this fixing the document?  Why are her documents not
getting routed properly?
 
Monique Stephens
SAP Analyst
Baylor College of Medicine
713-798-1349
713-798-1326 (FAX)
 


More information about the SAP-WUG mailing list