SAP USER_CHECK_FOR_EQUI_LOCATION Function Module for NOTRANSL: Aufruf des User-Exits beim Ändern des Equipmenteinbauortes

Search SAP Function Modules

USER_CHECK_FOR_EQUI_LOCATION is a standard user check for equi location 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: Aufruf des User-Exits beim Ändern des Equipmenteinbauortes 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 user check for equi location FM, simply by entering the name USER_CHECK_FOR_EQUI_LOCATION 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 USER_CHECK_FOR_EQUI_LOCATION 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 'USER_CHECK_FOR_EQUI_LOCATION'"NOTRANSL: Aufruf des User-Exits beim Ändern des Equipmenteinbauortes
  EXPORTING
   S_EQUI =  "Equipment/Sub-Equipment to be Installed
*  S_POSITION =  "Installation Position
*  R_EQUI =  "Installation Location: Superior Equipment
*  R_IFLO =  "Installation Location: Functional Location

EXCEPTIONS
   HIERARCHY_NOT_ALLOWED = 1    INSTALLATION_NOT_ALLOWED = 2 

.

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 USER_CHECK_FOR_EQUI_LOCATION

S_EQUI - Equipment/Sub-Equipment to be Installed

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

S_POSITION - Installation Position

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

R_EQUI - Installation Location: Superior Equipment

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

R_IFLO - Installation Location: Functional Location

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

EXCEPTIONS details

HIERARCHY_NOT_ALLOWED - Hierarchy not Allowed

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

INSTALLATION_NOT_ALLOWED - Installation not Allowed

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

Copy and paste ABAP code example for USER_CHECK_FOR_EQUI_LOCATION 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.

ABAP code using 7.40 inline data declarations to call FM USER_CHECK_FOR_EQUI_LOCATION

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.

Search for further information about these or an SAP related objects