SAP ABAP Data Element SATC_D_AC_SETUP_SYSTEM_POLICY ('ABAP Check Layer' per system / or per client)
Hierarchy
☛ SAP_BASIS (Software Component) SAP Basis Component
   ⤷ BC-DWB-TOO-ATF (Application Component) ABAP Test Frameworks ( ATC, CheckMan, Code Inspector)
     ⤷ SATC_ABAP_CHECK_DDIC_TYPES (Package) INTERNAL: - *NO* REUSE - Type definitions
Basic Data
Data Element SATC_D_AC_SETUP_SYSTEM_POLICY
Short Description 'ABAP Check Layer' per system / or per client  
Data Type
Category of Dictionary Type D   Domain
Type of Object Referenced     No Information
Domain / Name of Reference Type SATC_AC_SETUP_SYSTEM_POLICY    
Data Type CHAR   Character String 
Length 1    
Decimal Places 0    
Output Length 1    
Value Table      
Further Characteristics
Search Help: Name    
Search Help: Parameters    
Parameter ID   
Default Component name    
Change document    
No Input History    
Basic direction is set to LTR    
No BIDI Filtering    
Field Label
  Length  Field Label  
Short 10 Sy. cient 
Medium 15 System client 
Long 20 Use system client 
Heading 25 Use System Client 
Documentation

Definition




ATC in general is technically client independent. With the System Policy set to 'Appearance per Client' the ABAP Check Layer of ATC seems to be client dependent.

  • 'Per Client' enables individual configuration of the 'ABAP Check Layer' per client. Only results created within the client are displayed by default.
  • 'System Wide' enables that the settings of the 'ABAP Check Layer' are identical for all clients. Results are visible regardless in which client they have been computed.

Use

This setting can only be changed in the system client (000).

Restrictions

Settings that are related to other system functions depend on the capabilities of these functions

  • The behavior on 'transport tools' is fixed per system.
  • In the ByDesign landscape RFC destinations are client dependent. The ATC setup specifies RFC destinations. For this RFC destination it is recommended to configure them in all clients of a ByDesign system identical.
  • Technically most of the ATC repositories are client independent. The 'System Policy' only takes effect one the few aspects described above. The 'ABAP Check Layer' only appears to be client dependent.

Most of the ATC repositories are client independent. The 'System Policy' basically makes the ABAP Check Layer to appear to be client dependent. The System Policy does not provide a technical content separation!

The data of the ''Base Layer' (e.g. the monitoring data in transaction ATC_A) is fixed visible in all clients.

History
Last changed by/on SAP  20140117 
SAP Release Created in 732