SAP ABAP Data Element ALVALUEBTCMON (Severity of the Alert for Non-Existent Jobs)

Hierarchy

☛ SAP_BASIS (Software Component) SAP Basis Component
   ⤷ BC-CCM-MON (Application Component) Monitoring
     ⤷ SMOI (Package) CCMS: Monitoring Architecture

Basic Data

Data Element	ALVALUEBTCMON
Short Description	Severity of the Alert for Non-Existent Jobs

Data Type

Category of Dictionary Type	D	Domain
Type of Object Referenced		No Information
Domain / Name of Reference Type	ALVALUEBTCMON
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	Alert Val.
Medium	15	Alert Value
Long	36	Alert Value for Non-Existent Jobs
Heading	10	Alert Val.

Documentation

The severity of the alert if there is no released job with the specified name pattern.

By default, an (as yet) unscheduled job is not regarded as an error in job monitoring. The job monitoring reports "no released job exists" as a green alert.

To identify terminations of job chains and generate appropriate alert messages, it can be useful to classify the message "no released job exists" as a warning or as an error.

The following key figures describe the behavior of the job monitoring if no released job exists for a name pattern.

• 0 = Default, it is insignificant, if there is no released job
• 1 = Green means it is insignificant if there is no released job
• 2 = Yellow, warns if there is no released job
• 3 = Red, an unreleased job represents a severe problem.

You should specify the severity level in accordance with these classifications.

History

Last changed by/on	SAP	20060330
SAP Release Created in	732