CapabilityDeveloper ExperienceStandard ABAP, read from its artifacts

Local development

On the ABAP door the laptop runs a whole system: SAP's trial image is an application server and a database in one container, and a developer's own setup happens in that system after it starts, which is the part abapDevSysInit by Mike Pokraka scripts.

Showing artifacts, examples and content with confirmed Standard ABAP applicability. View All ABAP

Overview

SAP SHIPS

No SAP artifact is confirmed here for Standard ABAP.

A Standard ABAP coverage assessment has not been written. View all flavors

THE COMMUNITY ADDS
open-steamgate

Runs the ABAP side on the developer's own machine — the ICF tree, the Gateway, the apps and the database as one unit started from a clone, a container, a single binary or a browser page — and lets Eclipse ADT and vsp edit the source in it as they would a system, with every change landing on the git tree as abapGit files.

pokrakam/abapDevSysInit

Runs as a checklist of setup actions, from the user profile and a GitHub RFC destination to abapGit Standalone and a configured pull of repositories, to take a freshly provisioned ABAP Developer Edition or trial system towards a working development setup.

A Standard ABAP coverage assessment has not been written. View all flavors

Artifacts2

2 of 2 artifacts
ArtifactSignals
Apps2
open-steamgateLocal ABAP server serving /IWBEP/ OData v2 without an SAP system
Signals
Functional boundary
pokrakam/abapDevSysInitABAP report setting up a new ABAP Developer Edition or trial system
Signals
Quiet+1

Details

Coverage
statecommunity only, ABAP, Standard ABAP, derived
also inCAP
For your agent
Ref
capability:local-development
JSON
/capabilities/local-development.json
MCP
Connecting an agent