Problems establishing agents
Kjetil Kilhavn
KJETILK at statoil.com
Tue Jun 5 04:33:12 EDT 2001
Just in case you missed a fine little detail when you said the organization plan
was OK: does your manager have a user in the system? In our development systems
we don't have all the users that we have in the production systems, that's why I
thought of this potential issue. Thus it could be that your plan has the manger
as a person, but there is no user to be found. Since you use the role "Superior
(as user) ..." you must have a user defined (and connected via infotype 0105)
for your manager.
--
Kjetil Kilhavn
|--------+------------------------------>
| | "Dart, Jocelyn" |
| | <jocelyn.dart at sap.co|
| | m> |
| | Sent by: SAP |
| | Workflow |
| | <Owner-SAP-WUG at MITVM|
| | A.MIT.EDU> |
| | |
| | |
| | 05.06.2001 08:35 |
| | Please respond to |
| | "SAP Workflow Users'|
| | Group" |
| | |
|--------+------------------------------>
>----------------------------------------------------------------------------|
| |
| To: SAP-WUG at MITVMA.MIT.EDU |
| cc: (bcc: Kjetil Kilhavn) |
| Subject: Re: Problems establishing agents |
>----------------------------------------------------------------------------|
Hi Kris,
Ok, you're going to have to debug SWX_GET_MANAGER in detail to
see where it is falling over.
Immediately after you execute statements
SWC_GET_ELEMENT AC_CONTAINER 'OTYPE' ORG_TYPE.
SWC_GET_ELEMENT AC_CONTAINER 'OBJID' ORG_ID.
Use the ABAP debugger to force the value of org_type to "US" and
org_id to "WILSON".
You'll see there are 2 parts to SWX_GET_MANAGER - the call to
RH_ACT_LEADING_POSITION to find the manager, followed by a call
to RH_STRUC_GET to find the user id of the manager.
You'll need to debug both to see where the problem is - a failure
in either will cause the role to fail.
If you single step through RH_ACT_LEADING_POSITION you'll see there
is a call to RH_GET_ACTIVE_WF_PLVAR which picks up the plan version,
and a call to RH_GET_LEADING_POSITION. RH_GET_LEADING_POSITION is the
most interesting as this is where it finds the position of the user, finds
the org unit of the position, and finds the chief position of the org unit.
I'd also suggest you grab an HR person there who understands your org plan
in detail to check that the evaluation paths are working correctly and
that all the infotype relationships are really there.
If you still can't track it down, you'll need to report it in to OSS.
Good luck!
Regards,
Jocelyn
-----Original Message-----
From: Wilson, Kris [mailto:wilsonk-csc at kaman.com]
Sent: Tuesday, 5 June 2001 4:08 PM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: Problems establishing agents
Hi Jocelyn,
I checked both the plan version being used in our HR Org. plan
and all managers have an infotype set up linking their userid. I also tried
debugging the function module SWX_GET_MANAGER all to no avail. I'm not sure
how to fix this problem, I understand exactly what it means but I can't seem
to isolate where the problem could be. The workflow checks out fine, it
matches exactly what we have running on our PRD server, the Org. Structure
matches as well. What I can't figure out is why workflow is telling me that
there is no chief position for US WILSON when in the org. plan my manager is
set up as a chief position and I have an infotype reflecting this. The
workflow error diagnosis is telling me to either change the org. plan so
that standard role AC00000168 provides a number of users other than zero, or
to change the agent assignment in the step where the manager should review
the employee's purchase request. It works in production but not development
which is damn weird.
Is there anything you can possibly advise to look at here Jocelyn? Sorry to
trouble you with this, but I have heard on the grape vine that you are the
top workflower in Australia so maybe you might have seen this problem
somewhere. We are running 4.5B incidentally.
Regards,
Kris Wilson
SAP Workflow Administrator
CSC - 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
-----Original Message-----
From: Dart, Jocelyn [mailto:jocelyn.dart at sap.com]
Sent: Tuesday, June 05, 2001 11:54 AM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: Problems establishing agents
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
-------------------------------------------------------------------
Statoil: The information contained in this message may be CONFIDENTIAL and is
intended for the addressee only. Any unauthorised use, dissemination of the
information or copying of this message is prohibited. If you are not the
addressee, please notify the sender immediately by return e-mail and delete this
message.
Thank you.
More information about the SAP-WUG
mailing list