Managing transports across multiple test clients

[Former Member]

With TDMS, we are able to quickly create new clients in our test environment.  Our management is looking to use TDMS to create new clients on a fairly regular basis (we might end up with a production support test client, and individual clients for each of our major projects).  My major concern with this strategy is how we can manage transports.  It is possible that we would only want certain transports sent to specific clients for testing (because functionality for different projects could impact the same object, and cause issues with our testing).  Are there any best practices on managing transports in this setup?  Obviously, we need to be sure we don't miss transports, or cause issues with transport order, etc.

Any thoughts or feedback you can provide would be greatly appreciated.

Thanks,

Dan

[Former Member · Accepted solution]

Hi,

This is not really a TDMS topic as it is mainly related to the setup of your Transport landscape.

As long as your tranports only contain client dependent customizing or workbench requests that do no changes on DDIC level you are ok and can copy these transports to the other clients that are not currently refreshed (this requires for sure manual overhead!)

Any client dependend transport into the receiver client will most likely have a negative impact on your current run. The same is true for any ddic change (-> This will invalidate the related conversion object -> with the automatic repair this can be repaired but will increase the overall runtime of the run.)

Best Regards

Joerg

[Former Member]

Hi Daniel,

You can use TDMS System Shell creation method for this.

Depending on your requirements, you can use one of the following types of shells:

Save shell: A save shell is a simple backup of the system shell created in preparation to an SAP TDMS implementation. When a new system is built up using a save shell, all transports that have gone into the related sender system after creation of the backup must be imported to the shell.

Master shell: A master shell is also created as a copy of the original system shell. However it is included in the transport chain and receives all transports that go into the production system. As a consequence, it always reflects the current status of the DDIC and cross-client information in the production system, and no additional transports are required when a new system is to be created based on the master shell.

Thanks,

Ravi