SAP CNV_CDMC_CC_EXECUTE_CHECKS Function Module for Extended Syntax Check & Code Inspector Check

Search SAP Function Modules

CNV_CDMC_CC_EXECUTE_CHECKS is a standard cnv cdmc cc execute checks SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Extended Syntax Check & Code Inspector Check 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 execute checks FM, simply by entering the name CNV_CDMC_CC_EXECUTE_CHECKS 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_EXECUTE_CHECKS 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_EXECUTE_CHECKS'"Extended Syntax Check & Code Inspector Check
  EXPORTING
*  IV_OBJ_TYPE =  "CDMC - Object Type in Upgrade Change Impact Analysis
*  IV_OBJ_NAME =  "ABAP/4 Development Workbench: LIMU name
*  IV_OPERATION =  "Char20
*  IV_ENCLOSING_OBJECT =  "ABAP/4 Development Workbench: LIMU name
*  IV_POSITION = ' ' "Position
*  IV_MAIN_OBJ_TYPE =  "CDMC - Object Type in Upgrade Change Impact Analysis
*  IV_MAIN_OBJ_NAME =  "CDMC - Name of an object in Object Directory Entry (TADIR)

EXCEPTIONS
   INVALID_OPERATION = 1    INVALID_USER_TYPE = 2    NOT_EXECUTED = 3    INVALID_OBJ_TYPE = 4    OBJECT_NOT_EXIST = 5    MAIN_OBJECT_NOT_EXIST = 6    NOT_DIRECT_CALL = 7    OBJ_REF_IN_SUPER_CLASS = 8 

.

IMPORTING Parameters details for CNV_CDMC_CC_EXECUTE_CHECKS

IV_OBJ_TYPE - CDMC - Object Type in Upgrade Change Impact Analysis

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

IV_OBJ_NAME - ABAP/4 Development Workbench: LIMU name

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

IV_OPERATION - Char20

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

IV_ENCLOSING_OBJECT - ABAP/4 Development Workbench: LIMU name

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

IV_POSITION - Position

Data type: CHAR5
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_MAIN_OBJ_TYPE - CDMC - Object Type in Upgrade Change Impact Analysis

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

IV_MAIN_OBJ_NAME - CDMC - Name of an object in Object Directory Entry (TADIR)

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

EXCEPTIONS details

INVALID_OPERATION - Operation not possible

Data type:
Optional: No
Call by Reference: Yes

INVALID_USER_TYPE - Invalid User Type

Data type:
Optional: No
Call by Reference: Yes

NOT_EXECUTED - Operation could not be executed

Data type:
Optional: No
Call by Reference: Yes

INVALID_OBJ_TYPE - Invalid Object type

Data type:
Optional: No
Call by Reference: Yes

OBJECT_NOT_EXIST - Object does not exist

Data type:
Optional: No
Call by Reference: Yes

MAIN_OBJECT_NOT_EXIST - Main Object does not exist

Data type:
Optional: No
Call by Reference: Yes

NOT_DIRECT_CALL - Object is not referred/called directly

Data type:
Optional: No
Call by Reference: Yes

OBJ_REF_IN_SUPER_CLASS - Object is referred in its super class or interface

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for CNV_CDMC_CC_EXECUTE_CHECKS 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.

ABAP code using 7.40 inline data declarations to call FM CNV_CDMC_CC_EXECUTE_CHECKS

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