SAP BBP_DELETE_ALERTS Function Module for









BBP_DELETE_ALERTS is a standard bbp delete alerts SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 bbp delete alerts FM, simply by entering the name BBP_DELETE_ALERTS into the relevant SAP transaction such as SE37 or SE38.

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



Function BBP_DELETE_ALERTS 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 'BBP_DELETE_ALERTS'"
EXPORTING
* MONITOR_MTSYSID = "
* MONITOR_MTMCNAME = "
* MONITOR_MTNUMRANGE = "
* MONITOR_MTUID = "
* MONITOR_MTCLASS = "
* MONITOR_MTINDEX = "
* MONITOR_EXTINDEX = "

IMPORTING
RETURN1 = "
ALERT_LIST_EMPTY = "

TABLES
ALERT_LIST = "
* ATTRIBUT_LIST = "
.



IMPORTING Parameters details for BBP_DELETE_ALERTS

MONITOR_MTSYSID -

Data type: BAPITID-MTSYSID
Optional: Yes
Call by Reference: No ( called with pass by value option)

MONITOR_MTMCNAME -

Data type: BAPITID-MTMCNAME
Optional: Yes
Call by Reference: No ( called with pass by value option)

MONITOR_MTNUMRANGE -

Data type: BAPITID-MTNUMRANGE
Optional: Yes
Call by Reference: No ( called with pass by value option)

MONITOR_MTUID -

Data type: BAPITID-MTUID
Optional: Yes
Call by Reference: No ( called with pass by value option)

MONITOR_MTCLASS -

Data type: BAPITID-MTCLASS
Optional: Yes
Call by Reference: No ( called with pass by value option)

MONITOR_MTINDEX -

Data type: BAPITID-MTINDEX
Optional: Yes
Call by Reference: No ( called with pass by value option)

MONITOR_EXTINDEX -

Data type: BAPITID-EXTINDEX
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for BBP_DELETE_ALERTS

RETURN1 -

Data type: BAPIRET2
Optional: No
Call by Reference: No ( called with pass by value option)

ALERT_LIST_EMPTY -

Data type: CHAR1
Optional: No
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for BBP_DELETE_ALERTS

ALERT_LIST -

Data type: BBP_ALERT_DISPLAY
Optional: No
Call by Reference: No ( called with pass by value option)

ATTRIBUT_LIST -

Data type: BAPITNDEXT
Optional: Yes
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for BBP_DELETE_ALERTS 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_return1  TYPE BAPIRET2, "   
lt_alert_list  TYPE STANDARD TABLE OF BBP_ALERT_DISPLAY, "   
lv_monitor_mtsysid  TYPE BAPITID-MTSYSID, "   
lt_attribut_list  TYPE STANDARD TABLE OF BAPITNDEXT, "   
lv_alert_list_empty  TYPE CHAR1, "   
lv_monitor_mtmcname  TYPE BAPITID-MTMCNAME, "   
lv_monitor_mtnumrange  TYPE BAPITID-MTNUMRANGE, "   
lv_monitor_mtuid  TYPE BAPITID-MTUID, "   
lv_monitor_mtclass  TYPE BAPITID-MTCLASS, "   
lv_monitor_mtindex  TYPE BAPITID-MTINDEX, "   
lv_monitor_extindex  TYPE BAPITID-EXTINDEX. "   

  CALL FUNCTION 'BBP_DELETE_ALERTS'  "
    EXPORTING
         MONITOR_MTSYSID = lv_monitor_mtsysid
         MONITOR_MTMCNAME = lv_monitor_mtmcname
         MONITOR_MTNUMRANGE = lv_monitor_mtnumrange
         MONITOR_MTUID = lv_monitor_mtuid
         MONITOR_MTCLASS = lv_monitor_mtclass
         MONITOR_MTINDEX = lv_monitor_mtindex
         MONITOR_EXTINDEX = lv_monitor_extindex
    IMPORTING
         RETURN1 = lv_return1
         ALERT_LIST_EMPTY = lv_alert_list_empty
    TABLES
         ALERT_LIST = lt_alert_list
         ATTRIBUT_LIST = lt_attribut_list
. " BBP_DELETE_ALERTS




ABAP code using 7.40 inline data declarations to call FM BBP_DELETE_ALERTS

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 MTSYSID FROM BAPITID INTO @DATA(ld_monitor_mtsysid).
 
 
 
"SELECT single MTMCNAME FROM BAPITID INTO @DATA(ld_monitor_mtmcname).
 
"SELECT single MTNUMRANGE FROM BAPITID INTO @DATA(ld_monitor_mtnumrange).
 
"SELECT single MTUID FROM BAPITID INTO @DATA(ld_monitor_mtuid).
 
"SELECT single MTCLASS FROM BAPITID INTO @DATA(ld_monitor_mtclass).
 
"SELECT single MTINDEX FROM BAPITID INTO @DATA(ld_monitor_mtindex).
 
"SELECT single EXTINDEX FROM BAPITID INTO @DATA(ld_monitor_extindex).
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!