Defining and Distributing a Standard Code Inspector Check Variant

In this release, the ATC runs in Code Inspector Compatibility mode. This means that you use Code Inspector check variants to control what the ATC checks, uses the Code Inspector priorities for messages, and so on.

For quality checking, you specify the Code Inspector variant(s) to use in the ATC administration transaction, ATC.

You can continue to define your Code Inspector profiles using the Code Inspector functionality. Or you can maintain your Code Inspector variants directly from transaction ATC.

If you already have a standard Code Inspector variant, then you need only ensure that this variant is present on each ATC master system and also on each satellite development system.

Note: Your standard variant should be present on each development system so that your developers use the same checks for local testing as you do for central quality checks.

You must ensure that your Code Inspector variants are defined as follows:

‘global’ (visible to all users) and
‘transportable’ (transportable with SAP transport requests).

If you do not have a standard Code Inspector variant, then you should define one. It should include all of the quality checks that you want to apply to your ABAP code.

Result:

You have defined one or more Code Inspector variants for performing the quality checks on your code that you want to have done.
You have distributed the Code Inspector variants to all of your central quality checking systems as well as to all of your development systems.

Both quality managers and developers will use the same Code Inspector variants and checks.