SAP MD_CHECK_DELIVERY_DATE Function Module for NOTRANSL: Berechnung Lieferdatum (auch feste Tage)
MD_CHECK_DELIVERY_DATE is a standard md check delivery date 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: Berechnung Lieferdatum (auch feste Tage) 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 md check delivery date FM, simply by entering the name MD_CHECK_DELIVERY_DATE into the relevant SAP transaction such as SE37 or SE38.
Function Group: M61S
Program Name: SAPLM61S
Main Program:
Appliation area: W
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function MD_CHECK_DELIVERY_DATE 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 'MD_CHECK_DELIVERY_DATE'"NOTRANSL: Berechnung Lieferdatum (auch feste Tage).
EXPORTING
E_WERKS = "Plant
E_FABKL = "Factory calendar key
* E_ANLIEFKAL = "PPC planning calendar
E_PLIFZ = "Planned Delivery Time
E_DISPODATUM = "MRP Date
* E_LIEFERDATUM = "Receipt/Requirements date
* E_KZ_BZTEK = "New Input Values
IMPORTING
I_LIEFERTAG_FRUEHEST = "Receipt/Requirements date
I_RHYTHM_TAG_VORHER = "Receipt/Requirements date
I_RHYTHM_TAG_NACHHER = "Receipt/Requirements date
EXCEPTIONS
DATE_OUT_OF_CAL = 1
IMPORTING Parameters details for MD_CHECK_DELIVERY_DATE
E_WERKS - Plant
Data type: MARC-WERKSOptional: No
Call by Reference: No ( called with pass by value option)
E_FABKL - Factory calendar key
Data type: T001W-FABKLOptional: No
Call by Reference: No ( called with pass by value option)
E_ANLIEFKAL - PPC planning calendar
Data type: MARC-MRPPPOptional: Yes
Call by Reference: No ( called with pass by value option)
E_PLIFZ - Planned Delivery Time
Data type: MARC-PLIFZOptional: No
Call by Reference: No ( called with pass by value option)
E_DISPODATUM - MRP Date
Data type: MDPS-DAT00Optional: No
Call by Reference: No ( called with pass by value option)
E_LIEFERDATUM - Receipt/Requirements date
Data type: MDPS-DAT00Optional: Yes
Call by Reference: No ( called with pass by value option)
E_KZ_BZTEK - New Input Values
Data type: XFLAGOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for MD_CHECK_DELIVERY_DATE
I_LIEFERTAG_FRUEHEST - Receipt/Requirements date
Data type: MDPS-DAT00Optional: No
Call by Reference: No ( called with pass by value option)
I_RHYTHM_TAG_VORHER - Receipt/Requirements date
Data type: MDPS-DAT00Optional: No
Call by Reference: No ( called with pass by value option)
I_RHYTHM_TAG_NACHHER - Receipt/Requirements date
Data type: MDPS-DAT00Optional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
DATE_OUT_OF_CAL -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for MD_CHECK_DELIVERY_DATE 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_e_werks | TYPE MARC-WERKS, " | |||
| lv_date_out_of_cal | TYPE MARC, " | |||
| lv_i_liefertag_fruehest | TYPE MDPS-DAT00, " | |||
| lv_e_fabkl | TYPE T001W-FABKL, " | |||
| lv_i_rhythm_tag_vorher | TYPE MDPS-DAT00, " | |||
| lv_e_anliefkal | TYPE MARC-MRPPP, " | |||
| lv_i_rhythm_tag_nachher | TYPE MDPS-DAT00, " | |||
| lv_e_plifz | TYPE MARC-PLIFZ, " | |||
| lv_e_dispodatum | TYPE MDPS-DAT00, " | |||
| lv_e_lieferdatum | TYPE MDPS-DAT00, " | |||
| lv_e_kz_bztek | TYPE XFLAG. " |
|   CALL FUNCTION 'MD_CHECK_DELIVERY_DATE' "NOTRANSL: Berechnung Lieferdatum (auch feste Tage) |
| EXPORTING | ||
| E_WERKS | = lv_e_werks | |
| E_FABKL | = lv_e_fabkl | |
| E_ANLIEFKAL | = lv_e_anliefkal | |
| E_PLIFZ | = lv_e_plifz | |
| E_DISPODATUM | = lv_e_dispodatum | |
| E_LIEFERDATUM | = lv_e_lieferdatum | |
| E_KZ_BZTEK | = lv_e_kz_bztek | |
| IMPORTING | ||
| I_LIEFERTAG_FRUEHEST | = lv_i_liefertag_fruehest | |
| I_RHYTHM_TAG_VORHER | = lv_i_rhythm_tag_vorher | |
| I_RHYTHM_TAG_NACHHER | = lv_i_rhythm_tag_nachher | |
| EXCEPTIONS | ||
| DATE_OUT_OF_CAL = 1 | ||
| . " MD_CHECK_DELIVERY_DATE | ||
ABAP code using 7.40 inline data declarations to call FM MD_CHECK_DELIVERY_DATE
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 WERKS FROM MARC INTO @DATA(ld_e_werks). | ||||
| "SELECT single DAT00 FROM MDPS INTO @DATA(ld_i_liefertag_fruehest). | ||||
| "SELECT single FABKL FROM T001W INTO @DATA(ld_e_fabkl). | ||||
| "SELECT single DAT00 FROM MDPS INTO @DATA(ld_i_rhythm_tag_vorher). | ||||
| "SELECT single MRPPP FROM MARC INTO @DATA(ld_e_anliefkal). | ||||
| "SELECT single DAT00 FROM MDPS INTO @DATA(ld_i_rhythm_tag_nachher). | ||||
| "SELECT single PLIFZ FROM MARC INTO @DATA(ld_e_plifz). | ||||
| "SELECT single DAT00 FROM MDPS INTO @DATA(ld_e_dispodatum). | ||||
| "SELECT single DAT00 FROM MDPS INTO @DATA(ld_e_lieferdatum). | ||||
Search for further information about these or an SAP related objects