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 | SWLNWAITMTA |
| Short Description | N3 Wokload: Average Call Time per Transaction (ms) |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | SAPWLTIME1 | |
| Data Type | DEC | Counter or amount field with comma and sign |
| Length | 15 | |
| Decimal Places | 1 | |
| Output Length | 20 | |
| 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 | Ø CallTime |
| Medium | 17 | Ø Call Time (ms) |
| Long | 35 | Average Call Time/Transaction (ms) |
| Heading | 40 | Average Call Time per Transaction (ms) |
Documentation
Definition
This field specifies the average call time per transaction of all requests from a particular service, a particular action, or a particular user to a component. The time is given in milliseconds.
Use
Call time is comparable with the roll wait time of the ABAP statistics records. However, the roll wait time does not, for example, contain the database response time, which is measured specially there. In the task types ALE, RFC, and CPIC, the roll wait time is also calculated from the response time.
If a component that writes distributed statistics records calls another component, it measures the time that passes between calling the component and the response. This is also the case, for example, when the component calls a database. The total of all call times is stored in the statistics main record, if several calls are made to further components within one request.
Dependencies
To be able to determine the average response time per transaction, the component must set the transaction start and transaction end indicators. In some components, the start and end of a business process cannot be identified using the incoming requests. The term "transaction" must be redefined in these components (see also the field Number of transactions).
Example
The Internet Transaction Server can, for example, call a ABAP System or different module providers within user requests. The response time contains the total of the call times (Response times of the called components and network times) as well as the time that is required to send the response to the request to the WGate. The call times of the individual components come from the call subrecords.
History
| Last changed by/on | SAP | 20040312 |
| SAP Release Created in | 620 |
