SAP RS_DME_MCI_MODEL_LOCK Function Module for Activate model
RS_DME_MCI_MODEL_LOCK is a standard rs dme mci model lock SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Activate model 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 rs dme mci model lock FM, simply by entering the name RS_DME_MCI_MODEL_LOCK into the relevant SAP transaction such as SE37 or SE38.
Function Group: RS_DME_MP_CONSUMER_INT
Program Name: SAPLRS_DME_MP_CONSUMER_INT
Main Program: SAPLRS_DME_MP_CONSUMER_INT
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function RS_DME_MCI_MODEL_LOCK 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 'RS_DME_MCI_MODEL_LOCK'"Activate model.
EXPORTING
I_MODEL = "Analytical Model
* I_OBJVERS = 'A' "Object version
TABLES
* E_T_RETURN = "Return parameter
IMPORTING Parameters details for RS_DME_MCI_MODEL_LOCK
I_MODEL - Analytical Model
Data type: RSDMEM_MODELOptional: No
Call by Reference: No ( called with pass by value option)
I_OBJVERS - Object version
Data type: RSOBJVERSDefault: 'A'
Optional: Yes
Call by Reference: Yes
TABLES Parameters details for RS_DME_MCI_MODEL_LOCK
E_T_RETURN - Return parameter
Data type: BAPIRET2Optional: Yes
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for RS_DME_MCI_MODEL_LOCK 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: | ||||
| lv_i_model | TYPE RSDMEM_MODEL, " | |||
| lt_e_t_return | TYPE STANDARD TABLE OF BAPIRET2, " | |||
| lv_i_objvers | TYPE RSOBJVERS. " 'A' |
|   CALL FUNCTION 'RS_DME_MCI_MODEL_LOCK' "Activate model |
| EXPORTING | ||
| I_MODEL | = lv_i_model | |
| I_OBJVERS | = lv_i_objvers | |
| TABLES | ||
| E_T_RETURN | = lt_e_t_return | |
| . " RS_DME_MCI_MODEL_LOCK | ||
ABAP code using 7.40 inline data declarations to call FM RS_DME_MCI_MODEL_LOCK
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.| DATA(ld_i_objvers) | = 'A'. | |||
Search for further information about these or an SAP related objects