SAP EQUI_HIERARCHY_READ Function Module for NOTRANSL: Lesen von existierenden Equipmenthierarchien
EQUI_HIERARCHY_READ is a standard equi hierarchy read 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: Lesen von existierenden Equipmenthierarchien 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 equi hierarchy read FM, simply by entering the name EQUI_HIERARCHY_READ into the relevant SAP transaction such as SE37 or SE38.
Function Group: IEL2
Program Name: SAPLIEL2
Main Program: SAPLIEL2
Appliation area: I
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function EQUI_HIERARCHY_READ 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 'EQUI_HIERARCHY_READ'"NOTRANSL: Lesen von existierenden Equipmenthierarchien.
EXPORTING
EQUIPMENT = "Equipment whose hierarchy is to be read
LEVEL_DOWN = "Number of levels of resolution (downwards)
IMPORTING
EQUI_COUNT = "Number of allocated sub-equipment
TABLES
HIER_TAB = "Table of the determined equipment hierarchy
Customer Function user exits
Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.EXIT_SAPLIEL2_001 Check of User-Defined Rules When Defining the Equipment Hierarchy
EXIT_SAPLIEL2_002 Check of User-Defined Rules on Installation of Equipments at FunctLoc
IMPORTING Parameters details for EQUI_HIERARCHY_READ
EQUIPMENT - Equipment whose hierarchy is to be read
Data type: EQUI-EQUNROptional: No
Call by Reference: No ( called with pass by value option)
LEVEL_DOWN - Number of levels of resolution (downwards)
Data type: RIHEA-LEVDOOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for EQUI_HIERARCHY_READ
EQUI_COUNT - Number of allocated sub-equipment
Data type: SY-TABIXOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for EQUI_HIERARCHY_READ
HIER_TAB - Table of the determined equipment hierarchy
Data type: RIHEQUIOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for EQUI_HIERARCHY_READ 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_hier_tab | TYPE STANDARD TABLE OF RIHEQUI, " | |||
| lv_equipment | TYPE EQUI-EQUNR, " | |||
| lv_equi_count | TYPE SY-TABIX, " | |||
| lv_level_down | TYPE RIHEA-LEVDO. " |
|   CALL FUNCTION 'EQUI_HIERARCHY_READ' "NOTRANSL: Lesen von existierenden Equipmenthierarchien |
| EXPORTING | ||
| EQUIPMENT | = lv_equipment | |
| LEVEL_DOWN | = lv_level_down | |
| IMPORTING | ||
| EQUI_COUNT | = lv_equi_count | |
| TABLES | ||
| HIER_TAB | = lt_hier_tab | |
| . " EQUI_HIERARCHY_READ | ||
ABAP code using 7.40 inline data declarations to call FM EQUI_HIERARCHY_READ
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 EQUNR FROM EQUI INTO @DATA(ld_equipment). | ||||
| "SELECT single TABIX FROM SY INTO @DATA(ld_equi_count). | ||||
| "SELECT single LEVDO FROM RIHEA INTO @DATA(ld_level_down). | ||||
Search for further information about these or an SAP related objects