Statistics records are created to enable you to monitor the performance of an SAP System and its components. These statistics records provide information about the workload generated and the resources used in the system by actions. This provides you with a very exact picture of the quality of a system. The extension of this concept for non-ABAP components uses Distributed Statistics Records (DSRs). With DSRs, as with the statistics records for ABAP systems, you can trace actions that are processed over several components.
For this reason, there is a passport that is sent together with every communication. 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.
A DSR (= an action) consists of a main record and the subrecords connected to it:
The main record contains performance and administration information about the action of a component.
The certificate subrecord specifies the source of the LUW. The data contained in this subrecord forms the passport, together with the GUID. There is a maximum of one certificate subrecord for each main record.
The call subrecord contains information about the called component. There can be any number of call subrecords for each main record.
You can display the DSR in the monitoring SAP System using the Global Workload Monitor and the functional trace:
For more information, see Difference Between Functional Trace and Global Workload Monitor.