SAP FSBP_READ_PARTNER_BANK Function Module for









FSBP_READ_PARTNER_BANK is a standard fsbp read partner bank SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, showing its interface including any import and export parameters, exceptions etc. there is also a full "cut and paste" ABAP pattern code example, along with implementation ABAP coding, documentation and contribution comments specific to this or related objects.


See here to view full function module documentation and code listing for fsbp read partner bank FM, simply by entering the name FSBP_READ_PARTNER_BANK into the relevant SAP transaction such as SE37 or SE38.

Function Group: FSBP_READ
Program Name: SAPLFSBP_READ
Main Program: SAPLFSBP_READ
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function FSBP_READ_PARTNER_BANK pattern details

In-order to call this FM within your sap programs, simply using the below ABAP pattern details to trigger the function call...or see the full ABAP code listing at the end of this article. You can simply cut and paste this code into your ABAP progrom as it is, including variable declarations.
CALL FUNCTION 'FSBP_READ_PARTNER_BANK'"
EXPORTING
I_PARTNER = "Business Partner Number
* I_BKVID = "
* I_BANKS = "
* I_BANKL = "
* I_XEZER = "
* I_XMEMORY = "
* I_XWA = "

TABLES
* T_BUT0BK = "Bank Details
* T_BNKA = "

EXCEPTIONS
NO_BANKDATA_FOUND = 1 NO_PARTNER_FOUND = 2 NO_BKVID_FOUND = 3
.



IMPORTING Parameters details for FSBP_READ_PARTNER_BANK

I_PARTNER - Business Partner Number

Data type: BUT000-PARTNER
Optional: No
Call by Reference: No ( called with pass by value option)

I_BKVID -

Data type: BUT0BK-BKVID
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_BANKS -

Data type: BUT0BK-BANKS
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_BANKL -

Data type: BUT0BK-BANKL
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_XEZER -

Data type: BUT0BK-XEZER
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_XMEMORY -

Data type: BOOLE-BOOLE
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_XWA -

Data type: BOOLE-BOOLE
Optional: Yes
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for FSBP_READ_PARTNER_BANK

T_BUT0BK - Bank Details

Data type: BUT0BK
Optional: Yes
Call by Reference: No ( called with pass by value option)

T_BNKA -

Data type: BNKA
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

NO_BANKDATA_FOUND -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

NO_PARTNER_FOUND -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

NO_BKVID_FOUND -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for FSBP_READ_PARTNER_BANK Function Module

The ABAP code below is a full code listing to execute function module POPUP_TO_CONFIRM including all data declarations. The code uses the original data declarations rather than 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 newer method of declaring data variables on the fly. 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), which i why i have stuck to the origianl for this example.

DATA:
lt_t_but0bk  TYPE STANDARD TABLE OF BUT0BK, "   
lv_i_partner  TYPE BUT000-PARTNER, "   
lv_no_bankdata_found  TYPE BUT000, "   
lt_t_bnka  TYPE STANDARD TABLE OF BNKA, "   
lv_i_bkvid  TYPE BUT0BK-BKVID, "   
lv_no_partner_found  TYPE BUT0BK, "   
lv_i_banks  TYPE BUT0BK-BANKS, "   
lv_no_bkvid_found  TYPE BUT0BK, "   
lv_i_bankl  TYPE BUT0BK-BANKL, "   
lv_i_xezer  TYPE BUT0BK-XEZER, "   
lv_i_xmemory  TYPE BOOLE-BOOLE, "   
lv_i_xwa  TYPE BOOLE-BOOLE. "   

  CALL FUNCTION 'FSBP_READ_PARTNER_BANK'  "
    EXPORTING
         I_PARTNER = lv_i_partner
         I_BKVID = lv_i_bkvid
         I_BANKS = lv_i_banks
         I_BANKL = lv_i_bankl
         I_XEZER = lv_i_xezer
         I_XMEMORY = lv_i_xmemory
         I_XWA = lv_i_xwa
    TABLES
         T_BUT0BK = lt_t_but0bk
         T_BNKA = lt_t_bnka
    EXCEPTIONS
        NO_BANKDATA_FOUND = 1
        NO_PARTNER_FOUND = 2
        NO_BKVID_FOUND = 3
. " FSBP_READ_PARTNER_BANK




ABAP code using 7.40 inline data declarations to call FM FSBP_READ_PARTNER_BANK

The below ABAP code uses the newer in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. Please note some of the newer syntax below, such as the @DATA is not available until 4.70 EHP 8.

 
"SELECT single PARTNER FROM BUT000 INTO @DATA(ld_i_partner).
 
 
 
"SELECT single BKVID FROM BUT0BK INTO @DATA(ld_i_bkvid).
 
 
"SELECT single BANKS FROM BUT0BK INTO @DATA(ld_i_banks).
 
 
"SELECT single BANKL FROM BUT0BK INTO @DATA(ld_i_bankl).
 
"SELECT single XEZER FROM BUT0BK INTO @DATA(ld_i_xezer).
 
"SELECT single BOOLE FROM BOOLE INTO @DATA(ld_i_xmemory).
 
"SELECT single BOOLE FROM BOOLE INTO @DATA(ld_i_xwa).
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!