SAP RPY_BMEV_MULTI_INSERT_30 Function Module for Insert Events
RPY_BMEV_MULTI_INSERT_30 is a standard rpy bmev multi insert 30 SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Insert 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 rpy bmev multi insert 30 FM, simply by entering the name RPY_BMEV_MULTI_INSERT_30 into the relevant SAP transaction such as SE37 or SE38.
Function Group: SIBU
Program Name: SAPLSIBU
Main Program:
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function RPY_BMEV_MULTI_INSERT_30 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 'RPY_BMEV_MULTI_INSERT_30'"Insert Events.
EXPORTING
LANGUAGE = "Masterlanguage
CICO_REQUEST_NO = "Check-In-Check-Out-Request-Number
IMPORTING
ERROR_OCCURED = "Error occured and is listed in Table 'ERRORS'
PROCESSING_STATUS = "Processing Status of operation
TABLES
EVENTS = "Events
ERRORS = "Errors that occured
IMPORTING Parameters details for RPY_BMEV_MULTI_INSERT_30
LANGUAGE - Masterlanguage
Data type: SY-LANGUOptional: No
Call by Reference: No ( called with pass by value option)
CICO_REQUEST_NO - Check-In-Check-Out-Request-Number
Data type: RPYBMGF-CICO_REQNOOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for RPY_BMEV_MULTI_INSERT_30
ERROR_OCCURED - Error occured and is listed in Table 'ERRORS'
Data type: RPYGSGF-ERR_EXISTOptional: No
Call by Reference: No ( called with pass by value option)
PROCESSING_STATUS - Processing Status of operation
Data type: RPYGSGF-PROC_STATOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for RPY_BMEV_MULTI_INSERT_30
EVENTS - Events
Data type: RPYBM0330Optional: No
Call by Reference: No ( called with pass by value option)
ERRORS - Errors that occured
Data type: RPYBMER31Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for RPY_BMEV_MULTI_INSERT_30 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_events | TYPE STANDARD TABLE OF RPYBM0330, " | |||
| lv_language | TYPE SY-LANGU, " | |||
| lv_error_occured | TYPE RPYGSGF-ERR_EXIST, " | |||
| lt_errors | TYPE STANDARD TABLE OF RPYBMER31, " | |||
| lv_cico_request_no | TYPE RPYBMGF-CICO_REQNO, " | |||
| lv_processing_status | TYPE RPYGSGF-PROC_STAT. " |
|   CALL FUNCTION 'RPY_BMEV_MULTI_INSERT_30' "Insert Events |
| EXPORTING | ||
| LANGUAGE | = lv_language | |
| CICO_REQUEST_NO | = lv_cico_request_no | |
| IMPORTING | ||
| ERROR_OCCURED | = lv_error_occured | |
| PROCESSING_STATUS | = lv_processing_status | |
| TABLES | ||
| EVENTS | = lt_events | |
| ERRORS | = lt_errors | |
| . " RPY_BMEV_MULTI_INSERT_30 | ||
ABAP code using 7.40 inline data declarations to call FM RPY_BMEV_MULTI_INSERT_30
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 LANGU FROM SY INTO @DATA(ld_language). | ||||
| "SELECT single ERR_EXIST FROM RPYGSGF INTO @DATA(ld_error_occured). | ||||
| "SELECT single CICO_REQNO FROM RPYBMGF INTO @DATA(ld_cico_request_no). | ||||
| "SELECT single PROC_STAT FROM RPYGSGF INTO @DATA(ld_processing_status). | ||||
Search for further information about these or an SAP related objects