SAP RPY_BMEV_MULTI_READ_LOCK_30 Function Module for Read events locking

Search SAP Function Modules

RPY_BMEV_MULTI_READ_LOCK_30 is a standard rpy bmev multi read lock 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 Read events locking 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 read lock 30 FM, simply by entering the name RPY_BMEV_MULTI_READ_LOCK_30 into the relevant SAP transaction such as SE37 or SE38.

Function Group: SIBM
Program Name: SAPLSIBM
Main Program:
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function RPY_BMEV_MULTI_READ_LOCK_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_READ_LOCK_30'"Read events locking
  EXPORTING
*  LANGUAGE = SY-LANGU "Language of objects to read
   CICO_REQUEST_NO =  "Number of Check-In-Check-Out-Request

 IMPORTING
   ERROR_OCCURED =  "Error occured, error table has entries
   PROCESSING_STATUS =  "Status of processing

TABLES
   OBJECTS_TO_READ =  "ID's of objects to read
   EVENTS =  "Result table
   ERRORS =  "Errors

.

IMPORTING Parameters details for RPY_BMEV_MULTI_READ_LOCK_30

LANGUAGE - Language of objects to read

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

CICO_REQUEST_NO - Number of Check-In-Check-Out-Request

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

EXPORTING Parameters details for RPY_BMEV_MULTI_READ_LOCK_30

ERROR_OCCURED - Error occured, error table has entries

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

PROCESSING_STATUS - Status of processing

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

TABLES Parameters details for RPY_BMEV_MULTI_READ_LOCK_30

OBJECTS_TO_READ - ID's of objects to read

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

EVENTS - Result table

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

ERRORS - Errors

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

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

ABAP code using 7.40 inline data declarations to call FM RPY_BMEV_MULTI_READ_LOCK_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.

Search for further information about these or an SAP related objects