SAP CME_API_DSCOPE_LOCK Function Module for CME Definition Scope - Lock
CME_API_DSCOPE_LOCK is a standard cme api dscope 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 CME Definition Scope - Lock 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 cme api dscope lock FM, simply by entering the name CME_API_DSCOPE_LOCK into the relevant SAP transaction such as SE37 or SE38.
Function Group: CME_API_DSCOPE
Program Name: SAPLCME_API_DSCOPE
Main Program:
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function CME_API_DSCOPE_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 'CME_API_DSCOPE_LOCK'"CME Definition Scope - Lock.
EXPORTING
* IT_KEY = "CME Distr. Scope - Key Fields in Internal/External Format
IMPORTING
ET_KEY = "CME Distr. Scope - Key Fields in Internal/External Format
TABLES
* ET_RETURN = "Messages
EXCEPTIONS
EX_ERROR = 1
IMPORTING Parameters details for CME_API_DSCOPE_LOCK
IT_KEY - CME Distr. Scope - Key Fields in Internal/External Format
Data type: CME_T_DSCOPE_KEY_INT_EXTOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for CME_API_DSCOPE_LOCK
ET_KEY - CME Distr. Scope - Key Fields in Internal/External Format
Data type: CME_T_DSCOPE_KEY_INT_EXTOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for CME_API_DSCOPE_LOCK
ET_RETURN - Messages
Data type: BAPIRET2Optional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
EX_ERROR - An error has occurred
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for CME_API_DSCOPE_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_et_key | TYPE CME_T_DSCOPE_KEY_INT_EXT, " | |||
| lv_it_key | TYPE CME_T_DSCOPE_KEY_INT_EXT, " | |||
| lv_ex_error | TYPE CME_T_DSCOPE_KEY_INT_EXT, " | |||
| lt_et_return | TYPE STANDARD TABLE OF BAPIRET2. " |
|   CALL FUNCTION 'CME_API_DSCOPE_LOCK' "CME Definition Scope - Lock |
| EXPORTING | ||
| IT_KEY | = lv_it_key | |
| IMPORTING | ||
| ET_KEY | = lv_et_key | |
| TABLES | ||
| ET_RETURN | = lt_et_return | |
| EXCEPTIONS | ||
| EX_ERROR = 1 | ||
| . " CME_API_DSCOPE_LOCK | ||
ABAP code using 7.40 inline data declarations to call FM CME_API_DSCOPE_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.Search for further information about these or an SAP related objects