SAP ME_VARIANTS_PURCHASING Function Module for NOTRANSL: Pflegen von Varianten

Search SAP Function Modules

ME_VARIANTS_PURCHASING is a standard me variants purchasing 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: Pflegen von Varianten 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 me variants purchasing FM, simply by entering the name ME_VARIANTS_PURCHASING into the relevant SAP transaction such as SE37 or SE38.

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

Function ME_VARIANTS_PURCHASING 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 'ME_VARIANTS_PURCHASING'"NOTRANSL: Pflegen von Varianten
  EXPORTING
   I_EKPO =  "Purchasing Document Item
   I_EKKO =  "Purchasing Document Header
*  I_AKTYP =  "
*  I_SUBSCREEN =  "

 IMPORTING
   E_MENGE =  "Purchase Order Quantity
   E_CODE =  "ABAP System Field: Current Dynpro Number
   E_DYNPRO =  "ABAP Program, Current Screen Number

CHANGING
   E_CHANGE =  "

TABLES
   TEKPO =  "Purchasing Document Item
   TVAR =  "Variant Data: Purchasing
   TETT =  "Tfr. Structure Sch. Lines for Ord. Acceptance Confirmations

.

IMPORTING Parameters details for ME_VARIANTS_PURCHASING

I_EKPO - Purchasing Document Item

Data type: EKPO
Optional: No
Call by Reference: No ( called with pass by value option)

I_EKKO - Purchasing Document Header

Data type: EKKO
Optional: No
Call by Reference: No ( called with pass by value option)

I_AKTYP -

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

I_SUBSCREEN -

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

EXPORTING Parameters details for ME_VARIANTS_PURCHASING

E_MENGE - Purchase Order Quantity

Data type: EKPO-MENGE
Optional: No
Call by Reference: No ( called with pass by value option)

E_CODE - ABAP System Field: Current Dynpro Number

Data type: SY-DYNNR
Optional: No
Call by Reference: No ( called with pass by value option)

E_DYNPRO - ABAP Program, Current Screen Number

Data type: SY-DYNNR
Optional: No
Call by Reference: No ( called with pass by value option)

CHANGING Parameters details for ME_VARIANTS_PURCHASING

E_CHANGE -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for ME_VARIANTS_PURCHASING

TEKPO - Purchasing Document Item

Data type: EKPO
Optional: No
Call by Reference: No ( called with pass by value option)

TVAR - Variant Data: Purchasing

Data type: EVARART
Optional: No
Call by Reference: No ( called with pass by value option)

TETT - Tfr. Structure Sch. Lines for Ord. Acceptance Confirmations

Data type: BEKET
Optional: No
Call by Reference: No ( called with pass by value option)

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

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