SAP CMSO_DEV_GET Function Module for Movables -> Generic GET module









CMSO_DEV_GET is a standard cmso dev get SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Movables -> Generic GET module 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 cmso dev get FM, simply by entering the name CMSO_DEV_GET into the relevant SAP transaction such as SE37 or SE38.

Function Group: CMS_BDT_DEV
Program Name: SAPLCMS_BDT_DEV
Main Program: SAPLCMS_BDT_DEV
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function CMSO_DEV_GET 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 'CMSO_DEV_GET'"Movables -> Generic GET module
IMPORTING
E_STR_DEV_DATA = "Aircrafts GET data
E_STR_DEV_ADDR_DATA = "Address details
E_TAB_DEV_BP_DATA = "Business Partner Link (Get data)
E_TAB_DEV_DOC_DATA = "Document Service Link (Get Data)
E_TAB_DEV_VAL_DATA = "Value service link (Get data)
E_TAB_DEV_PRT_DATA = "Part Data - GET
E_TAB_DEV_INS_DATA = "Insurance Data - GET
E_TAB_DEV_INS_BP_DATA = "Business Partner Link (Get data)
E_TAB_DEV_INS_DOC_DATA = "Document Service Link (Get Data)
.



EXPORTING Parameters details for CMSO_DEV_GET

E_STR_DEV_DATA - Aircrafts GET data

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

E_STR_DEV_ADDR_DATA - Address details

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

E_TAB_DEV_BP_DATA - Business Partner Link (Get data)

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

E_TAB_DEV_DOC_DATA - Document Service Link (Get Data)

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

E_TAB_DEV_VAL_DATA - Value service link (Get data)

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

E_TAB_DEV_PRT_DATA - Part Data - GET

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

E_TAB_DEV_INS_DATA - Insurance Data - GET

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

E_TAB_DEV_INS_BP_DATA - Business Partner Link (Get data)

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

E_TAB_DEV_INS_DOC_DATA - Document Service Link (Get Data)

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

Copy and paste ABAP code example for CMSO_DEV_GET 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_str_dev_data  TYPE CMS_STR_DEV_DATA_GET, "   
lv_e_str_dev_addr_data  TYPE CMS_STR_MOV_ADDR, "   
lv_e_tab_dev_bp_data  TYPE CMS_TAB_OMS_BP_LNK_GET_DATA, "   
lv_e_tab_dev_doc_data  TYPE CMS_TAB_OMS_DOC_LNK_GET_DATA, "   
lv_e_tab_dev_val_data  TYPE CMS_TAB_OMS_VAL_LNK_GET_DATA, "   
lv_e_tab_dev_prt_data  TYPE CMS_TAB_MOV_PRT_DATA_GET, "   
lv_e_tab_dev_ins_data  TYPE CMS_TAB_OMS_INS_DATA_GET, "   
lv_e_tab_dev_ins_bp_data  TYPE CMS_TAB_OMS_BP_LNK_GET_DATA, "   
lv_e_tab_dev_ins_doc_data  TYPE CMS_TAB_OMS_DOC_LNK_GET_DATA. "   

  CALL FUNCTION 'CMSO_DEV_GET'  "Movables -> Generic GET module
    IMPORTING
         E_STR_DEV_DATA = lv_e_str_dev_data
         E_STR_DEV_ADDR_DATA = lv_e_str_dev_addr_data
         E_TAB_DEV_BP_DATA = lv_e_tab_dev_bp_data
         E_TAB_DEV_DOC_DATA = lv_e_tab_dev_doc_data
         E_TAB_DEV_VAL_DATA = lv_e_tab_dev_val_data
         E_TAB_DEV_PRT_DATA = lv_e_tab_dev_prt_data
         E_TAB_DEV_INS_DATA = lv_e_tab_dev_ins_data
         E_TAB_DEV_INS_BP_DATA = lv_e_tab_dev_ins_bp_data
         E_TAB_DEV_INS_DOC_DATA = lv_e_tab_dev_ins_doc_data
. " CMSO_DEV_GET




ABAP code using 7.40 inline data declarations to call FM CMSO_DEV_GET

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



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!