Role Resolution Error

[Soady, Phil]

The Topic Role Resolution. Time for a group discussion ?
The MOST important aspect of building and planning workflow development
is probably Role resolution.
 
If done properly it be used over and over again in Workflows.
 
The more workflows the more the return.
There  is of course the initial overhead in building the role resolution.
However, as all WF admin folk will tell you, a good role resolution,
will pay for itself with the saved time in error handling and correct
and timely delivery. Ie No unnecessary deadlines, missing agents etc
 
When defining your role resolution, consider the following:
o How is the manager / approved determined.  (relationship 012 ?)
o What is the next level up. When Manager1 not found or escalation occurs.
o How many levels up to go.
o Is there a fall back group/person / job etc
 
When is a manager considered to be appropriate before going up a level.
Should exclude oneself !
 
Position not vacant? (008 exists)
Employee on Position not terminated?  (i0000-stat2 value)
Active Employee on position not on leave ? I2001 records.....
Is the employee currently assigned to another position? (Higher duties or other duties)
What substitution policy is to be used?  Is A210 used... is HRUS_D2 used ?
 
 
In other words the topic role resolution is bigger than first one might expect
and should also consider substitution.
 
 
Your role resolution tool can and should be used for escalations.
It can consider some or even more aspects than above.
But spend  more than 10 mins time thinking about it!
If you make the function appropriately,you have ALL business rules in one place,
for ROLE Resolution and Escalation.
 
 
 
 
 
 
 
Phil Soady
Senior Consultant
Business Technologies
SAP Australia
* : 0412 213 079
* : phil.soady at sap.com
 
 
 
 
 
-----Original Message-----
From: David Weston [mailto:weston at clockwork.ca]
Sent: Friday, May 09, 2003 12:19 AM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: Role Resolution Error
 
 
Dadi, we did this for a client in Ottawa by creating our own function module that calls the RH_ACT_LEADING_POSITION and then the RH_STRUC_GET functions in a loop. We also check that if no infotype 105 relationship is created we also go up the org chain again.
 
Hope this helps.
Dave
 
Quoting "Panthaki, Dadi" <Dadi_Panthaki at sony.ca>:
 
> Folks,
>
> We have modified the Travel Expense Approval template # WS20000040.
> The trigger for start of the workflow is BUS2089 Created.
>
> The very first step in the workflow is a Decision Step, to either
> approve or reject the expense report. In this step the Agent is
> determined by Role 00000168 Manager(US).
>
> The workflow works fine as long as the Manager of the employee is
> active in our HR org structure.
>
> We have cases where a manager position is vacant, as the employee has
> left the company. In these cases when an employee of a manager, who is
> no longer occupying this position, submits an expense report the
> workflow errors out with a message "Role could not be resolved: agent
> not determined".
>
> Is there any way in which I can get the workflow to go to the
> Manager's Manager? (Manager's Manager position is not vacant)
>
> How Can I deal with this situation so that the workflow does not error
> out?
>
> Also how can I restart the workflow and direct it to the manager's
> Manager?
>
> Thanks
>
> Dadi
>
>
>