SAP BINARY_RELATION_DELETE_COMMIT Function Module for









BINARY_RELATION_DELETE_COMMIT is a standard binary relation delete commit 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 binary relation delete commit FM, simply by entering the name BINARY_RELATION_DELETE_COMMIT into the relevant SAP transaction such as SE37 or SE38.

Function Group: BREL
Program Name: SAPLBREL
Main Program: SAPLBREL
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function BINARY_RELATION_DELETE_COMMIT 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 'BINARY_RELATION_DELETE_COMMIT'"
EXPORTING
OBJ_ROLEA = "
OBJ_ROLEB = "
RELATIONTYPE = "

EXCEPTIONS
ENTRY_NOT_EXISTING = 1 INTERNAL_ERROR = 2 NO_RELATION = 3 NO_ROLE = 4
.



IMPORTING Parameters details for BINARY_RELATION_DELETE_COMMIT

OBJ_ROLEA -

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

OBJ_ROLEB -

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

RELATIONTYPE -

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

EXCEPTIONS details

ENTRY_NOT_EXISTING -

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

INTERNAL_ERROR -

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

NO_RELATION -

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

NO_ROLE -

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

Copy and paste ABAP code example for BINARY_RELATION_DELETE_COMMIT 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_obj_rolea  TYPE BORIDENT, "   
lv_entry_not_existing  TYPE BORIDENT, "   
lv_obj_roleb  TYPE BORIDENT, "   
lv_internal_error  TYPE BORIDENT, "   
lv_no_relation  TYPE BORIDENT, "   
lv_relationtype  TYPE BRELTYP-RELTYPE, "   
lv_no_role  TYPE BRELTYP. "   

  CALL FUNCTION 'BINARY_RELATION_DELETE_COMMIT'  "
    EXPORTING
         OBJ_ROLEA = lv_obj_rolea
         OBJ_ROLEB = lv_obj_roleb
         RELATIONTYPE = lv_relationtype
    EXCEPTIONS
        ENTRY_NOT_EXISTING = 1
        INTERNAL_ERROR = 2
        NO_RELATION = 3
        NO_ROLE = 4
. " BINARY_RELATION_DELETE_COMMIT




ABAP code using 7.40 inline data declarations to call FM BINARY_RELATION_DELETE_COMMIT

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 RELTYPE FROM BRELTYP INTO @DATA(ld_relationtype).
 
 


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!