SAP ABAP Data Element SATC_D_AC_RFC_2_MASTER_EXEMPT (RFC destination to master system for exemption process)
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_RFC_2_MASTER_EXEMPT
Short Description RFC destination to master system for exemption process  
Data Type
Category of Dictionary Type D   Domain
Type of Object Referenced     No Information
Domain / Name of Reference Type RFCDEST    
Data Type CHAR   Character String 
Length 32    
Decimal Places 0    
Output Length 32    
Value Table RFCDES    
Further Characteristics
Search Help: Name F4_RFCDESTYPEALL    
Search Help: Parameters RFCDEST   
Parameter ID RFC  
Default Component name    
Change document    
No Input History    
Basic direction is set to LTR    
No BIDI Filtering    
Field Label
  Length  Field Label  
Short 10 RFC Dest. 
Medium 15 Destination 
Long 20 Destination Exempt. 
Heading 40 Destination to Master for Exemptions 
Documentation

Definition

Use

Enter the name of the RFC destination to the ATC master system. The destination is used when a developer requests an exemption for a central ATC result. Such exemptions are managed on the master system.

The destination must be available on this ATC satellite system.

Dependencies

Example

SAP recommends using trusted RFC destinations for this connection. Trusted destinations have these advantages:

  • They allow developers to request exemptions without having to logon to the master system.
  • They use the authorizations associated with users, so that one destination can be used both by developers requesting exemptions and quality managers granting exemptions. You do not need to define a second destination for approving exemptions.

The prerequisite for this solution is that you set up user accounts for all of your developers on the master system. The user accounts must use the same user ID on both the satellite development system and the master system.

The alternative RFC solutions for this connection are as follows:

  • RFC destinations defined with a user and password.

    This strategy allows users to apply for exemptions without logging on to the ATC master system. It also means that you do not need to provide users for developers on the central system.

    But you must define an RFC user with carefully restricted authorizations. The master system has an 'open' RFC destination. And you must provide a separate RFC destination with a different user and different authorizations for approving exemptions.

  • You can provide a single RFC destination to the ATC master system and require developers and quality managers to log on explicitly to the master system.

History
Last changed by/on SAP  20130604 
SAP Release Created in 740