SAP DB6_ALM_GET_ALERT_CONFIG Function Module for DB6: get alert configuration
DB6_ALM_GET_ALERT_CONFIG is a standard db6 alm get alert config 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: get alert configuration 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 config FM, simply by entering the name DB6_ALM_GET_ALERT_CONFIG into the relevant SAP transaction such as SE37 or SE38.
Function Group: SDBAALCFG
Program Name: SAPLSDBAALCFG
Main Program: SAPLSDBAALCFG
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function DB6_ALM_GET_ALERT_CONFIG 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_CONFIG'"DB6: get alert configuration.
EXPORTING
* COLLECTOR = "Alert: Logical Name of Tool
* OBJECT = "Alert: Short Name of Monitoring Type
* ATTRIBUTE = "Alert: Short Name of Monitoring Type
* CONNECTION = "Logical name for a database connection
TABLES
CONFIGURATION = "DB2 UDB: Alert Configuration Data
EXCEPTIONS
NO_CONFIGURATION_DATA = 1 SYSTEM_ERROR = 2
IMPORTING Parameters details for DB6_ALM_GET_ALERT_CONFIG
COLLECTOR - Alert: Logical Name of Tool
Data type: DB6ALRTCFG_STRU-COLLECTOROptional: Yes
Call by Reference: No ( called with pass by value option)
OBJECT - Alert: Short Name of Monitoring Type
Data type: DB6ALRTCFG_STRU-OBJECTOptional: Yes
Call by Reference: No ( called with pass by value option)
ATTRIBUTE - Alert: Short Name of Monitoring Type
Data type: DB6ALRTCFG_STRU-ATTRIBUTEOptional: Yes
Call by Reference: No ( called with pass by value option)
CONNECTION - Logical name for a database connection
Data type: DB6NAVSYST-DBCNAMEOptional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for DB6_ALM_GET_ALERT_CONFIG
CONFIGURATION - DB2 UDB: Alert Configuration Data
Data type: DB6ALRTCFG_STRUOptional: No
Call by Reference: Yes
EXCEPTIONS details
NO_CONFIGURATION_DATA -
Data type:Optional: No
Call by Reference: Yes
SYSTEM_ERROR -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for DB6_ALM_GET_ALERT_CONFIG 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.| DATA: | ||||
| lv_collector | TYPE DB6ALRTCFG_STRU-COLLECTOR, " | |||
| lt_configuration | TYPE STANDARD TABLE OF DB6ALRTCFG_STRU, " | |||
| lv_no_configuration_data | TYPE DB6ALRTCFG_STRU, " | |||
| lv_object | TYPE DB6ALRTCFG_STRU-OBJECT, " | |||
| lv_system_error | TYPE DB6ALRTCFG_STRU, " | |||
| lv_attribute | TYPE DB6ALRTCFG_STRU-ATTRIBUTE, " | |||
| lv_connection | TYPE DB6NAVSYST-DBCNAME. " |
|   CALL FUNCTION 'DB6_ALM_GET_ALERT_CONFIG' "DB6: get alert configuration |
| EXPORTING | ||
| COLLECTOR | = lv_collector | |
| OBJECT | = lv_object | |
| ATTRIBUTE | = lv_attribute | |
| CONNECTION | = lv_connection | |
| TABLES | ||
| CONFIGURATION | = lt_configuration | |
| EXCEPTIONS | ||
| NO_CONFIGURATION_DATA = 1 | ||
| SYSTEM_ERROR = 2 | ||
| . " DB6_ALM_GET_ALERT_CONFIG | ||
ABAP code using 7.40 inline data declarations to call FM DB6_ALM_GET_ALERT_CONFIG
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.| "SELECT single COLLECTOR FROM DB6ALRTCFG_STRU INTO @DATA(ld_collector). | ||||
| "SELECT single OBJECT FROM DB6ALRTCFG_STRU INTO @DATA(ld_object). | ||||
| "SELECT single ATTRIBUTE FROM DB6ALRTCFG_STRU INTO @DATA(ld_attribute). | ||||
| "SELECT single DBCNAME FROM DB6NAVSYST INTO @DATA(ld_connection). | ||||
Search for further information about these or an SAP related objects