SAP MVKE_SINGLE_READ Function Module for Access (Select Single) to MVKE with Addition to Buffer









MVKE_SINGLE_READ is a standard mvke single read SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Access (Select Single) to MVKE with Addition to Buffer 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 mvke single read FM, simply by entering the name MVKE_SINGLE_READ into the relevant SAP transaction such as SE37 or SE38.

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



Function MVKE_SINGLE_READ 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 'MVKE_SINGLE_READ'"Access (Select Single) to MVKE with Addition to Buffer
EXPORTING
* KZRFB = ' ' "Indicator: Refresh Buffer Entry
* MAXTZ = 0 "Max. No. of Entries in Buffer
MATNR = "
VKORG = "
VTWEG = "
* SPERRMODUS = ' ' "Lock mode (none, shared, excl.)
* STD_SPERRMODUS = ' ' "Standard lock mode (if different)

IMPORTING
WMVKE = "
O_MVKE = "

EXCEPTIONS
LOCK_ON_MVKE = 1 LOCK_SYSTEM_ERROR = 2 WRONG_CALL = 3 NOT_FOUND = 4
.



IMPORTING Parameters details for MVKE_SINGLE_READ

KZRFB - Indicator: Refresh Buffer Entry

Data type: MTCOM-KZRFB
Default: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)

MAXTZ - Max. No. of Entries in Buffer

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

MATNR -

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

VKORG -

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

VTWEG -

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

SPERRMODUS - Lock mode (none, shared, excl.)

Data type: TVGVI-SPERA
Default: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)

STD_SPERRMODUS - Standard lock mode (if different)

Data type: TVGVI-SPERA
Default: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for MVKE_SINGLE_READ

WMVKE -

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

O_MVKE -

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

EXCEPTIONS details

LOCK_ON_MVKE -

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

LOCK_SYSTEM_ERROR -

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

WRONG_CALL -

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

NOT_FOUND -

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

Copy and paste ABAP code example for MVKE_SINGLE_READ 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_kzrfb  TYPE MTCOM-KZRFB, "   ' '
lv_wmvke  TYPE MVKE, "   
lv_lock_on_mvke  TYPE MVKE, "   
lv_maxtz  TYPE MTCOM-MAXTZ, "   0
lv_o_mvke  TYPE MVKE, "   
lv_lock_system_error  TYPE MVKE, "   
lv_matnr  TYPE MVKE-MATNR, "   
lv_wrong_call  TYPE MVKE, "   
lv_vkorg  TYPE MVKE-VKORG, "   
lv_not_found  TYPE MVKE, "   
lv_vtweg  TYPE MVKE-VTWEG, "   
lv_sperrmodus  TYPE TVGVI-SPERA, "   ' '
lv_std_sperrmodus  TYPE TVGVI-SPERA. "   ' '

  CALL FUNCTION 'MVKE_SINGLE_READ'  "Access (Select Single) to MVKE with Addition to Buffer
    EXPORTING
         KZRFB = lv_kzrfb
         MAXTZ = lv_maxtz
         MATNR = lv_matnr
         VKORG = lv_vkorg
         VTWEG = lv_vtweg
         SPERRMODUS = lv_sperrmodus
         STD_SPERRMODUS = lv_std_sperrmodus
    IMPORTING
         WMVKE = lv_wmvke
         O_MVKE = lv_o_mvke
    EXCEPTIONS
        LOCK_ON_MVKE = 1
        LOCK_SYSTEM_ERROR = 2
        WRONG_CALL = 3
        NOT_FOUND = 4
. " MVKE_SINGLE_READ




ABAP code using 7.40 inline data declarations to call FM MVKE_SINGLE_READ

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 KZRFB FROM MTCOM INTO @DATA(ld_kzrfb).
DATA(ld_kzrfb) = ' '.
 
 
 
"SELECT single MAXTZ FROM MTCOM INTO @DATA(ld_maxtz).
 
 
 
"SELECT single MATNR FROM MVKE INTO @DATA(ld_matnr).
 
 
"SELECT single VKORG FROM MVKE INTO @DATA(ld_vkorg).
 
 
"SELECT single VTWEG FROM MVKE INTO @DATA(ld_vtweg).
 
"SELECT single SPERA FROM TVGVI INTO @DATA(ld_sperrmodus).
DATA(ld_sperrmodus) = ' '.
 
"SELECT single SPERA FROM TVGVI INTO @DATA(ld_std_sperrmodus).
DATA(ld_std_sperrmodus) = ' '.
 


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!