SAP Basis

Troubleshooting Guidelines
Mohamed Awny
February 2024
SAP BASIS
Troubleshooting Guidelines (1/3)

Troubleshooting Basics
• Overview
• Basic Procedure
• Fiori Troubleshooting

2
Overview

In every SAP system, errors will sometimes occur that you'll be required to resolve yourself, or you'll need to at
least collaborate in their correction. Some errors are trivial and can be solved after you read the error message.
Other issues are caused by an application error, incorrect system settings, or by an actual programming error.

SAP provides the SAP for Me Portal to help you find solutions to system errors. The Portal has an extensive
database of solutions and SAP Notes to help you resolve issues. We will outline the basic principle of error
handling, demonstrate how to use the SAP for Me for troubleshooting, and show you the tools that can be used
for troubleshooting on the SAP System.

2
Troubleshooting
Basic Procedure
Basic Procedure

The general procedure for troubleshooting described here isn't a new one. It has been used for many years in a range of industries:

1. Gather data.

2. Analyze the problem.

3. Determine solution options.

4. Eliminate the error.

5. Make the necessary adjustments.

6. Document the changes.

7. Test the results.

Some of these steps are described in more detail next.

Basic Procedure
Gather data
When an error occurs, the first step is to gather data. Pay particular attention to the following questions:
 What is the precise nature of the problem?
 What causes the problem?
 Is it possible that the problem will occur frequently, or has it already occurred several times?
 Can the problem be systematically reproduced?
 Which error messages, dumps, or other diagnostic information was displayed in connection with this problem?
Basic Procedure
Gather data – Tools

Use the available system tools to analyze the error messages, for example:
Transaction Code Action Explanation

Display all users currently logged on to the system, together with their
Users AL08/SM04 Allows administrators to detect faulty or multiple logons.
user ID and terminal.

Allows administrators to detect possible OS and hardware problems (e.g., a failed

OS Monitor ST06 Display operating system logs.
drive).

Select background
Allows the administrator to detect any critical jobs that have been executed
jobs/Job Scheduling SM37/RZ01 Select and monitor batch jobs scheduled in the background.
incorrectly. Other tasks may depend on the successful execution of these jobs.
Monitor

Monitor servers (DEV, QAS, Test, PRD, etc.) in your environment using a
CCMS Alert Monitor RZ20 Alerts indicate potentially serious problems that require an immediate solution.
central program.

Display a list of all lock entries. Locks prevent other users from changing
Select lock entries SM12 Allows the administrator to remove old locks or locks that need to be removed.
data records that you're in the process of editing.
Basic Procedure
Gather data – Tools

Use the available system tools to analyze the error messages, for example:
Transaction Code Action Explanation

Display, process, test, reset, delete, and

Update records SM13 Administrators can process any update records that haven't yet been processed.
access statistics for update records.

System log SM21 Analyze system logs. Supports the administrator in the early detection of system problems in the SAP system.

Batch input SM35 Manage batch input sessions. Alerts the administrator to the existence of new or faulty batch input sessions.

Display the status of work processes;

Transaction SM50 is used for systems
without an application server.
Allows users to monitor work processes and check whether any have been processed incorrectly or have been
Work processes SM50/SM51  Transaction SM51 is the central
running for too long.
transaction.

 Transaction SM50 is started for each

application server.

Spool requests SP01 SAP System Output Manager. Helps you resolve time-critical print job issues.
Basic Procedure
Gather data – Tools

Use the available system tools to analyze the error messages, for example:

Transaction Code Action Explanation

Display statistics relating to SAP buffer

performance, fine-tuning of buffer Enables the solving of problems with extensive buffer swaps. Search for entries shown in red in
Tune summary ST02
parameters, SAP database parameters, and the Swaps column, and monitor the time details to identify trends.
operating system parameters.

Load analysis in the If you know the normal load distribution when the system is running, you can make minor adjustments that may
ST03N Determine system performance.
SAP system help when problems occur.

