SAP SD_DELIVERY_DATE_CHECK Function Module for NOTRANSL: Überprufung der Warenannahmezeiten eines Kunden
SD_DELIVERY_DATE_CHECK is a standard sd delivery date check 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: Überprufung der Warenannahmezeiten eines Kunden 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 date check FM, simply by entering the name SD_DELIVERY_DATE_CHECK into the relevant SAP transaction such as SE37 or SE38.
Function Group: V45E
Program Name: SAPLV45E
Main Program: SAPLV45E
Appliation area: V
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function SD_DELIVERY_DATE_CHECK 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_DATE_CHECK'"NOTRANSL: Überprufung der Warenannahmezeiten eines Kunden.
EXPORTING
I_DATE = "
I_TIME = "
RECEIVER = "
* I_INDEX = "
* I_STATUS = "
IMPORTING
E_DATE = "
E_TIME = "
E_SUBRC = "
EXCEPTIONS
ERROR = 1 MESSAGE_ISSUED = 2 MESSAGE_WITH_CURSOR = 3
IMPORTING Parameters details for SD_DELIVERY_DATE_CHECK
I_DATE -
Data type: VBEP-EDATUOptional: No
Call by Reference: No ( called with pass by value option)
I_TIME -
Data type: VBEP-EZEITOptional: No
Call by Reference: No ( called with pass by value option)
RECEIVER -
Data type: KUWEVOptional: No
Call by Reference: No ( called with pass by value option)
I_INDEX -
Data type: SY-INDEXOptional: Yes
Call by Reference: No ( called with pass by value option)
I_STATUS -
Data type: SY-MSGTYOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for SD_DELIVERY_DATE_CHECK
E_DATE -
Data type: VBEP-EDATUOptional: No
Call by Reference: No ( called with pass by value option)
E_TIME -
Data type: VBEP-EZEITOptional: No
Call by Reference: No ( called with pass by value option)
E_SUBRC -
Data type: SY-SUBRCOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
ERROR -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
MESSAGE_ISSUED -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
MESSAGE_WITH_CURSOR -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for SD_DELIVERY_DATE_CHECK 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_error | TYPE STRING, " | |||
| lv_e_date | TYPE VBEP-EDATU, " | |||
| lv_i_date | TYPE VBEP-EDATU, " | |||
| lv_e_time | TYPE VBEP-EZEIT, " | |||
| lv_i_time | TYPE VBEP-EZEIT, " | |||
| lv_message_issued | TYPE VBEP, " | |||
| lv_e_subrc | TYPE SY-SUBRC, " | |||
| lv_receiver | TYPE KUWEV, " | |||
| lv_message_with_cursor | TYPE KUWEV, " | |||
| lv_i_index | TYPE SY-INDEX, " | |||
| lv_i_status | TYPE SY-MSGTY. " |
|   CALL FUNCTION 'SD_DELIVERY_DATE_CHECK' "NOTRANSL: Überprufung der Warenannahmezeiten eines Kunden |
| EXPORTING | ||
| I_DATE | = lv_i_date | |
| I_TIME | = lv_i_time | |
| RECEIVER | = lv_receiver | |
| I_INDEX | = lv_i_index | |
| I_STATUS | = lv_i_status | |
| IMPORTING | ||
| E_DATE | = lv_e_date | |
| E_TIME | = lv_e_time | |
| E_SUBRC | = lv_e_subrc | |
| EXCEPTIONS | ||
| ERROR = 1 | ||
| MESSAGE_ISSUED = 2 | ||
| MESSAGE_WITH_CURSOR = 3 | ||
| . " SD_DELIVERY_DATE_CHECK | ||
ABAP code using 7.40 inline data declarations to call FM SD_DELIVERY_DATE_CHECK
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 EDATU FROM VBEP INTO @DATA(ld_e_date). | ||||
| "SELECT single EDATU FROM VBEP INTO @DATA(ld_i_date). | ||||
| "SELECT single EZEIT FROM VBEP INTO @DATA(ld_e_time). | ||||
| "SELECT single EZEIT FROM VBEP INTO @DATA(ld_i_time). | ||||
| "SELECT single SUBRC FROM SY INTO @DATA(ld_e_subrc). | ||||
| "SELECT single INDEX FROM SY INTO @DATA(ld_i_index). | ||||
| "SELECT single MSGTY FROM SY INTO @DATA(ld_i_status). | ||||
Search for further information about these or an SAP related objects