SAP MM_PARTNER_INFO Function Module for Partner Data (Name, City)









MM_PARTNER_INFO is a standard mm partner info SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Partner Data (Name, City) 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 partner info FM, simply by entering the name MM_PARTNER_INFO into the relevant SAP transaction such as SE37 or SE38.

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



Function MM_PARTNER_INFO 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_PARTNER_INFO'"Partner Data (Name, City)
EXPORTING
I_PARVW = "Partner Role
I_GPARN = "
* I_LFA1 = "

IMPORTING
E_NAME1 = "Name of partner
E_ORT01 = "Location of partner

EXCEPTIONS
PARTNER_NOT_FOUND = 1
.



IMPORTING Parameters details for MM_PARTNER_INFO

I_PARVW - Partner Role

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

I_GPARN -

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

I_LFA1 -

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

EXPORTING Parameters details for MM_PARTNER_INFO

E_NAME1 - Name of partner

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

E_ORT01 - Location of partner

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

EXCEPTIONS details

PARTNER_NOT_FOUND -

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

Copy and paste ABAP code example for MM_PARTNER_INFO 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_name1  TYPE LFA1-NAME1, "   
lv_i_parvw  TYPE TPAR-PARVW, "   
lv_partner_not_found  TYPE TPAR, "   
lv_e_ort01  TYPE LFA1-ORT01, "   
lv_i_gparn  TYPE WRF02K-GPARN, "   
lv_i_lfa1  TYPE LFA1. "   

  CALL FUNCTION 'MM_PARTNER_INFO'  "Partner Data (Name, City)
    EXPORTING
         I_PARVW = lv_i_parvw
         I_GPARN = lv_i_gparn
         I_LFA1 = lv_i_lfa1
    IMPORTING
         E_NAME1 = lv_e_name1
         E_ORT01 = lv_e_ort01
    EXCEPTIONS
        PARTNER_NOT_FOUND = 1
. " MM_PARTNER_INFO




ABAP code using 7.40 inline data declarations to call FM MM_PARTNER_INFO

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 NAME1 FROM LFA1 INTO @DATA(ld_e_name1).
 
"SELECT single PARVW FROM TPAR INTO @DATA(ld_i_parvw).
 
 
"SELECT single ORT01 FROM LFA1 INTO @DATA(ld_e_ort01).
 
"SELECT single GPARN FROM WRF02K INTO @DATA(ld_i_gparn).
 
 


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!