Data Consistency when Copying/ Refreshing ECC 6.0 and SRM-SUS 5.0 Systems

Question

Hello,
We are planning a refresh / system copy of an ECC 6.0 and SRM-SUS 5.0 system
The refreshes will be completed from backups taken of production systems refreshed onto the QA Landscape.
I have referenced the following SDN thread that provides some guidelines on how to refresh R/3 and SRM systems and maintain data consistency between the systems using BDLS and changing entries that correspond to backend RFC destinations:
[Is there a process/program  to update tables/data after System Refresh?;
This thread is fairly old and relates to earlier versions of R/3 (4.7) and SRM (3.0).  We have heard that at higher system versions there may be technical reasons why a refresh canu2019t be performed.
Does anyone have experience of completing successful refreshes of landscape that contain ECC and SRM systems at higher SAP versions (ideally ECC 6.0 and SRM-SUS 5.0)  Does anyone know whether it is technically possible?
Are there any additional steps that we need to be aware of at these higher SAP versions in completing the copy to ensure that the data remains consistent between ECC and SRM?
Thanks
Frances

Answer 1

I have seen this somewhere in the forum: See if this helps you
BDLS: Convertion of logical system (SRM).
Check entry in table TWPURLSVR.
Check RFC connections (R/3 and SRM)
SPRO, check or set the following points:
Set up Distribution Model and distribute it
Define backend system
Define backend sytem per product category
Setting for vendor synchronization
Numbe ranges
Define object in backend sytem
Define external services (catalogs)
Check WF customizing: SWU3, settings for tasks
SICF: maintain the service BBPSTART, SAPCONNECT
SE38:
Run SIAC_PUBLISH_ALL_INTERNAL
Run BBP_LOCATIONS_GET_ALL
Update vendor BBPUPDVD
Check Middleware if used.
Run BBP_GET_EXRATE.
Schedule jobs (bbp_get_status2, clean_reqreq_up)
Convert attributes with RHOM_ATTRIBUTE_REPLACE