BUPA_BSP_SHAREHOLDER_DELETE SAP Function module

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

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

Pattern for FM BUPA_BSP_SHAREHOLDER_DELETE - BUPA BSP SHAREHOLDER DELETE

CALL FUNCTION 'BUPA_BSP_SHAREHOLDER_DELETE' "
  EXPORTING
    iv_relation_type =          " bu_reltyp     Business Partner Relationship Category
    iv_partner1 =               " bu_partner    Business Partner Number
    iv_partner2 =               " bu_partner    Business Partner Number
    iv_valid_from =             " bu_datfrom    Validity Date (Valid From)
    iv_valid_to =               " bu_datto      Validity Date (Valid To)
    iv_rel_number =             " but050-relnr  BP Relationship Number
    iv_all =                    " bu_boolean    'X' = Delete all Partner Functions for this Relationship
  TABLES
    et_messages =               " bapiret2      Return Parameters
    .  "  BUPA_BSP_SHAREHOLDER_DELETE

ABAP code example for Function Module BUPA_BSP_SHAREHOLDER_DELETE

The ABAP code below is a full code listing to execute function module BUPA_BSP_SHAREHOLDER_DELETE 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:
it_et_messages  
 
 TYPE STANDARD TABLE OF BAPIRET2,"TABLES PARAM
wa_et_messages
 
 LIKE LINE OF it_et_messages
.


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

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

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

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

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

SELECT single RELNR 
  FROM BUT050 
  INTO @DATA(ld_iv_rel_number).


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

"populate fields of struture and append to itab
append wa_et_messages to it_et_messages.
.

CALL FUNCTION 'BUPA_BSP_SHAREHOLDER_DELETE'
  EXPORTING
    iv_relation_type =           ld_iv_relation_type
    iv_partner1 =                ld_iv_partner1
    iv_partner2 =                ld_iv_partner2
    iv_valid_from =              ld_iv_valid_from
    iv_valid_to =                ld_iv_valid_to
    iv_rel_number =              ld_iv_rel_number
    iv_all =                     ld_iv_all
  TABLES
    et_messages =                it_et_messages
    .  "  BUPA_BSP_SHAREHOLDER_DELETE

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_iv_relation_type
 
 TYPE BU_RELTYP ,
it_et_messages
 
 TYPE STANDARD TABLE OF BAPIRET2 ,
wa_et_messages
 
 LIKE LINE OF it_et_messages,
ld_iv_partner1
 
 TYPE BU_PARTNER ,
ld_iv_partner2
 
 TYPE BU_PARTNER ,
ld_iv_valid_from
 
 TYPE BU_DATFROM ,
ld_iv_valid_to
 
 TYPE BU_DATTO ,
ld_iv_rel_number
 
 TYPE BUT050-RELNR ,
ld_iv_all
 
 TYPE BU_BOOLEAN .


ld_iv_relation_type = 'Check type of data required'. 

"populate fields of struture and append to itab
append wa_et_messages to it_et_messages.
ld_iv_partner1 = 'Check type of data required'.
ld_iv_partner2 = 'Check type of data required'.
ld_iv_valid_from = 'Check type of data required'.
ld_iv_valid_to = 'Check type of data required'.

SELECT single RELNR 
  FROM BUT050 
  INTO ld_iv_rel_number.

ld_iv_all = 'Check type of data required'.