Hierarchy

⤷

⤷

Basic Data
Data Element | SWLNIUSERN |
Short Description | N3 Workload. Initial User (Triggered Transaction) |
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 | Init. User |
Medium | 17 | Initial User |
Long | 30 | Initial User |
Heading | 40 | User (ID) in Initial System |
Documentation
Definition
This field contains the name or ID of a user with which it is logged on to the initial component (the component within a transaction that is first to record statistical data).
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.
Dependencies
It is a prerequisite that the user logs on to the component with an ID.
Example
- In the Internet Transaction Server, this is the ID of the logged-on user.
- In ABAP systems, the ID of the logged-on user can also be the ID defined in an (RFC) destination.
History
Last changed by/on | SAP | 20040312 |
SAP Release Created in | 630 |