SAP Basis & S/4HANA Integration: Architecture, System Refreshes & DMO

A complete practical guide bridging SAP Basis infrastructure and SAP HANA DBA responsibilities: application-to-database connectivity, homogeneous database system refreshes (PRD to QAS), mandatory post-refresh activities (BDLS, SECSTORE, licenses), and SUM with Database Migration Option (DMO).

IntermediateSAP Basis Integration~20 min studySAP S/4HANA 1909 to 2023+ / NetWeaver 7.5x

Core Learning Objectives

  • 1.Understand how SAP NetWeaver and S/4HANA connect to SAP HANA via SQLDBC.
  • 2.Differentiate Basis operational responsibilities from HANA DBA tasks.
  • 3.Execute an end-to-end Homogeneous Database Refresh from PRD to QAS using backup/restore.
  • 4.Perform mandatory post-refresh configuration: BDLS, SECSTORE, STRUST, and RFC repairs.
  • 5.Understand SUM DMO (Database Migration Option) one-step upgrade and migration.
Prerequisites:hana-architecture-multitenant-mdchana-backup-pitr-catalog

Definition & Architectural Rationale

Technical Definition:

SAP Basis is the administrative middleware layer managing the SAP NetWeaver and ABAP application runtime (work processes, batch scheduling, transport management, RFCs), integrating directly with the underlying SAP HANA in-memory database engine via SQLDBC client libraries.

Why this component exists:

An SAP HANA database never runs in isolation; it powers business applications like SAP S/4HANA ERP, BW/4HANA, or CRM. Senior DBAs must understand application server work processes (DIA, BGD, UPD), system refresh procedures, and cross-tier troubleshooting.

Internal Working & Mechanics

1. Application-to-Database Connection Architecture: - Application servers (PAS/AAS) communicate with SAP HANA using the SAP HANA Client (SQLDBC library). - In SAP S/4HANA, the application server reads /usr/sap/<SID>/SYS/profile/DEFAULT.PFL: dbs/hdb/dbname = <TENANT_NAME> dbs/hdb/server = <hana_host>:<tenant_sql_port> (e.g. site-primary:30015) - Authentication is secured via hdbuserstore key: Default key 'DEFAULT' or 'SAP<SID>DB' stored in /home/<sapsid>adm/.hdb/. 2. Homogeneous Database Refresh Workflow (PRD -> QAS): Phase 1 (Pre-Refresh on QAS): - Export critical technical tables: BDLS mappings, RFC destinations (SM59), logon groups (SMLG), printer definitions (SPAD), user master records (SCC8/SCC7 or export). - Suspend background jobs: Execute report BTCTRNS1 to pause all released batch jobs. - Stop SAP application server on QAS (stopsap). Phase 2 (Database Restore): - On QAS HANA host: connect to SystemDB. - Stop target QAS tenant: ALTER SYSTEM STOP DATABASE QAS; - Restore using production full data backup: RECOVER DATABASE FOR QAS USING DATA PATH ('/backup/PRD_FULL') USING LOG PATH ('/backup/PRD_LOG') CLEAR LOG; - Start tenant: ALTER SYSTEM START DATABASE QAS; Phase 3 (Post-Refresh on QAS): - Start SAP application server on QAS (startsap). - Install new QAS SAP License (SLICENSE). - Check and repair Secure Storage (SECSTORE). - BDLS Execution: Convert logical system names across all tables (e.g. PRDCLNT100 -> QASCLNT100). - Reconfigure RFC connections (SM59) to prevent QAS from accidentally connecting to PRD external systems! - Resume background jobs: Execute report BTCTRNS2.

Architecture Flow Diagram

Mermaid DiagramSAP Basis & S/4HANA Integration: Architecture, System Refreshes & DMO
Architectural Flow: The system refresh moves through pre-refresh configuration export, database restore in SystemDB, and mandatory post-refresh BDLS conversions, licenses, and RFC isolation.

Production Best Practices & Operational Risks

Mandatory Best Practices

  • ALWAYS isolate or delete RFC destinations (SM59) immediately after a refresh so the refreshed test system does not communicate with live production bank interfaces or vendors!
  • Execute BDLS in parallel batch mode (transaction BDLS with parallel processing enabled) to avoid taking 24+ hours on massive tables like ACDOCA.

Senior DBA Interview Mastery

3–5 Year Experience Target

Official Documentation & SAP Notes

SAP Note 2568736 - SAP HANA Database: System Copy / Refresh Guide

SAP Note: 2568736

SAP S/4HANA System Refresh Best Practices

DBA Study Notes & Lab Observations