Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 

Relocations in SE01, SE09, SE10

arunkumar_vr
Participant
0 Kudos

Hi All,

There is an option RELOCATIONS in the tcodes SE01, SE09 and SE10 (Transport Organizer). Please provide information regarding this option.

1 ACCEPTED SOLUTION

Former Member
0 Kudos

This option is similar to "Transport of Copies".

Generally if you want to move your objects from one system to another (outside your landscape) then you create a Transport of Copies and import it in the other system. This option still retails the original system as the source for modification of the objects.

In the case of Relocations the original system is changed to target system for modification of objects.

- Cheers

4 REPLIES 4

Former Member
0 Kudos

This option is similar to "Transport of Copies".

Generally if you want to move your objects from one system to another (outside your landscape) then you create a Transport of Copies and import it in the other system. This option still retails the original system as the source for modification of the objects.

In the case of Relocations the original system is changed to target system for modification of objects.

- Cheers

0 Kudos

Hi Prakash/ Michael,

Thank you very much for the information. I have got the idea of Relocations, but want some more clarification. In such cases where we need to change the origincal system, what I usually do is to change the original system manually through the CHANGE OBJECT DIRECTORY ENTRIES option in SE03. Now, through RELOCATIONS would I be able to avaoid the above procedure?

Arun

Message was edited by:

Arun Kumar V. R.

former_member589029
Active Contributor
0 Kudos

Hello Arun,

Basically every object in a SAP system has a 'source' system where the original version of the object is held. You can only change that object in the original system. This is supposed to prevent that object from being changed in two different systems.

E.g. You have systems XX1 and XX2. Both systems transport into XY1.

If you would be allowed to change a certain object in XX1 AND XX2 changes done in the object in XX2 will overwrite changes made to the object in XX1 if the change from XX2 is transported after the one from XX1.

To avoid this an object has a source system and only there the original can be changed. If you want to transfer the original from one system to another, then you would use a relocation.

In the above example assumed that the original of the object is XX1, but for whatever reason you want the original of that object to be in XX2 you would have to relocate that object from XX1 to XX2 which would overwrite the XX2 version with the XX1 version and sets the original of the object to XX2.

Hope that helps,

Michael

Former Member
0 Kudos

Yes. If you use relocations you can avoid adjusting the transport layer.

- Cheers