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.