SAP MBEW_ZKPRS Function Module for NOTRANSL: Prüfen Zukünftiger Preis und Zukünftiges Datum
MBEW_ZKPRS is a standard mbew zkprs 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 Zukünftiger Preis und Zukünftiges Datum 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 zkprs FM, simply by entering the name MBEW_ZKPRS 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_ZKPRS 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_ZKPRS'"NOTRANSL: Prüfen Zukünftiger Preis und Zukünftiges Datum.
EXPORTING
WMBEW_ZKPRS = "Future Price
LMBEW_ZKDAT = "
WMBEW_ZKDAT = "Future Date
WMBEW_VPRSV = "
P_AKTYP = "Activity Type
* P_MESSAGE = ' ' "
WMBEW_MATNR = "
WRMMG1_BWKEY = "
WRMMG1_BWTAR = "
LMBEW_ZKPRS = "
IMPORTING
WMBEW_ZKDAT = "Future Date
EXCEPTIONS
ERROR_NACHRICHT = 1
IMPORTING Parameters details for MBEW_ZKPRS
WMBEW_ZKPRS - Future Price
Data type: MBEW-ZKPRSOptional: No
Call by Reference: No ( called with pass by value option)
LMBEW_ZKDAT -
Data type: MBEW-ZKDATOptional: No
Call by Reference: No ( called with pass by value option)
WMBEW_ZKDAT - Future Date
Data type: MBEW-ZKDATOptional: No
Call by Reference: No ( called with pass by value option)
WMBEW_VPRSV -
Data type: MBEW-VPRSVOptional: No
Call by Reference: No ( called with pass by value option)
P_AKTYP - Activity Type
Data type: T130M-AKTYPOptional: No
Call by Reference: No ( called with pass by value option)
P_MESSAGE -
Data type: RMMG08_012-MSGTYPDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
WMBEW_MATNR -
Data type: RMMG1-MATNROptional: No
Call by Reference: No ( called with pass by value option)
WRMMG1_BWKEY -
Data type: RMMG1-BWKEYOptional: No
Call by Reference: No ( called with pass by value option)
WRMMG1_BWTAR -
Data type: RMMG1-BWTAROptional: No
Call by Reference: No ( called with pass by value option)
LMBEW_ZKPRS -
Data type: MBEW-ZKPRSOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for MBEW_ZKPRS
WMBEW_ZKDAT - Future Date
Data type: MBEW-ZKDATOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
ERROR_NACHRICHT -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for MBEW_ZKPRS 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_wmbew_zkdat | TYPE MBEW-ZKDAT, " | |||
| lv_wmbew_zkprs | TYPE MBEW-ZKPRS, " | |||
| lv_error_nachricht | TYPE MBEW, " | |||
| lv_lmbew_zkdat | TYPE MBEW-ZKDAT, " | |||
| lv_wmbew_zkdat | TYPE MBEW-ZKDAT, " | |||
| lv_wmbew_vprsv | TYPE MBEW-VPRSV, " | |||
| lv_p_aktyp | TYPE T130M-AKTYP, " | |||
| lv_p_message | TYPE RMMG08_012-MSGTYP, " SPACE | |||
| lv_wmbew_matnr | TYPE RMMG1-MATNR, " | |||
| lv_wrmmg1_bwkey | TYPE RMMG1-BWKEY, " | |||
| lv_wrmmg1_bwtar | TYPE RMMG1-BWTAR, " | |||
| lv_lmbew_zkprs | TYPE MBEW-ZKPRS. " |
| CALL FUNCTION 'MBEW_ZKPRS' "NOTRANSL: Prüfen Zukünftiger Preis und Zukünftiges Datum |
| EXPORTING | ||
| WMBEW_ZKPRS | = lv_wmbew_zkprs | |
| LMBEW_ZKDAT | = lv_lmbew_zkdat | |
| WMBEW_ZKDAT | = lv_wmbew_zkdat | |
| WMBEW_VPRSV | = lv_wmbew_vprsv | |
| P_AKTYP | = lv_p_aktyp | |
| P_MESSAGE | = lv_p_message | |
| WMBEW_MATNR | = lv_wmbew_matnr | |
| WRMMG1_BWKEY | = lv_wrmmg1_bwkey | |
| WRMMG1_BWTAR | = lv_wrmmg1_bwtar | |
| LMBEW_ZKPRS | = lv_lmbew_zkprs | |
| IMPORTING | ||
| WMBEW_ZKDAT | = lv_wmbew_zkdat | |
| EXCEPTIONS | ||
| ERROR_NACHRICHT = 1 | ||
| . " MBEW_ZKPRS | ||
ABAP code using 7.40 inline data declarations to call FM MBEW_ZKPRS
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 ZKDAT FROM MBEW INTO @DATA(ld_wmbew_zkdat). | ||||
| "SELECT single ZKPRS FROM MBEW INTO @DATA(ld_wmbew_zkprs). | ||||
| "SELECT single ZKDAT FROM MBEW INTO @DATA(ld_lmbew_zkdat). | ||||
| "SELECT single ZKDAT FROM MBEW INTO @DATA(ld_wmbew_zkdat). | ||||
| "SELECT single VPRSV FROM MBEW INTO @DATA(ld_wmbew_vprsv). | ||||
| "SELECT single AKTYP FROM T130M INTO @DATA(ld_p_aktyp). | ||||
| "SELECT single MSGTYP FROM RMMG08_012 INTO @DATA(ld_p_message). | ||||
| DATA(ld_p_message) | = ' '. | |||
| "SELECT single MATNR FROM RMMG1 INTO @DATA(ld_wmbew_matnr). | ||||
| "SELECT single BWKEY FROM RMMG1 INTO @DATA(ld_wrmmg1_bwkey). | ||||
| "SELECT single BWTAR FROM RMMG1 INTO @DATA(ld_wrmmg1_bwtar). | ||||
| "SELECT single ZKPRS FROM MBEW INTO @DATA(ld_lmbew_zkprs). | ||||
Search for further information about these or an SAP related objects