SAP SD_DELIVERY_VIEW Function Module for Data collection for printing









SD_DELIVERY_VIEW is a standard sd delivery view SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Data collection for printing 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 sd delivery view FM, simply by entering the name SD_DELIVERY_VIEW into the relevant SAP transaction such as SE37 or SE38.

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



Function SD_DELIVERY_VIEW 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 'SD_DELIVERY_VIEW'"Data collection for printing
EXPORTING
COMWA = "
* AUFTRAG_NICHT_LESEN = ' ' "
* EXPORTDATEN_NICHT_LESEN = ' ' "
* GEFAHRGUT_NICHT_LESEN = ' ' "
* EDI = ' ' "EDI processing

IMPORTING
VBPLA_WA = "

TABLES
VBDKL_TAB = "
VBDPL_TAB = "
VBPLK_TAB = "
VBPLP_TAB = "
VBPLS_TAB = "

EXCEPTIONS
OBJECT_NOT_FOUND = 1
.



IMPORTING Parameters details for SD_DELIVERY_VIEW

COMWA -

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

AUFTRAG_NICHT_LESEN -

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

EXPORTDATEN_NICHT_LESEN -

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

GEFAHRGUT_NICHT_LESEN -

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

EDI - EDI processing

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

EXPORTING Parameters details for SD_DELIVERY_VIEW

VBPLA_WA -

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

TABLES Parameters details for SD_DELIVERY_VIEW

VBDKL_TAB -

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

VBDPL_TAB -

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

VBPLK_TAB -

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

VBPLP_TAB -

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

VBPLS_TAB -

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

EXCEPTIONS details

OBJECT_NOT_FOUND -

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

Copy and paste ABAP code example for SD_DELIVERY_VIEW 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_comwa  TYPE VBCO3, "   
lv_vbpla_wa  TYPE VBPLA, "   
lt_vbdkl_tab  TYPE STANDARD TABLE OF VBDKL, "   
lv_object_not_found  TYPE VBDKL, "   
lt_vbdpl_tab  TYPE STANDARD TABLE OF VBDPL, "   
lv_auftrag_nicht_lesen  TYPE RVSEL-XFELD, "   SPACE
lt_vbplk_tab  TYPE STANDARD TABLE OF VBPLK, "   
lv_exportdaten_nicht_lesen  TYPE RVSEL-XFELD, "   SPACE
lt_vbplp_tab  TYPE STANDARD TABLE OF VBPLP, "   
lv_gefahrgut_nicht_lesen  TYPE RVSEL-XFELD, "   SPACE
lv_edi  TYPE RVSEL, "   SPACE
lt_vbpls_tab  TYPE STANDARD TABLE OF VBPLS. "   

  CALL FUNCTION 'SD_DELIVERY_VIEW'  "Data collection for printing
    EXPORTING
         COMWA = lv_comwa
         AUFTRAG_NICHT_LESEN = lv_auftrag_nicht_lesen
         EXPORTDATEN_NICHT_LESEN = lv_exportdaten_nicht_lesen
         GEFAHRGUT_NICHT_LESEN = lv_gefahrgut_nicht_lesen
         EDI = lv_edi
    IMPORTING
         VBPLA_WA = lv_vbpla_wa
    TABLES
         VBDKL_TAB = lt_vbdkl_tab
         VBDPL_TAB = lt_vbdpl_tab
         VBPLK_TAB = lt_vbplk_tab
         VBPLP_TAB = lt_vbplp_tab
         VBPLS_TAB = lt_vbpls_tab
    EXCEPTIONS
        OBJECT_NOT_FOUND = 1
. " SD_DELIVERY_VIEW




ABAP code using 7.40 inline data declarations to call FM SD_DELIVERY_VIEW

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 XFELD FROM RVSEL INTO @DATA(ld_auftrag_nicht_lesen).
DATA(ld_auftrag_nicht_lesen) = ' '.
 
 
"SELECT single XFELD FROM RVSEL INTO @DATA(ld_exportdaten_nicht_lesen).
DATA(ld_exportdaten_nicht_lesen) = ' '.
 
 
"SELECT single XFELD FROM RVSEL INTO @DATA(ld_gefahrgut_nicht_lesen).
DATA(ld_gefahrgut_nicht_lesen) = ' '.
 
DATA(ld_edi) = ' '.
 
 


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!