SAP SZDM_CC_CR_CHECK_VERSION Function Module for Checks a version of defintion for a category
SZDM_CC_CR_CHECK_VERSION is a standard szdm cc cr check version SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Checks a version of defintion for a category 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 szdm cc cr check version FM, simply by entering the name SZDM_CC_CR_CHECK_VERSION into the relevant SAP transaction such as SE37 or SE38.
Function Group: SZDM_CC_CR_FUNCTION_GROUP
Program Name: SAPLSZDM_CC_CR_FUNCTION_GROUP
Main Program: SAPLSZDM_CC_CR_FUNCTION_GROUP
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function SZDM_CC_CR_CHECK_VERSION 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 'SZDM_CC_CR_CHECK_VERSION'"Checks a version of defintion for a category.
EXPORTING
* IV_ERROR_HANDLING_TYPE = 'M' "Error handling type in central repository
IV_CATEGORY = "Category in central repository
IV_VERSION = "Information about versioning of definitions
IMPORTING
EV_VERSION_EXISTS = "Single-Character Flag
EV_RC = "Natural number
ET_ERROR = "Table Type of central repository for error texts
EXCEPTIONS
NO_READ_AUTHORIZATION = 1 ERROR_CHECK_VERSION = 2 ERROR_REQUESTING_LOCK = 3
IMPORTING Parameters details for SZDM_CC_CR_CHECK_VERSION
IV_ERROR_HANDLING_TYPE - Error handling type in central repository
Data type: SZDM_CC_CR_ERROR_HANDLING_TYPEDefault: 'M'
Optional: Yes
Call by Reference: No ( called with pass by value option)
IV_CATEGORY - Category in central repository
Data type: SZDM_CC_CR_CATEGORYOptional: No
Call by Reference: No ( called with pass by value option)
IV_VERSION - Information about versioning of definitions
Data type: SZDM_CC_CR_VERSIONOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for SZDM_CC_CR_CHECK_VERSION
EV_VERSION_EXISTS - Single-Character Flag
Data type: CHAR1Optional: No
Call by Reference: No ( called with pass by value option)
EV_RC - Natural number
Data type: INT4Optional: No
Call by Reference: No ( called with pass by value option)
ET_ERROR - Table Type of central repository for error texts
Data type: SZDM_CC_CR_ERROR_TOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
NO_READ_AUTHORIZATION -
Data type:Optional: No
Call by Reference: Yes
ERROR_CHECK_VERSION - An error occured while checking version
Data type:Optional: No
Call by Reference: Yes
ERROR_REQUESTING_LOCK - Unable to get enqueue to create definition
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for SZDM_CC_CR_CHECK_VERSION 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_ev_version_exists | TYPE CHAR1, " | |||
| lv_no_read_authorization | TYPE CHAR1, " | |||
| lv_iv_error_handling_type | TYPE SZDM_CC_CR_ERROR_HANDLING_TYPE, " 'M' | |||
| lv_ev_rc | TYPE INT4, " | |||
| lv_iv_category | TYPE SZDM_CC_CR_CATEGORY, " | |||
| lv_error_check_version | TYPE SZDM_CC_CR_CATEGORY, " | |||
| lv_et_error | TYPE SZDM_CC_CR_ERROR_T, " | |||
| lv_iv_version | TYPE SZDM_CC_CR_VERSION, " | |||
| lv_error_requesting_lock | TYPE SZDM_CC_CR_VERSION. " |
|   CALL FUNCTION 'SZDM_CC_CR_CHECK_VERSION' "Checks a version of defintion for a category |
| EXPORTING | ||
| IV_ERROR_HANDLING_TYPE | = lv_iv_error_handling_type | |
| IV_CATEGORY | = lv_iv_category | |
| IV_VERSION | = lv_iv_version | |
| IMPORTING | ||
| EV_VERSION_EXISTS | = lv_ev_version_exists | |
| EV_RC | = lv_ev_rc | |
| ET_ERROR | = lv_et_error | |
| EXCEPTIONS | ||
| NO_READ_AUTHORIZATION = 1 | ||
| ERROR_CHECK_VERSION = 2 | ||
| ERROR_REQUESTING_LOCK = 3 | ||
| . " SZDM_CC_CR_CHECK_VERSION | ||
ABAP code using 7.40 inline data declarations to call FM SZDM_CC_CR_CHECK_VERSION
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.| DATA(ld_iv_error_handling_type) | = 'M'. | |||
Search for further information about these or an SAP related objects