Transport management
Moving changes between ABAP systems as transport requests: collecting the objects a change needs into one, copying a request to a test system before it is released, and seeing what a request carries. Getting objects into git is source controlSource controlKeeping source code and development objects in version control, comparing their revisions, and moving them between development environments. Managed delivery of changes belongs to transport management.SAP and community, community owns it, and reading what changed is code reviewCode reviewReading a change before it moves on: which files or objects a change contains, what changed in each since an earlier version, and what a reviewer decided about each part. Comparing two versions of one object is where it starts; the review is the record kept of the decision.SAP and community, unassessed.
Showing artifacts, examples and content with confirmed ABAP Cloud applicability. View All ABAP
Overview
In the SAP BTP ABAP environment, gCTS moves a software component between systems in one global account through the Manage Software Components app: releasing its transport request and exporting the component to the target instance, DEV to TEST to PROD. In SAP S/4HANA Cloud Public Edition, developer extensions are still recorded on workbench transport requests and business configuration on customizing transport requests, and Export Software Collection bundles the extensibility items a key user or developer assigned to a collection for Import Collection to bring into the next tenant.
Not covered: gCTS does not cross a global account: it can move a software component between systems inside one account only, never into another. A Software Collection export carries the extensibility items assigned to it, not a snapshot of the rest of the system.
No community artifact is documented here.
Artifacts
Details
Coverage
For your agent
- Ref
capability:change-promotion- JSON
- /capabilities/change-promotion.json
- MCP
- Connecting an agent