Database
Allows you to monitor the growth of the database, capacity, input/output statistics, and alerts. You can drill down
performance ST04 High-level database performance monitor.
to display additional information.
analysis
ABAP dump
ST22 Display the logs of ABAP short dumps. Allows you to determine why a report or transaction terminated.
analysis
Transport
Management STMS Check transport queues and logs. Allows you to detect errors in the import of transport requests.
System
Basic Procedure
Analyze the problem
After you've formed a detailed picture of the situation, proceed with the analysis of the problem. Use the resources available to you for
solving the problem for this purpose:
• SAP Help Portal (http://help.sap.com)
• SAP Technology Troubleshooting Guide (https://help.sap.com/docs/SUPPORT_CONTENT/techtsg/3362709955.html)
• SAP Fiori Troubleshooting Guide (
https://help.sap.com/docs/SAP_FIORI_OVERVIEW/47d8a2e60bf2442c8e0675961953eef6/231b6852c1d5725fe10000000a441470.html
)
• SAP Help Portal (http://help.sap.com)
• SAP Notes and documentations in the SAP Support Portal (https://support.sap.com or https://ga.support.sap.com/dtp/viewer/)
• Troubleshooting Tools (https://support.sap.com/en/tools/troubleshooting.html)
• Diagnostic Tools (https://support.sap.com/en/tools/diagnostic-tools.html)
• SAP Community Network (https://community.sap.com/)

If you're unable to turn up any useful information, seek the assistance of an expert:
• Internal specialists and administrators
• External consultants
• Other SAP customers (in your network)
Basic Procedure
Determine solution options
Compare the various solutions options you've identified. Check which changes would be necessary in each case and how these
changes would impact on the behavior and stability of your SAP system.

Compare the impact to be expected (costs) with the result foreseen (benefits) for each individual option.
Basic Procedure
Eliminate the error
Errors may have many different causes. For example, a problem may occur because of a user error, incomplete or missing system
settings, or program errors.

In every case, you should begin by excluding the possibility of incorrect use or configuration of the system before consulting external
partners.

After you've identified one or more approaches to eliminating the error, take care not to jump the gun. For one thing, not every solution
will suit your situation every time. And, for another, you may cause further problems by making a snap decision.
Basic Procedure
Make the necessary adjustments
Only implement one change at a time if possible. If a problem occurs and you implement several changes simultaneously, you may then
be unable to identify which change solved the original problem or which change caused a new one.

In some cases, however, you need to make several changes to solve a problem.

Only implement more than one change at a time if this is absolutely essential, for example, in the case of related program changes.
Basic Procedure
Document the changes
All changes are to be documented thoroughly. If a change produces an additional problem, you must undo that change.

To do this, you need to know what the configuration was before the change was implemented and exactly what change was made. If
changes are to be applied across various systems, you must know exactly what changes are to be made and how this is to be done.

The same steps must be performed in exactly the same way in all systems.
SAP BASIS
Troubleshooting Guidelines (2/3)

Fiori Troubleshooting
• Fiori Communication Flow
• Common Error Types
• Troubleshooting Tools

2
Fiori Troubleshooting
Fiori Communication Flow
 Fiori Communication Flow
Hub Deployment

NW 7.5x

NW 7.5x
RFC SAP HTTP(S)

Frontend
SAP UI5 Add-ons Web HTTP(S)

Backend HTTP(S)
dispatcher
Webdynpro & ESH
HDB

Intranet DMZ Internet

 SAP Backend contains RFC functions, Odata Models, CDS  Exposes UI layer web  Consume apps
Views and Webdynpro objects. services for remote access
 These development objects contain the business logic to through public internet
perform any business function in SAP.  Handles cross-domain
 Frontend server consumes these objects and exposes them  URL redirect,
requests
through web services. filtering, rewriting
 Frontend server consumes web services by implementing a UI  Can connect to the
layer based on Html5, javascript, xml. backend or
 Masksfrontend
internal server
names
17
 Fiori Communication Flow
Embedded Deployment

FES Add-ons

NW 7.5x UI5 Add-ons

SAP HTTP(S) Web HTTP(S)

Backend dispatcher
HDB

Intranet DMZ Internet

 SAP Backend contains RFC functions, Odata Models, CDS  Exposes UI layer web  Consume apps
Views and Webdynpro objects. services for remote access
 These development objects contain the business logic to through public internet
perform any business function in SAP.  Handles cross-domain
 Frontend server add-on components consume these objects  URL redirect,
requests
and exposes them through web services. filtering, rewriting
 Frontend server add-on component consumes web services  Connects to the
by implementing a UI layer based on Html5, javascript, xml.  Masksbackend
internal server
names

18
Fiori Communication Flow
S/4HANA ABAP Programming Model for Fiori and RESTful ABAP Programming Model

Fiori Launchpad SAP Fiori

is a collection of apps with a simple and easy-
User Interface to- use experience for broadly used SAP
software functions that work seamlessly across
(Fiori)
devices – desktop, tablet, and smartphone.

OData (Open Data Protocol)

OData Service is an OASIS standard that defines the best
practice for building and consuming RESTful APIs.

Application CDS (Core Data Services)

(ABAP | CDS)
CDS is an enhancement of SQL which provides a
data definition language (DDL) for defining
semantically rich database tables/views (CDS
entities) in the database. The enhancements
Database Table include annotations, associations, and expressions

19
Fiori Troubleshooting
Common Error Types
Common Error Types
Front-End Layer

Rendering errors
Fiori Launchpad Wrong app routing
Wrong app navigation
User Interface
Missing tiles
(Fiori)
Missing Frontend
Authorizations High UI load
times

OData Service

Application
(ABAP | CDS)

Database Table

21
Common Error Types
Back-End Layer

Fiori Launchpad

User Interface
(Fiori)

Inactive OData services

OData Service Inactive CDS views (DCL, DDL)
ABAP coding error
Inactive ABAP objects
Inactive Business Functions
Application
Missing / Wrong Functional
(ABAP | CDS) configurations
Missing Backend Authorizations
High OData response times
Database Table

22
Common Error Types
Database Layer

Fiori Launchpad

User Interface
(Fiori)

OData Service

Application
(ABAP | CDS)

Data inconsistencies
Database Table Errors in data replication
No data

23
Fiori Troubleshooting
Troubleshooting Tools
Troubleshooting Tools
Always remember these facts and transactions

1. Understand Landscape Architecture:

– Transactional Apps implement OData calls from the Frontend server but Webdynpro and Object Page
require a direct connection the Backend server.
– Hub Deployments: Several RFC connections are required.
▫ Firewall adjustments may be needed in complex network architectures.

2. Catalog Replication / Index Calculation:

– Set up Fiori Catalog Replication and Index Calculation jobs to run at least once a day, this will make sure
that Catalog and Application ID status is consistent.
▫ Report /UI5/APP_INDEX_CALCULATE
▫ Report /UI2/GET_APP_DESCR_REMOTE

3. Update UI libraries:
–Important corrections are delivered in UI libraries that will help stabilize Fiori apps.

25
Troubleshooting Tools
Always remember these facts and transactions

4. Hub Deployments - One frontend for multiple backends:

– In this case, try to maintain 1 frontend client per backend client within the same landscape.
Backend Frontend

Launchpad
100 100
200 200
300 300

5. Hub Deployments - Security:

– Enabling trust relationship between the frontend and backend server requires all users to possess
authorization object: S_RFCACL
– Replication of user ID’s between frontend and backend clients is required.
Backend Frontend
ID: JOHNDOE Sys. Trust ID: JOHNDOE
Auth. Obj. Auth. Obj.
S_RFCACL S_RFCACL

26
Troubleshooting Tools
Always remember these facts and transactions

6. Know your tools:

General Administration
Transaction Code Description
SU01 User Maintenance
PFCG Role Maintenance
SICF Maintain Services
SM59 RFC Destinations (Display/Maintain)
SPRO Configure SAP System as per client requirement
SMICM ICM Monitor
SHMM System Shared Objects Monitor
STC01, STC02 Execute/Display Task List Runs
ST22 System Dumps
/UI2/CUST Customizing of UI Technologies
SACM Access Control Management
27
Troubleshooting Tools
Always remember these facts and transactions

6. Know your tools:

Frontend Administration
Transaction Code Description
/UI2/FLP Launch SAP Fiori Launchpad
/UI2/FLC Fiori Launchpad Checks
/UI2/FLP_CUS_CONF Fiori Launchpad System Settings (client-specific)
/UI2/FLP_SYS_CONF Fiori Launchpad System Settings (cross-client)
/UI2/FLP_DEL_PERS Delete Personalization of SAP FLP
/UI2/CSU Cache Statistics Utility
/UI2/FSAC System Alias Consistency Check
/IWFND/CACHE_CLEANUP Cleanup of Model Cache
/IWFND/MAINT_SERVICE Activate and Maintain OData Services
/IWFND/ERROR_LOG SAP NetWeaver Gateway Error Log
/IWFND/GW_CLIENT Simulate OData Service execution
/IWFND/TRACES SAP NetWeaver Gateway: Tracing Tools
/IWFND/APPS_LOG Application Log Viewer
/IWFND/CACHE_REBUILD Rebuild Gateway Model Cache
28
Troubleshooting Tools
Always remember these facts and transactions

6. Know your tools:

Frontend Administration (continued)
Transaction Code Description
/IWFND/V4_ADMIN OData V4 Administration (for Notifications)
/IWNGW/R_HUB_CLEAR_CACHE OData Cache (for Notifications
SBGRFCMON Monitor bgRFC queues (for Notifications)

29
Troubleshooting Tools
Always remember these facts and transactions

6. Know your tools:

Backend Administration
Transaction Code Description
/IWBEP/CACHE_CLEANUP Cleanup of Model Cache
/IWBEP/ERROR_LOG SAP Gateway Backend Error Log
/IWBEP/TRACES SAP Gateway Backend Traces
/IWBEP/VIEW_LOG SAP Gateway Log Viewer
/IWBEP/CONFIG_CHECK Check Configuration of BEP

ESH_DASHBOARD Enterprise Search Connector Analysis and Troubleshooting

ESH_TEST_SEARCH Enterprise Search Connector Test
ESH_QUERY_LOG Enterprise Search Connector Query Log

30
Troubleshooting Tools
Always remember these facts and transactions

6. Know your tools:

Business Role Administration
Transaction Code Description
/UI2/FLIA Fiori Launchpad Intent Analysis
/UI2/FLC Fiori Launchpad Checks
/UI2/FLPCM_CUST Fiori Launchpad Content Manager (client-specific)
/UI2/FLPCM_CONF Fiori Launchpad Content Manager (cross-client)
/UI2/FLPAM Fiori Launchpad App Manager
/UI2/FLP_APPDESC_GET Replicate Backend Catalogs
/UI2/FLPD_CONF Fiori Launchpad Designer (cross-client)
/UI2/FLPD_CUST Fiori Launchpad Designer (client-specific)
/UI2/SEMOBJ Define Semantic Object – Customer
/UI2/SEMOBJ_SAP Define Semantic Object – SAP
SACMDCLS CDS Access Controls

31
Troubleshooting Tools
Always remember these facts and transactions

6. Know your tools:

SAP Fiori Administrator Launchpad Support Tools
Tools listed in the SAP Reference
Implementation Guide
 SAP GUI Transaction SPRO >
SAP Ref IMG >
SAP NetWeaver >
UI Technologies >
SAP Fiori >
Launchpad
Support Tools

In the SAP Help

Portal
 SAP Fiori
launchpad >
Administration
Guide 32
Troubleshooting Tools
Always remember these facts and transactions

7. Useful reports for FLP checks and system alias:

33
Troubleshooting Tools
Always remember these facts and transactions

8. Many issues relate to cached content.

– Make sure to delete cache in case of issues and also particularly after deployment of corrections /
FPS. Run report /UI2/INVALIDATE_GLOBAL_CACHES to clear the FLP caches.

9. Intents (combination of semantic object and action) not resolving.

– Make use of FLP Intent Resolution Analyzer (TA code /UI2/FLIA)

10. Data missing in app typically related to Authorizations.

– TA code SU53 for authorization traces (see SAP Note 2147808)

34
Troubleshooting Tools
Always remember these facts and transactions

11.Rapid Activation is the

recommended procedure to activate SAP
Fiori since the release of SAP S/4HANA
1709 FPS01
– Rapid Activation is available on any version
higher or equal to SAP S/4HANA 1709
FPS01.

12.Rapid Activation is available only

on embedded SAP Fiori deployments

13. Rapid Activation – Error

Troubleshooting.
– Known issues and solutions are mentioned in the
Rapid Activation note for each version of
SAP S/4HANA. Overview note with links to
version specific notes is available: 2902673 -
Rapid Activation for SAP Fiori in SAP S/4HANA - 35
Troubleshooting Tools
Always remember these facts and transactions

14. Deploy App Support for the SAP Fiori Launchpad plugin in your landscape
– App support is available for SAP S/4HANA as part of the SAP_UI component from the following
versions:
▫ SAP_UI 7.54 SP06 in S/4HANA 1909 SP04 or Frontend Server 6.0 SP04
▫ SAP_UI 7.55 SP02 in S/4HANA 2020 FPS01 or Frontend Server 2020 SP01

15. You can run SAP Fiori Launchpad health checks as a proactive maintenance activity in
your system
– Via task list /UI2/FLP_HEALTH_CHECKS
– Using Launchpad Content Manager

36
Thank you!