Lesson 5 of 5
ATC as a transport release quality gate
10 min
Listen to this lesson
Running ATC is useful; making it a gate changes behavior. When ATC checks run automatically at transport release and block requests that carry serious findings, nobody has to remember to check, and nobody can quietly ship a priority 1 problem to CMQ. Set up well, the gate is invisible on good days and decisive on bad ones.
- Developer releases the taskOptionally checked too, if task-level checks are switched on
- Request releaseATC runs the configured variant over the request’s objects
- Findings evaluatedApproved exemptions are masked; remaining findings compared to the blocking priorities
- BlockedPriority 1 or 2 findings: a pop-up lists them; the request stays open
- ReleasedNo blocking findings: the request is exported for import into CMQ
Setting up the gate
Guidance from SAP PRESS and SAPinsider describes the classic setup. In transaction ATC, under the basic settings, activate object checks at request release and set the behavior on release in the transport tool integration section; the option to block on priority 1 and 2 errors is the one SAP is reported to recommend. In the Transport Organizer's global customizing (transaction SE03), activate checks of objects when a request is released. Checks at task release are not blocking by default; SAP PRESS cites SAP Note 2495410 for adding them, with a warning about the overhead. In the SAP BTP ABAP environment, the Configure ABAP Test Cockpit app sets the priority levels that block or interrupt transport releases.
| Setting | Where | Contoso choice |
|---|---|---|
| Object checks at request release | ATC basic settings | Globally activated in CMD |
| Behavior on release | ATC, transport tool integration | Block on priority 1 and 2 |
| Check objects when request released | SE03 global customizing | Globally activated |
| Checks at task release | Note-dependent option | Not used: developers run ATC in ADT before task release |
| Global check variant | ATC basic settings | ZCMC_CLOUD_DEV and ZCMC_CLASSIC_DEV by package scope, per local configuration |
Contoso’s gate configuration in CMD (illustrative; menu names vary by release).
Limits to know
- The gate checks objects in transport requests. A SAPinsider walkthrough notes it does not apply to transports of copies, which some teams use for test imports.
- The gate is only as strict as the variant and the exemptions behind it; review both.
- Converted code may carry many old findings. Agree a time-boxed approach, for example narrow, dated exemptions for legacy findings, so the gate blocks new problems without stopping every change.
- An emergency fix still goes through the gate; if a finding must be accepted, it needs an emergency exemption approved by a named person and reviewed afterward.
- Did the request get blocked?Yes → read the findings in the pop-up or ATC Problems · No → proceed to import
- Is the finding real?Yes → fix the code, rerun ATC, release again · No → request a narrow exemption with a reason
- Is this an emergency fix for production?Yes → emergency exemption with named approval and a review date · No → normal approval
- Is the same check blocking many requests?Yes → review the variant or the code pattern with Kenji · No → handle case by case
Gate metrics
A gate produces data worth reporting. Contoso tracks, per release: requests blocked at first release, the most frequent blocking checks, exemptions approved and their scope, and time from block to release. Rising blocks on one check usually point to a training need or a noisy check; rising exemptions point to a gate that is losing its teeth. Priya includes the figures in the release quality report next to defect counts, and the change records in SAP Cloud ALM carry the ATC result for each request.
What would you do?
On the Saturday of the go-live cutover, an urgent fix for the deposit report is blocked by a priority 2 performance finding. Luis asks Sam to switch the gate off for an hour. What is the best response?
- A gate runs ATC at transport release and blocks requests with blocking-priority findings.
- Activate checks in ATC basic settings and SE03; block on priority 1 and 2.
- Task-level checks need extra setup; the gate does not cover transports of copies.
- Handle emergencies with narrow, approved, dated exemptions, never by switching the gate off.
- Report gate metrics with each release.
Check your understanding · not graded
Lesson check
1. Which behavior-on-release option is SAP reported to recommend?
2. Where are object checks at request release activated in the Transport Organizer?
3. Which transports does the ATC gate not apply to, according to a SAPinsider walkthrough?
4. An urgent fix is blocked during cutover. What is the right path?