SAP MM_PARTNER_HIERARCHY Function Module for Vendor Hierarchy: Determination of the hierarchy path
MM_PARTNER_HIERARCHY is a standard mm partner hierarchy SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Vendor Hierarchy: Determination of the hierarchy path 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 hierarchy FM, simply by entering the name MM_PARTNER_HIERARCHY 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_HIERARCHY 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_HIERARCHY'"Vendor Hierarchy: Determination of the hierarchy path.
EXPORTING
I_DATUM = "Validity Time
* I_HITYP = "Hierarchy Type
I_EKORG = "Purchasing Organization
TABLES
T_MMPA = "
IMPORTING Parameters details for MM_PARTNER_HIERARCHY
I_DATUM - Validity Time
Data type: LFMH-DATABOptional: No
Call by Reference: No ( called with pass by value option)
I_HITYP - Hierarchy Type
Data type: LFMH-HITYPOptional: Yes
Call by Reference: No ( called with pass by value option)
I_EKORG - Purchasing Organization
Data type: LFMH-EKORGOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for MM_PARTNER_HIERARCHY
T_MMPA -
Data type: MMPAOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for MM_PARTNER_HIERARCHY 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: | ||||
| lt_t_mmpa | TYPE STANDARD TABLE OF MMPA, " | |||
| lv_i_datum | TYPE LFMH-DATAB, " | |||
| lv_i_hityp | TYPE LFMH-HITYP, " | |||
| lv_i_ekorg | TYPE LFMH-EKORG. " |
|   CALL FUNCTION 'MM_PARTNER_HIERARCHY' "Vendor Hierarchy: Determination of the hierarchy path |
| EXPORTING | ||
| I_DATUM | = lv_i_datum | |
| I_HITYP | = lv_i_hityp | |
| I_EKORG | = lv_i_ekorg | |
| TABLES | ||
| T_MMPA | = lt_t_mmpa | |
| . " MM_PARTNER_HIERARCHY | ||
ABAP code using 7.40 inline data declarations to call FM MM_PARTNER_HIERARCHY
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 DATAB FROM LFMH INTO @DATA(ld_i_datum). | ||||
| "SELECT single HITYP FROM LFMH INTO @DATA(ld_i_hityp). | ||||
| "SELECT single EKORG FROM LFMH INTO @DATA(ld_i_ekorg). | ||||
Search for further information about these or an SAP related objects