SAP /MRSS/R3_API_DEMAND_LOCK_READ Function Module for Read the lock attributes of demand

Search SAP Function Modules

/MRSS/R3_API_DEMAND_LOCK_READ is a standard /mrss/r3 api demand lock read 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 the lock attributes of demand 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 /mrss/r3 api demand lock read FM, simply by entering the name /MRSS/R3_API_DEMAND_LOCK_READ into the relevant SAP transaction such as SE37 or SE38.

Function Group: /MRSS/R3_BO_INTERACTION
Program Name: /MRSS/SAPLR3_BO_INTERACTION
Main Program: /MRSS/SAPLR3_BO_INTERACTION
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function /MRSS/R3_API_DEMAND_LOCK_READ 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 '/MRSS/R3_API_DEMAND_LOCK_READ'"Read the lock attributes of demand
  EXPORTING
   IS_DEMAND_KEY =  "External Key of Demands
   IV_DEMAND_TYPE =  "Demand Type
*  IV_ORDER_ID =  "Demand ID

 IMPORTING
   ES_LOCK_ATTRIBUTES =  "Attributes of Lock
   EV_FAILED =  "Boolean Variable
   ET_MESSAGES =  "Messages

.

IMPORTING Parameters details for /MRSS/R3_API_DEMAND_LOCK_READ

IS_DEMAND_KEY - External Key of Demands

Data type: /MRSS/T_RSG_KEY_EXTERNAL
Optional: No
Call by Reference: No ( called with pass by value option)

IV_DEMAND_TYPE - Demand Type

Data type: /MRSS/T_RSG_DEM_TYPE
Optional: No
Call by Reference: No ( called with pass by value option)

IV_ORDER_ID - Demand ID

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

EXPORTING Parameters details for /MRSS/R3_API_DEMAND_LOCK_READ

ES_LOCK_ATTRIBUTES - Attributes of Lock

Data type: /MRSS/T_R3_LOCK_ATTRIBUTES
Optional: No
Call by Reference: No ( called with pass by value option)

EV_FAILED - Boolean Variable

Data type: /MRSS/T_RSG_BOOLEAN
Optional: No
Call by Reference: No ( called with pass by value option)

ET_MESSAGES - Messages

Data type: /MRSS/T_R3_MESSAGE_TAB
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for /MRSS/R3_API_DEMAND_LOCK_READ 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 /MRSS/R3_API_DEMAND_LOCK_READ

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