ECC, SLT Replication, HANA System Copy Process (System Refresh)

[former_member188886]

Is there a best practice for a System Copy Process from production to a test systems when using ECC, SLT Replication & HANA?

Use case:

- 2 ECC sytems, using 1 SLT sytem, replicating to 1 HANA Database.

>>Replication user/schema is same in prod & test, as is the secondary DB connections.

>>One ECC using CO-PA Accelerator with alternate SLT replication to HDB.

>>Second ECC using SLT repllciation for SD tables to HDB.

>>ECC systems are copied back at different times (North America & International).

- Data Services loading HDB with non-sap data.

Would we System copy the SLT (and export only table entries that apply to the ECC system that was copied back)?

Or NOT copy the SLT, & adjust entreis in the Copied ECC system?

Also, would we have to Export the HDB ECC user/Schema from Prod HDB to Test HDB?

And if so, are there other HDB table entreis that would also need to be exported from prod HDB & imported into the Test HDB?

(SYS.REPL.RS_REPLICATION_COMPONENTS, <replication User>/RS_STATUS, etc)

We are tyring to avoid doing an initial replication to re-load of all the ECC data in replication status.

Thanks for any input.

Jay

[rindia]

Hi Jay,

My inputs are:

1. If you want to use Data services(BODS) tool for loading the non-sap data into HANA then the same BODS tool can be used to load data from ECC too.

It is very powerful tool and co do much complex transformations before loading the data into HANA.

There are some limitations in SLT for doing transformations and BODS is good substitute for SLT,

means we can avoid using SLT itself.

Regards

Raj