Conversion to SAP S/4HANA using SUM: ABAP Systems on UNIX and Linux

Landscape Reorganization

If you run an SAP HANA scale out landscape as a target for a migration of SAP BW powered by SAP HANA, you can perform a landscape reorganization.

You can enable the landscape reorganization in phase HDB_MIGCONFIG during the preprocessing phases of the migration. If you decide not to run the SAP HANA landscape reorganization, which is usually the case for SAP ERP or SAP S/4HANA, SUM performs the phases for the scale up scenario.

If you run SAP HANA 1.0 with SPS 10 or higher, the SQL-files for the SAP HANA table placement are loaded and executed automatically without a dialogue. You can disable this automated load of table placement SQL-files in phase HDB_MIGCONFIG and run the same dialogs as for SAP HANA 1.0 SPS 09 in case you have to modify the SQL-files delivered by SAP.

SAP HANA scale out

The scale out scenario means the deployment of multiple server nodes in case memory requirements exceed the available memory of a single server node after the migration to SAP HANA database. For this, several phases are carried out during the SUM with DMO run.

If your SAP HANA version is SPS 09 or lower, you have to perform the following manual phases:

  • REQ_LANDSCAPE_REORG

    In this phase, SUM prompts you in a dialogue to import an SQL-file from SAP Note 1958346 Information published on SAP site into the database.

  • REQ_LANDSCAPE_REORG_2

    In this phase, SUM prompts you in a dialogue to import an SQL-file for SAP BW powered by SAP HANA from SAP Note 1908075 Information published on SAP site into the database.
If your SAP HANA version is SPS 10 or higher, the following phases load and execute the SQL-files automatically:

  • SQLDB_LANDSCAPE_REORG

    In this phase, SUM imports an SQL-file from SAP Note 1958346 Information published on SAP site into the database.

  • SQLDB_LANDSCAPE_REORG_2

    In this phase, SUM imports a procedure for the SQL-files for SAP BW powered by SAP HANA from SAP Note 1908075 Information published on SAP site into the database.

  • SQLDB_LANDSCAPE_REORG_EXEC

    In this phase, SUM executes the procedure loaded in phase SQLDB_LANDSCAPE_REORG_2.

The following landscape reorganization phases run automatically:

  • HDB_CHK_LANDSCAPE_REORG_PRE

    In this phase, SUM checks whether the prerequisites for the landscape reorganization are met.

  • HDB_LANDSCAPE_REORG

    In this phase, the landscape reorganization is performed.

  • HDB_CHK_LANDSCAPE_REORG_POST

    In this phase, SUM checks whether the landscape reorganization has been performed correctly.

SAP HANA scale up

Even if you run an SAP HANA single-node system with a scale up scenario, you must import a file with specific SQL-information to enable the optimal table partition. For this, the following phases are carried out during the SUM with DMO run.

If your SAP HANA version is SPS 09 or lower, you have to perform the following manual phase:

  • REQ_SCALEUP_PREREQ

    In this phase, SUM prompts you in a dialogue to import an SQL-file from one of the following notes into the database according to your product:

    • BW on SAP HANA: SAP Note 1908075 Information published on SAP site

    • SAP Business Suite on HANA or SAP S/4HANA: SAP Note 1899817 Information published on SAP site

If your SAP HANA version is SPS 10 or higher, the following phases load and execute the SQL-files automatically:

  • SQLDB_SCALEUP_PRER

    In this phase, SUM imports a procedure for the SQL-files from one of the following notes into the database according to your product:

    • BW on SAP HANA: SAP Note 1908075 Information published on SAP site

    • SAP Business Suite on HANA or SAP S/4HANA: SAP Note 1899817 Information published on SAP site

  • SQLDB_SCALEUP_PREREQ _EXEC

    In this phase, SUM executes the procedure loaded in phase SQLDB_SCALEUP_PREREQ.