SAP INPUT_IBAN Function Module for Input of Bank Data Via IBAN (No Online Entry)
INPUT_IBAN is a standard input iban SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Input of Bank Data Via IBAN (No Online Entry) 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 input iban FM, simply by entering the name INPUT_IBAN into the relevant SAP transaction such as SE37 or SE38.
Function Group: IBMA
Program Name: SAPLIBMA
Main Program: SAPLIBMA
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function INPUT_IBAN 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 'INPUT_IBAN'"Input of Bank Data Via IBAN (No Online Entry).
EXPORTING
I_IBAN = "IBAN (International Bank Account Number)
I_VALID_FROM = "Date and Time, Current (Application Server) Date
* I_TABNAME = "
* I_TABKEY = "
* I_SWIFT = "
IMPORTING
E_BANKS = "Bank Country Key
E_BANKL = "Bank Key
E_BANKN = "Bank Account Number of the Payee
E_BKONT = "Bank Control Key of the Payee's Bank
E_IBAN = "IBAN (International Bank Account Number)
E_VALID_FROM = "Date and Time, Current (Application Server) Date
E_BKREF = "Reference specifications for bank details
EXCEPTIONS
IBAN_NOT_VALID = 1 BANK_NOT_FOUND = 2 NO_CONVERSION = 3
IMPORTING Parameters details for INPUT_IBAN
I_IBAN - IBAN (International Bank Account Number)
Data type: TIBAN-IBANOptional: No
Call by Reference: No ( called with pass by value option)
I_VALID_FROM - Date and Time, Current (Application Server) Date
Data type: SY-DATUMOptional: No
Call by Reference: No ( called with pass by value option)
I_TABNAME -
Data type: TIBAN-TABNAMEOptional: Yes
Call by Reference: No ( called with pass by value option)
I_TABKEY -
Data type: TIBAN-TABKEYOptional: Yes
Call by Reference: No ( called with pass by value option)
I_SWIFT -
Data type: BNKA-SWIFTOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for INPUT_IBAN
E_BANKS - Bank Country Key
Data type: BNKA-BANKSOptional: No
Call by Reference: No ( called with pass by value option)
E_BANKL - Bank Key
Data type: BNKA-BANKLOptional: No
Call by Reference: No ( called with pass by value option)
E_BANKN - Bank Account Number of the Payee
Data type: REGUH_BF-ZBNKNOptional: No
Call by Reference: No ( called with pass by value option)
E_BKONT - Bank Control Key of the Payee's Bank
Data type: REGUH_BF-ZBKONOptional: No
Call by Reference: No ( called with pass by value option)
E_IBAN - IBAN (International Bank Account Number)
Data type: TIBAN-IBANOptional: No
Call by Reference: No ( called with pass by value option)
E_VALID_FROM - Date and Time, Current (Application Server) Date
Data type: SY-DATUMOptional: No
Call by Reference: No ( called with pass by value option)
E_BKREF - Reference specifications for bank details
Data type: REGUH_BF-BKREFOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
IBAN_NOT_VALID - IBAN is Not Valid
Data type:Optional: No
Call by Reference: Yes
BANK_NOT_FOUND - Bank Does Not Exist
Data type:Optional: No
Call by Reference: Yes
NO_CONVERSION - Generation Not Possible
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for INPUT_IBAN 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_i_iban | TYPE TIBAN-IBAN, " | |||
| lv_e_banks | TYPE BNKA-BANKS, " | |||
| lv_iban_not_valid | TYPE BNKA, " | |||
| lv_e_bankl | TYPE BNKA-BANKL, " | |||
| lv_i_valid_from | TYPE SY-DATUM, " | |||
| lv_bank_not_found | TYPE SY, " | |||
| lv_e_bankn | TYPE REGUH_BF-ZBNKN, " | |||
| lv_i_tabname | TYPE TIBAN-TABNAME, " | |||
| lv_no_conversion | TYPE TIBAN, " | |||
| lv_e_bkont | TYPE REGUH_BF-ZBKON, " | |||
| lv_i_tabkey | TYPE TIBAN-TABKEY, " | |||
| lv_e_iban | TYPE TIBAN-IBAN, " | |||
| lv_i_swift | TYPE BNKA-SWIFT, " | |||
| lv_e_valid_from | TYPE SY-DATUM, " | |||
| lv_e_bkref | TYPE REGUH_BF-BKREF. " |
|   CALL FUNCTION 'INPUT_IBAN' "Input of Bank Data Via IBAN (No Online Entry) |
| EXPORTING | ||
| I_IBAN | = lv_i_iban | |
| I_VALID_FROM | = lv_i_valid_from | |
| I_TABNAME | = lv_i_tabname | |
| I_TABKEY | = lv_i_tabkey | |
| I_SWIFT | = lv_i_swift | |
| IMPORTING | ||
| E_BANKS | = lv_e_banks | |
| E_BANKL | = lv_e_bankl | |
| E_BANKN | = lv_e_bankn | |
| E_BKONT | = lv_e_bkont | |
| E_IBAN | = lv_e_iban | |
| E_VALID_FROM | = lv_e_valid_from | |
| E_BKREF | = lv_e_bkref | |
| EXCEPTIONS | ||
| IBAN_NOT_VALID = 1 | ||
| BANK_NOT_FOUND = 2 | ||
| NO_CONVERSION = 3 | ||
| . " INPUT_IBAN | ||
ABAP code using 7.40 inline data declarations to call FM INPUT_IBAN
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 IBAN FROM TIBAN INTO @DATA(ld_i_iban). | ||||
| "SELECT single BANKS FROM BNKA INTO @DATA(ld_e_banks). | ||||
| "SELECT single BANKL FROM BNKA INTO @DATA(ld_e_bankl). | ||||
| "SELECT single DATUM FROM SY INTO @DATA(ld_i_valid_from). | ||||
| "SELECT single ZBNKN FROM REGUH_BF INTO @DATA(ld_e_bankn). | ||||
| "SELECT single TABNAME FROM TIBAN INTO @DATA(ld_i_tabname). | ||||
| "SELECT single ZBKON FROM REGUH_BF INTO @DATA(ld_e_bkont). | ||||
| "SELECT single TABKEY FROM TIBAN INTO @DATA(ld_i_tabkey). | ||||
| "SELECT single IBAN FROM TIBAN INTO @DATA(ld_e_iban). | ||||
| "SELECT single SWIFT FROM BNKA INTO @DATA(ld_i_swift). | ||||
| "SELECT single DATUM FROM SY INTO @DATA(ld_e_valid_from). | ||||
| "SELECT single BKREF FROM REGUH_BF INTO @DATA(ld_e_bkref). | ||||
Search for further information about these or an SAP related objects