SAP INHERITANCE_FROM_LOCATION Function Module for NOTRANSL: Weitergabe der Daten des Techn. Platzes auf eingebautes Equipmen
INHERITANCE_FROM_LOCATION is a standard inheritance from 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: Weitergabe der Daten des Techn. Platzes auf eingebautes Equipmen 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 inheritance from location FM, simply by entering the name INHERITANCE_FROM_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 INHERITANCE_FROM_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 'INHERITANCE_FROM_LOCATION'"NOTRANSL: Weitergabe der Daten des Techn. Platzes auf eingebautes Equipmen.
EXPORTING
* LOCATION = ' ' "No. of functional location / optional (see below)
* LOC_VIEW = ' ' "View of functional location / optional (see above)
OLD_EQUI_DATA = "installed equipment: old status
* I_SWITCH_INHER = ' ' "
IMPORTING
INHER_CHANGE = "Indicator, whether inheritance occurred
NEW_EQUI_DATA = "installed equipment: new status
NO_DB_IMAGE = "Indicator, whether inheritance occurred
EV_ADDRESS_CHANGE = "
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 INHERITANCE_FROM_LOCATION
LOCATION - No. of functional location / optional (see below)
Data type: IFLOT-TPLNRDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
LOC_VIEW - View of functional location / optional (see above)
Data type: IFLODefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
OLD_EQUI_DATA - installed equipment: old status
Data type: EQUI_INHEROptional: No
Call by Reference: No ( called with pass by value option)
I_SWITCH_INHER -
Data type: IREF-IINDDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for INHERITANCE_FROM_LOCATION
INHER_CHANGE - Indicator, whether inheritance occurred
Data type: RM63E-INDUOptional: No
Call by Reference: No ( called with pass by value option)
NEW_EQUI_DATA - installed equipment: new status
Data type: EQUI_INHEROptional: No
Call by Reference: No ( called with pass by value option)
NO_DB_IMAGE - Indicator, whether inheritance occurred
Data type: RM63E-INDUOptional: No
Call by Reference: No ( called with pass by value option)
EV_ADDRESS_CHANGE -
Data type: FLAGOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for INHERITANCE_FROM_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.| DATA: | ||||
| lv_location | TYPE IFLOT-TPLNR, " SPACE | |||
| lv_inher_change | TYPE RM63E-INDU, " | |||
| lv_loc_view | TYPE IFLO, " SPACE | |||
| lv_new_equi_data | TYPE EQUI_INHER, " | |||
| lv_no_db_image | TYPE RM63E-INDU, " | |||
| lv_old_equi_data | TYPE EQUI_INHER, " | |||
| lv_i_switch_inher | TYPE IREF-IIND, " SPACE | |||
| lv_ev_address_change | TYPE FLAG. " |
|   CALL FUNCTION 'INHERITANCE_FROM_LOCATION' "NOTRANSL: Weitergabe der Daten des Techn. Platzes auf eingebautes Equipmen |
| EXPORTING | ||
| LOCATION | = lv_location | |
| LOC_VIEW | = lv_loc_view | |
| OLD_EQUI_DATA | = lv_old_equi_data | |
| I_SWITCH_INHER | = lv_i_switch_inher | |
| IMPORTING | ||
| INHER_CHANGE | = lv_inher_change | |
| NEW_EQUI_DATA | = lv_new_equi_data | |
| NO_DB_IMAGE | = lv_no_db_image | |
| EV_ADDRESS_CHANGE | = lv_ev_address_change | |
| . " INHERITANCE_FROM_LOCATION | ||
ABAP code using 7.40 inline data declarations to call FM INHERITANCE_FROM_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.| "SELECT single TPLNR FROM IFLOT INTO @DATA(ld_location). | ||||
| DATA(ld_location) | = ' '. | |||
| "SELECT single INDU FROM RM63E INTO @DATA(ld_inher_change). | ||||
| DATA(ld_loc_view) | = ' '. | |||
| "SELECT single INDU FROM RM63E INTO @DATA(ld_no_db_image). | ||||
| "SELECT single IIND FROM IREF INTO @DATA(ld_i_switch_inher). | ||||
| DATA(ld_i_switch_inher) | = ' '. | |||
Search for further information about these or an SAP related objects