AW: Agent not being resolved

[Becker Stephan (extern)]

Hi Jose,
 
agent assignments are client-dependent HR settings, and are transported
separate from the workflow definitions. Look out for PD* entries in
transports, that's them..
 
Greetings,
Stephan
 
-----Urspr=FCngliche Nachricht-----
Von: Jose Burgman [mailto:Jose.Burgman at palabora.co.za]
Gesendet: Donnerstag, 6. Juni 2002 14:42
An: SAP-WUG at MITVMA.MIT.EDU
Betreff: Re: Agent not being resolved
 
 
Hi there
 
Yes, he is. The problem I have found now is that the workflow is not =
truly
client independent! The tasks do not have agents assigned in our test =
box,
but they are assigned in the dev box. ??? We're on 4.6C. Am going to =
have to
maintain them manually when its moved to QA and PRD? The tasks were =
assigned
to general users. I used transaction SWU_OBUF to synchronize the
buffers....but it made no difference! I also used transaction SCC1 to =
copy
the transports between clients - also made no difference.....
 
Thanks.
 
Jos=E9
 
-----Original Message-----
From: NAT GOVENDER [mailto:nat at tac.toyota.co.za]
Sent: 06 June 2002 12:29
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: Agent not being resolved
 
 
Make sure that the user creating the record is linked in the org. plan.
 
>>> Jose.Burgman at palabora.co.za Thursday, June 06, 2002 12:09:34 PM >>>
Hi Every-one
 
I'm having a problem with a role not being resolved. I'm using the =
standard
role 168, and I've tested it under my user id and it finds the =
superior. The
workflow is rather simple - a user captures his leave in pa61, which =
starts
the workflow and sends it to his supervisor for approval. The problem =
is
that the agent is not found. Could it be an authorization issue, if so, =
how
can I go about confirming this and finding out what is lacking in the
authorisation?
 
Thanks for the trouble.
 
Regards
 
Jos=E9=20