
If you start a local ATC check with Check > ABAP Test Cockpit, then the standard check variant determines which checks are run.
The standard check variant in your satellite development system may have been set by the central ATC administrator. If no such setting has been made, then it is the DEFAULT check variant of the Code Inspector (transaction SCI).
But you can choose the check variant for a local ATC run. That way, you can run your own set of checks, perhaps a more stringent set than the corporate standard.
To choose the check variant for a local ATC check, do the following:
Select the repository object to check. For example, you might want to check the contents of a package in the navigation panel of transaction SE80.
Choose Check > ABAP Test Cockpit with ...
Switch to the Options tab to specify the check variant to use.
Use the F4 input help in field Code Inspector Check Variant to choose from the globally-visible check variants in your system.
Global check variants are defined in the Code Inspector, transaction SCI.
Choose Execute Checks to start the local ATC run. The check variant that you have chosen is used only for this run. Other runs revert to the system default check variant, unless you once again choose a different check variant.
See also Running Local Quality Checks with the ATC for details on working with ATC results and findings.