Problems establishing agents

Dart, Jocelyn jocelyn.dart at sap.com
Mon Jun 4 21:53:37 EDT 2001


Kris,
Check the plan version being used for your HR org plan -
workflow only works on the current plan version but
sometimes HR folk use other plan versions.
Plan version set for workflow can be checked via transaction
SWU3.
 
Check all the managers have an infotype 105 set up linking to
their userid.
 
If you are on 4.6 you can use the simulate role function in
transaction PFAC to check what manager/userids are found for the role.
 
Other than that you could try debugging function module
SWX_GET_MANAGER using transaction SE37 and feeding in the
OTYPE/OBJID parameters via ABAP debug at the appropriate point.
 
Regards,
        Jocelyn Dart
Consultant (BBP, Ecommerce, Internet Transaction Server, Workflow)
SAP Australia
Email jocelyn.dart at sap.com <mailto:jocelyn.dart at sap.com>
Tel: +61 412 390 267
Fax: +61 2 9935 4880
 
 
-----Original Message-----
From: Wilson, Kris [mailto:wilsonk-csc at kaman.com]
Sent: Monday, 4 June 2001 12:12 PM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Problems establishing agents
 
 
Hello Workflowers,
                    My name is Kris Wilson and I have been into workflow
administration for the last 9 months, the last month has seen me get into
workflow development and I have discovered a problem with one of the
workflows my company is maintaining for our client.  The funny thing is, I
have discovered the problem in our development client yet the workflow works
fine in production (scary?).
 
The workflow in question is used to request non-HP(Helicoptor) parts and
services.  It requires the user to provide details of the required items
including description, quantity, etc.  This information will be forwarded
for consideration to the user's manager and then the Business Manager.  If
it is approved the Purchasing Officer will order the goods.  The user is
then notified of the outcome via workflow messages.
 
The problem is occurring when the workflow is sent to the user's manager, it
just isn't reaching them in our development client, in production there is
no such problem.  The error I keep receiving essentially says that there is
an error or exception resolving role "AC000000168" Superior (as user) for...
It is telling me that there is no chief position for the user who is
starting the workflow, yet we have a cheif position in every org. unit in
our organisation.  I understand the problem, the thing is, I can't isolate
the cause of it.
 
Like I said, the workflow works fine in PRD yet not in DV1, we had made a
change to the organisational structure but so far I can't fathom why it
can't find an agent when we have cheif positions assigned.  If anyone out
there has any ideas on what might be causing this problem, or how to solve
it, it would be greatly appreciated.  Thanks.
 
Regards,
 
Kris Wilson
SAP Workflow Administrator
 
CSC Australia - Defence Operations
SH-2G(A) Super Seasprite Helicoptor Support Centre
Tel:  +61-2-4429-4667     Fax:  +61-2-4429-4661
Mobile:  0404057781
Email:  wilsonk-csc at kaman.com
 


More information about the SAP-WUG mailing list