Hierarchy
SAP_BASIS (Software Component) SAP Basis Component⤷
BC-CCM-MON (Application Component) Monitoring⤷
SMOI_OO (Package) Object-Oriented Nesting of Monitoring Infrastructure
Basic Data
| Data Element | ALXMBINFOSUBTYPE |
| Short Description | Information Subtype for Monitoring Data |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | ALXMBINFOSUBTYPE | |
| Data Type | CHAR | Character String |
| Length | 40 | |
| Decimal Places | 0 | |
| Output Length | 40 | |
| 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 | Subtype |
| Medium | 15 | Subtype |
| Long | 20 | Subtype |
| Heading | 6 | Subtyp |
Documentation
Definition
The information subtype is a character-type ID that you can freely define, in contrast to the characteristics information class and information type. Together with these two values, it forms a unique key for identifying a message recipient. The potential recipients for messages for a particular combination of Information class/ information type are therefore only differentiated by theirinformation subtypes.
Use
If system errors occur in the Exchange Infrastructure, it can be useful to number the recipients sequentially using the information types, such as:
SYSERROR QOSBE 001 <User1>
SYSERROR QOSBE 002 <User2>
...
Every other character string is, of course, also permissible for subtypes. The only condition is that the combination information class/ information type/information subtype is unique.
The subtype plays a special role if application errors occur. It allows recipients to specify that only the errors of particular applications interest them. To do this, these applications must be registered with a namespace in the Landscape Directory of the Exchange Infrastructure. So that the recipient can be specified, the same namespace must be contained in the subtype. Assume that you were specifying recipients for errors of the APO application. In this case, all of the following entries would lead to a correct recipient specification:
APPERROR APPNAME APOxxxx <User3>
APPERROR APPNAME xAPOxxx <User4>
APPERROR APPNAME xxxxAPO <User5>
Dependencies
Example
History
| Last changed by/on | SAP | 20040312 |
| SAP Release Created in | 620 |
