BUR_BUPR_EVENT_RADEL SAP Function module

BUR_BUPR_EVENT_RADEL 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 BUR_BUPR_EVENT_RADEL into the relevant SAP transaction such as SE37 or SE80.

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

Pattern for FM BUR_BUPR_EVENT_RADEL - BUR BUPR EVENT RADEL

CALL FUNCTION 'BUR_BUPR_EVENT_RADEL' "
* EXPORTING
*   iv_relnr =                  " bu_relnr
*   iv_partner1 =               " bu_partner    Business Partner Number
*   iv_partner_guid1 =          " bu_partner_guid  Business Partner GUID
*   iv_partner2 =               " bu_partner    Partner Number
*   iv_partner_guid2 =          " bu_partner_guid
*   iv_date_to =                " bu_datto      Validity Date (Valid To)
*   iv_reltyp =                 " bu_reltyp     Business partner-Relationship category
*   iv_xrf =                    " bu_xrf        Business partner role definition instead of BP relationship
*   iv_dftval =                 " bu_dftval     BP: Differentiation Type Characteristic (Change Document-Relevant)
*   iv_rltyp =                  " bu_rltype     Business partner role (change doc.-relevant)
*   iv_addrnumber =             " ad_addrnum    Address Number
*   iv_address_guid =           " bu_address_guid  Address GUID
*   iv_persnumber =             " ad_persnum    Person Number
  IMPORTING
    ev_result =                 " char1
    .  "  BUR_BUPR_EVENT_RADEL

ABAP code example for Function Module BUR_BUPR_EVENT_RADEL

The ABAP code below is a full code listing to execute function module BUR_BUPR_EVENT_RADEL 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_ev_result  
 
 TYPE CHAR1
.


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

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

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

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

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

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

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

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

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

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

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

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

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

CALL FUNCTION 'BUR_BUPR_EVENT_RADEL'
* EXPORTING
*   iv_relnr =                   ld_iv_relnr
*   iv_partner1 =                ld_iv_partner1
*   iv_partner_guid1 =           ld_iv_partner_guid1
*   iv_partner2 =                ld_iv_partner2
*   iv_partner_guid2 =           ld_iv_partner_guid2
*   iv_date_to =                 ld_iv_date_to
*   iv_reltyp =                  ld_iv_reltyp
*   iv_xrf =                     ld_iv_xrf
*   iv_dftval =                  ld_iv_dftval
*   iv_rltyp =                   ld_iv_rltyp
*   iv_addrnumber =              ld_iv_addrnumber
*   iv_address_guid =            ld_iv_address_guid
*   iv_persnumber =              ld_iv_persnumber
  IMPORTING
    ev_result =                  ld_ev_result
    .  "  BUR_BUPR_EVENT_RADEL

IF SY-SUBRC EQ 0.
  "All OK
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_ev_result
 
 TYPE CHAR1 ,
ld_iv_relnr
 
 TYPE BU_RELNR ,
ld_iv_partner1
 
 TYPE BU_PARTNER ,
ld_iv_partner_guid1
 
 TYPE BU_PARTNER_GUID ,
ld_iv_partner2
 
 TYPE BU_PARTNER ,
ld_iv_partner_guid2
 
 TYPE BU_PARTNER_GUID ,
ld_iv_date_to
 
 TYPE BU_DATTO ,
ld_iv_reltyp
 
 TYPE BU_RELTYP ,
ld_iv_xrf
 
 TYPE BU_XRF ,
ld_iv_dftval
 
 TYPE BU_DFTVAL ,
ld_iv_rltyp
 
 TYPE BU_RLTYPE ,
ld_iv_addrnumber
 
 TYPE AD_ADDRNUM ,
ld_iv_address_guid
 
 TYPE BU_ADDRESS_GUID ,
ld_iv_persnumber
 
 TYPE AD_PERSNUM .


ld_iv_relnr = 'Check type of data required'.
ld_iv_partner1 = 'Check type of data required'.
ld_iv_partner_guid1 = 'Check type of data required'.
ld_iv_partner2 = 'Check type of data required'.
ld_iv_partner_guid2 = 'Check type of data required'.
ld_iv_date_to = 'Check type of data required'.
ld_iv_reltyp = 'Check type of data required'.
ld_iv_xrf = 'Check type of data required'.
ld_iv_dftval = 'Check type of data required'.
ld_iv_rltyp = 'Check type of data required'.
ld_iv_addrnumber = 'Check type of data required'.
ld_iv_address_guid = 'Check type of data required'.
ld_iv_persnumber = 'Check type of data required'.