SAP DB6_ALM_GET_ALERT_WEIGHT Function Module for DB6: compute alert weight of monitoring attribute

Search SAP Function Modules

DB6_ALM_GET_ALERT_WEIGHT is a standard db6 alm get alert weight SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for DB6: compute alert weight of monitoring attribute processing and below is the pattern details for this FM, showing its interface including any import and export parameters, exceptions etc. there is also a full "cut and paste" ABAP pattern code example, along with implementation ABAP coding, documentation and contribution comments specific to this or related objects.

See here to view full function module documentation and code listing for db6 alm get alert weight FM, simply by entering the name DB6_ALM_GET_ALERT_WEIGHT into the relevant SAP transaction such as SE37 or SE38.

Function Group: SDB6MON
Program Name: SAPLSDB6MON
Main Program: SAPLSDB6MON
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function DB6_ALM_GET_ALERT_WEIGHT pattern details

In-order to call this FM within your sap programs, simply using the below ABAP pattern details to trigger the function call...or see the full ABAP code listing at the end of this article. You can simply cut and paste this code into your ABAP progrom as it is, including variable declarations.

CALL FUNCTION 'DB6_ALM_GET_ALERT_WEIGHT'"DB6: compute alert weight of monitoring attribute
  EXPORTING
   PARTITN =  "
   OBJECT =  "Alert: Short Name of Monitoring Type
   ATTRIBUTE =  "Alert: Short Name of Monitoring Type
   CURRENT_UNIT =  "ALert: Unit for Perfomance Values
   DESTINATION =  "Logical destination (specified in function call)
   CONNECTION =  "Logical name for a database connection

 IMPORTING
   ALERTVALUE =  "Alert: alert value (1 = green, 2 = yellow, ....)

CHANGING
   CURRENT_VALUE =  "

EXCEPTIONS
   NO_CONFIGURATION_DATA = 1 

.

IMPORTING Parameters details for DB6_ALM_GET_ALERT_WEIGHT

PARTITN -

Data type: I
Optional: No
Call by Reference: Yes

OBJECT - Alert: Short Name of Monitoring Type

Data type: DB6ALRTCFG_STRU-OBJECT
Optional: No
Call by Reference: Yes

ATTRIBUTE - Alert: Short Name of Monitoring Type

Data type: DB6ALRTCFG_STRU-ATTRIBUTE
Optional: No
Call by Reference: Yes

CURRENT_UNIT - ALert: Unit for Perfomance Values

Data type: DB6ALRTCFG_STRU-PARAMUNIT
Optional: No
Call by Reference: Yes

DESTINATION - Logical destination (specified in function call)

Data type: DB6NAVSYST-RFCDEST
Optional: No
Call by Reference: Yes

CONNECTION - Logical name for a database connection

Data type: DB6NAVSYST-DBCNAME
Optional: No
Call by Reference: Yes

EXPORTING Parameters details for DB6_ALM_GET_ALERT_WEIGHT

ALERTVALUE - Alert: alert value (1 = green, 2 = yellow, ....)

Data type: DB6ALRTCFG_STRU-ALRTVALUE
Optional: No
Call by Reference: Yes

CHANGING Parameters details for DB6_ALM_GET_ALERT_WEIGHT

CURRENT_VALUE -

Data type:
Optional: No
Call by Reference: Yes

EXCEPTIONS details

NO_CONFIGURATION_DATA -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for DB6_ALM_GET_ALERT_WEIGHT Function Module

The ABAP code below is a full code listing to execute function module POPUP_TO_CONFIRM including all data declarations. The code uses the original data declarations rather than the latest in-line data DECLARATION SYNTAX but I have included an ABAP code snippet at the end to show how declarations would look using the newer method of declaring data variables on the fly. This will allow you to compare and fully understand the new inline method. Please note some of the newer syntax such as the @DATA is not available until a later 4.70 service pack (SP8), which i why i have stuck to the origianl for this example.

ABAP code using 7.40 inline data declarations to call FM DB6_ALM_GET_ALERT_WEIGHT

The below ABAP code uses the newer in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. Please note some of the newer syntax below, such as the @DATA is not available until 4.70 EHP 8.

Search for further information about these or an SAP related objects