SAP RMP_MPOBJ_INHERITANCE Function Module for NOTRANSL: ReferenzMesspunktObjekt: Vererbung Referenzmesspunkte an Messpun
RMP_MPOBJ_INHERITANCE is a standard rmp mpobj inheritance 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: ReferenzMesspunktObjekt: Vererbung Referenzmesspunkte an Messpun 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 rmp mpobj inheritance FM, simply by entering the name RMP_MPOBJ_INHERITANCE into the relevant SAP transaction such as SE37 or SE38.
Function Group: IMR0
Program Name: SAPLIMR0
Main Program: SAPLIMR0
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function RMP_MPOBJ_INHERITANCE 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 'RMP_MPOBJ_INHERITANCE'"NOTRANSL: ReferenzMesspunktObjekt: Vererbung Referenzmesspunkte an Messpun.
EXPORTING
* ONE_TRANSMITTER_OBJ = ' ' "General Indicator
* P_TRPNR = "Reference Functional Location
* IV_SHOW_INHER_BREAKS_LIST = 'X' "
IMPORTING
P_CNT_CHANGES = "Number of changes
P_CNT_IMPT_DEL = "
P_CNT_IMPT_INS = "
P_CNT_IMPT_UPD = "
P_INHERITANCE_BREAKS = "
TABLES
* IMPT_INHB_TAB = "Cancellation List for Data Transfer
EXCEPTIONS
DATA_TRANSMITTED = 1
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_SAPLIMR0_001 User Exit Before Update of Measuring Points/Documents (After COMMIT WORK)
EXIT_SAPLIMR0_002 User Exit for Customer Function in Measuring Point Menu
EXIT_SAPLIMR0_003 User Exit for Customer Function in Measurement Document Menu
EXIT_SAPLIMR0_004 Exit after standard checks for new measurement documents
IMPORTING Parameters details for RMP_MPOBJ_INHERITANCE
ONE_TRANSMITTER_OBJ - General Indicator
Data type: FLAGDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
P_TRPNR - Reference Functional Location
Data type: IRLOT-TRPNROptional: Yes
Call by Reference: No ( called with pass by value option)
IV_SHOW_INHER_BREAKS_LIST -
Data type: FLAGDefault: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for RMP_MPOBJ_INHERITANCE
P_CNT_CHANGES - Number of changes
Data type: IOptional: No
Call by Reference: Yes
P_CNT_IMPT_DEL -
Data type: IOptional: No
Call by Reference: Yes
P_CNT_IMPT_INS -
Data type: IOptional: No
Call by Reference: Yes
P_CNT_IMPT_UPD -
Data type: IOptional: No
Call by Reference: Yes
P_INHERITANCE_BREAKS -
Data type: IREF-IINDOptional: No
Call by Reference: Yes
TABLES Parameters details for RMP_MPOBJ_INHERITANCE
IMPT_INHB_TAB - Cancellation List for Data Transfer
Data type: INHB_TOBJK_USNAMOptional: Yes
Call by Reference: Yes
EXCEPTIONS details
DATA_TRANSMITTED -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for RMP_MPOBJ_INHERITANCE 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_impt_inhb_tab | TYPE STANDARD TABLE OF INHB_TOBJK_USNAM, " | |||
| lv_p_cnt_changes | TYPE I, " | |||
| lv_data_transmitted | TYPE I, " | |||
| lv_one_transmitter_obj | TYPE FLAG, " SPACE | |||
| lv_p_trpnr | TYPE IRLOT-TRPNR, " | |||
| lv_p_cnt_impt_del | TYPE I, " | |||
| lv_p_cnt_impt_ins | TYPE I, " | |||
| lv_iv_show_inher_breaks_list | TYPE FLAG, " 'X' | |||
| lv_p_cnt_impt_upd | TYPE I, " | |||
| lv_p_inheritance_breaks | TYPE IREF-IIND. " |
|   CALL FUNCTION 'RMP_MPOBJ_INHERITANCE' "NOTRANSL: ReferenzMesspunktObjekt: Vererbung Referenzmesspunkte an Messpun |
| EXPORTING | ||
| ONE_TRANSMITTER_OBJ | = lv_one_transmitter_obj | |
| P_TRPNR | = lv_p_trpnr | |
| IV_SHOW_INHER_BREAKS_LIST | = lv_iv_show_inher_breaks_list | |
| IMPORTING | ||
| P_CNT_CHANGES | = lv_p_cnt_changes | |
| P_CNT_IMPT_DEL | = lv_p_cnt_impt_del | |
| P_CNT_IMPT_INS | = lv_p_cnt_impt_ins | |
| P_CNT_IMPT_UPD | = lv_p_cnt_impt_upd | |
| P_INHERITANCE_BREAKS | = lv_p_inheritance_breaks | |
| TABLES | ||
| IMPT_INHB_TAB | = lt_impt_inhb_tab | |
| EXCEPTIONS | ||
| DATA_TRANSMITTED = 1 | ||
| . " RMP_MPOBJ_INHERITANCE | ||
ABAP code using 7.40 inline data declarations to call FM RMP_MPOBJ_INHERITANCE
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.| DATA(ld_one_transmitter_obj) | = ' '. | |||
| "SELECT single TRPNR FROM IRLOT INTO @DATA(ld_p_trpnr). | ||||
| DATA(ld_iv_show_inher_breaks_list) | = 'X'. | |||
| "SELECT single IIND FROM IREF INTO @DATA(ld_p_inheritance_breaks). | ||||
Search for further information about these or an SAP related objects