Defining and transporting an organizational plan
Kouw, FA - SPLTC
fa.kouw at td.klm.com
Tue Dec 17 03:13:53 EST 2002
Thank you very much Dale, this really helps me out!
Regards,
Fred Kouw
Dale Davis wrote:
> Fred:
>
> Try this:
>
> |------------------------+------------------------+------------------------|
> |Object Type |Infotype |Subtype |
> |------------------------+------------------------+------------------------|
> |S |1001 |A008 |
> |------------------------+------------------------+------------------------|
>
> or this
>
> OT = S
> IT = 1001
> ST = A008
>
> Regards,
> Dale Davis Jones
> IBM Business Consulting Services
> Phone: 845-691-7861
> T/L 8-320-8440
> Internet Address: DKDAVIS at US.IBM.COM
>
> .......You can never discover new oceans unless you have the courage to
> lose sight of the shore..........
>
> "Kouw, FA - SPLTC" <fa.kouw at td.klm.com>@MITVMA.MIT.EDU> on 12/12/2002
> 11:32:51 AM
>
> Please respond to "SAP Workflow Users' Group" <SAP-WUG at MITVMA.MIT.EDU>
>
> Sent by: SAP Workflow <Owner-SAP-WUG at MITVMA.MIT.EDU>
>
> To: SAP-WUG at MITVMA.MIT.EDU
> cc:
> Subject: Re: Defining and transporting an organizational plan
>
> Dale,
>
> Thank you for your quick response again! Unfortunately I can't receive any
> attachments (picture etc.). Could you
> please show it using text?
>
> Thanks again, this forum really helps!
>
> Greetings Fred Kouw
>
> Dale Davis wrote:
>
> > Fred:
> >
> > It should look like the following. No additional set up should be
> > necessary.
> >
> > (Embedded image moved to file: pic20159.pcx)
> >
> > Regards,
> > Dale Davis Jones
> > IBM Business Consulting Services
> > Phone: 845-691-7861
> > T/L 8-320-8440
> > Internet Address: DKDAVIS at US.IBM.COM
> >
> > .......You can never discover new oceans unless you have the courage to
> > lose sight of the shore..........
> >
> > "Kouw, FA - SPLTC" <fa.kouw at td.klm.com>@MITVMA.MIT.EDU> on 12/12/2002
> > 11:10:15 AM
> >
> > Please respond to "SAP Workflow Users' Group" <SAP-WUG at MITVMA.MIT.EDU>
> >
> > Sent by: SAP Workflow <Owner-SAP-WUG at MITVMA.MIT.EDU>
> >
> > To: SAP-WUG at MITVMA.MIT.EDU
> > cc:
> > Subject: Re: Defining and transporting an organizational plan
> >
> > Hello,
> >
> > Thanks for the (quick and clear) answer. It's clear to me what to do:
> > production user masters only exist in our
> > production environment and we do not have HR implemented, so we will
> > maintain the org structure in the
> > development environment and transport it to the other environments.
> >
> > Can someone please tell me how to set up the 'is holder of relationship'
> in
> > the override table T77TR using
> > transaction OOTR? What entries should I use in the colums of the table
> > (must I define some values anywhere else
> > to be able to select the entries I need)?
> >
> > Kind regards,
> >
> > Fred Kouw
> >
> > Dale Davis wrote:
> >
> > > There are several approaches that can be taken to maintain org
> > assignments
> > > in a production environment.
> > >
> > > For SAP systems where HR is not implemented, and production user
> masters
> > > only exist in the production system, our preferred approach is to
> > maintain
> > > the org structure in the development environment and transport to test
> > and
> > > production, then assign the users to directly in production.
> > > In this scenario it is necessary to block the production org from
> > > development agent assignment overrides by setting up the is holder of
> > > relationship in the override table T77TR accessed through transaction
> > OOTR.
> > > This guarantees that user assignments from the development system do
> not
> > > wipe out the production systems when org structure changes are
> > transported
> > > to production.
> > >
> > > For SAP implementations where HR is implemented or production user
> > master
> > > tables are kept in synch with test user master tables, user assignments
> > are
> > > sometimes maintained in the test system and transported from that
> system
> > to
> > > the production system. This is a less desirable approach in an
> > environment
> > > where SAP security and basis teams do not allow transports to
> production
> > > systems which originate in test and lock the system against transport
> > > request generation. For this scenario,an alternative approach is to ALE
> > the
> > > user assignments from the test system to production.
> > >
> > > In general if we are implementing workflow in an environment where our
> > org
> > > structures are owned by HR, we follow the HR process's rule on where
> the
> > > user ids should be assigned and maintained and utilize transports with
> > > override blocks or ALE as appropriate.
> > >
> > > Regards,
> > > Dale Davis Jones
> > > IBM Business Consulting Services
> > > Phone: 845-691-7861
> > > T/L 8-320-8440
> > > Internet Address: DKDAVIS at US.IBM.COM
> > >
> > > .......You can never discover new oceans unless you have the courage to
> > > lose sight of the shore..........
> > >
> > > "Kouw, FA - SPLTC" <fa.kouw at td.klm.com>@MITVMA.MIT.EDU> on 12/09/2002
> > > 09:00:39 AM
> > >
> > > Please respond to "SAP Workflow Users' Group" <SAP-WUG at MITVMA.MIT.EDU>
> > >
> > > Sent by: SAP Workflow <Owner-SAP-WUG at MITVMA.MIT.EDU>
> > >
> > > To: SAP-WUG at MITVMA.MIT.EDU
> > > cc:
> > > Subject: Defining and transporting an organizational plan
> > >
> > > Hello,
> > >
> > > I tried to find an answer to my questions in the archives, but couldn't
> > > find it.
> > >
> > > Can anyone tell me what's the best way to define an organizational
> plan?
> > > Some people define it in development and transport it to acceptance and
> > > production. A problem that can arise is that all users are erased in
> the
> > > target environment (and thus must be defined again...). Others define
> it
> > > in development AND acceptance and copy it from acceptance to production
> > > (users defined on acceptance are the same as on production, so the
> > > problem mentioned before will not arise). Finally some set it up on all
> > > environments (development, acceptance and production) separately.
> > >
> > > What's the best solution (we are configuring a completely new SAP
> > > release)?
> > >
> > > Secondly: if you define the organizational plan on all environments
> > > separately, how does the agent assignment in the step know what
> position
> > > must be used, because, as far as I know, the intenal number assignment
> > > is used and these numbers can/will be different on
> > > deverlopment/acceptance/production?
> > >
> > > Thanks in advance!
> > >
> > > Greetings Fred Kouw
> > >
> > > **********************************************************************
> > > This e-mail and any attachment may contain confidential and privileged
> > > material intended for the addressee only. If you are not the addressee,
> > you
> > > are notified that no part of the e-mail or any attachment may be
> > disclosed,
> > > copied or distributed, and that any other action related to this e-mail
> > or
> > > attachment is strictly prohibited, and may be unlawful. If you have
> > > received
> > > this e-mail by error, please notify the sender immediately by return
> > > e-mail,
> > > and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM),
> > its
> > > subsidiaries and/or its employees shall not be liable for the incorrect
> > or
> > > incomplete transmission of this e-mail or any attachments, nor
> > responsible
> > > for any delay in receipt.
> > > **********************************************************************
> > >
> > >
> >
> _____________________________________________________________________________________________
>
> >
> > >
> > > This outbound message from KPN has been checked for all known viruses
> by
> > > KPN IV-Scan, powered by MessageLabs.
> > > For further information visit: http://www.veiliginternet.nl
> > >
> >
> _____________________________________________________________________________________________
>
> >
> > >
> > >
> >
> _________________________________________________________________________________________
>
> >
> > > This inbound message from KPN has been checked for all known viruses by
> > KPN IV-Scan, powered by MessageLabs.
> > > For further information visit: http://www.veiliginternet.nl
> > >
> >
> _____________________________________________________________________________________________
>
> >
> > **********************************************************************
> > This e-mail and any attachment may contain confidential and privileged
> > material intended for the addressee only. If you are not the addressee,
> you
> > are notified that no part of the e-mail or any attachment may be
> disclosed,
> > copied or distributed, and that any other action related to this e-mail
> or
> > attachment is strictly prohibited, and may be unlawful. If you have
> > received
> > this e-mail by error, please notify the sender immediately by return
> > e-mail,
> > and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM),
> its
> > subsidiaries and/or its employees shall not be liable for the incorrect
> or
> > incomplete transmission of this e-mail or any attachments, nor
> responsible
> > for any delay in receipt.
> > **********************************************************************
> >
> >
> _____________________________________________________________________________________________
>
> >
> > This outbound message from KPN has been checked for all known viruses by
> > KPN IV-Scan, powered by MessageLabs.
> > For further information visit: http://www.veiliginternet.nl
> >
> _____________________________________________________________________________________________
>
> >
> >
> _________________________________________________________________________________________
>
> > This inbound message from KPN has been checked for all known viruses by
> KPN IV-Scan, powered by MessageLabs.
> > For further information visit: http://www.veiliginternet.nl
> >
> _____________________________________________________________________________________________
>
> **********************************************************************
> This e-mail and any attachment may contain confidential and privileged
> material intended for the addressee only. If you are not the addressee, you
> are notified that no part of the e-mail or any attachment may be disclosed,
> copied or distributed, and that any other action related to this e-mail or
> attachment is strictly prohibited, and may be unlawful. If you have
> received
> this e-mail by error, please notify the sender immediately by return
> e-mail,
> and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its
> subsidiaries and/or its employees shall not be liable for the incorrect or
> incomplete transmission of this e-mail or any attachments, nor responsible
> for any delay in receipt.
> **********************************************************************
>
> _____________________________________________________________________________________________
>
> This outbound message from KPN has been checked for all known viruses by
> KPN IV-Scan, powered by MessageLabs.
> For further information visit: http://www.veiliginternet.nl
> _____________________________________________________________________________________________
>
> _________________________________________________________________________________________
> This inbound message from KPN has been checked for all known viruses by KPN IV-Scan, powered by MessageLabs.
> For further information visit: http://www.veiliginternet.nl
> _____________________________________________________________________________________________
**********************************************************************
This e-mail and any attachment may contain confidential and privileged
material intended for the addressee only. If you are not the addressee, you
are notified that no part of the e-mail or any attachment may be disclosed,
copied or distributed, and that any other action related to this e-mail or
attachment is strictly prohibited, and may be unlawful. If you have received
this e-mail by error, please notify the sender immediately by return e-mail,
and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its
subsidiaries and/or its employees shall not be liable for the incorrect or
incomplete transmission of this e-mail or any attachments, nor responsible
for any delay in receipt.
**********************************************************************
_____________________________________________________________________________________________
This outbound message from KPN has been checked for all known viruses by KPN IV-Scan, powered by MessageLabs.
For further information visit: http://www.veiliginternet.nl
_____________________________________________________________________________________________
More information about the SAP-WUG
mailing list