SAP VB_BATCH_CLASSIFIC_CHANGED Function Module for Checks if batch classification has been changed









VB_BATCH_CLASSIFIC_CHANGED is a standard vb batch classific changed SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Checks if batch classification has been changed 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 vb batch classific changed FM, simply by entering the name VB_BATCH_CLASSIFIC_CHANGED into the relevant SAP transaction such as SE37 or SE38.

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



Function VB_BATCH_CLASSIFIC_CHANGED 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 'VB_BATCH_CLASSIFIC_CHANGED'"Checks if batch classification has been changed
EXPORTING
IV_MATNR = "Material Number
IV_CHARG = "Batch Number
IV_WERKS = "Plant

IMPORTING
EV_CLASSIFICATION_CHANGED = "Checkbox
.




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_SAPLV01P_001 Initiator for Batch Status Change

IMPORTING Parameters details for VB_BATCH_CLASSIFIC_CHANGED

IV_MATNR - Material Number

Data type: MATNR
Optional: No
Call by Reference: Yes

IV_CHARG - Batch Number

Data type: CHARG_D
Optional: No
Call by Reference: Yes

IV_WERKS - Plant

Data type: WERKS_D
Optional: No
Call by Reference: Yes

EXPORTING Parameters details for VB_BATCH_CLASSIFIC_CHANGED

EV_CLASSIFICATION_CHANGED - Checkbox

Data type: XFELD
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for VB_BATCH_CLASSIFIC_CHANGED 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_iv_matnr  TYPE MATNR, "   
lv_ev_classification_changed  TYPE XFELD, "   
lv_iv_charg  TYPE CHARG_D, "   
lv_iv_werks  TYPE WERKS_D. "   

  CALL FUNCTION 'VB_BATCH_CLASSIFIC_CHANGED'  "Checks if batch classification has been changed
    EXPORTING
         IV_MATNR = lv_iv_matnr
         IV_CHARG = lv_iv_charg
         IV_WERKS = lv_iv_werks
    IMPORTING
         EV_CLASSIFICATION_CHANGED = lv_ev_classification_changed
. " VB_BATCH_CLASSIFIC_CHANGED




ABAP code using 7.40 inline data declarations to call FM VB_BATCH_CLASSIFIC_CHANGED

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



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!