APAR_EBPP_ADD_BANK SAP Function module

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

Associated Function Group: FIN_BUSPA_MASTER
Released Date: Not Released
Processing type: Remote-Enabled

Pattern for FM APAR_EBPP_ADD_BANK - APAR EBPP ADD BANK

CALL FUNCTION 'APAR_EBPP_ADD_BANK' "
  EXPORTING
    i_partner =                 " ebpp_partner  Financials: Partner Data
    i_bankdetaildata =          " ebpp_bank     SAP BP: BAPI Structure for Bank Details Data
    i_checkmodus = SPACE        " boole-boole
  IMPORTING
    e_newbank =                 " fin_bankid    Bank Details of Business Partner
    e_returncode =              " sy-subrc      Return Value, Return Value after ABAP Statements
    return =                    " bapiret1      Return Parameter(s)
* TABLES
*   t_messages =                " ebpp_messages  Biller Direct: Messages
    .  "  APAR_EBPP_ADD_BANK

ABAP code example for Function Module APAR_EBPP_ADD_BANK

The ABAP code below is a full code listing to execute function module APAR_EBPP_ADD_BANK 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_newbank  
 
 TYPE FIN_BANKID
,
ld_e_returncode  
 
 TYPE SY-SUBRC
,
ld_return  
 
 TYPE BAPIRET1
,
it_t_messages  
 
 TYPE STANDARD TABLE OF EBPP_MESSAGES,"TABLES PARAM
wa_t_messages
 
 LIKE LINE OF it_t_messages
.


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

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


DATA(ld_i_checkmodus) = some text here
 

"populate fields of struture and append to itab
append wa_t_messages to it_t_messages.
.

CALL FUNCTION 'APAR_EBPP_ADD_BANK'
  EXPORTING
    i_partner =                  ld_i_partner
    i_bankdetaildata =           ld_i_bankdetaildata
    i_checkmodus =               ld_i_checkmodus
  IMPORTING
    e_newbank =                  ld_e_newbank
    e_returncode =               ld_e_returncode
    return =                     ld_return
* TABLES
*   t_messages =                 it_t_messages
    .  "  APAR_EBPP_ADD_BANK

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_newbank
 
 TYPE FIN_BANKID ,
ld_i_partner
 
 TYPE EBPP_PARTNER ,
it_t_messages
 
 TYPE STANDARD TABLE OF EBPP_MESSAGES ,
wa_t_messages
 
 LIKE LINE OF it_t_messages,
ld_e_returncode
 
 TYPE SY-SUBRC ,
ld_i_bankdetaildata
 
 TYPE EBPP_BANK ,
ld_return
 
 TYPE BAPIRET1 ,
ld_i_checkmodus
 
 TYPE BOOLE-BOOLE .


ld_i_partner = 'Check type of data required'. 

"populate fields of struture and append to itab
append wa_t_messages to it_t_messages.
ld_i_bankdetaildata = 'Check type of data required'.

ld_i_checkmodus = some text here