SAP MM_PARTNER_HIERARCHY_CHECK Function Module for NOTRANSL: Check if Vendor is in a hierarchy









MM_PARTNER_HIERARCHY_CHECK is a standard mm partner hierarchy 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 NOTRANSL: Check if Vendor is in a hierarchy 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 check FM, simply by entering the name MM_PARTNER_HIERARCHY_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: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function MM_PARTNER_HIERARCHY_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_HIERARCHY_CHECK'"NOTRANSL: Check if Vendor is in a hierarchy
EXPORTING
I_LIFNR = "Vendor
* I_EKORG = "

EXCEPTIONS
NO_HIERARCHY_FOUND = 1
.



IMPORTING Parameters details for MM_PARTNER_HIERARCHY_CHECK

I_LIFNR - Vendor

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

I_EKORG -

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

EXCEPTIONS details

NO_HIERARCHY_FOUND -

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

Copy and paste ABAP code example for MM_PARTNER_HIERARCHY_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_i_lifnr  TYPE LFA1-LIFNR, "   
lv_no_hierarchy_found  TYPE LFA1, "   
lv_i_ekorg  TYPE LFM1-EKORG. "   

  CALL FUNCTION 'MM_PARTNER_HIERARCHY_CHECK'  "NOTRANSL: Check if Vendor is in a hierarchy
    EXPORTING
         I_LIFNR = lv_i_lifnr
         I_EKORG = lv_i_ekorg
    EXCEPTIONS
        NO_HIERARCHY_FOUND = 1
. " MM_PARTNER_HIERARCHY_CHECK




ABAP code using 7.40 inline data declarations to call FM MM_PARTNER_HIERARCHY_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 LIFNR FROM LFA1 INTO @DATA(ld_i_lifnr).
 
 
"SELECT single EKORG FROM LFM1 INTO @DATA(ld_i_ekorg).
 


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!