SAP BBP_CM_SUBMIT_ALERTS_GEN Function Module for Submit Batch job to generate alerts









BBP_CM_SUBMIT_ALERTS_GEN is a standard bbp cm submit alerts gen SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Submit Batch job to generate alerts 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 bbp cm submit alerts gen FM, simply by entering the name BBP_CM_SUBMIT_ALERTS_GEN into the relevant SAP transaction such as SE37 or SE38.

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



Function BBP_CM_SUBMIT_ALERTS_GEN 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_CM_SUBMIT_ALERTS_GEN'"Submit Batch job to generate alerts
  EXPORTING
   IV_ALERT_CATEGORY =  "Alert Category
*  IS_PROG_HEAD =  "Interface Fields for Program - Category Management
*  IS_INIT_HEAD =  "UI-Interface - Display Structure initiatve data
*  IS_MESSAGE =  "Return Parameter
*  IV_SCHED_GEN =  "Checkbox

TABLES
*  IT_MESSAGES =  "Return Parameter

EXCEPTIONS
   ALERT_PARMS_INCORRECT = 1    UNABLE_TO_CREATE_JOB = 2    UNABLE_TO_CLOSE_JOB = 3
.



IMPORTING Parameters details for BBP_CM_SUBMIT_ALERTS_GEN

IV_ALERT_CATEGORY - Alert Category

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

IS_PROG_HEAD - Interface Fields for Program - Category Management

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

IS_INIT_HEAD - UI-Interface - Display Structure initiatve data

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

IS_MESSAGE - Return Parameter

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

IV_SCHED_GEN - Checkbox

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

TABLES Parameters details for BBP_CM_SUBMIT_ALERTS_GEN

IT_MESSAGES - Return Parameter

Data type: BAPIRET2
Optional: Yes
Call by Reference: Yes

EXCEPTIONS details

ALERT_PARMS_INCORRECT - Input parameters for Alert not correct

Data type:
Optional: No
Call by Reference: Yes

UNABLE_TO_CREATE_JOB - Failure creating Job

Data type:
Optional: No
Call by Reference: Yes

UNABLE_TO_CLOSE_JOB - Failure Closing Job

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for BBP_CM_SUBMIT_ALERTS_GEN 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:
lt_it_messages  TYPE STANDARD TABLE OF BAPIRET2, "   
lv_iv_alert_category  TYPE SALRTDCAT, "   
lv_alert_parms_incorrect  TYPE SALRTDCAT, "   
lv_is_prog_head  TYPE BBPS_CM_PROGRAM_D, "   
lv_unable_to_create_job  TYPE BBPS_CM_PROGRAM_D, "   
lv_is_init_head  TYPE BBPS_CM_INITIATIVE_D, "   
lv_unable_to_close_job  TYPE BBPS_CM_INITIATIVE_D, "   
lv_is_message  TYPE BAPIRET2, "   
lv_iv_sched_gen  TYPE XFELD. "   

  CALL FUNCTION 'BBP_CM_SUBMIT_ALERTS_GEN'  "Submit Batch job to generate alerts
    EXPORTING
         IV_ALERT_CATEGORY = lv_iv_alert_category
         IS_PROG_HEAD = lv_is_prog_head
         IS_INIT_HEAD = lv_is_init_head
         IS_MESSAGE = lv_is_message
         IV_SCHED_GEN = lv_iv_sched_gen
    TABLES
         IT_MESSAGES = lt_it_messages
    EXCEPTIONS
        ALERT_PARMS_INCORRECT = 1
        UNABLE_TO_CREATE_JOB = 2
        UNABLE_TO_CLOSE_JOB = 3
. " BBP_CM_SUBMIT_ALERTS_GEN




ABAP code using 7.40 inline data declarations to call FM BBP_CM_SUBMIT_ALERTS_GEN

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



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!