Moving Transports from one client to another

[Former Member]

As part of refresh I created a new client and refreshed it from production, as to move transports from old client in development to newly created refresh client, I noticed below mentioned two transports which was created while applying sap note and new client creation, is it ok to move them to new client?

Transports:

Note-1685091 Executionerror:appliancecontrol get-bladecente

New Client creation : TBDLS & TBDLST tables.

[Matt_Fraser]

Syed,

This question is rather confusing. So, I presume this is not an Enterprise Search system, but you were receiving the error described in Note 1685091 while conducting a license audit? Anyway, it's not clear why applying this Note would create a transport containing tables TBDLS and TBDLST. It's not clear what would add those tables to a transport, really.

You say the transport (containing the TBDLS tables?) was created during new client creation, but this sounds odd to me too. Usually after a client copy or system refresh, these tables are automatically post-processed to update the logical system names for your landscape. Or you can manually manage or adapt logical system names with transaction BDLS.

So how are you performing this refresh? Is it really a client copy, or is it a system copy? Is it a new client in an existing instance, or is it a new system? Are you using SCCL or SCC9 to perform the copy, or SWPM? If it's a client copy and not a system copy, then I don't think you'd want to do anything with these tables, as they are client-independent. There's probably no harm in importing the transport; it's just confusing why it exists in the first place.

FYI, I adjusted the tags on your question (as I did with your last question; please be careful and judicious with your tag selection).

Cheers,
Matt