transport files not available in /trans directory

[Former Member]

Dear Experts,

By mistake, we haven't maintained the target system for transport request (workbench request). Now, this request is released and transport files are not generated in /trans directory.

It is mandatory to maintain the target system for this type of request? Is there a procedure, inorder to have these files in /trans directory?

Thank you for your response.

Best regards,

Sreenu

[mervin_joseph]

Hi Sreenu,

As Martiana suggested ,You can create a "Transport of copies" through tcode SE09/SE10 and include the local request with the target system details. After releasing the newly created request, you will have cofile/data files.

Please find the below link which gives you the step by step procedure to include an object/request from another request:

Including the Object Lists of a Request - Software Logistics - SAP Library

And If you have any more LOCAL request which are not yet released. you can change those Local request into Transportable request by following below steps:

Note: The below steps works only if all your TMS configuration are in place

- Execute tcode SE09/ SE10

- Double click on the request (Local request which is not yet released)

- You will get the below screen, here in properties tab, maintain the target system details in TARGET system input field which I have marked in red and save

then the request will be changed from LOCAL to TRANSPORTABLE request.

I hope this helps you

Best Regards,

Mervin Joseph

[Former Member]

Agreed with Martina. Either you create this request through Transport of Copies else the other way is create a virtual system, if you have only one system in your landscape and define transport route to this virtual system. Then after release data and cofiles will be created in /usr/sap/trans/data and cofile.

[former_member802413]

they are not in /trans

check them in usr/sap/trans/data and usr/sap/trans/cofiles

if you "released" the transport no matter you gave target or not, these files will be generated. Workbench / Customizing does not matter. STMS routes too does not matter.

Only problem will be during import into your target - they may give error as the target system is not mentioned.

[Akshay_G]

This is incorrect what you said

nick mccarthy wrote:

if you "released" the transport no matter you gave target or not, these files will be generated. Workbench / Customizing does not matter. STMS routes too does not matter.

If there is no Target defined and no route, how do you expect the TR to create data/cofiles on releasing the TR? This TR will be treated as Local Transport and no File would be created at all.

Below is a note from SAP's official Documentation. Hope you would agree!

[Martina_Gállego]

Hello Sreenu,

In order to transport your realeased request without target system you can create a request of transport of copies with the target system informed and  include the released request in this new request. After releasing it, you will have cofile/data files.

Best regards,

Martina

[former_member227283]

Hi,

It seems you have not created the target system in STMS.

Best pratice is whenever we install any system, if target system is not decieded yet, we should create the Virtual system and define the transport route to virutal.

By this it will help to assign transport target system automatically when we create any new transport request.

Empty target system is considered local and which is not required for movement to next system.

regards

Anil

[Mofizur]

Hi Sreenu,

If there is no Target system mentioned I believe it will be a LOCAL Change request.For them not data cofiles get created once you release them.

Thanks,

Mofizur