AW: Feedback Needed on Implementing Separate WF Organizational Tr ee

[Becker Stephan (extern)]

Hi Linda,
 
have you looked at using organisational object assignments as an
alternative? Using that, you can assign specific values from the =
documents
you are processing (e.g. the material group from a sales order item) to =
an
organisational element (like a position or org unit).=20
 
At runtime, the system will resolve the agents by finding the right
organisational element in the HR tree, consequently it means that you =
are
somewhat independent of the reporting structures depicted in the =
HR-based
tree. You are limited to one variable per role if you use the standard, =
but
by using a function module based role in combination with the retrieval
technique described here (just design the code based on the way SAP =
finds
the connections, and allow multiple assignments to the organisational
element), and that would allow you to make it as complex as you like.. =
the
whole thing with relative ease of maintenance -- certainly less than =
keeping
two organisational structures up to date and aligned, which in my =
experience
never works and it prohibitively expensive.. ask your HR responsible =
what it
costs him to maintain just 1 tree!
 
Technically, you would define a role of type organisational data, enter =
the
object type you want to use (have a look at the long text of message 5W =
200
for details on how to make any object an organisational type), and then =
in
PFOM assign the object instance to the organisational unit.
 
Hth,
Stephan
 
-----Urspr=FCngliche Nachricht-----
Von: Terrell, Linda M. [mailto:Linda.Terrell at Lyondell.com]
Gesendet: Mittwoch, 19. Juni 2002 21:47
An: SAP-WUG at MITVMA.MIT.EDU
Betreff: Feedback Needed on Implementing Separate WF Organizational =
Tree
 
 
Dear Experts,
We have implemented eight custom WFs and expect to implement seven more =
over
the next six months.  The biggest problem we have encountered with our =
WFs
is determining the agents of the tasks.  We have little control over =
the
structure of the organization and HR is generally focused on a =
hierarchical
reporting (superior/subordinate) relationship.  Our WFs are mostly
interested in logistical escalation procedures.  Often the steps in an
escalation process is not to notify the supervisor but a backup person, =
then
a whole team, then the supervisor or a person outside of that group
entirely.  Until now, we have been successful in using custom table to
resolve the agents needed for specific tasks.  However this is getting =
more
difficult as the number of WFs grows. =20
 
We would like to build an organizational tree with nodes that do not =
fit
within the reporting relationship within the company.  Although this =
creates
a dual maintenance situation, this would eliminate the contention =
between HR
and workflow requirements.  These separate organizations would allow us =
to
define Jobs, Positions, Organizational Units, etc. based on the =
logistical
processes.  Maintenance of these organizational structures could be
performed without impacting HR.=20
 
Before we approach HR with our solution, we need facts.  Any feedback =
on our
proposal, or how this issue has been addresses at your company would be
appreciated.
 
Thanks in advance for your help.
 
 
Linda Terrell
Lyondell Chemical=20