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

Function MM_PARTNER_TYPE 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_TYPE'"Partner type.
EXPORTING
I_PARVW = "
IMPORTING
E_NRART = "
E_STEIN = "Uniqueness in master record
EXCEPTIONS
PARTNERFUNCTION_NOT_FOUND = 1
IMPORTING Parameters details for MM_PARTNER_TYPE
I_PARVW -
Data type: TPAR-PARVWOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for MM_PARTNER_TYPE
E_NRART -
Data type: TPAR-NRARTOptional: No
Call by Reference: No ( called with pass by value option)
E_STEIN - Uniqueness in master record
Data type: TPAR-STEINOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
PARTNERFUNCTION_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_TYPE 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_nrart | TYPE TPAR-NRART, " | |||
| lv_i_parvw | TYPE TPAR-PARVW, " | |||
| lv_partnerfunction_not_found | TYPE TPAR, " | |||
| lv_e_stein | TYPE TPAR-STEIN. " |
|   CALL FUNCTION 'MM_PARTNER_TYPE' "Partner type |
| EXPORTING | ||
| I_PARVW | = lv_i_parvw | |
| IMPORTING | ||
| E_NRART | = lv_e_nrart | |
| E_STEIN | = lv_e_stein | |
| EXCEPTIONS | ||
| PARTNERFUNCTION_NOT_FOUND = 1 | ||
| . " MM_PARTNER_TYPE | ||
ABAP code using 7.40 inline data declarations to call FM MM_PARTNER_TYPE
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 NRART FROM TPAR INTO @DATA(ld_e_nrart). | ||||
| "SELECT single PARVW FROM TPAR INTO @DATA(ld_i_parvw). | ||||
| "SELECT single STEIN FROM TPAR INTO @DATA(ld_e_stein). | ||||
Search for further information about these or an SAP related objects