Skip to Content

SLT Replication due to a client copy

Hello, experts.

I would like to know if there is any Best Practice to manage SLT when a source system gets refreshed from its productive system. Out company refreshes our R/3 QA system quarterly to conduct integration testing. We have SLT QA system that gets feeds from the R/3 QA system. We have already done the initial load and have kept SLT QA with replication status. Our testers were entering test data into the R/3 QA system and then fresh new data comes in due to the client copy. Then they start entering another new set of test data. We have HR data and they may have created new SAP personnel numbers by hiring, transferring, etc., which get wiped out by the client copy. We will lose the personnel numbers and/or have the numbers that are assigned to totally someone else. Would SLT be able to capture all this using Replication? Or should we start it over by dropping all the data? I raised an OSS message and asked the same question but was told that there is no Best Practice for this.

I would like to hear approaches taken by other SAP clients. Can any of you please share your experience?

Thank you for reading my question. I would be very grateful if I get some answers.



Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • May 15, 2018 at 07:07 PM
    Add comment
    10|10000 characters needed characters exceeded