"No administator found" error message

[Scheinoha John]

Elad,
 
   We did an SAP support pack upgrade in 4.6C to support pack level 44.
 
After the upgrade, the WF Administrator could no longer reserve,
forward
or execute work items. We would receive the error message 5W 141 "No
Administrator found for this task."
 
 
   There are two OSS notes to resolve this situation. OSS Notes 653093
 
and 658738. 653093 is a pre-requisite to OSS Note 658738.
 
 
   This situation came up in an open forum discussion at the American
SAP User Group (ASUG) meeting held 10/26 - 10/30.
 
 
Thanks,
 
 
 
 
John Scheinoha
Briggs & Stratton Corporation
(414) 256 - 5136
scheinoha.john at basco.com
 
>>> PRoehlen at powercor.com.au 03/10/04 08:27PM >>>
Hi Elad,
 
I'll have a go at answering your questions:
 
1) The behaviour that you state that you prefer should be how it works
- ie
the workflow should error (and only error) in the case of the
unhandled
exceptions.  Other exceptions or no exceptions should result in the
workflow
continuing as modelled.
 
2) Check the workflow customising to ensure your workflow administrator
is
maintained correctly using SWU3.  If so, check also that you have not
assigned a person responsible in the task itself (Additonal
data->person
responsible.)  If you have, make sure that it is assigned correctly.
 
3) By default, when transporting a new version of a workflow template
to a
system, the new version is not used until the buffer is refreshed.
This
happens automatically at midnight, but can be done manually using
transaction SWU_OBUF.
 
Hope the above is of some help.
 
Peter Roehlen
 
Senior Analyst Programmer
Powercor Australia Ltd.
Phone +61 +3 9683 4296
Mobile 0403 961 768
 
 
 
 
-----Original Message-----
From: SAP Workflow [mailto:Owner-SAP-WUG at MITVMA.MIT.EDU] On Behalf Of
ezra
Sent: Thursday, 11 March 2004 2:34 AM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: "No administator found" error message
 
Hello,
I have several questions :
 
1. I have defined a method with several possible exceptions, Do I have
to
catch all of them in the WF definition ?
    I would like to catch some of these exceptions and if any other
exception occurs I want the WF to change to satus error.
    The problem is that when I don't catch all of the exceptions,
    I get an error message tells me that the task could not be
executed(that
doesn't happen when I don't catch any exception).
 
2. What does it mean when a user runs a WI and receives "No
administrator
found for the task" ?
 
3. This one is very strange :
    Sometimes, when we make changes in our DEV system, and transport
the
change request to our TEST system,
    even though the change request is transported successfully, the
actual
changes in the WF definition only takes place several hours later.
    Has anyone met with this kind of problem ?
 
Thanks,
Elad.
 
 
**********************************************************************
CitiPower Pty and Powercor Australia Ltd. This email and any file
attachments are confidential and intended solely for the use of the
individual or entity to whom they are addressed. If you have received
this email in error please tell us immediately by return email and
delete the document.
**********************************************************************