More on Substitutes, Profiles, and Task classes

[Susan Keohan]

Hello all,
 
Having successfully created a substitute profile, and assigned it to a
task classification, and assigned my tasks to a classification, I can
now see that when a user maintains a personal substitute, and choose to
fill in the field for 'Substitute Profile', if they choose the one I
defined, then all is well.  That is, I was able to classify my task so
that it was not included in this particular substitute profile, and
therefore, when the substitute profile is selected, the substitute user
will not get to execute my task.
 
However, how can we ensure that this substitute profile is always chosen
?  If the users do not choose to fill in the substitute profile
field(field is left blank), then the substitute has access to all of the
tasks.  There doesn't seem to be anything in OSS to enforce the
selection of a substitution profile, but I am sure someone out there has
the answer...
 
Thanks all,
Sue
 
Soady, Phil wrote:
 
>Substitutes: If we are talking the classic A 210 relationship.
>or            HRUS_D2 entries.  Either approach works.
>
>Define TASK Class, T77tc.
>Define Substitution Profile T77rp,
>Define Subst proxies in T77ro.
>
>Assign Task classes to Tasks, (Agent assignment screen).
>
>Create a substitute eg
>Position (S) A 210 to (P).  Or make an entry in HRUS_D2.
>
>On the second screen in PP01 the field PROFILE is entered.
>Or from Inbox or your own little program in HRUS_D2.
>
>No harm in filling HRUS_D2. Via A view generated on it.
>
>A PROFILE is link to 1 or more classes. (T77ro)
>
>
>So now a Task is assigned to class "leave"
>can be executed by a substitute who
>has been substituted to via (S) A 210 (P) with PROFILE (LEAVE_TASKS)
>or HRUS_D2 Profile "LEAVE_TASKS".
>
>Profile LEAVE_TASKS was linked to at least Task Class LEAVE.
>
>Now the subst can only see the workitems of tasks with the class "LEAVE"
>
>This way, concepts like "ALL", LEAVE, TIME, APPRAISAL, etc can be defined.
>
>
>The only trick is getting a user friendly ESS style of entry to update
>either HRP1001 or HRUS_D2.
>
>
>Good Luck.
>
>Phil Soady
>Senior Consultant
>Business Technologies
>SAP Australia
>* : 0412 213 079
>* : phil.soady at sap.com
>
>
>
>
>
>-----Original Message-----
>From: Susan Keohan [mailto:skeohan at mit.edu]
>Sent: Wednesday, 2 October 2002 4:58 AM
>To: SAP-WUG at MITVMA.MIT.EDU
>Subject: Preventing a substitute from processing a workflow task
>
>
>Hello,
>
>I have a situation where it is appropriate for a user to set up a substitute to process certain work items, but not all workitems (not
>specific tasks).   The documentation on this topic refers to entries in
>table T77So, using classes on the tasks, and defining substitute profiles. But somewhere along here, I suspect I am missing the key piece of information that will link it all together.  Has anyone used classes to prevent substitutes from executing workitems and if so, can you elaborate ?
>
>Thanks
>Sue
>