Transport requests

[Former Member]

Hi Everyone ,

1.Can anybody tell me what is the difference in transactions se09 and se10.

2.Also what is the role of "package" assignment while creating a TR.

3.What care should be taken while deleting/changing ownership of any TR.

4.What is TR dependency?

I have come across all these thingswhile working but dont know the real meaning of each.

Points for well explained answers.

[Former Member]

Hi Everyone ,

1.Can anybody tell me what is the difference in transactions se09 and se10.

2.Also what is the role of "package" assignment while creating a TR.

3.What care should be taken while deleting/changing ownership of any TR.

4.What is TR dependency?

I have come across all these thingswhile working but dont know the real meaning of each.

Points for well explained answers.

[Former Member]

Hi!

1. Nothing, both transactions are calling the same program.

2. It is just a logical grouping for transports. Mostly there are groups for SAP modules, like ZMM, ZPM, ZSD, ZFI, etc...

3. TR has to be NOT enabled, else you can't change it.

4. What do you mean on it?

Regards

Tamá

[Former Member]

Hi Tamas,

I mean if any program is a global program and some TR is already created on it .Should we create a new TR for our set of changes? Is there any dependency of the existing TR on the New TR when it comes to releasing the two.Which should be released first?

[Former Member]

Hi,

1) There is no difference.

2) The package determines to what systems the TR is meant to be transported.

3) I never had any problem while doing this.

4) If related objects have been modified using different TRs, you should transport them in a certain order or the transport will fail. For example : a program uses many includes. You declare a new data in the TOP include and store your modification in a TR, then you modify another include using this new data and store the modification in another TR.

When you transport your modifications, you have to check that the TR concerning the TOP include is transported first cause if you don't, SAP will try to modify and activate the other include and will fail because the new data will not be declared in the TOP include.

When using a single TR, SAP will automatically handle the order in which objects have to be activated.

Also, the order in which you release your TRs does not matter.

Hope this helps.

Regards,

Nicolas.

[former_member404244]

Hi,

1.Can anybody tell me what is the difference in transactions se09 and se10.

ans->there is no such difference between the two tcodes.

2.Also what is the role of "package" assignment while creating a TR.

ans->logical grouping of elements...we bunch all the corresponding /relative elements under one package and under on TR.

3.What care should be taken while deleting/changing ownership of any TR.

ans->U can directly change the owner by right clicking on the transport reauest and press on change owner,now ucan change the owner....if u think that u don't need the TR to go to next system say quality after development,u can directly delete it,but in some cases u may need authorization...while changing the owner u need to takecare the correct userid and the correct person responsible.

4.What is TR dependency?

ans ->If you use projects to control your transports, but your projects overlap, then you must define dependency relationships between the objects that belong to different projects but contain some of the same objects.

When you import requests, the system analyzes the dependency relationships and lets the transport administrator know that more requests have to be imported to ensure the correct sequence. This is just a warning though, and the import can be continued.

When you release a request, the system automatically checks whether the request's object list overlaps with the object lists of released requests from other projects that have already been released.

If requests do contain the same object, the system identifies which requests the object was transported in. A dialog box proposes these requests as predecessors of the current request.

You can also edit the dependency information of a request yourself, and add predecessor and successor relationships independently of the system proposals. You can also create circular relationships, meaning that the requests have to be imported together.

To do this, go to the request overview in the Transport Organizer and choose Goto ® Dependency information.

reward points if u find useful.

regards,

Nagaraj