SAP CNV_CDMC_CC_FUNC_INCLUDE_INFO Function Module for CDMC: Find the Function Group of a Function module in Remote System
CNV_CDMC_CC_FUNC_INCLUDE_INFO is a standard cnv cdmc cc func include info SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for CDMC: Find the Function Group of a Function module in Remote System 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 cnv cdmc cc func include info FM, simply by entering the name CNV_CDMC_CC_FUNC_INCLUDE_INFO into the relevant SAP transaction such as SE37 or SE38.
Function Group: CNV_CDMC_CC_FUNCTIONS
Program Name: SAPLCNV_CDMC_CC_FUNCTIONS
Main Program: SAPLCNV_CDMC_CC_FUNCTIONS
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function CNV_CDMC_CC_FUNC_INCLUDE_INFO 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 'CNV_CDMC_CC_FUNC_INCLUDE_INFO'"CDMC: Find the Function Group of a Function module in Remote System.
EXPORTING
IV_FUNCNAME = "Name of function module
IMPORTING
ES_FUNCTAB = "Table Type of the structure CNVCDMCCA_FUNCTAB
EV_NAME' ' = "Namespace
EV_FUNCNAME = "Name of function module
EV_GROUP = "Function group, to which the function module belongs
EV_INCLUDE = "ABAP program name
EXCEPTIONS
COMMUNICATION_FAILURE = 1 SYSTEM_FAILURE = 2 FUNCTION_NOT_EXISTS = 3 INCLUDE_NOT_EXISTS = 4 GROUP_NOT_EXISTS = 5 NO_SELECTIONS = 6 NO_FUNCTION_INCLUDE = 7
IMPORTING Parameters details for CNV_CDMC_CC_FUNC_INCLUDE_INFO
IV_FUNCNAME - Name of function module
Data type: RS38L-NAMEOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for CNV_CDMC_CC_FUNC_INCLUDE_INFO
ES_FUNCTAB - Table Type of the structure CNVCDMCCA_FUNCTAB
Data type: CNVCDMCCA_FUNCTAB_TTYOptional: No
Call by Reference: No ( called with pass by value option)
EV_NAMESPACE - Namespace
Data type: RS38L-NAMESPACEOptional: No
Call by Reference: No ( called with pass by value option)
EV_FUNCNAME - Name of function module
Data type: RS38L-NAMEOptional: No
Call by Reference: No ( called with pass by value option)
EV_GROUP - Function group, to which the function module belongs
Data type: RS38L-AREAOptional: No
Call by Reference: No ( called with pass by value option)
EV_INCLUDE - ABAP program name
Data type: RS38L-INCLUDEOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
COMMUNICATION_FAILURE - Communication Failed
Data type:Optional: No
Call by Reference: Yes
SYSTEM_FAILURE - System Failed
Data type:Optional: No
Call by Reference: Yes
FUNCTION_NOT_EXISTS -
Data type:Optional: No
Call by Reference: Yes
INCLUDE_NOT_EXISTS -
Data type:Optional: No
Call by Reference: Yes
GROUP_NOT_EXISTS -
Data type:Optional: No
Call by Reference: Yes
NO_SELECTIONS -
Data type:Optional: No
Call by Reference: Yes
NO_FUNCTION_INCLUDE -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for CNV_CDMC_CC_FUNC_INCLUDE_INFO 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_es_functab | TYPE CNVCDMCCA_FUNCTAB_TTY, " | |||
| lv_iv_funcname | TYPE RS38L-NAME, " | |||
| lv_communication_failure | TYPE RS38L, " | |||
| lv_ev_namespace | TYPE RS38L-NAMESPACE, " | |||
| lv_system_failure | TYPE RS38L, " | |||
| lv_ev_funcname | TYPE RS38L-NAME, " | |||
| lv_function_not_exists | TYPE RS38L, " | |||
| lv_ev_group | TYPE RS38L-AREA, " | |||
| lv_include_not_exists | TYPE RS38L, " | |||
| lv_ev_include | TYPE RS38L-INCLUDE, " | |||
| lv_group_not_exists | TYPE RS38L, " | |||
| lv_no_selections | TYPE RS38L, " | |||
| lv_no_function_include | TYPE RS38L. " |
|   CALL FUNCTION 'CNV_CDMC_CC_FUNC_INCLUDE_INFO' "CDMC: Find the Function Group of a Function module in Remote System |
| EXPORTING | ||
| IV_FUNCNAME | = lv_iv_funcname | |
| IMPORTING | ||
| ES_FUNCTAB | = lv_es_functab | |
| EV_NAMESPACE | = lv_ev_namespace | |
| EV_FUNCNAME | = lv_ev_funcname | |
| EV_GROUP | = lv_ev_group | |
| EV_INCLUDE | = lv_ev_include | |
| EXCEPTIONS | ||
| COMMUNICATION_FAILURE = 1 | ||
| SYSTEM_FAILURE = 2 | ||
| FUNCTION_NOT_EXISTS = 3 | ||
| INCLUDE_NOT_EXISTS = 4 | ||
| GROUP_NOT_EXISTS = 5 | ||
| NO_SELECTIONS = 6 | ||
| NO_FUNCTION_INCLUDE = 7 | ||
| . " CNV_CDMC_CC_FUNC_INCLUDE_INFO | ||
ABAP code using 7.40 inline data declarations to call FM CNV_CDMC_CC_FUNC_INCLUDE_INFO
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.| "SELECT single NAME FROM RS38L INTO @DATA(ld_iv_funcname). | ||||
| "SELECT single NAMESPACE FROM RS38L INTO @DATA(ld_ev_namespace). | ||||
| "SELECT single NAME FROM RS38L INTO @DATA(ld_ev_funcname). | ||||
| "SELECT single AREA FROM RS38L INTO @DATA(ld_ev_group). | ||||
| "SELECT single INCLUDE FROM RS38L INTO @DATA(ld_ev_include). | ||||
Search for further information about these or an SAP related objects