SAP VBWS_BATCH_VALUATION_CHANGE_UD Function Module for NOTRANSL: Umbewertung einer Charge bei variablen ME (nur im Verwendungsent

Search SAP Function Modules

VBWS_BATCH_VALUATION_CHANGE_UD is a standard vbws batch valuation change ud 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: Umbewertung einer Charge bei variablen ME (nur im Verwendungsent 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 batch valuation change ud FM, simply by entering the name VBWS_BATCH_VALUATION_CHANGE_UD 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): Remote-Enabled
Update:

Function VBWS_BATCH_VALUATION_CHANGE_UD 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_BATCH_VALUATION_CHANGE_UD'"NOTRANSL: Umbewertung einer Charge bei variablen ME (nur im Verwendungsent
  EXPORTING
   I_MATNR =  "
   I_WERKS =  "
   I_CHARG =  "
*  I_QPLOS =  "Inspection Lot Number
*  BYPASS_POST = ' ' "

TABLES
*  E_IMSEG =  "MMIM: Input Structure for General FM to Post Goods Movement

EXCEPTIONS
   NO_MATERIAL = 1    NO_PLANT = 2    NO_BATCH = 3    NO_VALUATION_AREA = 4    NO_VARIABLE_VALUATION = 5    ERROR_FI_POSTING = 6 

.

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_BATCH_VALUATION_CHANGE_UD

I_MATNR -

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

I_WERKS -

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

I_CHARG -

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

I_QPLOS - Inspection Lot Number

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

BYPASS_POST -

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

TABLES Parameters details for VBWS_BATCH_VALUATION_CHANGE_UD

E_IMSEG - MMIM: Input Structure for General FM to Post Goods Movement

Data type: IMSEG
Optional: Yes
Call by Reference: Yes

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_BATCH -

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)

ERROR_FI_POSTING -

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

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

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