SAP ABAP Data Element ALSMSGCUSV (Alert: Status attribute type variant: value)
Hierarchy
☛
SAP_BASIS (Software Component) SAP Basis Component
⤷ BC-CCM-MON (Application Component) Monitoring
⤷ SMOI (Package) CCMS: Monitoring Architecture
⤷ BC-CCM-MON (Application Component) Monitoring
⤷ SMOI (Package) CCMS: Monitoring Architecture
Basic Data
Data Element | ALSMSGCUSV |
Short Description | Alert: Status attribute type variant: value |
Data Type
Category of Dictionary Type | Direct Type Entry | |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | ||
Data Type | INT4 | 4-byte integer, integer number with sign |
Length | 10 | |
Decimal Places | 0 | |
Output Length | 11 | |
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 | AlStAtCusV |
Medium | 15 | Al StatAttrCusV |
Long | 20 | AlertStatAttrCusVal |
Heading | 0 |
Documentation
Shows whether to "shift" the criticality of a status message before checking whether to trigger an alert based upon the message. "Shifting" the criticality of a message allow programmers of data suppliers and users to control how and whether status messages result in alerts.
Possible shifting modes include for example:
- Leave the default criticality of a message unchanged (accept the criticality as reported)
- Shift "red" criticalities to "yellow" (allow only yellow alerts)
- Shift "yellow" criticalities to "red" (allow only red alerts)
- ...
The mode is a customizing attribute that can be set separately for each status attribute. Possible values are specified in the ABAP member RSALEXTI.
History
Last changed by/on | SAP | 20130604 |
SAP Release Created in |