SAP BANK_DETAILS_API_TRANSFORM Function Module for
BANK_DETAILS_API_TRANSFORM is a standard bank details api transform 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 bank details api transform FM, simply by entering the name BANK_DETAILS_API_TRANSFORM into the relevant SAP transaction such as SE37 or SE38.
Function Group: BF_BANK_DETAILS
Program Name: SAPLBF_BANK_DETAILS
Main Program: SAPLBF_BANK_DETAILS
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function BANK_DETAILS_API_TRANSFORM 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 'BANK_DETAILS_API_TRANSFORM'".
EXPORTING
I_IBAN_OR_ACCOUNT_NUMBER = "
* I_BIC_OR_BANK_NUMBER = "
* I_BANK_KEY = "
* I_BANK_COUNTRY_KEY = "
* IX_IBAN_WITHOUT_BANKN = "
* IX_IBAN_INTO_TIBAN = "
IMPORTING
E_BANKS = "
E_BANKL = "
E_BANKN = "
E_BKONT = "
E_BKREF = "
E_IBAN = "
ET_BNKA = "
E_MESSAGE = "
IMPORTING Parameters details for BANK_DETAILS_API_TRANSFORM
I_IBAN_OR_ACCOUNT_NUMBER -
Data type: BANKN35Optional: No
Call by Reference: Yes
I_BIC_OR_BANK_NUMBER -
Data type: BANKLOptional: Yes
Call by Reference: Yes
I_BANK_KEY -
Data type: BANKKOptional: Yes
Call by Reference: Yes
I_BANK_COUNTRY_KEY -
Data type: BANKSOptional: Yes
Call by Reference: Yes
IX_IBAN_WITHOUT_BANKN -
Data type: BOOLEANOptional: Yes
Call by Reference: Yes
IX_IBAN_INTO_TIBAN -
Data type: BOOLEANOptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for BANK_DETAILS_API_TRANSFORM
E_BANKS -
Data type: BANKSOptional: No
Call by Reference: Yes
E_BANKL -
Data type: BANKKOptional: No
Call by Reference: Yes
E_BANKN -
Data type: BANKNOptional: No
Call by Reference: Yes
E_BKONT -
Data type: BKONTOptional: No
Call by Reference: Yes
E_BKREF -
Data type: BKREFOptional: No
Call by Reference: Yes
E_IBAN -
Data type: IBANOptional: No
Call by Reference: Yes
ET_BNKA -
Data type: BF_BNKAOptional: No
Call by Reference: Yes
E_MESSAGE -
Data type: BAPIRET2Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for BANK_DETAILS_API_TRANSFORM 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_e_banks | TYPE BANKS, " | |||
| lv_i_iban_or_account_number | TYPE BANKN35, " | |||
| lv_e_bankl | TYPE BANKK, " | |||
| lv_i_bic_or_bank_number | TYPE BANKL, " | |||
| lv_e_bankn | TYPE BANKN, " | |||
| lv_i_bank_key | TYPE BANKK, " | |||
| lv_e_bkont | TYPE BKONT, " | |||
| lv_i_bank_country_key | TYPE BANKS, " | |||
| lv_e_bkref | TYPE BKREF, " | |||
| lv_ix_iban_without_bankn | TYPE BOOLEAN, " | |||
| lv_e_iban | TYPE IBAN, " | |||
| lv_ix_iban_into_tiban | TYPE BOOLEAN, " | |||
| lv_et_bnka | TYPE BF_BNKA, " | |||
| lv_e_message | TYPE BAPIRET2. " |
|   CALL FUNCTION 'BANK_DETAILS_API_TRANSFORM' " |
| EXPORTING | ||
| I_IBAN_OR_ACCOUNT_NUMBER | = lv_i_iban_or_account_number | |
| I_BIC_OR_BANK_NUMBER | = lv_i_bic_or_bank_number | |
| I_BANK_KEY | = lv_i_bank_key | |
| I_BANK_COUNTRY_KEY | = lv_i_bank_country_key | |
| IX_IBAN_WITHOUT_BANKN | = lv_ix_iban_without_bankn | |
| IX_IBAN_INTO_TIBAN | = lv_ix_iban_into_tiban | |
| IMPORTING | ||
| E_BANKS | = lv_e_banks | |
| E_BANKL | = lv_e_bankl | |
| E_BANKN | = lv_e_bankn | |
| E_BKONT | = lv_e_bkont | |
| E_BKREF | = lv_e_bkref | |
| E_IBAN | = lv_e_iban | |
| ET_BNKA | = lv_et_bnka | |
| E_MESSAGE | = lv_e_message | |
| . " BANK_DETAILS_API_TRANSFORM | ||
ABAP code using 7.40 inline data declarations to call FM BANK_DETAILS_API_TRANSFORM
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.Search for further information about these or an SAP related objects