E_S4HCON2023 Questions and Answers

Check the "Charts Control Center" in the SUM UI

Check logs for jobs starting with "RSUPG_SGEN" in the system

Check the log files written under "SUM\abap\log"

Check the dump size of the database export on disk

Keep archiving on during the whole procedure.

Use the Near Zero Downtime Maintenance Technology (NZDM).

Reuse a profile for the shadow instance from a previous run.

Choose the instance number of the shadow instance.

AA

A Standalone SAP system with ABAP 7.51 or above

An SAP S4HANA 1709 sandbox system

Check the compatibility of custom code with SAP S/4HANA.

Run the database migration to the SAP HANA database.

Solve problems from the simplification item (SI) checks.

Perform the migration of data to the new data structure.

SAP S/4HANA conversion including DMO

Prerequisite check

DMO without system update

SAP S/4HANA conversion without DMO

Benchmark tool

The benchmaking option allows you to migration a specified set of tables

The benchmaking option allows you to repeat the uptime migration

The repetition option allows you to run the migration without a shadow system

The repetition option allows you to repeat the complete migration

Target DB size will increase temporarily

A

DMO can only be run with systems NW740 or NW731

The source system is non-Unicode and the target database is a scale-out system.

The target database size increases temporarily because of the Shadow Repository.

SAP HANA Landscape Reorganization required a manual step to edit a file.

Network capacity between exporting and importing R3load processes must be.

Unicode conversion is part of DMO only in case of target version AS ABAP 7.40 or 7.31.

The SAP S/HANA Conversion Guide

The Application Guide

The major SUM Guide

The DMO Guide

Credentials of a named user in client 000 of the shadow system

Credentials of a named user in the development client of the development system

Credentials of user DDIC in client 000 of the shadow system

Credentials of user DDIC in the development client of the development system

To optimize the migration

To optimize the activation

To optimize the conversion

To optimize the main import

The SAP S/4HANA Conversion is without DMO.

The SAP S/4HANA Conversion includes a DMO.

The start release is too old for DOC.

The source database is not supported

During downtime

During SPDD

Post-downtime

During uptime

There is a maximum of 40 parallel R31oad processes within this specific downtime phase.

SUM is still running in uptime; the number of 40 defined R31oad processes is considered.

The number of CPU cores does not allow more than 40 R31oad processes to be run in parallel.

These are 40 pairs of R3load processes, so there are 80 R3load processes running.

Check the running batch job via Job Overview (SM37).

Check for running R3trans processes on the host where SUM is running.

Check for running R3load processes on the host where SUM is running.

Check the latest log files in the SUM directory, subdirectory abap, subdirectory tmp.

AA

As soon as the next SP level of SUM is available, the current version of SUM passes into "patch on request mode" immediately.

Depending on the SAP S/4HANA version, there are different SI check frameworks.

The SI checks are executed in the development system and the results are transported into the subsequent systems.

You need an SAP system based on AS ABAP 7.50 or above for the SI check framework.

You need to build up a SI check framework by applying SAP notes.

It explains the database migration option (DMO) of SUM.

It contains a section about the simplification item (SI) checks.

It explains where to find information about the custom code analysis.

It is a database-specific document.

By searching for transport requests that are assigned to the project SAP_ADJUST

By searching for transport requests named K0

By searching for transport requests in DIR_TRANS, subdirectory "transport"

By searching for transport requests in the file umodauto.Ist