SAP RPY_BMEP_READ_LOCK_31 Function Module for Read diagram locking









RPY_BMEP_READ_LOCK_31 is a standard rpy bmep read lock 31 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 diagram 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 bmep read lock 31 FM, simply by entering the name RPY_BMEP_READ_LOCK_31 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_BMEP_READ_LOCK_31 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_BMEP_READ_LOCK_31'"Read diagram locking
EXPORTING
CICO_REQUEST_NO = "Number of Check-In-Check-Out-Request
OBJECT_ID = "Model ID
* LANGUAGE = SY-LANGU "

IMPORTING
MODEL_INFO = "Model information
ERROR_OCCURED = "Error occured, error table has entries
PROCESSING_STATUS = "Stateus of processing

TABLES
NODES = "Nodes
LINES = "Lines
ERRORS = "Errors
.



IMPORTING Parameters details for RPY_BMEP_READ_LOCK_31

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)

OBJECT_ID - Model ID

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

LANGUAGE -

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

EXPORTING Parameters details for RPY_BMEP_READ_LOCK_31

MODEL_INFO - Model information

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

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 - Stateus of processing

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

TABLES Parameters details for RPY_BMEP_READ_LOCK_31

NODES - Nodes

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

LINES - Lines

Data type: RPYBM4231
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_BMEP_READ_LOCK_31 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_nodes  TYPE STANDARD TABLE OF RPYBM4131, "   
lv_model_info  TYPE RPYBM4031, "   
lv_cico_request_no  TYPE RPYBMGF-CICO_REQNO, "   
lt_lines  TYPE STANDARD TABLE OF RPYBM4231, "   
lv_object_id  TYPE RPYBM4031-MODEL_ID, "   
lv_error_occured  TYPE RPYGSGF-ERR_EXIST, "   
lt_errors  TYPE STANDARD TABLE OF RPYBMER31, "   
lv_language  TYPE SY-LANGU, "   SY-LANGU
lv_processing_status  TYPE RPYGSGF-PROC_STAT. "   

  CALL FUNCTION 'RPY_BMEP_READ_LOCK_31'  "Read diagram locking
    EXPORTING
         CICO_REQUEST_NO = lv_cico_request_no
         OBJECT_ID = lv_object_id
         LANGUAGE = lv_language
    IMPORTING
         MODEL_INFO = lv_model_info
         ERROR_OCCURED = lv_error_occured
         PROCESSING_STATUS = lv_processing_status
    TABLES
         NODES = lt_nodes
         LINES = lt_lines
         ERRORS = lt_errors
. " RPY_BMEP_READ_LOCK_31




ABAP code using 7.40 inline data declarations to call FM RPY_BMEP_READ_LOCK_31

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 CICO_REQNO FROM RPYBMGF INTO @DATA(ld_cico_request_no).
 
 
"SELECT single MODEL_ID FROM RPYBM4031 INTO @DATA(ld_object_id).
 
"SELECT single ERR_EXIST FROM RPYGSGF INTO @DATA(ld_error_occured).
 
 
"SELECT single LANGU FROM SY INTO @DATA(ld_language).
DATA(ld_language) = SY-LANGU.
 
"SELECT single PROC_STAT FROM RPYGSGF INTO @DATA(ld_processing_status).
 


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!