Setting to save changes to org. model PPOME??

[Wilbert Mulleners]

Robert,

The named setting in OOTR is a one-time change which you have to transport.
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.

You do not need to make a change to the settings in SCC4, that would not be
appreciated at all.
Unlike the message you are not allowed to, changes are saved! The setting in
OOTR is of no relevance here.

Regards,
Wilbert Mulleners

2010/11/9 Robert van den Berg <wug at bergtop-ict.nl>

>  Wilbert,
>
>
>
> thanx for the info! Very usefull!
>
>
>
> 1 question: we have the setting in OOCR with a space. We don't have the
> entry in OOTR. Does this make it possible to save the assignment of users to
> positions or do I have to change a setting in SCC4?
>
>
>
> Kind regards,
>
> Robert
>
> On Nov 9, 2010 11:36 "Wilbert Mulleners" <w.mulleners at pyramid.nl><w.mulleners at pyramid.nl>wrote:
>
> What we usually want to achieve and do implement is:
> - maintain structure (organizational units, positions, ...) on Devl system
> and transport to QAss/Prod system
> - 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
>
> How to configure this:
> - Transaction *OOCR *(PD Transport Connection)
> TRSP CORR should be set to space (= Automatic Transport)
> so all changes have to be included in a request
> - Transaction *OOTR* (Transport Lock for Infotypes/Subtypes)
> Include an entry for Object type S (Position) Infotype 1001 (Relations)
> Subtype A008 (Holder)
> so assignments of users/holders are skipped when the request is imported on
> a QA/Prod system
>
> 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).
>
> Regards,
> Wilbert Mulleners
>
> 2010/11/9 Gavin Mooney <gavinmooney at gmail.com>
>
>>  Hi Robert - I always thought that what you described was a 'feature'
>> that SAP let us get away with and not enabled by any configuration setting.
>> I'd be interested to hear of this has been tightened up now.
>>
>> Gavin
>>
>> Sent from my iPhone
>>
>> On 09/11/2010, at 19:59, "Robert van den Berg " <wug at bergtop-ict.nl>
>> wrote:
>>
>>   Hi all,
>>
>>
>>
>> a very basic question perhaps but I can't find it....
>>
>>
>>
>> When we want to change something in de organizational model (using
>> transaction PPOME) on a productive system, we get a message that no change
>> is allowed. But when we change something and save it, the change is still
>> saved. Works strange but fine.
>>
>>
>>
>> Now, we have implemented some suppport packages (SP stack 18) and we now
>> can no longer save the changes.
>>
>>
>>
>> Does anyone know where this setting can be changes so we can edit the
>> organizational model in a productive system wihtout transports?
>>
>>
>>
>> Kind regards,
>>
>> Robert
>>
>>  _______________________________________________
>> SAP-WUG mailing list
>> SAP-WUG at mit.edu
>> http://mailman.mit.edu/mailman/listinfo/sap-wug
>>
>>
>> _______________________________________________
>> SAP-WUG mailing list
>> SAP-WUG at mit.edu
>> http://mailman.mit.edu/mailman/listinfo/sap-wug
>>
>>
>
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20101109/35dcf3af/attachment.htm