ATC Central and Local Check Runs

The ATC distinguishes between central and local check runs.

A central check run is any ATC run that you start from transaction ATC, the ATC administrative transaction. A central check run is visible to all users, and you can designate it as the active check run.

With respect to central runs:

• You can define a set of objects to check. You can save such an object set definition for reuse.

• You can replicate a central run from an ATC master system to a satellite development system.

• You can designate a central check run as the active check run. You can make a central run the active run no matter where you start it, on an ATC master system or on a satellite development system.

• In the standard ATC set up, developers can apply for exemptions for findings in central runs.

• Central runs are organized in ATC series. A series lets you save ATC start parameters, including the object set to check and the check variant. You can start new instances of a central check in a series. The ATC keeps a history within the runs in a series of when an ATC finding first was found.

A local check run is started by a developer from one of the development transactions (SE80, SE24, SE38...). A developer runs a local check for his or her own use; it remains available for viewing in the ATC Result Browser under the developer's user ID. The developer can run a check for individual repository objects or for sets of objects chosen from the navigator pane of transaction SE80, the Object Navigator, as well as from other major ABAP Workbench transactions (SE24, SE38, SE11, and so on).