Preventing a substitute from processing a workflow task

[Soady, Phil]

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