SAP ICL_CVERM_UNI_SUSPENSE_CHANGE Function Module for Checks whether a version in suspense would cause any changes

Search SAP Function Modules

ICL_CVERM_UNI_SUSPENSE_CHANGE is a standard icl cverm uni suspense change 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 whether a version in suspense would cause any changes 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 icl cverm uni suspense change FM, simply by entering the name ICL_CVERM_UNI_SUSPENSE_CHANGE into the relevant SAP transaction such as SE37 or SE38.

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

Function ICL_CVERM_UNI_SUSPENSE_CHANGE 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 'ICL_CVERM_UNI_SUSPENSE_CHANGE'"Checks whether a version in suspense would cause any changes
  EXPORTING
   I_VER_TABNAME =  "
   IS_SUSP_VERSION =  "
   I_GEN_TABNAME =  "Name of ABAP Dictionary Object

 IMPORTING
   E_XNO_MATCH =  "Data Element for BOOLE Domain: TRUE (='X') and FALSE (=' ')

TABLES
   ET_TABDIFF =  "

.

IMPORTING Parameters details for ICL_CVERM_UNI_SUSPENSE_CHANGE

I_VER_TABNAME -

Data type: DCOBJDEF-NAME
Optional: No
Call by Reference: Yes

IS_SUSP_VERSION -

Data type:
Optional: No
Call by Reference: Yes

I_GEN_TABNAME - Name of ABAP Dictionary Object

Data type: DCOBJDEF-NAME
Optional: No
Call by Reference: Yes

EXPORTING Parameters details for ICL_CVERM_UNI_SUSPENSE_CHANGE

E_XNO_MATCH - Data Element for BOOLE Domain: TRUE (='X') and FALSE (=' ')

Data type: BOOLE_D
Optional: No
Call by Reference: Yes

TABLES Parameters details for ICL_CVERM_UNI_SUSPENSE_CHANGE

ET_TABDIFF -

Data type: ICL_TABDIFF
Optional: No
Call by Reference: Yes

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

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