SAP MBEW_VERPR Function Module for NOTRANSL: Prüfen Verrechnungspreis

Search SAP Function Modules

MBEW_VERPR is a standard mbew verpr 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üfen Verrechnungspreis 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 verpr FM, simply by entering the name MBEW_VERPR into the relevant SAP transaction such as SE37 or SE38.

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

Function MBEW_VERPR 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_VERPR'"NOTRANSL: Prüfen Verrechnungspreis
  EXPORTING
   WMBEW_VERPR =  "Cost
   WRMMG1_BWKEY =  "
   WRMMG1_BWTAR =  "
*  LMBEW_PEINH =  "Price Unit
   WMBEW_LBKUM =  "
   WMBEW_VPRSV =  "Price Control
*  WMBEW_PEINH =  "
   LMBEW_VERPR =  "
*  WMBEW_SALKV =  "
   P_AKTYP =  "Activity Type
*  P_MESSAGE = ' ' "
   WMBEW_MATNR =  "

 IMPORTING
   WMBEW_SALKV =  "

TABLES
   P_PTAB =  "

EXCEPTIONS
   WRONG_VERPR = 1 

.

IMPORTING Parameters details for MBEW_VERPR

WMBEW_VERPR - Cost

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

WRMMG1_BWKEY -

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

WRMMG1_BWTAR -

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

LMBEW_PEINH - Price Unit

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

WMBEW_LBKUM -

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

WMBEW_VPRSV - Price Control

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

WMBEW_PEINH -

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

LMBEW_VERPR -

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

WMBEW_SALKV -

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

P_AKTYP - Activity Type

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

P_MESSAGE -

Data type: RMMG08_012-MSGTYP
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

WMBEW_MATNR -

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

EXPORTING Parameters details for MBEW_VERPR

WMBEW_SALKV -

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

TABLES Parameters details for MBEW_VERPR

P_PTAB -

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

EXCEPTIONS details

WRONG_VERPR -

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

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

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