SAP MEX_CHECK_LFDAT Function Module for Check Delivery Date









MEX_CHECK_LFDAT is a standard mex check lfdat SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Check Delivery Date 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 mex check lfdat FM, simply by entering the name MEX_CHECK_LFDAT into the relevant SAP transaction such as SE37 or SE38.

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



Function MEX_CHECK_LFDAT 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 'MEX_CHECK_LFDAT'"Check Delivery Date
EXPORTING
IM_LFDAT = "Item Delivery Date
IM_LPEIN = "Category of delivery date
IM_KALEN = "
IM_FABKL = "Key for Factory Calendar
IM_PSTYP = "Item Category in Purchasing Document
* IM_NO_MACRO_MSG = "
.




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_SAPLMEXF_001 No Invoice for Purchase Order Item but Conditions Allowed

IMPORTING Parameters details for MEX_CHECK_LFDAT

IM_LFDAT - Item Delivery Date

Data type: EBAN-LFDAT
Optional: No
Call by Reference: Yes

IM_LPEIN - Category of delivery date

Data type: EBAN-LPEIN
Optional: No
Call by Reference: Yes

IM_KALEN -

Data type: MMPUR_BOOL
Optional: No
Call by Reference: Yes

IM_FABKL - Key for Factory Calendar

Data type: T001W-FABKL
Optional: No
Call by Reference: Yes

IM_PSTYP - Item Category in Purchasing Document

Data type: PSTYP
Optional: No
Call by Reference: Yes

IM_NO_MACRO_MSG -

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

Copy and paste ABAP code example for MEX_CHECK_LFDAT 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_im_lfdat  TYPE EBAN-LFDAT, "   
lv_im_lpein  TYPE EBAN-LPEIN, "   
lv_im_kalen  TYPE MMPUR_BOOL, "   
lv_im_fabkl  TYPE T001W-FABKL, "   
lv_im_pstyp  TYPE PSTYP, "   
lv_im_no_macro_msg  TYPE PSTYP. "   

  CALL FUNCTION 'MEX_CHECK_LFDAT'  "Check Delivery Date
    EXPORTING
         IM_LFDAT = lv_im_lfdat
         IM_LPEIN = lv_im_lpein
         IM_KALEN = lv_im_kalen
         IM_FABKL = lv_im_fabkl
         IM_PSTYP = lv_im_pstyp
         IM_NO_MACRO_MSG = lv_im_no_macro_msg
. " MEX_CHECK_LFDAT




ABAP code using 7.40 inline data declarations to call FM MEX_CHECK_LFDAT

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 LFDAT FROM EBAN INTO @DATA(ld_im_lfdat).
 
"SELECT single LPEIN FROM EBAN INTO @DATA(ld_im_lpein).
 
 
"SELECT single FABKL FROM T001W INTO @DATA(ld_im_fabkl).
 
 
 


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!