Agent not being resolved
ASSY, SOSTHENE
S.ASSY at AFDB.ORG
Fri Jun 7 04:20:58 EDT 2002
You can a lot of reasons.
1. Check you binding if you pass the right information as parameter
2. Check is this staff has a chief (Chief position) transacction =
PPOM
3. Do the reporting structure to update the relation REPORT TO (A 002)
Good luck
=20
-----Original Message-----
From: NAT GOVENDER [mailto:nat at tac.toyota.co.za]=20
Sent: Thursday, June 06, 2002 10:29 AM
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
This e-mail and any attachment sent with it are confidential and =
intended
solely for the use of the individual to whom it is addressed. If you =
have
received this e-mail by error please delete it immediately. No =
reference
should be made of the information contained in this e-mail. The views =
or
opinions expressed in this message, unless otherwise clearly indicated, =
are
solely those of its author and do not necessarily represent those of =
the
ADB. Unauthorized publication, use, dissemination, forwarding, =
printing or
copying of this e-mail and its associated attachments is strictly
prohibited. ADB believes but does not warrant that this e-mail and any
attachments are virus-free. You must therefore take full =
responsibility for
checking for viruses therein. ADB disclaims any responsibility and =
liability
arising from your unauthorized use of the contents of this e-mail or =
your
failing to ensure that it is virus-free. =20
Ce message =E9lectronique et tous les documents attach=E9s qu'il =
contient sont
confidentiels et destin=E9s exclusivement =E0 la personne =E0 laquelle =
ils ont =E9t=E9
envoy=E9s. Si vous avez re=E7u ce message par erreur, veuillez le =
d=E9truire
imm=E9diatement; vous voudrez bien =E9galement vous abstenir de toute =
r=E9f=E9rence
aux informations qui y figurent. Sauf mention expresse, les id=E9es =
et
opinions pr=E9sent=E9es dans ce message sont celles de son auteur, et =
n'engagent
pas la BAD. La publication, l'usage, la distribution, l'impression =
ou la
copie non autoris=E9e de ce message et des fichiers attach=E9s qu'il =
contient
sont strictement interdits. La BAD a pris toute pr=E9caution pour =
=E9viter la
pr=E9sence de virus, mais nous ne pouvons vous garantir l'absence de =
virus.
Vous devez donc prendre toute disposition utile pour la v=E9rification =
de
l'absence de virus. La BAD d=E9gage toute responsabilit=E9 en cas de =
probl=E8me
pos=E9 par des virus.=20
More information about the SAP-WUG
mailing list