SAP System Refresh Activity – Overview & Steps
🔹 What is an SAP System Refresh?
SAP System Refresh is the process of copying data from a production system (PRD) to a
quality (QAS) or development (DEV) system to ensure testing, development, and
training environments have up-to-date data.
It is commonly performed for:
✅ Testing new developments with real-time data
✅ Performance testing before go-live
✅ Resolving data inconsistencies in non-production environments
✅ Training and user acceptance testing (UAT)
🔹 SAP System Refresh Steps (End-to-End Process)
The SAP refresh process consists of pre-refresh, execution, and post-refresh steps.
🔹 1. Pre-Refresh Activities (Before Starting the Refresh)
✅ Step 1: Inform Business Users & Take Approvals
• Notify functional teams and key users about downtime.
• Obtain approvals from business owners.
✅ Step 2: Backup the Target System (QAS/DEV)
• Take a full database backup of the target system in case of rollback.
• Run:
brbackup -c force -d disk -t online
• Take a SAP profile backup (/usr/sap/<SID>/SYS/profile/).
• Backup spool requests and table contents if needed.
✅ Step 3: Stop Background Jobs in Target System
Run Transaction Code SM37:
• Select Active Jobs → Click Cancel Active Jobs.
✅ Step 4: Export RFC Connections from Target System
Run:
SAP GUI → Transaction `SM59`
• Export all RFC connections (for re-import after refresh).
✅ Step 5: Lock Users (Except SAP Basis Team)
Run Transaction SU10:
• Select all users except Basis team.
• Lock using EWZ5 or:
UPDATE USR02 SET UFLAG=64 WHERE MANDT=100 AND BNAME NOT IN ('BASIS_USER');
✅ Only SAP Basis team should have access before refresh.
🔹 2. Execution Phase (Performing the Refresh)
✅ Step 6: Take Database Backup of Production (Source System)
• Take a full online backup from the production system.
• Run:
brbackup -c force -d disk -t online
✅ Step 7: Restore Production Backup on Target System
• Stop SAP on the target system:
stopsap all
• Restore database from PRD backup:
brrestore -m full -b <Backup_File> -d disk
• Once restore completes, start SAP services:
startsap all
✅ Step 8: Perform System-Specific Configuration
After the database is restored, modify configurations:
1. Change System ID (SID)
• Update DEFAULT.PFL to reflect the target system’s SID.
• Run:
chown -R <sid>adm /usr/sap/<SID>/
2. Modify Profile Parameters
• Update Instance Profile:
nano /usr/sap/<SID>/SYS/profile/DEFAULT.PFL
• Change system settings (e.g., SAP Instance Name, Gateway Hostname).
3. Adjust DBSID in Database
• Run:
UPDATE SAPDBA.TAB SET DBID='<NEW_SID>' WHERE DBID='<OLD_SID>';
4. Delete old Transport Requests
• Run:
rm -rf /usr/sap/trans/*
✅ Step 9: Perform Post-Restore Database Cleanup
Run Transaction SE14:
• Check and Activate Database Objects.
• Run:
DB02 → Check & Rebuild Indexes
🔹 3. Post-Refresh Activities (Validations & System Checks)
✅ Step 10: Unlock Users in Target System
• Run Transaction SU10:
• Unlock all users using:
UPDATE USR02 SET UFLAG=0 WHERE MANDT=100;
✅ Step 11: Reconfigure RFC Connections
• Open Transaction SM59.
• Re-import the saved RFCs and adjust system names.
✅ Step 12: Perform Basis System Checks
• Check SAP Application Logs (SM21).
• Verify Work Processes (SM50, SM66).
• Check Database Consistency (DB02).
✅ Step 13: Start Background Jobs
• Open Transaction SM37.
• Restart background jobs stopped before refresh.
✅ Step 14: Inform Users & Business Teams
• Notify business and functional teams to test the refreshed system.
• Validate custom developments, configurations, and workflows.
🚀 Final Checklist
✅ Step Transaction Code / Command
Stop Background Jobs SM37
Backup Source & Target Systems brbackup
Lock Users Before Refresh SU10, EWZ5
Restore PRD Backup on Target brrestore
Change SID & System Configs DEFAULT.PFL
Database Cleanup & Check SE14, DB02
✅ Step Transaction Code / Command
Unlock Users & Restart Jobs SU10, SM37
Reconfigure RFCs SM59
Validate System Health SM21, SM50, SM66
🎯 Conclusion
• System Refresh ensures QA/DEV systems have up-to-date production data.
• The process includes backup, restore, configuration updates, and validation.
• Proper pre-refresh and post-refresh activities ensure smooth operation.
Would you like an automated script for system refresh activities? 🚀
