SAP ISU_VARIANT_CHECK Function Module for









ISU_VARIANT_CHECK is a standard isu variant check 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 isu variant check FM, simply by entering the name ISU_VARIANT_CHECK into the relevant SAP transaction such as SE37 or SE38.

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



Function ISU_VARIANT_CHECK 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 'ISU_VARIANT_CHECK'"
EXPORTING
I_TCODE = "
I_REPID = "
I_VARIANT = "

IMPORTING
E_VARIANT = "
.



IMPORTING Parameters details for ISU_VARIANT_CHECK

I_TCODE -

Data type: SY-TCODE
Optional: No
Call by Reference: Yes

I_REPID -

Data type: SY-REPID
Optional: No
Call by Reference: Yes

I_VARIANT -

Data type: RSVAR-VARIANT
Optional: No
Call by Reference: Yes

EXPORTING Parameters details for ISU_VARIANT_CHECK

E_VARIANT -

Data type: RSVAR-VARIANT
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for ISU_VARIANT_CHECK 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_i_tcode  TYPE SY-TCODE, "   
lv_e_variant  TYPE RSVAR-VARIANT, "   
lv_i_repid  TYPE SY-REPID, "   
lv_i_variant  TYPE RSVAR-VARIANT. "   

  CALL FUNCTION 'ISU_VARIANT_CHECK'  "
    EXPORTING
         I_TCODE = lv_i_tcode
         I_REPID = lv_i_repid
         I_VARIANT = lv_i_variant
    IMPORTING
         E_VARIANT = lv_e_variant
. " ISU_VARIANT_CHECK




ABAP code using 7.40 inline data declarations to call FM ISU_VARIANT_CHECK

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 TCODE FROM SY INTO @DATA(ld_i_tcode).
 
"SELECT single VARIANT FROM RSVAR INTO @DATA(ld_e_variant).
 
"SELECT single REPID FROM SY INTO @DATA(ld_i_repid).
 
"SELECT single VARIANT FROM RSVAR INTO @DATA(ld_i_variant).
 


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!