SAP TDMS - Ensure Repository between Sender & Receiver

[Former Member]

Dear All,

I've some questions about TDMS prerequisites.

I know that repository consistency between Sender and Receiver need to be checked before performing SAP TDMS scenario.

But my question is, how to ensure consistency between Production System and Quality System?

Repository means workbench and cross client customizing.

So there are usually inconsistencies between production and quality systems.

TDMS does not work if  the two systems are not aligned?

Do we have some recommandations, or best practices to make it happened?

Regards,

Benjamin

[solnegros]

Hi there,

doing TDMS Client copies with one year of production Transaction data into two separate Clients into our development System out of our production System - here I have DDIC differences all the time for sure - TDMS will check this but you can go further on with your TDMS Client copy - thats Advantage against Standard Client copy tool from SAP which will stop when DDIC check have inconsistencies -

with this solution we have much more Options for testings into our development System without having Need to Import transports to next System Level cause of actual production data on Level development System -

We refresh those two Clients one time a year - thats very sufficient and enough in our enviroment - Size of such a Client is approx. 520GB for each approx. 1TB in total plus Standard size of DEV System is 1.3 TB in total -

before that solution we have had a four Level ERP System landscape  DEV  QAS  INT  PRD - now we could eliminate our QAS System with a DB size of approx. 3TB and reduce our maintanance and storage/Backup effort - costs a lot -

and it works

regards

Peter Wegner