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.
Overview
Table TVARVC holds variables for report variants, maintained per client with transaction STVARV; changing a value there changes every variant that uses it.
Not covered: At variants. SAP documents TVARVC as a source of values for selection screens in background processing; reading typed values, structures and tables from program code is not part of it, and that is where the ABAP libraries sit.
Libraries that keep parameters and constants out of ABAP code, as wrappers around TVARVC or replacements for it, such as abaKabaKA beta library for ABAP constants that lets each program register its own source, a custom table or CSV, XML or JSON content from a URL, standard text, server file or remote system, rather than one shared table.independent, abap and aqoaqoA library for defining ABAP application options as a structure or class, with change history, transport integration and a maintenance UI generated from that description, instead of SM30 tables or STVARV.independent, abap, and config-managementconfig-managementKeeps the theme, UI5 bootstrap source, custom CSS and Content-Security-Policy of an abap2UI5 page in database tables instead of in code, with a popup app to edit them.community org, abap from abap2UI5 addonsabap2UI5-addonsmaintains 21 entriesindependent, which keeps the theme, CSS and Content-Security-Policy settings of an abap2UI5 page in database tables.
Artifacts
Details
Coverage
For your agent
- Ref
capability:configuration- JSON
- /capabilities/configuration.json
- MCP
- Connecting an agent