Show TOC

Authorizations for the ABAP Test CockpitLocate this document in the navigation structure

You must ensure that the following users are set up with the authorizations needed for using the ATC:

  • Users with ATC administrator authorizations in the ATC master system and in satellite development systems.

  • Users with ATC developer authorizations in development systems and, if you are using trusted RFC connections, also in the ATC master system.

  • Users with ATC quality management authorizations in the ATC master system and optionally in development systems.

The user role templates for these users are shown below. Since the templates may not be directly assigned to users, you must create your own copies.

Authorizations for Administrators

Administrators need a customer-specific version of user role SAP_SATC_ADMIN for doing the following:

  • Setting up the ABAP Test Cockpit (ATC) for central quality checking

  • Performing recurring administrative chores.

Set up ATC administrators on both the ATC master system and on ATC satellite development systems.

Authorizations for Developers

Developers need only ABAP development (authorization object S_DEVELOP ACTVT 02 and 03) authorizations to use the ATC for running local ATC checks and requesting exemptions.

Set up developer users on both the development system and the ATC master system.

If you do not want to give development authorizations (for example, in an ATC master system), then you can substitute a customer-specific version of role SAP_SATC_XMTP_APPLICANT for the S_DEVELOP authorizations.

Authorizations for Quality Managers

Quality managers need a customer-specific version of user role SAP_SATC_QE in order to do the following:

  • Activate results of central ATC runs

  • Process active results

  • Approve or deny exemptions.

Quality manager users are required only on the ATC master system. But you may also want to create such users on development systems so that quality managers can work there as well.

Technical Users for RFC

If you choose to set up ATC RFC destinations in development systems with stored technical users for logging on to the ATC master system, then the technical users should have these roles:

  • For the logon user in the developer RFC destination to the ATC master system, only role SAP_SATC_XMTP_APPLICANT.

  • For the logon user in the quality manager RFC destination to the ATC master system, only role SAP_SATC_QE.

  • For the logon user for transfer of ATC results and exemptions between ATC master system and the development systems, only role SAP_SATC_ADMIN.

See also Setting Up RFC Communications.

More Information on Authorization Objects

The main authorization objects tested for ATC authorizations are as follows:

  • S_Q_ADM — General administrative and set up activities

  • S_Q_GOVERN — Profile maintenance, granting of exemptions, and sending of messages

Do you need detailed information on the ATC authorization objects? See transaction SU21 in your ABAP system. In transaction SU21, search for the authorization object for which you want documentation. Then double-click on the object. In the following screen, choose Display Object Documentation to see the online documentation.