Debugging
Seeing what running code did between an input arriving and a result coming out: which code ran, what the values were at each point, and why a value ended up as it did.
Overview
Seeing what the framework did between a request arriving and a query being issued — which handlers ran, how the query was rewritten, why a value ended up as it did.
@cap-js/console Connects a running CAP application to the CAP console.
@cap-js/data-inspector Inspects database entities and their contents at the CAP service level.
@sap/cds-dk The command line client and development toolkit for CAP projects, with the commands cds build, cds deploy, cds watch and cds add among them.
com.sap.cds:cds-feature-console A CAP Java plugin that connects a running application to CAP console, which consumes its remote monitoring data; CAP console itself is installed separately and still being developed.
com.sap.cds:cds-feature-dev-dashboard A browser dashboard for a running CAP Java service that shows and manages its messaging, resilience and multitenancy state while developing, open to users with the cds.Developer role.
Not covered: It stops at inspecting data. Seeing which handlers ran, how a query was rewritten and why a value came out as it did still means reading framework source.
Community tools reach the questions the core leaves open: sap-cap-debuggersap-cap-debuggerAttaches a debugger to a CAP application already running on Cloud Foundry — enables the Node inspector inside the container, assigns a port and hands you a Chrome DevTools or VS Code attach.independent, cap attaches a Node debugger to a CAP application already running on Cloud Foundry, and @saptools/service-flow@saptools/service-flowTraces one CAP operation end to end across several repositories without running anything — handlers, helper packages, local database access, remote OData calls, external HTTP and async channels.independent, cap traces one CAP operation through handlers, database access and remote calls without running anything.
Seeing what an ABAP program did at runtime in the system it runs in: the variables, internal tables and object instances at a step, the calls that led there, and where a value changed.
The ABAP Debugger stops a running program and shows up to four tools at once on its desktops; debugger scripting automates it from inside, stepping, reading and changing values and writing custom traces.
Not covered: At the current step. The documentation checked describes no way back to a step already passed, in the debugger or in a script.
Community debugger scripts and extensions sit on the debugger's own scripting: Smart DebuggerSmart DebuggerA debugger script for the SAP GUI New Debugger that records every step and variable change of an ABAP program, so execution can be stepped backwards with F5 and F8.independent, abap records every step so execution can be stepped backwards, and abap_debugger_object_graph_extensionabap_debugger_object_graph_extensionAn ABAP debugger extension that shows the object on the debugger's Objects tab as a Graphviz graph in a browser window, built on ABAP Graph and Graphviz-browser and tested on NetWeaver 7.5.independent, abap and ABAP-Object-VisualizerABAP-Object-VisualizerA debugger script that writes an object hierarchy to the clipboard at a breakpoint as a Graphviz description, for pasting into a renderer such as webgraphviz.com.independent, abap draw an object as a Graphviz graph. dbg_value_statementdbg_value_statementAn ABAP Debugger script that turns a variable's structure or table into the VALUE statement that recreates it, with a tree explorer, also callable as a function module from a report.independent, abap turns a variable into the VALUE statement that recreates it, and dump_infodump_infoDisplays the variables an ABAP short dump captured, for dumps selected on a selection screen; its documentation does not state which dumps it reads, which releases it runs on or how it installs.independent, abap shows the variables a short dump captured.
Artifacts
Content
Show 4 more
Seen working
Details
Coverage
For your agent
- Ref
capability:debugging- JSON
- /capabilities/debugging.json
- MCP
- Connecting an agent