CapabilityOperations & RuntimeStandard ABAP, read from its artifacts

Configuration

On an ABAP system configuration is mostly values a program reads at runtime instead of hard-coding them: parameters, selection ranges and mappings kept in TVARVC or a custom table, some of them maintained directly in production without a transport.

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
config-management

Holds an abap2UI5 installation's page settings in database tables read at runtime through a cached service, globally or per user, so a theme, a bootstrap source, custom CSS or a Content-Security-Policy changes without a change to the HTTP handler code.

abaK

Lets a program register its own constants source instead of reading one shared table, with the content held in a custom table or read as CSV, XML or JSON from inline text, a URL, an SO10 text, a GS03 set, a server file or a remote abaK instance over RFC.

Sourceabapinho/abaK — READMEchecked
aqo

Builds a maintenance UI and change history for application options described as an ABAP structure, registered through zcl_aqo_option=>create.

Sourcebizhuka/aqo — READMEchecked

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

Artifacts3

3 of 3 artifacts
ArtifactSignals
Apps1
config-managementTheme, CSS and CSP settings of abap2UI5 pages kept in tables
Signals
Functional boundary
Packages2
abaKLibrary for managing ABAP constants from registered sources
Signals
Quiet+1
aqoABAP application options as a structure with a generated editor
Signals
none

Details

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