Responsibilities vs. Org Objects

[Michael Pokraka]

Hmmm, that sounds an excellent idea. I have been looking at
authorization-based agent assignments in any case, but the combination
hadn't occurred to me in that context. It does basically make full use
of SAP's possible/actual agent determination concept.
Thanks again for your input.
Cheer
Mike
 
On Wed, Jan 08, 2003 at 11:19:41AM +0100, Van der Burg, Jeroen JA SITI-ITPSEE wrote:
> 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,