best way to handle the scenario

Tue Oct 25 00:36:09 EDT 2005

Hi Sushil,

This is what I would do assuming you have already determined you agents.

You can firstly assign a role say "Release PO" to all the possible agents.
In your task you then  assign the attribute General and forwarding allowed
or not allowed thereafter you assign a role say "Release PO" and this
become your possible agents.

Regards

Nat Govender
Toyota South Africa
IT - SAP - SAP Workflow
Internal Ext.  : 32645
Direct Line    : +27 31 910 2645
Fax                 : +27 31 902 9633
E-mail            : ngovender4 at toyota.co.za
==================================================================
Forgiveness is when one relinquishes the option to hurt the person that
hurt you.
Remember not to forget that which you do not need to know.
==================================================================

             "Sushil Guragain"                                            
             <sguragain at interp                                            
             ublic.com>                                                 To
             Sent by:                  "SAP Workflow Users' Group"        
             sap-wug-bounces at m         <sap-wug at mit.edu>                  
             it.edu                                                     cc

                                                                   Subject
             2005/10/24 04:55          best way to handle the scenario    
             PM                                                           

             Please respond to                                            
               "SAP Workflow                                              
               Users' Group"                                              
             <sap-wug at mit.edu>                                            

Hi WF Gurus,

I need to support over 50 plants and each plant has separate list of
approvers for each release code (of a PO). The users would like to have the
ability to select approvers on some cases and send the work item to all
approvers in others. I don't think building 50 branches with multiple
condition will be a good idea. Therefore I was thinking about building a
function module to handle this. However, since I have to define all
approvers as a possible agent (for the approval task) it will be hard to
analyze when there is a problem in workflow. Can you please suggest what
would be the best approach to handle this? (as to how to support the
correct list of possible agents and make sure we send the work items to
correct individuals).

I took a look at building rules but I did not see an option to build a rule
that will direct the work items to different roles. Looks like we can send
them to different individual, organization, position etc but we do not have
org structure setup in SAP and are using security roles to control
different group of approvers.

Thanks in advance for your suggestions.

Sushil

This message contains information which may be confidential and privileged.
Unless you are the intended recipient (or authorized to receive this
message
for the intended recipient), you may not use, copy, disseminate or disclose
to
anyone the message or any information contained in the message.  If you
have
received the message in error, please advise the sender by reply e-mail,
and
delete the message.  Thank you very much.
(A)
_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug

This message is a privileged and private communication and may be read, copied and used only by
the intended recipient(s). If you are not an intended recipient, please let us know by return email.
Please then delete the message and do not disclose its contents to any person. Neither the sender nor
Toyota South Africa Motors accepts any liability whatsoever as a result of the further dissemination
of this message. Whilst all reasonable steps are taken to avoid corruption of data or information,
we do not accept any liability should such corruption occur.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20051025/c83b59cb/attachment.htm
-------------- next part --------------
A non-text attachment was scrubbed...
Name: graycol.gif
Type: image/gif
Size: 105 bytes
Desc: not available
Url : http://mailman.mit.edu/pipermail/sap-wug/attachments/20051025/c83b59cb/attachment.gif
-------------- next part --------------
A non-text attachment was scrubbed...
Name: pic00292.gif
Type: image/gif
Size: 1255 bytes
Desc: not available
Url : http://mailman.mit.edu/pipermail/sap-wug/attachments/20051025/c83b59cb/attachment-0001.gif
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ecblank.gif
Type: image/gif
Size: 45 bytes
Desc: not available
Url : http://mailman.mit.edu/pipermail/sap-wug/attachments/20051025/c83b59cb/attachment-0002.gif