Hierarchy
SAP_BASIS (Software Component) SAP Basis Component⤷
BC-CCM-MON-SLG (Application Component) SAP System Log⤷
SLOG (Package) System log
Basic Data
| Data Element | RSLGUSER |
| Short Description | System log: SAP user name |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | CHAR12 | |
| Data Type | CHAR | Character String |
| Length | 12 | |
| Decimal Places | 0 | |
| Output Length | 12 | |
| 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 | User |
| Medium | 15 | User |
| Long | 35 | User |
| Heading | 12 | User |
Documentation
Definition
Name of a SAP user
Note
User names are client-specific. This means a user with the same name could be created in a different client for a different person.
The system uses the following IDs in the system log for R/3 System processes that cannot be assigned explicitly to one user name:
SAPSYS
Background control actions. SAPSYS is used by all background processes not started by a user. These are processes started due to an event or at a particular time, for example. You may also find system log messages from user-controlled parts of the system (job scheduling) under user IDs.
CPIC
Actions started on one instance by another instance.
<leer>
Actions outside 'actual processing'. (For example, system start, or cleanup actions)
Operating system user names
Actions in a program that occur before the SAP user and authorization system has been activated. Operating system user names can usually be recognized in that they contain uppercase and lowercase letters.
History
| Last changed by/on | SAP | 19950209 |
| SAP Release Created in |
