Show TOC

 PassportLocate this document in the navigation structure


If the system is generating Distributed Statistics Records (DSRs), that is, of statistical records of the instrumented non-ABAP systems, the passport is sent during communication between the components. Among other things, the passport contains a GUID that is generated with a new Logical Unit of Work (LUW) and which is used when calling other components within the LUW. By evaluating the DSRs globally, you can collect and analyze all of the data for a LUW. The passport contains a trace flag with which performance trace information can be written for every component involved in a LUW for exactly this LUW. 



The passport corresponds to the certificate subrecord (cert subrecord) of the DSR and contains the following fields:

  • TransID/GUID
  • TraceFlag to the set the trace flag
  • Initial SysID/ComponentID with the ID of the initial system or initial component
  • Initial ServiceType with the initial service type
  • Initial Action with the initial action
  • Initial ActionType with the initial action type
  • Initial UserID with the initial user ID.

    These fields are only filled when the passport is created. All subsequent components leave these fields unchanged.


  • PreSysID/PreComponentID with the ID of the previous system or previous component



The ID of the previous system or previous component is always filled with a system or component's own ID before the passport is sent. This means that the direct predecessor can be identified when the passport is received.


  • The functional trace (transaction STATTRACE) can filter raw statistics records using the data of the certificate subrecord (also known as client info record). To do this, you must enter the appropriate values in the data selection input parameters.
  • The figure below shows how the passport is forwarded and linked to the relevant statistics records:



  1. The passport is created in the component in which a LUW is initiated. In this example, this is the J2EE Engine. The J2EE Engine sends the passport to the ABAP system and writes a call subrecord.
  2. The ABAP system receives the passport and stores its data as a certificate subrecord. It calls another component, for which a call subrecord is written.
  3. The passport is transferred to another component during the RFC call and the certificate subrecord is written in turn into the statistics there.
  4. The complete statistics records are transferred to the central monitoring system (CEN) and displayed.