Hierarchy
⤷ BC-CCM-MON (Application Component) Monitoring
⤷ SAPWL_FRONTEND (Package) SAP: Workload Display, Enjoy & OO Version - ST03N
Basic Data
Data Element | SWLNLUWSTEP |
Short Description | N3 Workload: Number of Transactions |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | SAPWLP15 | |
Data Type | DEC | Counter or amount field with comma and sign |
Length | 15 | |
Decimal Places | 0 | |
Output Length | 19 | |
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 | # Transact |
Medium | 15 | # Transactions |
Long | 20 | No. Transactions |
Heading | 40 | Number of Transactions |
Documentation
Definition
A transaction is a group of logically connected requests. A business process should usually be combined in a transaction.
Use
The start and end of a transaction are identified in the Distributed Statistics Records. This means that the number of transactions can, for example, be determined by actions or users during the aggregation.
Dependencies
In some components, it is not possible to identify the start and end of the inbound requests of a business process. The term "transaction" must be redefined in these components.
Example
In the Internet Transaction Server, it is not possible to identify the business process using the inbound requests. In the Distributed Statistics Records (DSR) for the ITS, all actions within a user logon (session) are therefore combined into one transactions.
In ABAP systems, a transaction starts with the call of the new transaction, a previous update or commit, and also ends with these actions. It is also known as a Logical Unit of Work (LUW).
History
Last changed by/on | SAP | 20040312 |
SAP Release Created in | 620 |