Source control for ABAP
In the BTP ABAP environment and S/4HANA Cloud, this splits in two: gCTS moves objects between DEV, TEST and PROD inside one global account through the Manage Software Components app, and a cloud-preinstalled build of 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 crosses account boundaries, migrating on-premise code in and sharing code out, restricted to the object types the cloud programming model releases.
Showing artifacts, examples and content with confirmed ABAP Cloud applicability. View All ABAP
Overview
SAP ships two git-based mechanisms in the ABAP environment: gCTS, the recommended way to move objects between DEV, TEST and PROD within one global account through the Manage Software Components app, and a cloud-preinstalled build of 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 for moving source code across global accounts and in from on-premise systems.
Not covered: gCTS stays inside a single global account, and the cloud abapGit build exports only the released ABAP object types the environment supports, skipping anything unreleased on push and routing Fiori UI artifacts through a separate git repository.
No community artifact is documented here.
Artifacts
Nothing is mapped here yet.
Seen working
Not in production: "This repository contains sample code which should not be used in production", and the README sends a production reader to the officially supported libraries instead.
Details
Coverage
For your agent
- Ref
capability:abap-source-control- JSON
- /capabilities/abap-source-control.json
- MCP
- Connecting an agent