SAP MBEW_MD_SINGLE_READ Function Module for Select Single from Mat. Val. Rec. and Add to Buffer









MBEW_MD_SINGLE_READ is a standard mbew md 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 Select Single from Mat. Val. Rec. and Add 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 mbew md single read FM, simply by entering the name MBEW_MD_SINGLE_READ into the relevant SAP transaction such as SE37 or SE38.

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



Function MBEW_MD_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 'MBEW_MD_SINGLE_READ'"Select Single from Mat. Val. Rec. and Add to Buffer
EXPORTING
* KZRFB = ' ' "Indicator: Refresh Buffer Entry
* MAXTZ = 0 "Max. No. of Entries in Buffer
MATNR = "Material Number
BWKEY = "Valuation Area
BWTAR = "Valuation Type
* SPERRMODUS = ' ' "Lock mode (none, shared, excl.)
* STD_SPERRMODUS = ' ' "Standard lock mode (if different)

IMPORTING
WMBEW_MD = "Material Valuation
O_MBEW_MD = "Material Valuation

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



IMPORTING Parameters details for MBEW_MD_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 - Material Number

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

BWKEY - Valuation Area

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

BWTAR - Valuation Type

Data type: MBEW-BWTAR
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 MBEW_MD_SINGLE_READ

WMBEW_MD - Material Valuation

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

O_MBEW_MD - Material Valuation

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

EXCEPTIONS details

LOCK_ON_MBEW -

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 MBEW_MD_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_wmbew_md  TYPE V_MBEW_MD, "   
lv_lock_on_mbew  TYPE V_MBEW_MD, "   
lv_maxtz  TYPE MTCOM-MAXTZ, "   0
lv_o_mbew_md  TYPE V_MBEW_MD, "   
lv_lock_system_error  TYPE V_MBEW_MD, "   
lv_matnr  TYPE MBEW-MATNR, "   
lv_wrong_call  TYPE MBEW, "   
lv_bwkey  TYPE MBEW-BWKEY, "   
lv_not_found  TYPE MBEW, "   
lv_bwtar  TYPE MBEW-BWTAR, "   
lv_sperrmodus  TYPE TVGVI-SPERA, "   ' '
lv_std_sperrmodus  TYPE TVGVI-SPERA. "   ' '

  CALL FUNCTION 'MBEW_MD_SINGLE_READ'  "Select Single from Mat. Val. Rec. and Add to Buffer
    EXPORTING
         KZRFB = lv_kzrfb
         MAXTZ = lv_maxtz
         MATNR = lv_matnr
         BWKEY = lv_bwkey
         BWTAR = lv_bwtar
         SPERRMODUS = lv_sperrmodus
         STD_SPERRMODUS = lv_std_sperrmodus
    IMPORTING
         WMBEW_MD = lv_wmbew_md
         O_MBEW_MD = lv_o_mbew_md
    EXCEPTIONS
        LOCK_ON_MBEW = 1
        LOCK_SYSTEM_ERROR = 2
        WRONG_CALL = 3
        NOT_FOUND = 4
. " MBEW_MD_SINGLE_READ




ABAP code using 7.40 inline data declarations to call FM MBEW_MD_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 MBEW INTO @DATA(ld_matnr).
 
 
"SELECT single BWKEY FROM MBEW INTO @DATA(ld_bwkey).
 
 
"SELECT single BWTAR FROM MBEW INTO @DATA(ld_bwtar).
 
"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!