SAP FTR_PARTNER_GET_BY_BANK_ID Function Module for Search Partner via 'ID as Bank' (via Attributes: Swift, Address, ...)
FTR_PARTNER_GET_BY_BANK_ID is a standard ftr partner get by bank id SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Search Partner via 'ID as Bank' (via Attributes: Swift, Address, ...) processing and below is the pattern details for this FM, 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 ftr partner get by bank id FM, simply by entering the name FTR_PARTNER_GET_BY_BANK_ID into the relevant SAP transaction such as SE37 or SE38.
Function Group: FTR_REUSE_PARTNER
Program Name: SAPLFTR_REUSE_PARTNER
Main Program: SAPLFTR_REUSE_PARTNER
Appliation area: F
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FTR_PARTNER_GET_BY_BANK_ID 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 'FTR_PARTNER_GET_BY_BANK_ID'"Search Partner via 'ID as Bank' (via Attributes: Swift, Address, ...).
EXPORTING
* IV_SWIFT = "SWIFT Code for International Payments
* IV_COUNTRY = "Bank Country Key
* IV_NAME = "Name of Financial Institution
* IV_CITY = "Ort (und ggfs. PLZ)
* IV_STREET = "House No. and Street
TABLES
* ET_BANK_DATA = "Bank Master Record
* ET_PARTNER_DATA = "Partner Data
* ET_RETURN = "Return Parameter(s)
IMPORTING Parameters details for FTR_PARTNER_GET_BY_BANK_ID
IV_SWIFT - SWIFT Code for International Payments
Data type: SWIFTOptional: Yes
Call by Reference: No ( called with pass by value option)
IV_COUNTRY - Bank Country Key
Data type: BNKA-BANKSOptional: Yes
Call by Reference: No ( called with pass by value option)
IV_NAME - Name of Financial Institution
Data type: BNKA-BANKAOptional: Yes
Call by Reference: No ( called with pass by value option)
IV_CITY - Ort (und ggfs. PLZ)
Data type: BNKA-ORT01Optional: Yes
Call by Reference: No ( called with pass by value option)
IV_STREET - House No. and Street
Data type: BNKA-STRASOptional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for FTR_PARTNER_GET_BY_BANK_ID
ET_BANK_DATA - Bank Master Record
Data type: BNKAOptional: Yes
Call by Reference: No ( called with pass by value option)
ET_PARTNER_DATA - Partner Data
Data type: BUT0BANKOptional: Yes
Call by Reference: No ( called with pass by value option)
ET_RETURN - Return Parameter(s)
Data type: BAPIRET2Optional: Yes
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for FTR_PARTNER_GET_BY_BANK_ID 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: | ||||
| lv_iv_swift | TYPE SWIFT, " | |||
| lt_et_bank_data | TYPE STANDARD TABLE OF BNKA, " | |||
| lv_iv_country | TYPE BNKA-BANKS, " | |||
| lt_et_partner_data | TYPE STANDARD TABLE OF BUT0BANK, " | |||
| lv_iv_name | TYPE BNKA-BANKA, " | |||
| lt_et_return | TYPE STANDARD TABLE OF BAPIRET2, " | |||
| lv_iv_city | TYPE BNKA-ORT01, " | |||
| lv_iv_street | TYPE BNKA-STRAS. " |
|   CALL FUNCTION 'FTR_PARTNER_GET_BY_BANK_ID' "Search Partner via 'ID as Bank' (via Attributes: Swift, Address, ...) |
| EXPORTING | ||
| IV_SWIFT | = lv_iv_swift | |
| IV_COUNTRY | = lv_iv_country | |
| IV_NAME | = lv_iv_name | |
| IV_CITY | = lv_iv_city | |
| IV_STREET | = lv_iv_street | |
| TABLES | ||
| ET_BANK_DATA | = lt_et_bank_data | |
| ET_PARTNER_DATA | = lt_et_partner_data | |
| ET_RETURN | = lt_et_return | |
| . " FTR_PARTNER_GET_BY_BANK_ID | ||
ABAP code using 7.40 inline data declarations to call FM FTR_PARTNER_GET_BY_BANK_ID
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 BANKS FROM BNKA INTO @DATA(ld_iv_country). | ||||
| "SELECT single BANKA FROM BNKA INTO @DATA(ld_iv_name). | ||||
| "SELECT single ORT01 FROM BNKA INTO @DATA(ld_iv_city). | ||||
| "SELECT single STRAS FROM BNKA INTO @DATA(ld_iv_street). | ||||
Search for further information about these or an SAP related objects