SAP Function Modules
CNV_CMIS_A_GET_CUSTOM_OBJECTS SAP Function module
CNV_CMIS_A_GET_CUSTOM_OBJECTS is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.
See here to view full function module documentation and code listing, simply by entering the name CNV_CMIS_A_GET_CUSTOM_OBJECTS into the relevant SAP transaction such as SE37 or SE80.
Associated Function Group:
CNV_CMIS_10_SUPPORT
Released Date:
Not Released
Processing type: Normal fucntion module
Pattern for FM CNV_CMIS_A_GET_CUSTOM_OBJECTS - CNV CMIS A GET CUSTOM OBJECTS
CALL FUNCTION 'CNV_CMIS_A_GET_CUSTOM_OBJECTS' "
* EXPORTING
* iv_add_cu_flag1 = " cnvcmis_a_10_run-custom_objects
* iv_or_cu_flag1 = " cnvcmis_a_10_run-custom_objects
* iv_cust_furthersel1 = " cnvcmis_a_10_run-custom_objects
TABLES
et_tadir = " tadir
* xt_object_name1 = " cnvcmis_a_1_objname
* xt_dev_class1 = " cnvcmis_a_1_devclass
* xt_dev_class = " cnvcmis_a_1_devclass
* xt_object_type = " cnv_cmis_a_10_object_typ
. " CNV_CMIS_A_GET_CUSTOM_OBJECTS
ABAP code example for Function Module CNV_CMIS_A_GET_CUSTOM_OBJECTS
The ABAP code below is a full code listing to execute function module CNV_CMIS_A_GET_CUSTOM_OBJECTS including all data declarations. The code uses 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 original method of declaring data variables up front. 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).
| it_et_tadir | TYPE STANDARD TABLE OF TADIR,"TABLES PARAM |
| wa_et_tadir | LIKE LINE OF it_et_tadir , |
| it_xt_object_name1 | TYPE STANDARD TABLE OF CNVCMIS_A_1_OBJNAME,"TABLES PARAM |
| wa_xt_object_name1 | LIKE LINE OF it_xt_object_name1 , |
| it_xt_dev_class1 | TYPE STANDARD TABLE OF CNVCMIS_A_1_DEVCLASS,"TABLES PARAM |
| wa_xt_dev_class1 | LIKE LINE OF it_xt_dev_class1 , |
| it_xt_dev_class | TYPE STANDARD TABLE OF CNVCMIS_A_1_DEVCLASS,"TABLES PARAM |
| wa_xt_dev_class | LIKE LINE OF it_xt_dev_class , |
| it_xt_object_type | TYPE STANDARD TABLE OF CNV_CMIS_A_10_OBJECT_TYP,"TABLES PARAM |
| wa_xt_object_type | LIKE LINE OF it_xt_object_type . |
SELECT single CUSTOM_OBJECTS
FROM CNVCMIS_A_10_RUN
INTO @DATA(ld_iv_add_cu_flag1).
SELECT single CUSTOM_OBJECTS
FROM CNVCMIS_A_10_RUN
INTO @DATA(ld_iv_or_cu_flag1).
SELECT single CUSTOM_OBJECTS
FROM CNVCMIS_A_10_RUN
INTO @DATA(ld_iv_cust_furthersel1).
"populate fields of struture and append to itab
append wa_et_tadir to it_et_tadir.
"populate fields of struture and append to itab
append wa_xt_object_name1 to it_xt_object_name1.
"populate fields of struture and append to itab
append wa_xt_dev_class1 to it_xt_dev_class1.
"populate fields of struture and append to itab
append wa_xt_dev_class to it_xt_dev_class.
"populate fields of struture and append to itab
append wa_xt_object_type to it_xt_object_type. . CALL FUNCTION 'CNV_CMIS_A_GET_CUSTOM_OBJECTS' * EXPORTING * iv_add_cu_flag1 = ld_iv_add_cu_flag1 * iv_or_cu_flag1 = ld_iv_or_cu_flag1 * iv_cust_furthersel1 = ld_iv_cust_furthersel1 TABLES et_tadir = it_et_tadir * xt_object_name1 = it_xt_object_name1 * xt_dev_class1 = it_xt_dev_class1 * xt_dev_class = it_xt_dev_class * xt_object_type = it_xt_object_type . " CNV_CMIS_A_GET_CUSTOM_OBJECTS
IF SY-SUBRC EQ 0. "All OK ENDIF.
ABAP code to compare 7.40 inline data declaration with original syntax
The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.
DATA:
| ld_iv_add_cu_flag1 | TYPE CNVCMIS_A_10_RUN-CUSTOM_OBJECTS , |
| it_et_tadir | TYPE STANDARD TABLE OF TADIR , |
| wa_et_tadir | LIKE LINE OF it_et_tadir, |
| ld_iv_or_cu_flag1 | TYPE CNVCMIS_A_10_RUN-CUSTOM_OBJECTS , |
| it_xt_object_name1 | TYPE STANDARD TABLE OF CNVCMIS_A_1_OBJNAME , |
| wa_xt_object_name1 | LIKE LINE OF it_xt_object_name1, |
| ld_iv_cust_furthersel1 | TYPE CNVCMIS_A_10_RUN-CUSTOM_OBJECTS , |
| it_xt_dev_class1 | TYPE STANDARD TABLE OF CNVCMIS_A_1_DEVCLASS , |
| wa_xt_dev_class1 | LIKE LINE OF it_xt_dev_class1, |
| it_xt_dev_class | TYPE STANDARD TABLE OF CNVCMIS_A_1_DEVCLASS , |
| wa_xt_dev_class | LIKE LINE OF it_xt_dev_class, |
| it_xt_object_type | TYPE STANDARD TABLE OF CNV_CMIS_A_10_OBJECT_TYP , |
| wa_xt_object_type | LIKE LINE OF it_xt_object_type. |
SELECT single CUSTOM_OBJECTS
FROM CNVCMIS_A_10_RUN
INTO ld_iv_add_cu_flag1.
"populate fields of struture and append to itab
append wa_et_tadir to it_et_tadir.
SELECT single CUSTOM_OBJECTS
FROM CNVCMIS_A_10_RUN
INTO ld_iv_or_cu_flag1.
"populate fields of struture and append to itab
append wa_xt_object_name1 to it_xt_object_name1.
SELECT single CUSTOM_OBJECTS
FROM CNVCMIS_A_10_RUN
INTO ld_iv_cust_furthersel1.
"populate fields of struture and append to itab
append wa_xt_dev_class1 to it_xt_dev_class1.
"populate fields of struture and append to itab
append wa_xt_dev_class to it_xt_dev_class.
"populate fields of struture and append to itab
append wa_xt_object_type to it_xt_object_type.
Contribute (Add Comments)
Please help keep this info upto date and use the comments section below to add useful hints, tips and information specific to this SAP function. This will then be available for you and other users to easily find by simply searching on the object name CNV_CMIS_A_GET_CUSTOM_OBJECTS or its description.