SAP EQUI_HIERARCHY_EXIST Function Module for NOTRANSL: Prüfen, ob zum eingegebenen Unterequipment Equipmentierarchie vo









EQUI_HIERARCHY_EXIST is a standard equi hierarchy exist 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: Prüfen, ob zum eingegebenen Unterequipment Equipmentierarchie vo 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 exist FM, simply by entering the name EQUI_HIERARCHY_EXIST 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_EXIST 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_EXIST'"NOTRANSL: Prüfen, ob zum eingegebenen Unterequipment Equipmentierarchie vo
EXPORTING
EQUIPMENT = "Output equipment
* READ_DATE = SY-DATUM "

IMPORTING
EQUI_EXIST = "Indicator: Equipment hierarchy available
.




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_EXIST

EQUIPMENT - Output equipment

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

READ_DATE -

Data type: EQUZ-DATBI
Default: SY-DATUM
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for EQUI_HIERARCHY_EXIST

EQUI_EXIST - Indicator: Equipment hierarchy available

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

Copy and paste ABAP code example for EQUI_HIERARCHY_EXIST 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_equipment  TYPE EQUI-EQUNR, "   
lv_equi_exist  TYPE RM63H-SELKZ, "   
lv_read_date  TYPE EQUZ-DATBI. "   SY-DATUM

  CALL FUNCTION 'EQUI_HIERARCHY_EXIST'  "NOTRANSL: Prüfen, ob zum eingegebenen Unterequipment Equipmentierarchie vo
    EXPORTING
         EQUIPMENT = lv_equipment
         READ_DATE = lv_read_date
    IMPORTING
         EQUI_EXIST = lv_equi_exist
. " EQUI_HIERARCHY_EXIST




ABAP code using 7.40 inline data declarations to call FM EQUI_HIERARCHY_EXIST

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 SELKZ FROM RM63H INTO @DATA(ld_equi_exist).
 
"SELECT single DATBI FROM EQUZ INTO @DATA(ld_read_date).
DATA(ld_read_date) = SY-DATUM.
 


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!