Zero Downtime Option for SAP S/4HANA

General Troubleshooting Activities

This section deals with general activities to perform a successful troubleshooting.

Consider the following troubleshooting activities:

For additional known issues and their solution, see SAP Note 2707753 Information published on SAP site.

Checking the Relevant Log Files

As a first step in a problem, we recommend that you look at the SUM user interface. In many cases, an excerpt from a log file is displayed here, which is a good starting point for error analysis. Additional log files are available in the Start of the navigation pathabap Next navigation step logEnd of the navigation path subdirectory of the SUM Directory. Call up the list of log files and sort the display in descending order by time. Check the most recent files first, as SUM updates the log files frequently. In some cases, checking the most recent log files in the subdirectory Start of the navigation pathabap Next navigation step tmpEnd of the navigation path is also useful.

Analyzing Short Dumps

The analysis of short dumps can help to correct errors in the ABAP system. Use the ABAP Dump Analysis (transaction ST22), which you can use to list the short dumps that occurred in the ABAP system.

If the cause of a short dump is unclear or if you cannot correct the error yourself, report an incident for the application component listed in the header line of the short dump list.

Checking the Background Job Overview

Using transaction SM37, you can monitor jobs running in your SAP system and find information about aborted jobs. To check for aborted jobs, enter the following in the dialog Simple Job Selection:

Job Name

*

User Name

DDIC or *

Job Status

Choose Canceled

Job Start Condition

Enter a relevant timeframe.

Example: Enter the current date in From and To to get all aborted jobs of the current day.