Compare ABAP package and delivery tools¶
ABAP teams can choose among source-control clients, manifest conventions, package managers, transport files, and SAP add-on tooling. They overlap, but they are not interchangeable.
This comparison focuses on the lifecycle of independently versioned ABAP software. It is based on public documentation available on 19 October 2026. A blank or limited capability is not a quality judgment: each tool has a different purpose.
Capability matrix¶
| Capability | TRM | abapGit | Raw CTS transports | SAINT/SPAM |
|---|---|---|---|---|
| Git-based ABAP source workflow | Integrates with source metadata | Yes | No | No |
| Named, semantic package releases | Yes | Tags/releases can identify source | Manual convention | SAP add-on/support-package levels |
| Installable release artifact | .trm artifact |
Serialized repository/archive | Transport files | SAR/PAT delivery |
| Version-range dependency resolution | Yes | Not by itself | No | Prerequisite add-ons/support packages |
| Lockfile with integrity values | Yes | Git commit pins source | No | Delivery tooling controls archives |
| Public/private registry protocol | Yes | Git hosting rather than a package registry | No | SAP delivery channels |
| CTS-based install/update | Yes | No | Yes, manually | Uses SAP add-on mechanisms |
| Customizing and translation transports | Yes | Limited to serialized object support | Yes | Yes |
| Transport-based uninstall | Yes | No dedicated deletion-transport lifecycle | Must be engineered manually | Only add-ons explicitly prepared as deletable |
| CLI and CI/CD workflow | Yes | abapGit offers APIs/background modes; integrations vary | External tooling required | Primarily SAP administration tooling |
How to choose¶
- Choose abapGit for an ABAP development workflow centered on Git repositories, branches, source review, and synchronization.
- Choose TRM when the unit you distribute must be a versioned artifact with dependencies, registry delivery, repeatable installation, and uninstall across CTS landscapes.
- Use raw CTS transports for landscape-controlled change movement when package identity, resolution, registry discovery, and lifecycle automation are handled elsewhere.
- Use SAINT/SPAM and AAK for SAP-style add-on and support-package delivery when their governance, assembly, and registration model fits the product.
Method and sources¶
Capabilities are marked only when a public source documents them. Product behavior can change, so verify before making an architecture decision:
Open a documentation issue or pull request with a source if any cell needs correction.
Continue from the comparison¶
- Understand the package-manager lifecycle
- Compare TRM and abapGit in detail
- Follow the five-minute quick start
- See how TRM packages move across an SAP landscape
Author: TRM maintainers. Technical review: Regesta Group engineering. Last reviewed: 19 October 2026.