SAP ME_MESSAGES_FIND Function Module for NOTRANSL: FB zur Nachrichtenfindung im Einkauf

Search SAP Function Modules

ME_MESSAGES_FIND is a standard me messages find 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: FB zur Nachrichtenfindung im Einkauf 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 me messages find FM, simply by entering the name ME_MESSAGES_FIND into the relevant SAP transaction such as SE37 or SE38.

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

Function ME_MESSAGES_FIND 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 'ME_MESSAGES_FIND'"NOTRANSL: FB zur Nachrichtenfindung im Einkauf
  EXPORTING
   I_EKKO =  "Purchasing Document Header
   I_VORGA =  "Transaction/event
*  I_NEUDRUCK = ' ' "
*  I_DRUVO = ' ' "
*  I_OBJKY = ' ' "Object key
*  I_PARTNER_REFRESH = 'X' "
*  I_WEBRL =  "Internet release
*  I_EKPO =  "Purchasing Document Item

 IMPORTING
   E_T161N =  "Message Determination Schemas: Assignment

TABLES
   XNAST =  "Output status (update structure)
   YNAST =  "Message Status
*  EPART =  "Output partner

.

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_SAPLMEDRUCK_001 Enhancement of Print Program LMEDR001

IMPORTING Parameters details for ME_MESSAGES_FIND

I_EKKO - Purchasing Document Header

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

I_VORGA - Transaction/event

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

I_NEUDRUCK -

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

I_DRUVO -

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

I_OBJKY - Object key

Data type: NAST-OBJKY
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_PARTNER_REFRESH -

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

I_WEBRL - Internet release

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

I_EKPO - Purchasing Document Item

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

EXPORTING Parameters details for ME_MESSAGES_FIND

E_T161N - Message Determination Schemas: Assignment

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

TABLES Parameters details for ME_MESSAGES_FIND

XNAST - Output status (update structure)

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

YNAST - Message Status

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

EPART - Output partner

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

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

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