AZ-120 · Question #84
Drag and Drop Question You have an on-premises SAP environment that runs on SUSE Linux Enterprise Server (SLES) servers and Oracle. The version of the SAP ERP system is 6.06 and the version of the…
The correct answer is Software Update Manager (SUM) Database Migration Option (DMO) with System Update; Software Update Manager (SUM) Database Migration Option (DMO) without System Update. SAP Migration to Azure on HANA - Explanation The Two Components and Their Assigned Tools | Component | Version | Tool Assigned | |---|---|---| | SAP ERP system | 6.06 (EHP6) | SUM DMO with System Update | | SAP NetWeaver Portal | 7.3 | SUM DMO without System Update | --- Item…
Question
Exhibit
Answer Area
Drag items
Correct arrangement
- Software Update Manager (SUM) Database Migration Option (DMO) with System Update
- Software Update Manager (SUM) Database Migration Option (DMO) without System Update
Explanation
SAP Migration to Azure on HANA - Explanation
The Two Components and Their Assigned Tools
| Component | Version | Tool Assigned |
|---|---|---|
| SAP ERP system | 6.06 (EHP6) | SUM DMO with System Update |
| SAP NetWeaver Portal | 7.3 | SUM DMO without System Update |
Item 1: SAP ERP 6.06 → SUM DMO with System Update
Why: SAP ERP 6.06 (Enhancement Package 6) is not fully compatible with SAP HANA as a database at that version level. To run on HANA, SAP ERP typically needs to be at EHP7 or EHP8 minimum.
SUM DMO with System Update combines two operations in a single downtime window:
- Migrates the database from Oracle → HANA
- Simultaneously upgrades the SAP ERP application to a HANA-compatible enhancement package
Without the version upgrade, the ERP system would not be supportable on HANA. The "with System Update" option exists precisely for this scenario.
Item 2: SAP NetWeaver Portal 7.3 → SUM DMO without System Update
Why: SAP NetWeaver 7.3 already supports HANA as a database natively - no application version upgrade is required. Only the underlying database needs to change (Oracle → HANA).
SUM DMO without System Update performs only the database migration in a single pass, leaving the application version intact.
Why Not "SAP Heterogeneous System Copy"?
A heterogeneous system copy (via SWPM/R3load) handles OS/DB platform changes but:
- It is a more manual, export/import-based process
- It cannot simultaneously upgrade the SAP application version
- DMO is the SAP-recommended modern approach for Oracle-to-HANA migration, optimized for downtime reduction
Common Mistakes
- Swapping the two DMO tools - candidates often forget that ERP 6.06 is version-incompatible with HANA and mistakenly assign "without System Update" to it.
- Choosing heterogeneous system copy for either component - this is a distractor. It's valid in some scenarios, but DMO supersedes it for HANA migrations and is required here because the ERP version also needs upgrading.
- Assuming both components need the same tool - the version compatibility difference between ERP 6.06 and NetWeaver 7.3 is the key discriminator.
Topics
Community Discussion
No community discussion yet for this question.