Explaining the Product in an Overview

Explaining the SAP Service and Asset Manager Application Architecture

Performing the Installation, Deployment, and Setup

Performing the Configuration of an Out-of the Box Mobile App

Using the Application Extensibility

Performing the Debugging and Branding a Client

Performing a Root Cause Analysis and Performance Optimization

Describing Upgrade and Support

Trawling Through the Appendices

Debugging and Troubleshooting Overview

Objective

After completing this lesson, you will be able to give an overview of the debugging and troubleshooting tools

Overview Debugging and Troubleshooting Tools for SAP Service and Asset Manager

Let's look at the different tools available for debugging back end OData Service and MDK as well as tools that can be used to inspect the client data on your laptop or MAC.

Back end - ABAP Debugging (& Tracing):
- Gateway Trace (TCode /IWFND/TRACES).
- External Debugging in ABAP.
- Gateway Client (TCode /IWFND/GW_CLIENT)–for testing Asset Manager OData Services.
MDK Debugging via Visual Studio Code:
- Set up Visual Studio Code for debugging (Described in earlier units)
- Using Visual Studio Code for Debugging
Troubleshoot Client issues with ILOData.
Use Interactive Local OData (ILOData) command-line utility for Troubleshooting Client issues.
Client Branding
Create a Branded MDK Client.

Next lesson