SAP CMS_API_DEV_SET_MLT Function Module for Set Devices Data - Multiple
CMS_API_DEV_SET_MLT is a standard cms api dev set mlt SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Set Devices Data - Multiple 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 cms api dev set mlt FM, simply by entering the name CMS_API_DEV_SET_MLT into the relevant SAP transaction such as SE37 or SE38.
Function Group: CMS_API_DEV
Program Name: SAPLCMS_API_DEV
Main Program:
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function CMS_API_DEV_SET_MLT 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 'CMS_API_DEV_SET_MLT'"Set Devices Data - Multiple.
EXPORTING
I_TAB_DEV_GUID = "Movables Primary key
I_TAB_DEV_DATA = "Device Data - SET
* I_TAB_DEV_PRT_DATA = "Part Data - SET
* I_TAB_DEV_ADDR_DATA = "Address data for movables (Std tab)
* I_TAB_DEV_INS_DATA = "Insurance Data - SET
* I_TAB_DEV_BP_DATA = "Business Partner Link (Set data)
* I_TAB_DEV_DOC_DATA = "Documents Service Link (Set data)
* I_TAB_DEV_VAL_DATA = "Value service link (Set data)
IMPORTING
E_TAB_RC = "Return Code and corresponding Message
IMPORTING Parameters details for CMS_API_DEV_SET_MLT
I_TAB_DEV_GUID - Movables Primary key
Data type: CMS_TAB_MOV_PKYOptional: No
Call by Reference: No ( called with pass by value option)
I_TAB_DEV_DATA - Device Data - SET
Data type: CMS_TAB_DEV_DATA_SETOptional: No
Call by Reference: No ( called with pass by value option)
I_TAB_DEV_PRT_DATA - Part Data - SET
Data type: CMS_TAB_MOV_PRT_DATA_SETOptional: Yes
Call by Reference: No ( called with pass by value option)
I_TAB_DEV_ADDR_DATA - Address data for movables (Std tab)
Data type: CMS_TAB_MOV_ADDR_DATAOptional: Yes
Call by Reference: No ( called with pass by value option)
I_TAB_DEV_INS_DATA - Insurance Data - SET
Data type: CMS_TAB_OMS_INS_DATA_SETOptional: Yes
Call by Reference: No ( called with pass by value option)
I_TAB_DEV_BP_DATA - Business Partner Link (Set data)
Data type: CMS_TAB_OMS_BP_LNK_SET_DATAOptional: Yes
Call by Reference: No ( called with pass by value option)
I_TAB_DEV_DOC_DATA - Documents Service Link (Set data)
Data type: CMS_TAB_OMS_DOC_LNK_SET_DATAOptional: Yes
Call by Reference: No ( called with pass by value option)
I_TAB_DEV_VAL_DATA - Value service link (Set data)
Data type: CMS_TAB_OMS_VAL_LNK_SET_DATAOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for CMS_API_DEV_SET_MLT
E_TAB_RC - Return Code and corresponding Message
Data type: CMS_TAB_MSG_COL_MESSAGEOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for CMS_API_DEV_SET_MLT 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_e_tab_rc | TYPE CMS_TAB_MSG_COL_MESSAGE, " | |||
| lv_i_tab_dev_guid | TYPE CMS_TAB_MOV_PKY, " | |||
| lv_i_tab_dev_data | TYPE CMS_TAB_DEV_DATA_SET, " | |||
| lv_i_tab_dev_prt_data | TYPE CMS_TAB_MOV_PRT_DATA_SET, " | |||
| lv_i_tab_dev_addr_data | TYPE CMS_TAB_MOV_ADDR_DATA, " | |||
| lv_i_tab_dev_ins_data | TYPE CMS_TAB_OMS_INS_DATA_SET, " | |||
| lv_i_tab_dev_bp_data | TYPE CMS_TAB_OMS_BP_LNK_SET_DATA, " | |||
| lv_i_tab_dev_doc_data | TYPE CMS_TAB_OMS_DOC_LNK_SET_DATA, " | |||
| lv_i_tab_dev_val_data | TYPE CMS_TAB_OMS_VAL_LNK_SET_DATA. " |
|   CALL FUNCTION 'CMS_API_DEV_SET_MLT' "Set Devices Data - Multiple |
| EXPORTING | ||
| I_TAB_DEV_GUID | = lv_i_tab_dev_guid | |
| I_TAB_DEV_DATA | = lv_i_tab_dev_data | |
| I_TAB_DEV_PRT_DATA | = lv_i_tab_dev_prt_data | |
| I_TAB_DEV_ADDR_DATA | = lv_i_tab_dev_addr_data | |
| I_TAB_DEV_INS_DATA | = lv_i_tab_dev_ins_data | |
| I_TAB_DEV_BP_DATA | = lv_i_tab_dev_bp_data | |
| I_TAB_DEV_DOC_DATA | = lv_i_tab_dev_doc_data | |
| I_TAB_DEV_VAL_DATA | = lv_i_tab_dev_val_data | |
| IMPORTING | ||
| E_TAB_RC | = lv_e_tab_rc | |
| . " CMS_API_DEV_SET_MLT | ||
ABAP code using 7.40 inline data declarations to call FM CMS_API_DEV_SET_MLT
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