SAP VBWS_BATCHES_VALUATION_FUTURE Function Module for NOTRANSL: Setzen des zukünftigen Preises aller Chargen eines Wirkstoffmate
VBWS_BATCHES_VALUATION_FUTURE is a standard vbws batches valuation future 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: Setzen des zukünftigen Preises aller Chargen eines Wirkstoffmate 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 vbws batches valuation future FM, simply by entering the name VBWS_BATCHES_VALUATION_FUTURE into the relevant SAP transaction such as SE37 or SE38.
Function Group: MWSB
Program Name: SAPLMWSB
Main Program: SAPLMWSB
Appliation area: M
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function VBWS_BATCHES_VALUATION_FUTURE 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 'VBWS_BATCHES_VALUATION_FUTURE'"NOTRANSL: Setzen des zukünftigen Preises aller Chargen eines Wirkstoffmate.
EXPORTING
I_MATNR = "Material
I_BWKEY = "Valuation Area
I_WERKS = "
* I_ZKDAT = "
* NO_PERFORM_ON_COMMIT = "Checkbox
EXCEPTIONS
NO_MATERIAL = 1 NO_PLANT = 2 NO_VALUATION_AREA = 3 NO_VARIABLE_VALUATION = 4
Customer Function user exits
Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.EXIT_SAPLMWSB_001 Activate Workaround: Factory Output
IMPORTING Parameters details for VBWS_BATCHES_VALUATION_FUTURE
I_MATNR - Material
Data type: MBEW-MATNROptional: No
Call by Reference: No ( called with pass by value option)
I_BWKEY - Valuation Area
Data type: MBEW-BWKEYOptional: No
Call by Reference: No ( called with pass by value option)
I_WERKS -
Data type: MARC-WERKSOptional: No
Call by Reference: No ( called with pass by value option)
I_ZKDAT -
Data type: MBEW-ZKDATOptional: Yes
Call by Reference: No ( called with pass by value option)
NO_PERFORM_ON_COMMIT - Checkbox
Data type: XFELDOptional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
NO_MATERIAL -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NO_PLANT -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NO_VALUATION_AREA -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NO_VARIABLE_VALUATION -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for VBWS_BATCHES_VALUATION_FUTURE 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_i_matnr | TYPE MBEW-MATNR, " | |||
| lv_no_material | TYPE MBEW, " | |||
| lv_i_bwkey | TYPE MBEW-BWKEY, " | |||
| lv_no_plant | TYPE MBEW, " | |||
| lv_i_werks | TYPE MARC-WERKS, " | |||
| lv_no_valuation_area | TYPE MARC, " | |||
| lv_i_zkdat | TYPE MBEW-ZKDAT, " | |||
| lv_no_variable_valuation | TYPE MBEW, " | |||
| lv_no_perform_on_commit | TYPE XFELD. " |
|   CALL FUNCTION 'VBWS_BATCHES_VALUATION_FUTURE' "NOTRANSL: Setzen des zukünftigen Preises aller Chargen eines Wirkstoffmate |
| EXPORTING | ||
| I_MATNR | = lv_i_matnr | |
| I_BWKEY | = lv_i_bwkey | |
| I_WERKS | = lv_i_werks | |
| I_ZKDAT | = lv_i_zkdat | |
| NO_PERFORM_ON_COMMIT | = lv_no_perform_on_commit | |
| EXCEPTIONS | ||
| NO_MATERIAL = 1 | ||
| NO_PLANT = 2 | ||
| NO_VALUATION_AREA = 3 | ||
| NO_VARIABLE_VALUATION = 4 | ||
| . " VBWS_BATCHES_VALUATION_FUTURE | ||
ABAP code using 7.40 inline data declarations to call FM VBWS_BATCHES_VALUATION_FUTURE
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 MATNR FROM MBEW INTO @DATA(ld_i_matnr). | ||||
| "SELECT single BWKEY FROM MBEW INTO @DATA(ld_i_bwkey). | ||||
| "SELECT single WERKS FROM MARC INTO @DATA(ld_i_werks). | ||||
| "SELECT single ZKDAT FROM MBEW INTO @DATA(ld_i_zkdat). | ||||
Search for further information about these or an SAP related objects