SAP VALIDITY_CHECK_CLTYPE_CLASS Function Module for









VALIDITY_CHECK_CLTYPE_CLASS is a standard validity check cltype class SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 validity check cltype class FM, simply by entering the name VALIDITY_CHECK_CLTYPE_CLASS into the relevant SAP transaction such as SE37 or SE38.

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



Function VALIDITY_CHECK_CLTYPE_CLASS 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 'VALIDITY_CHECK_CLTYPE_CLASS'"
EXPORTING
* IV_VCL_VC_TICL011 = "
* IV_V_TICL189 = "

EXCEPTIONS
INVALID_KEY = 1 INVALID_VALUE = 2
.



IMPORTING Parameters details for VALIDITY_CHECK_CLTYPE_CLASS

IV_VCL_VC_TICL011 -

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

IV_V_TICL189 -

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

EXCEPTIONS details

INVALID_KEY -

Data type:
Optional: No
Call by Reference: Yes

INVALID_VALUE -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for VALIDITY_CHECK_CLTYPE_CLASS 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_invalid_key  TYPE STRING, "   
lv_iv_vcl_vc_ticl011  TYPE VCLSTRUC-VCLNAME, "   
lv_iv_v_ticl189  TYPE VCLSTRUC-OBJECT, "   
lv_invalid_value  TYPE VCLSTRUC. "   

  CALL FUNCTION 'VALIDITY_CHECK_CLTYPE_CLASS'  "
    EXPORTING
         IV_VCL_VC_TICL011 = lv_iv_vcl_vc_ticl011
         IV_V_TICL189 = lv_iv_v_ticl189
    EXCEPTIONS
        INVALID_KEY = 1
        INVALID_VALUE = 2
. " VALIDITY_CHECK_CLTYPE_CLASS




ABAP code using 7.40 inline data declarations to call FM VALIDITY_CHECK_CLTYPE_CLASS

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 VCLNAME FROM VCLSTRUC INTO @DATA(ld_iv_vcl_vc_ticl011).
 
"SELECT single OBJECT FROM VCLSTRUC INTO @DATA(ld_iv_v_ticl189).
 
 


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!