FSA1_BUPA_EVENT_ADDEL SAP Function module

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

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

Pattern for FM FSA1_BUPA_EVENT_ADDEL - FSA1 BUPA EVENT ADDEL

CALL FUNCTION 'FSA1_BUPA_EVENT_ADDEL' "
  EXPORTING
    i_partner =                 " but000-partner
*   i_partnerguid =             " but000-partner_guid
    i_addrnumber =              " but020-addrnumber
*   i_addrguid =                " but020-address_guid
    i_calltp =                  " bus000flds-char1
*   i_valid_from = '00000000'   " dats
*   i_valid_from_old = '00000000'  " dats
*   i_valid_to = '00000000'     " dats
*   i_valid_to_old = '00000000'  " dats
  IMPORTING
    e_result =                  " bus000flds-char1
    .  "  FSA1_BUPA_EVENT_ADDEL

ABAP code example for Function Module FSA1_BUPA_EVENT_ADDEL

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

 

SELECT single PARTNER 
  FROM BUT000 
  INTO @DATA(ld_i_partner).

 

SELECT single PARTNER_GUID 
  FROM BUT000 
  INTO @DATA(ld_i_partnerguid).

 

SELECT single ADDRNUMBER 
  FROM BUT020 
  INTO @DATA(ld_i_addrnumber).

 

SELECT single ADDRESS_GUID 
  FROM BUT020 
  INTO @DATA(ld_i_addrguid).



DATA(ld_i_calltp) = some text here

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

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

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

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

CALL FUNCTION 'FSA1_BUPA_EVENT_ADDEL'
  EXPORTING
    i_partner =                  ld_i_partner
*   i_partnerguid =              ld_i_partnerguid
    i_addrnumber =               ld_i_addrnumber
*   i_addrguid =                 ld_i_addrguid
    i_calltp =                   ld_i_calltp
*   i_valid_from =               ld_i_valid_from
*   i_valid_from_old =           ld_i_valid_from_old
*   i_valid_to =                 ld_i_valid_to
*   i_valid_to_old =             ld_i_valid_to_old
  IMPORTING
    e_result =                   ld_e_result
    .  "  FSA1_BUPA_EVENT_ADDEL

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_e_result
 
 TYPE BUS000FLDS-CHAR1 ,
ld_i_partner
 
 TYPE BUT000-PARTNER ,
ld_i_partnerguid
 
 TYPE BUT000-PARTNER_GUID ,
ld_i_addrnumber
 
 TYPE BUT020-ADDRNUMBER ,
ld_i_addrguid
 
 TYPE BUT020-ADDRESS_GUID ,
ld_i_calltp
 
 TYPE BUS000FLDS-CHAR1 ,
ld_i_valid_from
 
 TYPE DATS ,
ld_i_valid_from_old
 
 TYPE DATS ,
ld_i_valid_to
 
 TYPE DATS ,
ld_i_valid_to_old
 
 TYPE DATS .



SELECT single PARTNER 
  FROM BUT000 
  INTO ld_i_partner.


SELECT single PARTNER_GUID 
  FROM BUT000 
  INTO ld_i_partnerguid.


SELECT single ADDRNUMBER 
  FROM BUT020 
  INTO ld_i_addrnumber.


SELECT single ADDRESS_GUID 
  FROM BUT020 
  INTO ld_i_addrguid.


ld_i_calltp = some text here
ld_i_valid_from = 'Check type of data required'.
ld_i_valid_from_old = 'Check type of data required'.
ld_i_valid_to = 'Check type of data required'.
ld_i_valid_to_old = 'Check type of data required'.