Responsibilities vs. Org Objects

[Van der Burg, Jeroen JA SITI-ITPSEE]

Hi Michael,
 
We were sort of in the same situation here. Many of our situations are =
similar to what you describe; I decided to only use responsibilities and =
not use any org objects due to our scale and expected maintenance issues =
with org objects.
 
Currently live in seven countries with loads of responsibilities and =
experiences are good (although defining who goes where in your =
responsibilities can be a bit of a challenge - but that will not be =
different with org objects I am afraid!).
 
 
Regards,
 
 
Jeroen
 
 
 
-----Original Message-----
From: Michael Pokraka [mailto:workflow at quirky.me.uk]
Sent: 07 January 2003 19:46
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Responsibilities vs. Org Objects
 
 
Hi all,
This may be more of a point for discussion rather than a question:
 
At what point should one consider using a SAP Organizational Object
rather than a responsibility?
 
I have a scenario where the client has a number of tasks which need to
be routed to the same person in each country. Someting like a task which
needs to go to the sales managers for a list of countries. Another
workflow might address all the chief accountants and so on.
 
In the long term, would it be of any use doing this by creating jobs
and using zCountry org objects, or would one create a responsibility for
each task/step that involves different people per country.
(4.6c by the way, without HR - due sometime in future).
 
As I can see, both have their (dis)advantages in terms of overview and
maintainability - any ideas?
 
Cheers
Mike