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 | SWLNISERVI |
| Short Description | N3 Workload: Number of Initial Service Type |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | INT2 | |
| Data Type | INT2 | 2-byte integer, only for length field before LCHR or LRAW |
| Length | 5 | |
| Decimal Places | 0 | |
| Output Length | 5 | |
| 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 | I.Service |
| Medium | 15 | Init. Service |
| Long | 30 | Initial Service Type (Number) |
| Heading | 42 | Numerical Value of Initial Service Type |
Documentation
Definition
A service type characterizes the type of processing of a request in a component. This field specifies the number of the service type. The initial service type is the type within the transaction that records statistical data first.
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.
The service type is stored within the DSR as a number. During the registration of a DSR component in the monitoring system, the component must fill a conversion table with texts in english, that assign a name (short text) and a description (long text) to each number. When the data is displayed, the number of the service type is converted into the corresponding text.
Dependencies
If the conversion table was not filled (for example, due to errors during registration), the display transaction can only display the number of the action type. You can insert language-dependent texts in a translation table (see SAP Notes).
Example
For the first DSR instrumentation, the Internet Transaction Server has the service types WebGUI, FlowLogic, IAC, WebRFC, and unknown. An action is marked as of unknown type if it is running in one of the mixed modes (for example, WebGUI controls are displayed on IAC templates).
The service type of the DSR is comparable to the task type in ABAP statistics records. These have, for example, the types dialog, background , and update.
History
| Last changed by/on | SAP | 20130604 |
| SAP Release Created in | 630 |
