SAP RH_OM_BINDING_EDIT Function Module for









RH_OM_BINDING_EDIT is a standard rh om binding edit 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 binding edit FM, simply by entering the name RH_OM_BINDING_EDIT into the relevant SAP transaction such as SE37 or SE38.

Function Group: RHWE
Program Name: SAPLRHWE
Main Program:
Appliation area: H
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function RH_OM_BINDING_EDIT 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_BINDING_EDIT'"
EXPORTING
ACT_OTYPE_TEXT = "
* ACT_SHORT = ' ' "Name of task
DRAIN_OTYPE_TEXT = "
* DRAIN_SHORT = ' ' "Name of task
* B_DISPLAY = ' ' "

IMPORTING
INPUT_DONE = "Changes implemented

TABLES
ACT_CONT_DEF = "Definition Structure
DRAIN_CONT_DEF = "Definition Structure
ACT_BIND_DEF = "

EXCEPTIONS
INCONSISTENT_BINDINGDEFINITION = 1 INVALID_BINDINGTYPE = 2 INVALID_CONTAINERTYPE = 3
.



IMPORTING Parameters details for RH_OM_BINDING_EDIT

ACT_OTYPE_TEXT -

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

ACT_SHORT - Name of task

Data type: HRS1000-SHORT
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

DRAIN_OTYPE_TEXT -

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

DRAIN_SHORT - Name of task

Data type: HRS1000-SHORT
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

B_DISPLAY -

Data type: T77FC-MAINT
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for RH_OM_BINDING_EDIT

INPUT_DONE - Changes implemented

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

TABLES Parameters details for RH_OM_BINDING_EDIT

ACT_CONT_DEF - Definition Structure

Data type: SWCONTDEF
Optional: No
Call by Reference: Yes

DRAIN_CONT_DEF - Definition Structure

Data type: SWCONTDEF
Optional: No
Call by Reference: Yes

ACT_BIND_DEF -

Data type: SWFBINDDB
Optional: No
Call by Reference: Yes

EXCEPTIONS details

INCONSISTENT_BINDINGDEFINITION -

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

INVALID_BINDINGTYPE -

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

INVALID_CONTAINERTYPE -

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

Copy and paste ABAP code example for RH_OM_BINDING_EDIT 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_input_done  TYPE SWABINEDIT-CHANGED, "   
lt_act_cont_def  TYPE STANDARD TABLE OF SWCONTDEF, "   
lv_act_otype_text  TYPE T777O-OTEXT, "   
lv_inconsistent_bindingdefinition  TYPE T777O, "   
lv_act_short  TYPE HRS1000-SHORT, "   SPACE
lt_drain_cont_def  TYPE STANDARD TABLE OF SWCONTDEF, "   
lv_invalid_bindingtype  TYPE SWCONTDEF, "   
lt_act_bind_def  TYPE STANDARD TABLE OF SWFBINDDB, "   
lv_drain_otype_text  TYPE T777O-OTEXT, "   
lv_invalid_containertype  TYPE T777O, "   
lv_drain_short  TYPE HRS1000-SHORT, "   SPACE
lv_b_display  TYPE T77FC-MAINT. "   SPACE

  CALL FUNCTION 'RH_OM_BINDING_EDIT'  "
    EXPORTING
         ACT_OTYPE_TEXT = lv_act_otype_text
         ACT_SHORT = lv_act_short
         DRAIN_OTYPE_TEXT = lv_drain_otype_text
         DRAIN_SHORT = lv_drain_short
         B_DISPLAY = lv_b_display
    IMPORTING
         INPUT_DONE = lv_input_done
    TABLES
         ACT_CONT_DEF = lt_act_cont_def
         DRAIN_CONT_DEF = lt_drain_cont_def
         ACT_BIND_DEF = lt_act_bind_def
    EXCEPTIONS
        INCONSISTENT_BINDINGDEFINITION = 1
        INVALID_BINDINGTYPE = 2
        INVALID_CONTAINERTYPE = 3
. " RH_OM_BINDING_EDIT




ABAP code using 7.40 inline data declarations to call FM RH_OM_BINDING_EDIT

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 CHANGED FROM SWABINEDIT INTO @DATA(ld_input_done).
 
 
"SELECT single OTEXT FROM T777O INTO @DATA(ld_act_otype_text).
 
 
"SELECT single SHORT FROM HRS1000 INTO @DATA(ld_act_short).
DATA(ld_act_short) = ' '.
 
 
 
 
"SELECT single OTEXT FROM T777O INTO @DATA(ld_drain_otype_text).
 
 
"SELECT single SHORT FROM HRS1000 INTO @DATA(ld_drain_short).
DATA(ld_drain_short) = ' '.
 
"SELECT single MAINT FROM T77FC INTO @DATA(ld_b_display).
DATA(ld_b_display) = ' '.
 


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!