SAP system refresh checklist: BDLS logical system conversion and RFC outbound isolation

The risk of a system copy from production

When a quality assurance (QA) or sandbox system is refreshed with a database copy of production, the refreshed system initially contains production configuration: production RFC destinations, partner profiles, email servers, printer definitions, batch jobs and logical system names.

If outbound communication is not isolated before background processing resumes, the refreshed QA system can accidentally send test orders, IDocs or payment files to live external partners or production SAP systems.

Essential post-refresh verification steps

1. Logical system conversion (BDLS). Convert references from the production logical system name to the QA logical system name across client-dependent and cross-client tables.
2. RFC destination and partner profile isolation (SM59, WE20, WE21). Ensure no RFC destination or transactional port in QA still points to a production host or gateway.
3. Output and mail server redirection (SCOT, SPAD). Restrict or redirect outbound SMTP mail nodes, HTTP destinations and physical print queues so test outputs cannot reach real customers or vendors.
4. Batch job and inbound queue verification (SM37, SMQ1, SMQ2). Keep released production batch jobs suspended until delta configuration is restored, and clear lingering production qRFC/tRFC queues.

How to audit refresh readiness automatically

Compare an export of the target system's pre-refresh baseline (RFC destinations, logical systems, partner profiles, SCOT settings) with the post-refresh state before opening the system to users or releasing background jobs.

ERP Preflight's System Refresh Delta Guard compares pre- and post-refresh configuration exports and flags residual production endpoints and unconverted logical systems with exact artifact evidence. See Operations.