SAP ABAP Data Element SUTR_EPP_EVALUATION (Evaluate Extended Passport)
Hierarchy
SAP_BASIS (Software Component) SAP Basis Component
   BC-SEC-AUT-PFC (Application Component) ABAP Authorization and Role Management
     S_PROFGEN (Package) ABAP Role Administration (Profile Generator)
Basic Data
Data Element SUTR_EPP_EVALUATION
Short Description Evaluate Extended Passport  
Data Type
Category of Dictionary Type     Direct Type Entry
Type of Object Referenced     No Information
Domain / Name of Reference Type      
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 EPP 
Medium 20 Evaluate EPP 
Long 30 Evaluate Extended Passport 
Heading 40 Evaluate Extended Passport 
Documentation

Definition

The "Extended Passport" is part of the ABAP statistics records; a kernel function that records every dialog step with technical information, such as transaction, response time, or CPU time. You can use transaction STAD to display the individual statistics records.

The "Extended Passport" is particularly of interest because it provides cross-system information about the original initiator of an action. The relevant elements for evaluating the trace are:

Using the "Extended Passport", you can assign authorization checks in SAP ERP systems to initial actions, which can be particularly helpful when calling RFC function modules from remote systems.

The default setting for the evaluation of the "Extended Passport" is inactive, because the evaluation can be time-consuming due to the large number of ABAP statistics records.

The statistics records are written in the file system of the relevant instance, and are regularly overwritten (by default, every 48 hours). It is therefore no longer possible to evaluate older authorization checks.

Use

Dependencies

Example

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