Copy and import unreleased transports across systems

[Former Member]

Hello TMS Experts,

I would like some advice.

We have the usual Dev>QA>Prod landscape and a transport route

between these systems. We want to introduce a new system that will allow us to

carry out secure testing, separate from the Dev and QA environments. We

want to be able to transport objects, from Workbench and Customising

transports, from the Dev system into this new secure system WITHOUT releasing the

transports from Dev. Can you suggest a way that this can be done?

Ideally, we would want to specify a list of unreleased transport

numbers, and have the contents of these transports imported or copied into the new

system (in much the same way that SCC1 allows you to copy unreleased transports

across clients in the same system).

We have quite a lot of experience and knowledge relating to TMS, but

cannot think of a simple way of achieving this. Do you have any

suggestions?

Thanks for your help.

Derek Wood.

[Former Member]

Create a transport of copies, design specifically for this purpose.

[jason_oriordan]

Hello Derek,

I am afraid what you ask is not possible. You will have to export the change request as upon export

the data file is created. As you are already aware SCC1 is only to copy client dependent data from one client to the next in the same system. This allows you to copy a change request from one client to the next without a release.

Can I ask why you do not wish to export from DEV ? Is it because you only want to export to QAS ? If that is the only reason you could use a transport of copies. You can copy the object list from your DEVKxxxxxx request over to the transport of copies and release that. I know it still involves a release but it will mean your DEVKxxxxxx requests will be seperate and kept soley for export to QAS. You can release the transport of copies to the secure system. It does not even have to be part of your transport routes.

Alternatively you could add the secure system to the transport route but have it in parallel to QAS

DEV -> QAS -PRD

-> SEC

SEC is the secure system. So as to be able to transport both SAP objects and Z objects within the customer namespace I would suggest using a transport group as your consolidation route.

If I can be of any further help do not hesitate to reply to the thread.

Regards,

Jason (SAP CTS)

[Former Member]

Thanks Jason,

I was afraid that it might not be possible.

Ideally, we wanted to ensure that testing was complete in both DEV and SEC systems before releasing the transports from DEV. It looks like the only way we can do this is with the transport of copies method that you suggest.

Regards,

Derek