Assignment of SAP org. objects to positions on production?

[Soady, Phil]

Please be careful if you decide to create objects in DEV and transport them to production.
The most critical point is number ranges.
BE SURE to get the number ranges reset in production.
Ie make sure any objects created in production have a different number range to DEV.
 
The settings controlling whether PD objects created in DEV should be captured in transports or not is in TABLE T77s0.
See the section under TRSP for transport.
 
Option 2 is to use ALE to send objects from PRODUCTION back to DEV.
This is method I suggest normally. Means that a PRD system needs to be there. This may not be the case in a build scenario.
 
Option 3. A once ALE of HR objects to PRD. (TRANS may be easier if it is one off, and dangerous if left in place too long.)
 
The extra links you refer to are best only be maintained on PRD.
 
If possible create all the master data in PRD directly.
 
There is no fundamental reason why this can't happen weeks before go live, as soon as the system is available. Only project related issues could block this approach.
 
Note if you send an Object, say position from DEV to PRD, and if it
exists, it will be replaced along with relationships.
 
 
If you want dev and prd to have the same org structure,
and this is often the push behind the scenes,
then create the org structure in PRD and ALE it back to DEV.
 
See the Help CD under ALE business processes and the quick start guide to ALE.
 
Using BD64 to define a message HRMD_A from PRD to DEV.
BD64 to transfer model to DEV, BD64 to generate the profile in both
systems and the fire up transaction PFAL. Hey presto ! Org structure
is available on DEV.
 
One word of advice.
The org structure is the one of the most important master data and organisation disciplines you can introduce.
Get some input/help regarding this process if you are unfamiliar with it.  Workflow is a good way of highlighting a poorly constructed or non
representative org structure. The workflow administrator will kill
someone if the org structure is not accurate or poorly constructed or
not a true reflection of how the business is structured.
 
 
 
hth
 
 
 
 
Phil Soady
Senior Consultant
Business Technologies
SAP Australia
* : 0412 213 079
* : phil.soady at sap.com
 
 
 
 
-----Original Message-----
From: Kouw, FA - SPLTC [mailto:fa.kouw at td.klm.com]
Sent: Tuesday, 14 January 2003 2:28 AM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Assignment of SAP org. objects to positions on production?
 
Hello,
 
I tried to determine the best approach for our situation regarding the
transporting of the organizational plan. At the moment I have chosen for
the following:
 
   * we will set up our organizational plan (organizational units and
     jobs, nothing else) in the development client, and transport this
     to production using the standard transport mechanism
   * on production we create positions and users, and assign users and
     jobs to positions (normally one user per position)
 
Can someone tell me how to handle the assignment of SAP organizational
objects in this situation: we have some purchasing groups, for which I
think each position created (on production) must be linked to the
respective SAP organizational object. Can/should this be done on the
production system also (if positions are created there I have to....)?
Or should I use another approach, f.i. creating these positions on
development and assign the SAP org. objects to them there? All help is
welcome!
 
Regards,
 
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
_____________________________________________________________________________________________