Code Inspector Compliance Mode and ATC Check Variants
The ATC runs in Code Inspector Compatibility mode. This means that you use Code Inspector check variants (transaction SCI) to control what the ATC checks, what priorities are assigned to messages, and so on.
Code Inspector compatibility mode protects the investment that customers have made in setting up quality checking using the Code Inspector. The customizing effort that customers have invested in the Code Inspector can be reused for ATC quality checking.
Code inspector compatibility mode also offers continuity in quality checking. You can keep using the same Code Inspector check variant after switching to the ATC. Your quality statistics before and after the switch remain comparable, with respect to Code Inspector checks, if not with respect to new checks that the ATC brings with it.
As the ATC administrator, you set the standard Code Inspector check variant for ATC runs. You do this in transaction ATC, the ATC management transaction in the ATC master system. And you make this setting as well in a satellite development system, and distribute it from there to other development systems.
If you do not set a standard check variant or none has been set in satellite development systems, then the ATC looks for a check variant under the name DEFAULT.
You must ensure that the standard check variant is of type 'global' and 'transportable' and that it is present on all ATC master and development systems. Should the ATC not find the default check variant in a system, then it issues an error message when a check run is started.
In a satellite development system, the default check variant is automatically used for local ATC checks, started by a developer. This feature ensures that the developer runs the same checks in the development system as the quality manager does in the central system.
A developer does have the ability, if desired, to specify a different check variant. For example, a developer might decide to run a more stringent set of checks than the corporate standard.
In a master system, the default check variant is used for central ATC check runs unless the quality administrator specifies a different check variant when starting the check run.