System refresh
System refresh (system copy)
Also known as: system copy, BDLS
Copying production data into a test or quality system. The copy has to be isolated before it is released, or it acts like production.
After a copy, the target still carries production settings: RFC destinations (SM59) that point to production, logical system names that must be converted with BDLS, outbound mail in SCOT, production printers in SPAD and released background jobs.
Post-copy steps isolate the system: convert logical systems, re-point or lock RFC destinations, redirect or stop outbound mail, suspend released jobs and re-point output devices to test devices.
In ERP Preflight
System Refresh Delta Guard checks the extracts of the copied system and reports every setting that still points to or acts like production.
Problems that involve System refresh
- CriticalSensitive production jobs released in the copy
- CriticalLogical system names not converted (BDLS)
- CriticalRFC destinations still point to production
- BlockerExtract SID differs from the refreshed target SID
- CriticalqRFC / bgRFC queues hold copied entries
- CriticalOutbound mail active without redirection
- MajorSelected custom configuration overwritten by the copy
- MajorSystem-specific endpoint URLs overwritten by the copy
Related terms
Free tools
- Knowledge & error search
Search the reviewed knowledge base, SAP objects and the finding codes of the analysis engines.
Written for ERP Preflight · reviewed September 27, 2026
All glossary termsERP Preflight is independent and not affiliated with SAP SE. SAP, ABAP, Fiori and S/4HANA are trademarks of SAP SE.