SAP Basis System Copy

You are an SAP Basis administrator performing system and client copies for landscape management in an SAP environment.

What to check first

• Verify source system is in a consistent state: Run DB13 transaction to check backup status and SM51 to confirm no active work processes
• Confirm target system has sufficient disk space: Check CCMS monitoring or OS-level df -h / du -sh commands
• Review SAPSYSTEMNAME in /usr/sap/sapservices (Linux) or Registry (Windows) to identify system identifiers

Steps

1. Create full backup of source system using BRTOOLS or DB13 (SE01 for transport logs) and verify backup completion in system logs
2. Execute BRRESTORE to restore source backup to target system hardware, specifying correct instance number and SID mapping
3. Run post-restore ADDNEWHOST procedure via JSPM (Java System Provisioning Manager) or execute sap<SID>adm database initialization scripts
4. Login to target system with SAP* credentials and execute SCC1 (System Copy) to update system tables (SAPSYSTEM, DBCONNECTIONS)
5. For client copy within same system: Navigate to SCC1 transaction → Source Client → Select Copy Mode (Profile/Customizing/Complete) → Execute asynchronously via SM37
6. Update RFC destinations in SM59 to point correct application servers; regenerate sapgenpse certificates if cross-system copy involves security updates
7. Execute RSPO0041 batch job (spool cleanup) and RSPARAM to synchronize instance profiles across target landscape
8. Validate system via STMS (Transport Management System) to verify client isolation and transport routes reflect new landscape topology

Code

*&---------------------------------------------------------------------*
*& Report for SAP System and Client Copy Validation
*&---------------------------------------------------------------------*

REPORT ZSD_SYSTEM_COPY_VALIDATION.

DATA: lv_sysid TYPE sy-sysid,
      lv_client TYPE sy-mandt,
      lv_source_system TYPE rfcdes-rfcdest,
      lv_target_system TYPE rfcdes-rfcdest,
      lt_db_connections TYPE TABLE OF dbcon,
      ls_db_connection TYPE dbcon,
      lv_copy_status TYPE c,
      lv_error_msg TYPE string.

TABLES: sscrfields, t000, usobt, usobj.

SELECTION-SCREEN BEGIN OF BLOCK b1 WITH FRAME TITLE TEXT-001.
PARAMETERS: p_src_sys TYPE rfcdes-rfcdest OBLIGATORY,
            p_tgt_sys TYPE rfcdes-rfcdest OBLIGATORY,
            p_copy_mode TYPE c DEFAULT '1' AS LISTBOX
              VISIBLE LENGTH 15 USER-COMMAND cm.
SELECTION-SCREEN END OF BLOCK b1.

AT

Note: this example was truncated in the source. See the GitHub repo for the latest full version.

Common Pitfalls

• Treating this skill as a one-shot solution — most workflows need iteration and verification
• Skipping the verification steps — you don't know it worked until you measure
• Applying this skill without understanding the underlying problem — read the related docs first

When NOT to Use This Skill

• When a simpler manual approach would take less than 10 minutes
• On critical production systems without testing in staging first
• When you don't have permission or authorization to make these changes

How to Verify It Worked

• Run the verification steps documented above
• Compare the output against your expected baseline
• Check logs for any warnings or errors — silent failures are the worst kind

Production Considerations

• Test in staging before deploying to production
• Have a rollback plan — every change should be reversible
• Monitor the affected systems for at least 24 hours after the change