best way to handle the scenario

[lianghuan.x.hu@accenture.com]

I think you should use org structures with approver position for each
plant and then you can assign users to these positions. Larry

________________________________

From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of Sushil Guragain
Sent: Monday, October 24, 2005 10:56 AM
To: SAP Workflow Users' Group
Subject: best way to handle the scenario


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)


This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information.  If you have received it in error, please notify the sender immediately and delete the original.  Any other use of the email by you is prohibited.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20051024/670e80cd/attachment.htm