ISU_BINARY_RELATION_CREATE SAP Function module

ISU_BINARY_RELATION_CREATE is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name ISU_BINARY_RELATION_CREATE into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: ISU_BREL
Released Date: Not Released
Processing type: Normal fucntion module

Pattern for FM ISU_BINARY_RELATION_CREATE - ISU BINARY RELATION CREATE

CALL FUNCTION 'ISU_BINARY_RELATION_CREATE' "
  EXPORTING
    obj_rolea =                 " borident
    obj_roleb =                 " borident
    relationtype =              " breltyp-reltype
    client =                    " mandt
  IMPORTING
    binrel =                    " gbinrel
* TABLES
*   binrel_attrib =             " brelattr
  EXCEPTIONS
    NO_MODEL = 1                "
    INTERNAL_ERROR = 2          "
    UNKNOWN = 3                 "
    .  "  ISU_BINARY_RELATION_CREATE

ABAP code example for Function Module ISU_BINARY_RELATION_CREATE

The ABAP code below is a full code listing to execute function module ISU_BINARY_RELATION_CREATE including all data declarations. The code uses 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 original method of declaring data variables up front. 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).

DATA:
ld_binrel  
 
 TYPE GBINREL
,
it_binrel_attrib  
 
 TYPE STANDARD TABLE OF BRELATTR,"TABLES PARAM
wa_binrel_attrib
 
 LIKE LINE OF it_binrel_attrib
.


DATA(ld_obj_rolea) = 'Check type of data required'.

DATA(ld_obj_roleb) = 'Check type of data required'.


DATA(ld_relationtype) = some text here

DATA(ld_client) = 'Check type of data required'.
 

"populate fields of struture and append to itab
append wa_binrel_attrib to it_binrel_attrib.
.

CALL FUNCTION 'ISU_BINARY_RELATION_CREATE'
  EXPORTING
    obj_rolea =                  ld_obj_rolea
    obj_roleb =                  ld_obj_roleb
    relationtype =               ld_relationtype
    client =                     ld_client
  IMPORTING
    binrel =                     ld_binrel
* TABLES
*   binrel_attrib =              it_binrel_attrib
  EXCEPTIONS
    NO_MODEL =                   1
    INTERNAL_ERROR =             2
    UNKNOWN =                    3
    .  "  ISU_BINARY_RELATION_CREATE

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 2. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 3. "Exception
  "Add code for exception here
ENDIF.

ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:

ld_binrel
 
 TYPE GBINREL ,
ld_obj_rolea
 
 TYPE BORIDENT ,
it_binrel_attrib
 
 TYPE STANDARD TABLE OF BRELATTR ,
wa_binrel_attrib
 
 LIKE LINE OF it_binrel_attrib,
ld_obj_roleb
 
 TYPE BORIDENT ,
ld_relationtype
 
 TYPE BRELTYP-RELTYPE ,
ld_client
 
 TYPE MANDT .


ld_obj_rolea = 'Check type of data required'. 

"populate fields of struture and append to itab
append wa_binrel_attrib to it_binrel_attrib.
ld_obj_roleb = 'Check type of data required'.

ld_relationtype = some text here
ld_client = 'Check type of data required'.