SAP MM_PARTNER_CHECK Function Module for Partner Processing
MM_PARTNER_CHECK is a standard mm partner check 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 Processing 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 check FM, simply by entering the name MM_PARTNER_CHECK into the relevant SAP transaction such as SE37 or SE38.
Function Group: WY09
Program Name: SAPLWY09
Main Program: SAPLWY09
Appliation area: W
Release date: 06-Oct-1995
Mode(Normal, Remote etc): Normal Function Module
Update:

Function MM_PARTNER_CHECK 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_CHECK'"Partner Processing.
EXPORTING
I_PARVW = "Partner Function
* I_CHECK_CPD = ' ' "One-Time Account Check
I_GPARN = "Number of Business Partner
* I_EKORG = "Purchasing Organization
* I_LFA1 = "Vendor Master
I_PARGR = "PartnerDetermProced.
* I_TEXTINT = "Text for Internal No. Assignment
* I_WOERROR = "Indicator for Supression of Warnings and Errors
* I_NOWARNING = ' ' "
* I_SD_CHECK = ' ' "Check Roles from SD View
IMPORTING
E_NAME1 = "Name of Partner
E_GPARN = "Business Partner Number
E_VTEXT = "
E_NRART = "
E_ORT01 = "
EXCEPTIONS
ERROR_OCCURED = 1
IMPORTING Parameters details for MM_PARTNER_CHECK
I_PARVW - Partner Function
Data type: WYT3-PARVWOptional: No
Call by Reference: No ( called with pass by value option)
I_CHECK_CPD - One-Time Account Check
Data type: RF02K-D0110Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_GPARN - Number of Business Partner
Data type: WRF02K-GPARNOptional: No
Call by Reference: No ( called with pass by value option)
I_EKORG - Purchasing Organization
Data type: LFM1-EKORGOptional: Yes
Call by Reference: No ( called with pass by value option)
I_LFA1 - Vendor Master
Data type: LFA1Optional: Yes
Call by Reference: No ( called with pass by value option)
I_PARGR - PartnerDetermProced.
Data type: TPAER-PARGROptional: No
Call by Reference: No ( called with pass by value option)
I_TEXTINT - Text for Internal No. Assignment
Data type: WRF02K-GPARNOptional: Yes
Call by Reference: No ( called with pass by value option)
I_WOERROR - Indicator for Supression of Warnings and Errors
Data type: RF02K-D0110Optional: Yes
Call by Reference: No ( called with pass by value option)
I_NOWARNING -
Data type: RF02K-D0110Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_SD_CHECK - Check Roles from SD View
Data type: RF02K-D0110Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for MM_PARTNER_CHECK
E_NAME1 - Name of Partner
Data type: WRF02K-REF_NAME1Optional: No
Call by Reference: No ( called with pass by value option)
E_GPARN - Business Partner Number
Data type: WRF02K-GPARNOptional: No
Call by Reference: No ( called with pass by value option)
E_VTEXT -
Data type: TPART-VTEXTOptional: No
Call by Reference: No ( called with pass by value option)
E_NRART -
Data type: TPAR-NRARTOptional: No
Call by Reference: No ( called with pass by value option)
E_ORT01 -
Data type: LFA1-ORT01Optional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
ERROR_OCCURED -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for MM_PARTNER_CHECK 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 WRF02K-REF_NAME1, " | |||
| lv_i_parvw | TYPE WYT3-PARVW, " | |||
| lv_error_occured | TYPE WYT3, " | |||
| lv_i_check_cpd | TYPE RF02K-D0110, " SPACE | |||
| lv_e_gparn | TYPE WRF02K-GPARN, " | |||
| lv_i_gparn | TYPE WRF02K-GPARN, " | |||
| lv_e_vtext | TYPE TPART-VTEXT, " | |||
| lv_i_ekorg | TYPE LFM1-EKORG, " | |||
| lv_i_lfa1 | TYPE LFA1, " | |||
| lv_e_nrart | TYPE TPAR-NRART, " | |||
| lv_e_ort01 | TYPE LFA1-ORT01, " | |||
| lv_i_pargr | TYPE TPAER-PARGR, " | |||
| lv_i_textint | TYPE WRF02K-GPARN, " | |||
| lv_i_woerror | TYPE RF02K-D0110, " | |||
| lv_i_nowarning | TYPE RF02K-D0110, " SPACE | |||
| lv_i_sd_check | TYPE RF02K-D0110. " SPACE |
|   CALL FUNCTION 'MM_PARTNER_CHECK' "Partner Processing |
| EXPORTING | ||
| I_PARVW | = lv_i_parvw | |
| I_CHECK_CPD | = lv_i_check_cpd | |
| I_GPARN | = lv_i_gparn | |
| I_EKORG | = lv_i_ekorg | |
| I_LFA1 | = lv_i_lfa1 | |
| I_PARGR | = lv_i_pargr | |
| I_TEXTINT | = lv_i_textint | |
| I_WOERROR | = lv_i_woerror | |
| I_NOWARNING | = lv_i_nowarning | |
| I_SD_CHECK | = lv_i_sd_check | |
| IMPORTING | ||
| E_NAME1 | = lv_e_name1 | |
| E_GPARN | = lv_e_gparn | |
| E_VTEXT | = lv_e_vtext | |
| E_NRART | = lv_e_nrart | |
| E_ORT01 | = lv_e_ort01 | |
| EXCEPTIONS | ||
| ERROR_OCCURED = 1 | ||
| . " MM_PARTNER_CHECK | ||
ABAP code using 7.40 inline data declarations to call FM MM_PARTNER_CHECK
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 REF_NAME1 FROM WRF02K INTO @DATA(ld_e_name1). | ||||
| "SELECT single PARVW FROM WYT3 INTO @DATA(ld_i_parvw). | ||||
| "SELECT single D0110 FROM RF02K INTO @DATA(ld_i_check_cpd). | ||||
| DATA(ld_i_check_cpd) | = ' '. | |||
| "SELECT single GPARN FROM WRF02K INTO @DATA(ld_e_gparn). | ||||
| "SELECT single GPARN FROM WRF02K INTO @DATA(ld_i_gparn). | ||||
| "SELECT single VTEXT FROM TPART INTO @DATA(ld_e_vtext). | ||||
| "SELECT single EKORG FROM LFM1 INTO @DATA(ld_i_ekorg). | ||||
| "SELECT single NRART FROM TPAR INTO @DATA(ld_e_nrart). | ||||
| "SELECT single ORT01 FROM LFA1 INTO @DATA(ld_e_ort01). | ||||
| "SELECT single PARGR FROM TPAER INTO @DATA(ld_i_pargr). | ||||
| "SELECT single GPARN FROM WRF02K INTO @DATA(ld_i_textint). | ||||
| "SELECT single D0110 FROM RF02K INTO @DATA(ld_i_woerror). | ||||
| "SELECT single D0110 FROM RF02K INTO @DATA(ld_i_nowarning). | ||||
| DATA(ld_i_nowarning) | = ' '. | |||
| "SELECT single D0110 FROM RF02K INTO @DATA(ld_i_sd_check). | ||||
| DATA(ld_i_sd_check) | = ' '. | |||
Search for further information about these or an SAP related objects