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

Making Entries for Scenarios with Configuration File

This section is relevant when you have specified a scenario category with stack.xml configuration file.

Context

After you have provided the Software Update Manager the path to the download directory with the stack.xml file, it checks in the background the source database of your system.

  1. The source database is not SAP HANA
    If your source database is NOT SAP HANA database, you must decide first whether you want to carry out a database migration. For this decision, the following dialog appears first:

    • Decide on DMO

  2. The source database is SAP HANA
    If your source database is already SAP HANA database, the following dialogs appear successively:

    1. Scenario Strategy

    2. Additional Parameters for <scenario>

Procedure

  1. Decide on DMO

    This dialog appears only, if your source database is not SAP HANA database and the database migration is not required.

    If your source database is not SAP HANA database, and you carry out a system conversion to SAP S/4HANA, the dialog is NOT displayed. In this case, a database migration to SAP HANA database is required so that the Software Update Manager performs it automatically.

    You can decide if you want to use the Database Migration Option (DMO) of the Software Update Manager to migrate your source database to one of the following databases:

    • SAP HANA

    • SAP ASE

    If you do not want to use the DMO feature, choose No migration.

  2. Specify the scenario strategy
    Depending on the scenario category and the decision on DMO, one or more of the following options are available for selection:

    • Single System

    • Standard

    • Downtime-optimized

    • Prerequisite Check Tool

    1. Single System

      This option means a longer downtime, and no shadow instance is running in uptime. Note that this option is only available for the update of support packages or support package stacks.

    2. Standard

      This option is the standard configuration for the most scenarios.

    3. Downtime-optimized

      One of the following variants of this option is available:
      Source database is SAP HANA? Wanted scenario Available option
      Yes Update or upgrade with business downtime reduction near-Zero Downtime Maintenance (nZDM) or Zero Downtime Option (ZDO)
      No Update or upgrade with database migration to SAP HANA database Uptime Migration (Downtime-optimized DMO)
      No Update or upgrade, but no database migration to SAP HANA database near-Zero Downtime Maintenance (nZDM)
      Yes Conversion to SAP S/4HANA near-Zero Downtime Maintenance (nZDM)
      No, but

      • Oracle

      • IBM Db2 for Linux, Unix, and Windows (DB6)
      		Conversion to SAP S/4HANA Uptime Migration (Downtime-optimized DMO)
      Yes, or

      • Oracle

      • IBM Db2 for Linux, Unix, and Windows (DB6)
      		Downtime-optimized conversion to SAP S/4HANA Downtime-optimized Conversion

    4. Prerequisite Check Tool

      You can choose between three checks:

      • The Software Update Manager executes a Prerequisite Check as a separate step. If specific mandatory preparatory steps are required, the conversion procedure can stop to ensure a consistent system conversion. However, the conversion is stopped if errors persist.

      • The Prerequisite Check Extended executes a system conversion, but not for later productive use. The check ends before the downtime would have started. In contrast to the normal prerequisite check, the Software Update Manager ignores all identified errors and collects them. They are summarized at the end of the uptime in a list.

      • The Prerequisite Check Extended without Target Database is similar to the extended prerequisite check.

        You can apply this check if no SAP HANA target database is not available yet. The check runs only on the source database and certain dialogs related to the transfer are not displayed.

      For more information, see Checking the Prerequisites for the Conversion with SUM.

    For more information on the scenario strategy options, see Initial Dialogs for the Scenario Specification (Get Roadmap).

  3. Decide on additional parameters

    The following options are available:

    • Check Archive Authenticity

      Select this checkbox if you want the authenticity of all archives in the download directory to be checked. For more information, see Verifying SAP Archives (Digital Signature Handling).

    • Add-On Verification

      Select this checkbox if you want the default add-on handling with all checks to be performed during the prerequisite check extended. You must then decide on all installed add-ons as described in Important Entries for the Configuration Roadmap Step -> Start of the navigation path Decision About Add-Ons (Phase IS_SELECT)End of the navigation path. Otherwise, add-ons without a version for the SAP S/4HANA target release are treated internally as passive deletions. For more information, see Performing an Extended Prerequisites Check.

    • Switch expert mode on

      Choose this option if you want to adapt additional tool configuration options during the update:

      • The Software Update Manager always displays a Support Package overview in phase BIND_PATCH, even if manual adjustment is not necessary. You can overrule the Support Package level, which is derived from the stack configuration file. For more information about phase BIND_PATCH, see Important Entries for the Configuration Roadmap Step.

      • You can change the automatically generated instance number for the shadow instance and enter a password manually. (See also: Shadow Instance Parameters.)

      • You can decide if you want to use saved profiles from a previous update for the shadow system.

    • Customer Transport Integration

      If you

      • have selected the strategy mode Standard or Downtime-optimized

      • meet the conditions for the Software Update Manager including customer transport requests according to SAP Note 1759080 Information published on SAP site

      you can include customer transport requests into the procedure to reduce business downtime.

      Select the checkbox Consider Customer Buffer File, if a customer buffer file shall be considered that contains customer transports for the target release. A subsequent dialog prompts you to enter the path and the name of the buffer file. For more information, see Integration of Customer Transports.

      Note that this option is not displayed if the scenario strategy Single System has been selected beforehand.

  4. Decide on Migration Parameters
    You can

    • decide on the table selection, if you want to perform a table comparison

    • enter the migration key, if necessary

    • enable the migration repetition option for testing purposes

    • enable the System Move option, if you want to move of the primary application server from source to target system