SAP MM_PARTNERS_FOR_MESSAGING Function Module for NOTRANSL: Füllen der Partnertabelle PART für die Nachrichtenfindung

Search SAP Function Modules

MM_PARTNERS_FOR_MESSAGING is a standard mm partners for messaging 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: Füllen der Partnertabelle PART für die Nachrichtenfindung 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 mm partners for messaging FM, simply by entering the name MM_PARTNERS_FOR_MESSAGING into the relevant SAP transaction such as SE37 or SE38.

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

Function MM_PARTNERS_FOR_MESSAGING 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 'MM_PARTNERS_FOR_MESSAGING'"NOTRANSL: Füllen der Partnertabelle PART für die Nachrichtenfindung
  EXPORTING
   APPLICATION =  "ABAP System Field: Message Type
*  VORGA =  "Transaction/event
*  NEUPR = ' ' "New partner role determination
*  IEKKO =  "Purchasing Document Header

TABLES
*  PART =  "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_SAPLEKPA_001 Specification of Search Strategy for Mandatory Roles
EXIT_SAPLEKPA_002 User Exit: Automatically Adopt Partner from Vendor Master?

IMPORTING Parameters details for MM_PARTNERS_FOR_MESSAGING

APPLICATION - ABAP System Field: Message Type

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

VORGA - Transaction/event

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

NEUPR - New partner role determination

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

IEKKO - Purchasing Document Header

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

TABLES Parameters details for MM_PARTNERS_FOR_MESSAGING

PART - Output partner

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

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

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