SAP ISP_JVTMODZEBU_BUFFER_READ Function Module for









ISP_JVTMODZEBU_BUFFER_READ is a standard isp jvtmodzebu buffer read SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 isp jvtmodzebu buffer read FM, simply by entering the name ISP_JVTMODZEBU_BUFFER_READ into the relevant SAP transaction such as SE37 or SE38.

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



Function ISP_JVTMODZEBU_BUFFER_READ 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 'ISP_JVTMODZEBU_BUFFER_READ'"
EXPORTING
* BFS_STUFE = ' ' "
ZEBUART = "
* DRERZ = ' ' "
LAND = "
* LIEFERART = ' ' "
* NETZ = ' ' "
* PLZ = ' ' "
* PVA = ' ' "
WERK = "
* XGENERIC = ' ' "

IMPORTING
OUT_JVTMODZEBU = "

TABLES
MODZEBU_TAB = "

EXCEPTIONS
DRERZ_NOT_FOUND = 1
.



IMPORTING Parameters details for ISP_JVTMODZEBU_BUFFER_READ

BFS_STUFE -

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

ZEBUART -

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

DRERZ -

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

LAND -

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

LIEFERART -

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

NETZ -

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

PLZ -

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

PVA -

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

WERK -

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

XGENERIC -

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

EXPORTING Parameters details for ISP_JVTMODZEBU_BUFFER_READ

OUT_JVTMODZEBU -

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

TABLES Parameters details for ISP_JVTMODZEBU_BUFFER_READ

MODZEBU_TAB -

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

EXCEPTIONS details

DRERZ_NOT_FOUND -

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

Copy and paste ABAP code example for ISP_JVTMODZEBU_BUFFER_READ 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_bfs_stufe  TYPE JVTMODZEBU-BFS_STUFE, "   SPACE
lt_modzebu_tab  TYPE STANDARD TABLE OF JVTMODZEBU, "   
lv_out_jvtmodzebu  TYPE JVTMODZEBU, "   
lv_drerz_not_found  TYPE JVTMODZEBU, "   
lv_zebuart  TYPE JVTMODZEBU-ZEBUART, "   
lv_drerz  TYPE JVTMODZEBU-DRERZ, "   SPACE
lv_land  TYPE JVTMODZEBU-LAND1, "   
lv_lieferart  TYPE JVTMODZEBU-LIEFERART, "   SPACE
lv_netz  TYPE JVTMODZEBU-NETZ, "   SPACE
lv_plz  TYPE JVTMODZEBU-PLZ, "   SPACE
lv_pva  TYPE JVTMODZEBU-PVA, "   SPACE
lv_werk  TYPE JVTMODZEBU-DRUCKEREI, "   
lv_xgeneric  TYPE JVTMODZEBU-XBUND. "   SPACE

  CALL FUNCTION 'ISP_JVTMODZEBU_BUFFER_READ'  "
    EXPORTING
         BFS_STUFE = lv_bfs_stufe
         ZEBUART = lv_zebuart
         DRERZ = lv_drerz
         LAND = lv_land
         LIEFERART = lv_lieferart
         NETZ = lv_netz
         PLZ = lv_plz
         PVA = lv_pva
         WERK = lv_werk
         XGENERIC = lv_xgeneric
    IMPORTING
         OUT_JVTMODZEBU = lv_out_jvtmodzebu
    TABLES
         MODZEBU_TAB = lt_modzebu_tab
    EXCEPTIONS
        DRERZ_NOT_FOUND = 1
. " ISP_JVTMODZEBU_BUFFER_READ




ABAP code using 7.40 inline data declarations to call FM ISP_JVTMODZEBU_BUFFER_READ

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 BFS_STUFE FROM JVTMODZEBU INTO @DATA(ld_bfs_stufe).
DATA(ld_bfs_stufe) = ' '.
 
 
 
 
"SELECT single ZEBUART FROM JVTMODZEBU INTO @DATA(ld_zebuart).
 
"SELECT single DRERZ FROM JVTMODZEBU INTO @DATA(ld_drerz).
DATA(ld_drerz) = ' '.
 
"SELECT single LAND1 FROM JVTMODZEBU INTO @DATA(ld_land).
 
"SELECT single LIEFERART FROM JVTMODZEBU INTO @DATA(ld_lieferart).
DATA(ld_lieferart) = ' '.
 
"SELECT single NETZ FROM JVTMODZEBU INTO @DATA(ld_netz).
DATA(ld_netz) = ' '.
 
"SELECT single PLZ FROM JVTMODZEBU INTO @DATA(ld_plz).
DATA(ld_plz) = ' '.
 
"SELECT single PVA FROM JVTMODZEBU INTO @DATA(ld_pva).
DATA(ld_pva) = ' '.
 
"SELECT single DRUCKEREI FROM JVTMODZEBU INTO @DATA(ld_werk).
 
"SELECT single XBUND FROM JVTMODZEBU INTO @DATA(ld_xgeneric).
DATA(ld_xgeneric) = ' '.
 


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!