<div>What we usually want to achieve and do implement is: <br>- maintain structure (organizational units, positions, ...) on Devl system and transport to QAss/Prod system <br>- assign users/holders to positions on each system/client since not all the users are created throughout the system landscape plus we do not want to overwrite these assignments by transport requests <br>
<br>How to configure this: <br>- Transaction OOCR (PD Transport Connection) <br>TRSP CORR should be set to space (= Automatic Transport) <br>so all changes have to be included in a request <br>- Transaction OOTR (Transport Lock for Infotypes/Subtypes) <br>
Include an entry for Object type S (Position) Infotype 1001 (Relations) Subtype A008 (Holder) <br>so assignments of users/holders are skipped when the request is imported on a QA/Prod system <br> <br>When you assign users on a non-customizing client, indeed you get a message that changes are not allowed. This is not consistent to the settings but the assignments are saved (and they should). <br>
</div>
<div>The named setting in OOTR is a one-time change which you have to transport. <br>When importing any subsequent transports with changes to Organizational Management, the assignment of users/holders to positions are skipped, that is, existing assignments of these kind are not overwritten. <br>
<br>You do not need to make a change to the settings in SCC4, that would not be appreciated at all. <br>Unlike the message you are not allowed to, changes are saved! The setting in OOTR is of no relevance here. </div>
<div><br>Regards, <br>Wilbert Mulleners<br><br></div>
<div class="gmail_quote">2011/6/8 Mad ABAPper <span dir="ltr"><<a href="mailto:madabapper@gmail.com" target="_blank">madabapper@gmail.com</a>></span><br>
<blockquote style="BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex; PADDING-LEFT: 1ex" class="gmail_quote">
<div>Greetings,</div>
<div> </div>
<div>We are on ECC 6, and recently installed service pack 8 which is preventing us from being able to maintain position assignments in our non-development boxes. There are several OSS notes pertaining to this topic (163897, 33582, 208746, 1574023). However, if we update DB Table T77S0 (key TRSP CORR) with 'X' as described in OSS 163897, we also allow for the creation of new organizational objects. On this project, all organization objects get created in development, and transported through the landscape. However, we must be able to maintain assignments (primarily between Position and Users) in our non-development boxes. Any thoughts are appreciated.</div>
<div> </div>
<div>MadABAPper</div><br>_______________________________________________<br>SAP-WUG mailing list<br><a href="mailto:SAP-WUG@mit.edu" target="_blank">SAP-WUG@mit.edu</a><br><a href="http://mailman.mit.edu/mailman/listinfo/sap-wug" target="_blank">http://mailman.mit.edu/mailman/listinfo/sap-wug</a><br>
<br></blockquote></div><br>