Creating a New Transport to Include Objects?

[Former Member]

I created the transport as a workbench request. I figured out how to change the lower tree to type dev/correction.

But when I include objects they always go to the upper tree? Instead of the lower dev/corrections tree? Thank-You.

Message was edited by:

Tom M.

[Former Member]

I created the transport as a workbench request. I figured out how to change the lower tree to type dev/correction.

But when I include objects they always go to the upper tree? Instead of the lower dev/corrections tree? Thank-You.

Message was edited by:

Tom M.

[Former Member]

Hi,

It seems you first create the transport & then assign objects to it. Hence the problem.

Once you assign the objects to the TR, then it will automatically change to Development/Correction.

If the task is still unclassified, then simply right click & DELETE.

Best regards,

Prashant

[Former Member]

I am not understanding the order of steps.

1)I create the transport

2) The lower tree is also created

3)I rename the lower tree to dev/corrections

4)I include, can only do this by selecting the higher tree (main) transport

5)All objects go to upper tree not lower tree

What am I missing? Thank-You

[uwe_schieferstein]

Hello Tom

If you have the authorizations to create transport requests then there is no need to create them in advance. As soon as you create or change an object (assigned package <> '$TMP') the SAP system will automatically display a popup and ask you for an existing request. Alternatively, you can create a new request.

If you create a new request the system automatically adds a task to the request where the objects are collected. The type of the task is set automatically to the correct value (either <i>dev/corrections </i>or <i>Repair</i>).

Regards

Uwe

[Former Member]

I have authorization, I am a developer. These are objects that were on a failed transport I am trying to retransport again. I really am not changing anything. Is it OK to have the objects only in the upper tree?....Thank-You.

Message was edited by:

Tom M.

[uwe_schieferstein]

Hello Tom

When you create a new request and take over the object list of another request (in your case the one of the failed transport) then all objects are added directly to the new transport request (and not into any existing task).

However, this is no problem at all. You can think of request tasks like pockets of a pair of trousers. At the end all objects in the different pockets belong to the trousers.

If your newly created request contains a task with undefined type you can either delete this task or change its type to dev/corrections.

Be aware that if you retransport the objects of the failed transport again (with a new request) the objects may have been changed in the meantime. If somebody else had changed one of the objects and had released the corresponding request you will not see this change yet transport it with your new request.

Regards

Uwe

[Former Member]

OK, Thanks. I was always under the impression their had to be a subordinate tree for the objects to be contained in.....a lower tree. But, now that I know that all objects can be included and tranported in one upper tree transport this clarifies thigs better.....Thank-You All.

[Former Member]

Hi,

Yes that is fine, if the upper tree has all the objects.

Simply delete the lower tree task, if it doesnt have any objects under it.

Best regards,

Prashant