Transport of Agent Assignment

[Steve Johnson]

This helps a lot, I think rather than system/workflow
group involvement there should be a functional person
from HR should be involved more to make this process
sync.
 
Thanks,
Steve
--- "Dart, Jocelyn" <jocelyn.dart at sap.com> wrote:
> Steve,
> I think what you really need at this point is some
> help from a specialist SAP HR consultant.  That's
> the best
> way to understand the options and implications of
> what you are trying to do.
>
> It is not the sort of thing that can be covered
> adequately in an email and of course getting it
> wrong could be costly. Plus which option is best may
> depend on how your org plan is configured.
>
> Suggest you contact your partner or SAP Account
> Manager or put a message in OSS to organise for some
> time from an HR  consultant.
>
> Make sure you be very specific about what you need
> to discuss and ensure you get someone knowledgable
> in HR transport so that you can cover your
> requirements and get an answer in few hours rather
> than days.
>
> You will also need to involve whoever at your site
> is responsible for your org plan and understands how
> it has been configured if that's not you.
> Regards,
>         Jocelyn Dart
> Consultant (SRM, EBP, Workflow)
> and co-author of the book
> "Practical Workflow for SAP"
> SAP Australia
> email: jocelyn.dart at sap.com
> phone: +61 412 390 267
> fax:   +61 2 9935 4880
>
>
>
>
> -----Original Message-----
>> From: Steve Johnson [mailto:steve_basis at yahoo.com]
> Sent: Tuesday,18 November 2003 2:30 PM
> To: SAP-WUG at MITVMA.MIT.EDU
> Subject: Re: Transport of Agent Assignment
>
>
> Jocelyn,
>
> thank you. Can you please explain about the org
> plans
> regarding my questions in previous email about
> T77SO,
> TRSP/CORR?
>
> Thnaks,
> Steve
> - "Dart, Jocelyn" <jocelyn.dart at sap.com> wrote:
> > Steve,
> > Transaction OOTR allows you to maintain table
> T77TR
> > which
> > should apply to all HR org plan distribution
> > techniques.
> >
> > You need to enter:
> > * Object type e.g. O for org unit, S for position
> > * Infotype e.g. 1001 for any org plan relationship
> > * Subtype e.g. A008 is the holder subtype for 1001
> -
> > 1001 subtypes are
> > based on the evaluation path code for the
> > relationship defined.
> >
> > Jocelyn
> >
> > -----Original Message-----
> > From: Steve Johnson [mailto:steve_basis at yahoo.com]
> > Sent: Tuesday,18 November 2003 12:59 PM
> > To: SAP-WUG at MITVMA.MIT.EDU
> > Subject: Re: Transport of Agent Assignment
> >
> >
> > Hello All,
> >
> > I think I am not up to the point of knowledge with
> > these organization plans. But I would like to
> > privent
> > the over writting of ORG PLANS and values every
> time
> > when DEV to PRD chnages are transported.
> >
> > I understand from below message that we cna
> privent
> > doing this.
> >
> > Can some one please explain me what is the first
> > setting i need to do to make sure PPMOE t-cd
> > customizing values are not transported when some
> one
> > chnages one node change this t-cd PPMOE.
> >
> > Please advise me how do i do this. Is the TRSP or
> > CORR
> > is tables or t-cd? or fields in T77S0.
> >
> > Thanks,
> > Steve
> > --- "Kouw, FA - SPLTX" <fa.kouw at td.klm.com> wrote:
> > > Hi Carolyn, Shayam,
> > >
> > > We also made the following setting:
> > >
> > > Transport lock for infotypes and subtypes per
> > object
> > > (transaction  OOTR  Entry: S/1001/A008): this
> > > setting is
> > > made to prevent holders of positions being
> > > overwritten after transporting organizational
> plan
> > > changes from
> > > development tot production.
> > >
> > > Regards,
> > >
> > > Fred Kouw
> > >
> > > Carolyn Fuller wrote:
> > >
> > > > Shayam,
> > > >
> > > > We found that this configuration switch
> > (TRSP/CORR
> > > of T77S0)
> > > > transported much more than we wanted
> > transported.
> > > We now assign agents
> > > > in each of our environments manually.
> > > >
> > > > Carolyn
> > > > On Monday, November 17, 2003, at 05:24 AM,
> > Shayam
> > > Agrawal wrote:
> > > >
> > > > > Thanks a lot for the useful information,
> > > > > yeah, i also had traced out entry TRSP/CORR
> of
> > > T77S0 and did the
> > > > > transport the same way,
> > > > >
> > > > > Thanks and regards
> > > > > Shayam Agrawal
> > > > >
> > > > > --
> > > > >
> > > > > --------- Original Message ---------
> > > > >
> > > > > DATE: Mon, 17 Nov 2003 09:56:56
> > > > > From: "Kouw, FA - SPLTX"
> <fa.kouw at td.klm.com>
> > > > > To: SAP-WUG at MITVMA.MIT.EDU
> > > > > Cc:
> > > > >
> > > > >> Hi,
> > > > >>
> > > > >> From 'the book' (page 128):
> > > > >>
> > > > >> There are a number of options for
> > transporting
> > > the organizational
> > > > >> plan:
> > > > >>
> > > > >>   * Automatic transport of all changes:
> table
> > > T77S0, entry TRSP.CORR
> > > > >> is set to space
> > > > >>   * Manual transport of changes, by
> manually
> > > selecting what is to be
> > > > >> transported: table T77S0, entry TRSP.CORR
> > > > >>     is set to 'X', program RHMOVE30
> performs
> > > the transport
> > > > >>   * Transport via an object lock by using a
> > > change request:: table
> > > > >> T77S0, entry TRSP.CORR is set to 'T',
> > > > >>     program RHMOVE50 performs the transport
> > > > >>
> > > > >> Regards,
> > > > >>
> > > > >> Fred Kouw
> > > > >>
> > > > >> Robert.vande.Berg at nuon.com wrote:
> > > > >>
> > > > >>> With report RHMOVE30, you can transport
> the
> > > agent assignment(s).
> > > > >>> It is possible to set whether or nog this
> > > assignment should be
> > > > >>> included in
> > > > >>> the tranport, but I don't know where this
> > can
> > > be set...
>
=== message truncated ===
 
 
=====
Thanks,
Steve Johnson
BSHG