SAP MCH01_VARIANT_EXIST Function Module for NOTRANSL: Prüfung, ob die Variante existiert









MCH01_VARIANT_EXIST is a standard mch01 variant exist SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Prüfung, ob die Variante existiert 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 mch01 variant exist FM, simply by entering the name MCH01_VARIANT_EXIST into the relevant SAP transaction such as SE37 or SE38.

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



Function MCH01_VARIANT_EXIST 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 'MCH01_VARIANT_EXIST'"NOTRANSL: Prüfung, ob die Variante existiert
EXPORTING
* I_OBJECT = 'MPLA' "Object Type
I_VARNAME = "Variant Name

IMPORTING
ES_VARIANT = "Data Structure for Mass Maintenance Variants

TABLES
* ET_CHANGES = "Field Changes in Mass Maintenance

EXCEPTIONS
VARIANT_NOT_FOUND = 1
.



IMPORTING Parameters details for MCH01_VARIANT_EXIST

I_OBJECT - Object Type

Data type: MASSFUNC-OBJECT
Default: 'MPLA'
Optional: Yes
Call by Reference: Yes

I_VARNAME - Variant Name

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

EXPORTING Parameters details for MCH01_VARIANT_EXIST

ES_VARIANT - Data Structure for Mass Maintenance Variants

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

TABLES Parameters details for MCH01_VARIANT_EXIST

ET_CHANGES - Field Changes in Mass Maintenance

Data type: MASS_CHANGES
Optional: Yes
Call by Reference: Yes

EXCEPTIONS details

VARIANT_NOT_FOUND - Variant does not exist

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for MCH01_VARIANT_EXIST 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_object  TYPE MASSFUNC-OBJECT, "   'MPLA'
lv_es_variant  TYPE MASSVAR, "   
lt_et_changes  TYPE STANDARD TABLE OF MASS_CHANGES, "   
lv_variant_not_found  TYPE MASS_CHANGES, "   
lv_i_varname  TYPE MASSVARNAM. "   

  CALL FUNCTION 'MCH01_VARIANT_EXIST'  "NOTRANSL: Prüfung, ob die Variante existiert
    EXPORTING
         I_OBJECT = lv_i_object
         I_VARNAME = lv_i_varname
    IMPORTING
         ES_VARIANT = lv_es_variant
    TABLES
         ET_CHANGES = lt_et_changes
    EXCEPTIONS
        VARIANT_NOT_FOUND = 1
. " MCH01_VARIANT_EXIST




ABAP code using 7.40 inline data declarations to call FM MCH01_VARIANT_EXIST

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 OBJECT FROM MASSFUNC INTO @DATA(ld_i_object).
DATA(ld_i_object) = 'MPLA'.
 
 
 
 
 


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!