Source control for ABAP
Getting ABAP objects out of a system and into git, and back into another system — the closest thing ABAP has to a package manager.
Showing artifacts, examples and content with confirmed Standard ABAP applicability. View All ABAP
Overview
No SAP artifact is confirmed here for Standard ABAP.
A Standard ABAP coverage assessment has not been written. View all flavors
Clones, pulls and pushes ABAP objects between a system and a git repository, from inside the system.
Covers the entries of a transport that abapGitabapGitA Git client written in ABAP that runs inside the system, so objects are cloned, pulled and pushed without leaving it; with no package manager in ABAP, a cloned repository is how code is distributed.community org, abap does not serialise. Table rows (TABU, TDAT, VDAT, CDAT), report variants, authorization profiles, old OTR texts, ALV layouts and SAP Note entries are written as JSON under content/ in the same commit as the objects under src/, and the report ZTR_APPLY_CONTENT reads them back into another system, recording the keys on a transport request first and then writing the rows. What neither abapGit nor ZCL_TR_CONTENT can write is listed on the pull request under "Not in Git", and the setting ZTR_REQUIRE_COMPLETE turns that listing into a refused release.
A Standard ABAP coverage assessment has not been written. View all flavors
Artifacts
Content
Details
Coverage
For your agent
- Ref
capability:abap-source-control- JSON
- /capabilities/abap-source-control.json
- MCP
- Connecting an agent