SAP VB_BATCH_READ_CLOG_BUFFER Function Module for Read batch from buffer / db
VB_BATCH_READ_CLOG_BUFFER is a standard vb batch read clog buffer SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Read batch from buffer / db 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 read clog buffer FM, simply by entering the name VB_BATCH_READ_CLOG_BUFFER into the relevant SAP transaction such as SE37 or SE38.
Function Group: V01P
Program Name: SAPLV01P
Main Program: SAPLV01P
Appliation area: M
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function VB_BATCH_READ_CLOG_BUFFER 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_READ_CLOG_BUFFER'"Read batch from buffer / db.
EXPORTING
* MATNR = "Reference Material
* CHARG = "
* WERKS = "Reference Plant
* IMP_OBJECT = "Key of Object to Be Classified
IMPORTING
BATCH_CUOBJ = "Configuration (Internal Object Number)
BATCH_OBJEK = "Key of Object to Be Classified
BATCH_CLASS = "Class Number
EXCEPTIONS
NO_MATERIAL = 1 NO_BATCH = 2 NO_PLANT = 3 OBJECT_NOT_FOUND = 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_SAPLV01P_001 Initiator for Batch Status Change
IMPORTING Parameters details for VB_BATCH_READ_CLOG_BUFFER
MATNR - Reference Material
Data type: MARA-MATNROptional: Yes
Call by Reference: No ( called with pass by value option)
CHARG -
Data type: MCH1-CHARGOptional: Yes
Call by Reference: No ( called with pass by value option)
WERKS - Reference Plant
Data type: T001W-WERKSOptional: Yes
Call by Reference: No ( called with pass by value option)
IMP_OBJECT - Key of Object to Be Classified
Data type: INOB-OBJEKOptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for VB_BATCH_READ_CLOG_BUFFER
BATCH_CUOBJ - Configuration (Internal Object Number)
Data type: INOB-CUOBJOptional: No
Call by Reference: No ( called with pass by value option)
BATCH_OBJEK - Key of Object to Be Classified
Data type: INOB-OBJEKOptional: No
Call by Reference: No ( called with pass by value option)
BATCH_CLASS - Class Number
Data type: RMCLF-CLASSOptional: No
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_BATCH -
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)
OBJECT_NOT_FOUND -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for VB_BATCH_READ_CLOG_BUFFER 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_matnr | TYPE MARA-MATNR, " | |||
| lv_batch_cuobj | TYPE INOB-CUOBJ, " | |||
| lv_no_material | TYPE INOB, " | |||
| lv_charg | TYPE MCH1-CHARG, " | |||
| lv_no_batch | TYPE MCH1, " | |||
| lv_batch_objek | TYPE INOB-OBJEK, " | |||
| lv_werks | TYPE T001W-WERKS, " | |||
| lv_no_plant | TYPE T001W, " | |||
| lv_batch_class | TYPE RMCLF-CLASS, " | |||
| lv_imp_object | TYPE INOB-OBJEK, " | |||
| lv_object_not_found | TYPE INOB. " |
|   CALL FUNCTION 'VB_BATCH_READ_CLOG_BUFFER' "Read batch from buffer / db |
| EXPORTING | ||
| MATNR | = lv_matnr | |
| CHARG | = lv_charg | |
| WERKS | = lv_werks | |
| IMP_OBJECT | = lv_imp_object | |
| IMPORTING | ||
| BATCH_CUOBJ | = lv_batch_cuobj | |
| BATCH_OBJEK | = lv_batch_objek | |
| BATCH_CLASS | = lv_batch_class | |
| EXCEPTIONS | ||
| NO_MATERIAL = 1 | ||
| NO_BATCH = 2 | ||
| NO_PLANT = 3 | ||
| OBJECT_NOT_FOUND = 4 | ||
| . " VB_BATCH_READ_CLOG_BUFFER | ||
ABAP code using 7.40 inline data declarations to call FM VB_BATCH_READ_CLOG_BUFFER
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 MARA INTO @DATA(ld_matnr). | ||||
| "SELECT single CUOBJ FROM INOB INTO @DATA(ld_batch_cuobj). | ||||
| "SELECT single CHARG FROM MCH1 INTO @DATA(ld_charg). | ||||
| "SELECT single OBJEK FROM INOB INTO @DATA(ld_batch_objek). | ||||
| "SELECT single WERKS FROM T001W INTO @DATA(ld_werks). | ||||
| "SELECT single CLASS FROM RMCLF INTO @DATA(ld_batch_class). | ||||
| "SELECT single OBJEK FROM INOB INTO @DATA(ld_imp_object). | ||||
Search for further information about these or an SAP related objects