SAP RV_DISPATCH_DUE_DATE_POSITION Function Module for NOTRANSL: Ermitteln versandfälliger Positionen

Search SAP Function Modules

RV_DISPATCH_DUE_DATE_POSITION is a standard rv dispatch due date position 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: Ermitteln versandfälliger Positionen 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 rv dispatch due date position FM, simply by entering the name RV_DISPATCH_DUE_DATE_POSITION into the relevant SAP transaction such as SE37 or SE38.

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

Function RV_DISPATCH_DUE_DATE_POSITION 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 'RV_DISPATCH_DUE_DATE_POSITION'"NOTRANSL: Ermitteln versandfälliger Positionen
  EXPORTING
*  COMWA = '000' "
   VEPVG_WA =  "Delivery due index data record
   ZAEHLER =  "Pointer from item due for shipping

 IMPORTING
   BRGEW =  "
   GEWEI =  "
   MAXZT =  "
   POSITIONS =  "
   VOLEH =  "
   VOLUM =  "

TABLES
   VBVFP_TAB =  "determined items due for shipping

.

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_SAPLV05I_001 User Exit for Order-Related Billing Index
EXIT_SAPLV05I_002 User Exit for Billing Index for Delivery Reference
EXIT_SAPLV05I_003 User Exit for Billing Index with Reference to IV
EXIT_SAPLV05I_004 User Exit for Billing Index for Invoice List Reference

IMPORTING Parameters details for RV_DISPATCH_DUE_DATE_POSITION

COMWA -

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

VEPVG_WA - Delivery due index data record

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

ZAEHLER - Pointer from item due for shipping

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

EXPORTING Parameters details for RV_DISPATCH_DUE_DATE_POSITION

BRGEW -

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

GEWEI -

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

MAXZT -

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

POSITIONS -

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

VOLEH -

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

VOLUM -

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

TABLES Parameters details for RV_DISPATCH_DUE_DATE_POSITION

VBVFP_TAB - determined items due for shipping

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

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

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