Responsibilities vs. Org Objects

[Van der Burg, Jeroen JA SITI-ITPSEE]

Agree that that is definitely an issue. A possible solution (well, risk =
reduction approach) is -if you are using HR- to move the level of the =
responsibility as high as possible in the org structure (org unit level) =
and use authorisations to define the possible agents for the task. This =
allows a high level of flexibility within the org unit (at a performance =
cost) for your responsibility; and I assume it will work very well for =
central service centre organisations.
 
 
Regards,
 
 
Jeroen
 
-----Original Message-----
From: Michael Pokraka [mailto:workflow at quirky.me.uk]
Sent: 08 January 2003 11:05
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: Responsibilities vs. Org Objects
 
 
Hi Jeroen,
 
Thanks, that was pretty much what my guess would indicate. The only
hitch I see with this approach is when things get shuffled around in
terms of the organization - as is the trend these days. I've had it in
the past where responsibilities are not that obvious and nobody thinks
of them when org changes are done - they only become apparent when
somebody doesn't get what they should.
I think I'll stick with reposnsibilities though - it just seemed that
country was a nice candidate for playing with custom org objects :-)
 
Thanks for your input.
Cheers
Mike
 
On Wed, Jan 08, 2003 at 09:28:12AM +0100, Van der Burg, Jeroen JA =
SITI-ITPSEE wrote:
> 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