SAP MEX_CHECK_LFM2 Function Module for NOTRANSL: Lieferant prüfen, Status LFM2

Search SAP Function Modules

MEX_CHECK_LFM2 is a standard mex check lfm2 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: Lieferant prüfen, Status LFM2 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 lfm2 FM, simply by entering the name MEX_CHECK_LFM2 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_LFM2 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_LFM2'"NOTRANSL: Lieferant prüfen, Status LFM2
  EXPORTING
   IM_LFM2 =  "Vendor Master Record: Purchasing Data

.

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_LFM2

IM_LFM2 - Vendor Master Record: Purchasing Data

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

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

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