SAP ABAP Parameters Monitoring

SAP ABAP Parameters Monitoring

This monitor supervises SAP ABAP profile parameters per application server,
with rule-based alarms on value mismatch, value drift, and non-default configuration.

What Can Be Monitored

You can detect and alert on:

Parameter value mismatch against an expected value
Parameter runtime changes between executions
Parameter values that differ from SAP default values

This supports proactive detection of configuration drift and policy deviations across ABAP instances.

Monitored Data

The monitor collects ABAP parameters and evaluates, per application server:

Parameter name
Current value
Default value

Configuration Hints

One surveillance row targets one ABAP parameter name.
Param name must be explicit (* is not valid and should not be used).
Set Expected value to * to disable value-matching for that row.
Enable Check changes to detect value drift since previous run.
Enable Check default to detect values different from SAP defaults.
If Severity is disabled, the matching row is ignored for alarms.
Auto clear controls whether emitted alarms are clearable.
Alarm controls alarm generation for the row.
Report controls evaluation in report mode.

Configuration

Surveillance Table

Field	Required	Default	Description
Active	Yes	`true`	Enables/disables this surveillance row.
Param name	Yes	(empty)	Exact ABAP parameter name to monitor.
Expected value	Yes	(empty)	Expected value/pattern. If set to `*`, value mismatch checking is disabled.
Default value	Yes	(empty)	Display/reference column populated from collected data (hidden in UI).
Expected unsub value	No	`*`	Reserved hidden field; currently not used for alarm generation.
Check changes	Yes	`false`	Alarm if current parameter value changed compared to last stored run value.
Check default	Yes	`false`	Alarm if current value is set and differs from SAP default value.
Severity	Yes	MAJOR	Alarm severity used when a condition is met.
Auto clear	Yes	`true`	Alarms generated by this monitor are clearable when condition recovers.
Alarm Tag	No	(empty)	Optional custom alarm tag/prefix.
Alarm	No	`true`	Enables/disables alarm generation for this row.
Report	No	`false`	Enables/disables evaluation of this row in report mode.

Alarm Conditions

For each active surveillance row matching a parameter:

Expected value alarm: triggered when current value (or default value if current value is empty) does not match Expected value and Expected value is not *
Check changes alarm: triggered when current value differs from previously stored value
Check default alarm: triggered when current value is not empty and differs from default value

Generated Alarms

Alarm messages include parameter and application server context, for example:

Parameter <param> set to <currentOrDefault> instead of <expected> on <appServer>
Parameter <param> changed from <previous> to <current> on <appServer>
Parameter <param> set to <current> instead of <default> (Default) on <appServer>

Example

Active	Param name	Expected value	Check changes	Check default	Severity	Auto clear	Alarm Tag	Alarm	Report
true	`rdisp/wp_no_dia`	`20`	false	false	MAJOR	true	`ABAP,CAPACITY`	true	false
true	`abap/heap_area_dia`	`2147483648`	true	false	Minor	true	`ABAP,MEMORY`	true	false
true	`login/min_password_lng`	`*`	false	true	WARNING	true	`ABAP,SECURITY`	true	false

Resulting alarms:

Parameter rdisp/wp_no_dia set to 18 instead of 20 on DVEBMGS00
Parameter abap/heap_area_dia changed from 1073741824 to 2147483648 on DVEBMGS00
Parameter login/min_password_lng set to 6 instead of 8 (Default) on DVEBMGS00

Table of Contents