Functions and Structure of DSRs 

While statistics records for an ABAP system can only trace actions that are processed by ABAP components, with DSRs you can trace actions that are processed using the non-ABAP components J2EE, ITS, and BC.

There is a passport that is sent together with every communication to allow this. Among other things, the passport contains a GUID that is generated with a new Logical Unit of Work (LUW) ‑ in the case of the J2EE Engine, with a new session ‑ and which is used when calling other components within the LUW. By evaluating the DSRs and the passport information contained in them globally, you can collect and analyze all of the data for a LUW.

Structure

A DSR (= an action) consists of a main record and the subrecords connected to it:

·        Main Record (Main)

The main record contains performance and administration information about the action of a component.

·        Certificate Subrecord (Cert Subrecord)

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.

·        Call Subrecord

The call subrecord contains information about the called component. There can be any number of call subrecords for each main record.

For more information about writing and the structure of DSRs, see DSR Example: Simple Transaction Step.