SAP RH_OM_MAINTAIN_RELATION Function Module for
RH_OM_MAINTAIN_RELATION is a standard rh om maintain relation SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 rh om maintain relation FM, simply by entering the name RH_OM_MAINTAIN_RELATION into the relevant SAP transaction such as SE37 or SE38.
Function Group: RHGP
Program Name: SAPLRHGP
Main Program: SAPLRHGP
Appliation area: H
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function RH_OM_MAINTAIN_RELATION 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 'RH_OM_MAINTAIN_RELATION'".
EXPORTING
ACT_FCODE = "
ACT_INFTY = "
ACT_SUBTY = "
CHILD_OBJECT = "
* MOVE_FLAG = "
* OLD_PARENT_OBJECT = "
* OLD_VBEGDA = "
* OLD_VENDDA = "
* NO_DIALOG = "
* ACT_PLVAR = "
* ACT_ISTAT = '1' "
VBEGDA = "
VENDDA = "
* DEFIBEGDA = "
* DEFIENDDA = "
* VPROZT = "
PARENT_OBJECT = "
IMPORTING
VBEGDA = "
VENDDA = "
EXCEPTIONS
FCODE_NOT_SUPPORTED = 1 USER_ABORT = 2 NO_ACTIVE_PLVAR = 3
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_SAPLRHGP_001 Additional information on / off
EXIT_SAPLRHGP_002 Text Fill Customer-Specific Field
EXIT_SAPLRHGP_003 Header Fill Customer-Specific Field
IMPORTING Parameters details for RH_OM_MAINTAIN_RELATION
ACT_FCODE -
Data type: T77FC-FCODEOptional: No
Call by Reference: No ( called with pass by value option)
ACT_INFTY -
Data type: WPLOG-INFTYOptional: No
Call by Reference: No ( called with pass by value option)
ACT_SUBTY -
Data type: WPLOG-SUBTYOptional: No
Call by Reference: No ( called with pass by value option)
CHILD_OBJECT -
Data type: OBJECOptional: No
Call by Reference: No ( called with pass by value option)
MOVE_FLAG -
Data type: COptional: Yes
Call by Reference: No ( called with pass by value option)
OLD_PARENT_OBJECT -
Data type: OBJECOptional: Yes
Call by Reference: No ( called with pass by value option)
OLD_VBEGDA -
Data type: WPLOG-BEGDAOptional: Yes
Call by Reference: No ( called with pass by value option)
OLD_VENDDA -
Data type: WPLOG-ENDDAOptional: Yes
Call by Reference: No ( called with pass by value option)
NO_DIALOG -
Data type: COptional: Yes
Call by Reference: No ( called with pass by value option)
ACT_PLVAR -
Data type: WPLOG-PLVAROptional: Yes
Call by Reference: No ( called with pass by value option)
ACT_ISTAT -
Data type: WPLOG-ISTATDefault: '1'
Optional: Yes
Call by Reference: No ( called with pass by value option)
VBEGDA -
Data type: WPLOG-BEGDAOptional: No
Call by Reference: No ( called with pass by value option)
VENDDA -
Data type: WPLOG-ENDDAOptional: No
Call by Reference: No ( called with pass by value option)
DEFIBEGDA -
Data type: WPLOG-BEGDAOptional: Yes
Call by Reference: No ( called with pass by value option)
DEFIENDDA -
Data type: WPLOG-ENDDAOptional: Yes
Call by Reference: No ( called with pass by value option)
VPROZT -
Data type: P1001-PROZTOptional: Yes
Call by Reference: No ( called with pass by value option)
PARENT_OBJECT -
Data type: OBJECOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for RH_OM_MAINTAIN_RELATION
VBEGDA -
Data type: WPLOG-BEGDAOptional: No
Call by Reference: No ( called with pass by value option)
VENDDA -
Data type: WPLOG-ENDDAOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
FCODE_NOT_SUPPORTED -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
USER_ABORT -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NO_ACTIVE_PLVAR -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for RH_OM_MAINTAIN_RELATION 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_vbegda | TYPE WPLOG-BEGDA, " | |||
| lv_act_fcode | TYPE T77FC-FCODE, " | |||
| lv_fcode_not_supported | TYPE T77FC, " | |||
| lv_act_infty | TYPE WPLOG-INFTY, " | |||
| lv_act_subty | TYPE WPLOG-SUBTY, " | |||
| lv_child_object | TYPE OBJEC, " | |||
| lv_move_flag | TYPE C, " | |||
| lv_old_parent_object | TYPE OBJEC, " | |||
| lv_old_vbegda | TYPE WPLOG-BEGDA, " | |||
| lv_old_vendda | TYPE WPLOG-ENDDA, " | |||
| lv_no_dialog | TYPE C, " | |||
| lv_vendda | TYPE WPLOG-ENDDA, " | |||
| lv_act_plvar | TYPE WPLOG-PLVAR, " | |||
| lv_user_abort | TYPE WPLOG, " | |||
| lv_act_istat | TYPE WPLOG-ISTAT, " '1' | |||
| lv_no_active_plvar | TYPE WPLOG, " | |||
| lv_vbegda | TYPE WPLOG-BEGDA, " | |||
| lv_vendda | TYPE WPLOG-ENDDA, " | |||
| lv_defibegda | TYPE WPLOG-BEGDA, " | |||
| lv_defiendda | TYPE WPLOG-ENDDA, " | |||
| lv_vprozt | TYPE P1001-PROZT, " | |||
| lv_parent_object | TYPE OBJEC. " |
|   CALL FUNCTION 'RH_OM_MAINTAIN_RELATION' " |
| EXPORTING | ||
| ACT_FCODE | = lv_act_fcode | |
| ACT_INFTY | = lv_act_infty | |
| ACT_SUBTY | = lv_act_subty | |
| CHILD_OBJECT | = lv_child_object | |
| MOVE_FLAG | = lv_move_flag | |
| OLD_PARENT_OBJECT | = lv_old_parent_object | |
| OLD_VBEGDA | = lv_old_vbegda | |
| OLD_VENDDA | = lv_old_vendda | |
| NO_DIALOG | = lv_no_dialog | |
| ACT_PLVAR | = lv_act_plvar | |
| ACT_ISTAT | = lv_act_istat | |
| VBEGDA | = lv_vbegda | |
| VENDDA | = lv_vendda | |
| DEFIBEGDA | = lv_defibegda | |
| DEFIENDDA | = lv_defiendda | |
| VPROZT | = lv_vprozt | |
| PARENT_OBJECT | = lv_parent_object | |
| IMPORTING | ||
| VBEGDA | = lv_vbegda | |
| VENDDA | = lv_vendda | |
| EXCEPTIONS | ||
| FCODE_NOT_SUPPORTED = 1 | ||
| USER_ABORT = 2 | ||
| NO_ACTIVE_PLVAR = 3 | ||
| . " RH_OM_MAINTAIN_RELATION | ||
ABAP code using 7.40 inline data declarations to call FM RH_OM_MAINTAIN_RELATION
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 BEGDA FROM WPLOG INTO @DATA(ld_vbegda). | ||||
| "SELECT single FCODE FROM T77FC INTO @DATA(ld_act_fcode). | ||||
| "SELECT single INFTY FROM WPLOG INTO @DATA(ld_act_infty). | ||||
| "SELECT single SUBTY FROM WPLOG INTO @DATA(ld_act_subty). | ||||
| "SELECT single BEGDA FROM WPLOG INTO @DATA(ld_old_vbegda). | ||||
| "SELECT single ENDDA FROM WPLOG INTO @DATA(ld_old_vendda). | ||||
| "SELECT single ENDDA FROM WPLOG INTO @DATA(ld_vendda). | ||||
| "SELECT single PLVAR FROM WPLOG INTO @DATA(ld_act_plvar). | ||||
| "SELECT single ISTAT FROM WPLOG INTO @DATA(ld_act_istat). | ||||
| DATA(ld_act_istat) | = '1'. | |||
| "SELECT single BEGDA FROM WPLOG INTO @DATA(ld_vbegda). | ||||
| "SELECT single ENDDA FROM WPLOG INTO @DATA(ld_vendda). | ||||
| "SELECT single BEGDA FROM WPLOG INTO @DATA(ld_defibegda). | ||||
| "SELECT single ENDDA FROM WPLOG INTO @DATA(ld_defiendda). | ||||
| "SELECT single PROZT FROM P1001 INTO @DATA(ld_vprozt). | ||||
Search for further information about these or an SAP related objects