SAP BM_EVENTS_FETCH Function Module for Reading of Events

Search SAP Function Modules

BM_EVENTS_FETCH is a standard bm events fetch SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Reading of Events 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 bm events fetch FM, simply by entering the name BM_EVENTS_FETCH into the relevant SAP transaction such as SE37 or SE38.

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

Function BM_EVENTS_FETCH 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 'BM_EVENTS_FETCH'"Reading of Events
  EXPORTING
*  LANGU = SY-LANGU "
*  READ_ATTRIBUTES = 'X' "
*  ENQUEUE = ' ' "
*  NO_DIALOG = ' ' "
*  CICO_REQUEST_NO =  "

 IMPORTING
   EVENTS =  "
   PROCESSING_STATUS =  "

TABLES
   OBJECTS_TO_READ =  "
*  ERRORS =  "

.

IMPORTING Parameters details for BM_EVENTS_FETCH

LANGU -

Data type: BMT_FLAG
Default: SY-LANGU
Optional: Yes
Call by Reference: No ( called with pass by value option)

READ_ATTRIBUTES -

Data type: BMT_FLAG
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

ENQUEUE -

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

NO_DIALOG -

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

CICO_REQUEST_NO -

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

EXPORTING Parameters details for BM_EVENTS_FETCH

EVENTS -

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

PROCESSING_STATUS -

Data type: RPYGSGF-PROC_STAT
Optional: No
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for BM_EVENTS_FETCH

OBJECTS_TO_READ -

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

ERRORS -

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

Copy and paste ABAP code example for BM_EVENTS_FETCH 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 BM_EVENTS_FETCH

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