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

Performing an Extended Prerequisites Check

You perform an extended prerequisite check of your source system before you start a system conversion to SAP S/4HANA.

Context

Prerequisite Check Extended

The Prerequisite Check Extended performs a system conversion, but not for productive use. The check ends before the downtime would have started.

The Software Update Manager ignores the relevant errors of checks and collects them in a list in csv format. The list is available at the end of the check. It allows you to analyze the ignored errors so that you can solve them and start a regular system conversion from the beginning.

Currently, you can ignore errors from the following checks:

  • Simplification items check

  • Check for inconsistencies in custom software components and ABAP repository objects

  • Version check of operating system and database

  • Check for safety transport requests for objects adjusted with SPDD

  • Check for unreleased repairs and corrections

Prerequisite Check Extended without Target Database

This check is a slightly reduced version of the extended prerequisites check described previously. It is applicable if no SAP HANA target database is available yet. In this case, the check runs only on the source database and certain dialogs related to the transfer are not displayed.

Procedure

  1. Start the Software Update Manager.

    For more information, see Starting or Restarting the Software Update Manager.

  2. Specify the scenario category with stack.xml configuration file.

    Enter the full path of the stack.xml configuration file calculated by the Maintenance Planner. For more information, see Specifying the Scenario to Get the Roadmap.

  3. Select the scenario strategy Prerequisite Check Tool and the option Prerequisite Check Extended or Prerequisite Check Extended without Target Database to start the check.

    You can recognize the extended prerequisite check at the top of the SUM UI. The upper line displays as normal the applied tool version. However, the lower line displays Prerequisite Check Extended or Prerequisite Check Extended without Target Database instead of the current scenario and strategy.

    During the extended prerequisite check run, a list in CSV format is being created. It collects the ignored errors from the checks mentioned at the beginning of this topic.

    At the end of roadmap step Configuration, you are prompted to confirm that you want to ignore failed checks and continue. Furthermore, you confirm during the roadmap step Preprocessing several times that you want to add errors to the error list and continue.

    The check ends before the downtime would have started. The downtime cannot be started technically at this point in time.

    After the check run is finished, the Software Update Manager is reset automatically to its initial state.

  4. Analyze the collected ignored errors that are listed in file precheckext_messages.csv.