Everything in ABAP / Standard ABAP
Type
Domain: Developer Experience
Origin
Signals
Standard ABAP: Answers in Standard ABAP
More: 2
Group by: Capability
MCP server driving SAP's ABAP debugger over ADT for an agent
A stopped program holds an SAP work process and its caller's request, so an interactive session is the wrong shape wherever that matters: one runs per SAP user at a time, other captures for that user are refused while it is open, and a Cloud Foundry deployment stays at one instance because the next call must reach the same process. Breakpoints in report and function-group includes are not accepted, and a message breakpoint catches `MESSAGE` statements only, so RAP messages from `new_message( … )` and BAPI return tables never stop a run. On SAP_BASIS 7.50 and older the system cannot name the session's debug user, so there `SAP_USER` is used behind Basic or cookie authentication only.
Local ABAP server serving /IWBEP/ OData v2 without an SAP system
Not a system to run a business application on: there is no business application in it, and what it implements of the language, the dictionary and Gateway is a stated subset of each. It is a clean-room reimplementation of the `/IWBEP/` interfaces that bundles no SAP source and no standard DDIC, so a service that reads standard objects has nothing to read, and `ANORMALIES.md` records every place the runtime differs from SAP before any workaround is written.
Local ABAP server serving /IWBEP/ OData v2 without an SAP system
Not a system to run a business application on: there is no business application in it, and what it implements of the language, the dictionary and Gateway is a stated subset of each. It is a clean-room reimplementation of the `/IWBEP/` interfaces that bundles no SAP source and no standard DDIC, so a service that reads standard objects has nothing to read, and `ANORMALIES.md` records every place the runtime differs from SAP before any workaround is written.