Now accepting guest editorial from SAP, Oracle, Workday and ServiceNow practitioners.Pitch a guide
The Sign-Off Table

Lesson 3 of 5

Central and remote ATC checks

9 min

Listen to this lesson

0:00 / 7:47

Checks improve with every SAP release, but your older systems do not get them automatically. Remote ATC solves that: a central check system on a recent release runs its checks against code in one or more checked systems, reaching them over RFC. The checked systems only need small remote stubs and the right notes; the check logic, the variants and the results live centrally. Community guides by SAP describe one central system checking many systems on various releases, and SAP's BTP documentation describes using the SAP BTP ABAP environment itself as a central check system for on-premise code.

  1. Central check systemRecent release, holds variants, runs checks, stores results and exemptions
  2. RFC destinationOne per checked system, usable without a logon dialog
  3. Checked systemRemote stubs and notes installed; provides code to the central system
  4. Run seriesScheduled runs of a variant against an object provider for the checked system
  5. ResultsReviewed centrally; developers jump from a finding to the code in the checked system
Remote ATC: one central system, many checked systems.
The Sign-Off Table · thesignofftable.com/academy/sap-abp-204

Why Contoso used it

Contoso's custom code lives in ECC systems ED1, EQ1 and EP1, which cannot run SAP S/4HANA readiness checks themselves. For the conversion, Sam set up a small standalone central ATC system, CMX, on a current release, loaded SAP's simplification content and ran the readiness variant remotely against ED1. The findings drove the custom code adaptation work before and between mock conversions. SAP Learning describes the same job from the other side: after conversion, developers run ATC with SAP S/4HANA checks in ADT, use quick fixes where available, and rerun because ATC only checks syntactically correct objects.

ED1 cannot run SAP S/4HANA readiness checks itself, so CMX pulls its custom code over RFC and runs the checks centrally.
The Sign-Off Table · thesignofftable.com/academy/sap-abp-204
Setup elementWhat community and SAP guidance says to check
Central system releaseRecent SAP_BASIS; guides cite 7.52 or later for current remote checks. Confirm for your scenario
Checked system releaseCan be much older; the check logic runs centrally
RFC destinationWorks without a logon dialog; test it in SM59; the user has enough RFC authorization
Notes and contentApply the notes SAP lists for remote checks; keep simplification content current for readiness runs
Object providerPoints to the checked system and the custom packages (Z*, Y*, namespaces)
Not every check works remotelyOnly checks enabled for RFC-based checking can be selected

Remote ATC setup checklist, summarized from SAP community setup guides. Notes and minimum releases change; verify for your release.

The developer scenario

Remote checks are not only for big readiness runs. In the ATC developer scenario, a developer works in the checked system as usual, but the system's ATC configuration names a central system as the reference check system, so every local ATC run uses the central checks. SAP's BTP documentation describes this setup with the SAP BTP ABAP environment as the central system: communication arrangements SAP_COM_0464 and SAP_COM_0936, an RFC connection through the Cloud Connector, a proxy check variant in the checked system and an SAP Note in the checked system. Developers then create exemptions in ADT's ATC Problems view and quality experts manage them in the central Approve ATC Exemptions app.

In the developer scenario, developers work as usual while every ATC run is executed by the central system, where exemptions are also approved.
The Sign-Off Table · thesignofftable.com/academy/sap-abp-204
Local ATCRemote mass runsDeveloper scenario
Where checks runIn the development systemIn the central systemIn the central system
Who starts runsDevelopersQuality lead, scheduledDevelopers, as usual
Best forSystems on a current releaseReadiness and estate-wide reportsOlder systems needing current checks daily
Exemptions liveLocallyCentrallyCentrally
Three ATC setups and when each fits.
The Sign-Off Table · thesignofftable.com/academy/sap-abp-204

What would you do?

Grace asks why Contoso needed CMX at all, when CMD (SAP S/4HANA 2025) already has the newest checks. What is the best answer?

Key points
  • Remote ATC runs current checks centrally against code in older checked systems over RFC.
  • Check releases, notes, RFC destinations and object providers before the first run.
  • Not every check is available remotely.
  • The developer scenario lets developers in a checked system use central checks daily.
  • The SAP BTP ABAP environment can act as the central check system for on-premise code.

Check your understanding · not graded

Lesson check

  1. 1. How does a central ATC system reach a checked system?

  2. 2. Why did Contoso run readiness checks remotely against ED1?

  3. 3. In the developer scenario, where are exemptions managed?

  4. 4. Which statement about remote checks is true?