Hierarchy
SAP_BASIS (Software Component) SAP Basis Component⤷
BC-CCM-MON (Application Component) Monitoring⤷
SAPWL_FRONTEND (Package) SAP: Workload Display, Enjoy & OO Version - ST03N
Basic Data
| Data Element | SWLNPRESYS |
| Short Description | N3 Workload: Name or ID of Preceding Component |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | CHAR32 | |
| Data Type | CHAR | Character String |
| Length | 32 | |
| Decimal Places | 0 | |
| Output Length | 32 | |
| 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 | Prec.Comp. |
| Medium | 20 | Preceding Component |
| Long | 30 | Name of Calling Component |
| Heading | 40 | Name or ID of Calling Component |
Documentation
Definition
This field specifies the name or ID of the component that called the component in which the statistics record was read.
Use
A main concern of Distributed Statistic Records is to be able to trace transactions over distributed system landscapes and determine the cause of workload or resource bottlenecks in a component. This is done as follows:
In the first component that writes statistics and in which a transaction runs (the initial system), a transaction ID is created. This ID is stored in the statistics main record, and is passed to successor components, in which this transaction runs using the passport. The transaction ID is therefore unique in the statistics records for a transaction beyond component boundaries.
The passport is transferred in SAP Web Application Server 6.20 using the RFC and DIAG communiation paths and contains, for example, information about the initial action and the initial user that started the transaction. Both are retained over the entire transaction. In the initial system, the action and the initial action and the user and the initial user in the first statistics main record for a transaction match those in the associated passport.
A DSR component registers itself at startup with a central monitoring system (Release status at least SAP Web Application Server 6.20). When it does so, it identifies itself with a Namen/ID and its component type. The name must be unique within the monitored system landsscape. The component type is specified for the component during the implementation of the DSR, and is then binding for all installations of a component of this type.
A component writes the name with which it has registered itself to the Predecessor field, and possibly to the Initial component field of the Passport.
Dependencies
Example
- In ABAP systems, the name of the component is the system ID.
- To allow unequivocal identification, the Internet Transaction Server also stores the host of the corresponding server.
History
| Last changed by/on | SAP | 20040312 |
| SAP Release Created in | 620 |
