Showing results for 
Search instead for 
Did you mean: 

SLT refresh/system copy

Former Member
0 Kudos


We would be going for a SLT refersh from production to Acceptance.

Please do share any documents related to this.



Accepted Solutions (1)

Accepted Solutions (1)


Hi Rajiv,

Early last year I discussed with my customer approaches how such a refresh could be realized and what needs to be considered.

I can share my thoughts with you, however I have to emphasize that we never tested the procedures in detail. And in nowadays versions of SLT some transactions might be different.

So please keep them as a hint but not as a guideline.

How-to refresh QAS from PRD in SLT scenario?


Production landscape consist of ERP-system PRD, with replication to HANA-database HAP via SLT-server SLP

Quality landscape consist of ERP-system QAS, with replication to HANA-database HAQ via SLT-server SLQ


QAS system should be refreshed with recent PRD data


A.      Refresh QAS from PRD, clean HAQ, repeat replication

B.      Refresh QAS from PRD, HAQ from HAP and SLQ from SLP

A. Detailed steps for approach A: Refresh + repeat replication

** not tested **

1.       Backup PRD

2.       Stop the master replication job in HAQ (transaction LTR -> jobs tab -> Edit -> Stop)

3.       Refresh QAS from ERP backup

4.       Clean up old replication

a.       Delete old configuration in HAQ (transaction LTR)

b.      Delete triggers in refreshed QAS system

i.      Call transaction IUUC_REMOTE à Expert Functions à Delete Triggers à Enter the names of the replicated tables à Execute

If step i. is successful, continue with step c., otherwise go on with next step ii.-iv.

ii.      Determine all triggers

iii.      Execute function module DB_DROP_TRIG in transaction SE37 for every trigger (specify EXEC  = X, TABNAME = tabname and TRIG_NAME = trigger name)

iv.      Verify that no triggers remain

Alternative: You can also write a sqlscript for all tables/triggers and run it on db level

c.       Delete logging tables in refreshed QAS system:

d.      List all logging tables: transaction SE11, enter /1CADMC/* à press F4 key; then copy the logging table names to notepad; copy all names into the clipboard

i.      Call transaction IUUC_REMOTE à Expert Functions à Delete Logging Tables à copy the trigger names from clipboard to the input selection à Execute

ii.      Verify that all logging tables have been deleted (as in i.). It seems that the logging tables for DD02L and DD02T will still exist; in this case drop the two logging tables in DB level.

e.      Cleanup SLT server HAQ:

i.      IUUC_REPL_CONFIG:                  Should be empty

ii.      IUUC_REPL_CONPAR:                 Should be empty

iii.      IUUC_REPL_HDR                           Should be empty

iv.      IUUC_REPL_MAP                          Should be empty

v.      IUUC_RS_STATUS                         Should be empty

vi.      IUUC_RS_ORDER                           Should be empty

vii.      IUUC_TABLES                                  Should be empty

viii.      DMC_COBJ                                       Should be empty

ix.      DMC_MT_TABLES                         Should be empty

x.      IUUC_LOGTAB_ID                         Will be filled, so delete the entries with transaction SE16

xi.      DMC_STRUC_ID                             Will be filled, so delete the entries with transaction SE16

xii.      DMC_ACT_REC                                              Will be filled, so delete the entries with transaction SE16

xiii.      Run report DMC_CLEANUP_USAGE in transaction SE38 with flag ‘delete all kinds of zombies’

xiv.      Run report DMC_CLEANUP_USAGE in transaction SE38 with flag ‘delete all kinds of zombies’ and subproject = ZIUUC_<MTID> with <MTID> is the name of the mass transfer id of the configuration

xv.      DMC_MT_HEADER                       Will be filled, so delete the entries with transaction SE16

f.        HANA Studio connect with SYSTEM user to HAQ, go to Catalog > Authorization > Users and delete the user of the replication (cascade option)

5.       Setup new configuration in SLQ

a.       Check RFC connection in transaction SM59 from SLQ to QAS

b.      Transaction LTR: Create new configuration

c.       In the studio, check schema created in HAQ

d.      In the studio, data provisioning, verify that tables DD02L, DD02T and DD08L are replicated

e.      Prepare a text file with all tables to be replicated

f.        In the studio, data provisioning, load the text file and add the tables to the replication

B. Detailed steps for approach B: Consistent Refresh all Systems

** not tested **

1.       Backup all systems

a.      Stop the master replication job in HAP (transaction LTR -> jobs tab -> Edit -> Stop)

b.      Backup first PRD, then HAP and finally SLP

c.       Start the master replication job in HAP again (transaction LTR)

2.       Refresh QAS from ERP backup, no BDLS

3.       Refresh HAQ from HAP backup

4.       Refresh SLQ from SLP backup

5.       Adapt SLT configuration, i.e. RFC connection to QAS  in SLQ

6.       Adopt hana server name in SLT configuration(/LTR), can be done inside db connection to HANA(/DBCO)

7.       Update table “SYS_REPL”.”RS_REPLICATION_COMPONENTS” in hana and change the server name and configuration for the SLT replications.

8.       Start the master replication job in HAQ again (transaction LTR)

9.       Run BDLS in QAS to change logical system name (SLT will replicate the changes to HANA)


Answers (1)

Answers (1)

Former Member
0 Kudos

Thanks Udo  for the detailed was very helpful..

Former Member
0 Kudos

@Rajiv did you implement the solution?

And did you see that there exists now a new document from SAP:

Resuming Replication Without Initial Load After System Refresh or OS/DB