TDMS - Looking for best approach

[Former Member]

Good day.

We're trying to successfully implement TDMS to populate our development system / QA system with 1 year's worth of production data. We are currently using a sandbox with a copy of our dev. system as a playground to validate the data.

Unfortunately, after executing a one year scenario, our Functional Analyst have found the data to be corrupt and unusable. All issues point to 2 major problems:

1) Missing configuration (ex: top level Cost Center S group missing)

2) Missing master data (ex: not all material masters transferred)

We were curious what the proper approach to solving this problem would be?

Here is the approach we took:

1) Copy DEV to a Sandbox.

2) Delete all un-nessassary clients

3) Export main client (100)

4) Import main client (config and user master data only)

5) Execute TDMS Time based reduction for 1 year.

We were curious if we could leverage any of the other package types to potentially resolve our issues.

- Shell Creation: Should this package be executed first?

- Master Data and Customizing: Will the master data from this package be deleted by the Time Based Reduction?

Any help would be greately appreciated.

Thank you,

Charles.

[sourabhshah]

Hello,

TDMS basically transfers the client dependant data and assumes that the repositories of the sender(PRD) and the receiver(QA) systems are same.Repository means that all client independant objects and cross client customizing be the same.

The TDTIM scenario is a time based reduction scenario which transfers the data based on a given period.This package also transfers the master & customizing data along with the sliced transaction data.This package can be executed independantly with out running the TDMDC scenario.

The TDMDC scenario transfers the Master data & Customizing only and not the transaction data.

The TDSHL or shell creation creates an empty repository and makes the system ready for the TDTIM or TDMDC scenarios.However after the shell creation it is necessary that the TDTIM or TDMDC scenario is run to obtain consistancy.

In your case, the material master should have been transferred as a part of the TDTIM/TDMDC package.Check if the conversion object for Material Master table is transferred.If not the trouble shooting provided for TDMS should help you to transfer a conversion object which has failed during migration.

Regards,

Sourabh