Ansicht
Dokumentation

SATC_AC_SETUP - System setup - CheckMan flavor

TXBHW - Original Tax Base Amount in Local Currency   PERFORM Short Reference  
This documentation is copyright by SAP AG.

Purpose

Use the options on this screen to control how the ATC works in this system.

With the Transfer Data button, you can also transfer this data to another ATC system. You can read the data from the ATC central system, if you are on a satellite development system. Or you can write the data to a remote development system or another ATC central system, if you are on the ATC central system.

ATC Policy Settings and Clients

It is strongly recommend using the option "system wide settings". This will result that ATC behaves in all clients the same way.

Note that ATC results are also client-independent. A user can see his or her results on any client in which they have a user ID. And central results are visible on all clients.

The Master System and Satellite Development Systems

The Master system is a single system that hosts / owns the exemption data. There can be only one Master system in a landscape. Most often a landscape exists of development systems and a consolidation system. It is best practice to make the consolidation system the master system.

You will need to configure the ATC at both the master system and at satellite systems.

At the master system:

• Central ATC checks are run. Usually, such central ATC results are published to satellite development systems, so that developers can work with an official result.

• Exemptions from ATC findings are centrally maintained. Developers at satellite development systems who request an exemption do so via RFC at the master system.

A satellite development system is one which transports code to the master system, and at which the transported code is original. Central ATC checks at the master system check the quality of new and changed code from the development systems.

The configuration strategy is as follows:

• At the master system, you make settings that are also important in development systems, such as the default STANDARD check variant. But most of the configuration is for master system features of the ATC. And it is recommended that you do not transmit this configuration to development systems.

• In order to configure the satellite development systems, you use transaction ATC at one system to do all of the setup, taking over the master system settings where necessary (for example, for the default check variant).

Then you use the configuration transfer function on this screen to replicate the development system configuration to all of the other development systems that deliver code to the same ATC master system.

Configuration Options

The configuration options on this screen, briefly described, are as follows. See the F1 documentation of the individual options for more detailed help.

• Exemptions

In this frame, you set the policy for applying for exemptions. Usually this policy should be the same in both the master system and satellite development systems.

The RFC destinations are needed only in the development systems. Developers and optionally approvers use the destinations when they apply for exemptions, since these are managed at the master system.

For recommendations on the RFC setup, please see the ATC setup documentation.

• Various: In this frame, you specify the check variant that is used for .transport checks and default for workbench check runs. It is strongly recommended to use the same profile in all systems of a landscape.

• Transport Tool Integration: In this frame, you specify the policy for automatic ATC checking of objects in transport requests, when a request is released. s

Requirements

Authorizations: In order to configure the ATC, you need role SAP_SATC_ADMIN in your user. Here is complete authorization information.

• Administrator roles and authorizations

• QM roles and authorizations

• Developer authorizations

Further Information

Transport Organizer & Test Tools

ABAP Short Reference   ROGBILLS - Synchronize billing plans  
This documentation is copyright by SAP AG.

Length: 4887 Date: 20240520 Time: 113958     sap01-206 ( 135 ms )