SAP FI_PAYMENT_BANK_CHAIN_SET Function Module for
FI_PAYMENT_BANK_CHAIN_SET is a standard fi payment bank chain set 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 fi payment bank chain set FM, simply by entering the name FI_PAYMENT_BANK_CHAIN_SET into the relevant SAP transaction such as SE37 or SE38.
Function Group: F11B
Program Name: SAPLF11B
Main Program: SAPLF11B
Appliation area: F
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FI_PAYMENT_BANK_CHAIN_SET 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 'FI_PAYMENT_BANK_CHAIN_SET'".
EXPORTING
I_UBNKS = "
I_UZAWE = "
I_WAERS = "
I_XEINZ = "Incoming Payment
* I_PROPOSAL = ' ' "
* I_MESSAGE_RUN = ' ' "
* I_MESSAGE_PROP = ' ' "
I_UBNKY = "
I_UBKNT = "
I_ZBNKS = "
I_ZBNKY = "
I_ZBNKN = "
I_ZBKON = "
I_BKREF = "
I_ZBNKL = "
CHANGING
* C_IBANK1 = "
* C_IBANK2 = "
* C_IBANK3 = "
EXCEPTIONS
BANKCHAIN_ERROR = 1 CONVERSION_ERROR = 2
IMPORTING Parameters details for FI_PAYMENT_BANK_CHAIN_SET
I_UBNKS -
Data type: REGUH_BF-UBNKSOptional: No
Call by Reference: No ( called with pass by value option)
I_UZAWE -
Data type: REGUH_BF-UZAWEOptional: No
Call by Reference: No ( called with pass by value option)
I_WAERS -
Data type: REGUH_BF-WAERSOptional: No
Call by Reference: No ( called with pass by value option)
I_XEINZ - Incoming Payment
Data type: BOOLE-BOOLEOptional: No
Call by Reference: No ( called with pass by value option)
I_PROPOSAL -
Data type: BOOLE-BOOLEDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_MESSAGE_RUN -
Data type: BOOLE-BOOLEDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_MESSAGE_PROP -
Data type: BOOLE-BOOLEDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_UBNKY -
Data type: REGUH_BF-UBNKYOptional: No
Call by Reference: No ( called with pass by value option)
I_UBKNT -
Data type: REGUH_BF-UBKNTOptional: No
Call by Reference: No ( called with pass by value option)
I_ZBNKS -
Data type: REGUH_BF-UBNKSOptional: No
Call by Reference: No ( called with pass by value option)
I_ZBNKY -
Data type: REGUH_BF-UBNKYOptional: No
Call by Reference: No ( called with pass by value option)
I_ZBNKN -
Data type: REGUH_BF-UBKNTOptional: No
Call by Reference: No ( called with pass by value option)
I_ZBKON -
Data type: REGUH_BF-UBKONOptional: No
Call by Reference: No ( called with pass by value option)
I_BKREF -
Data type: REGUH_BF-BKREFOptional: No
Call by Reference: No ( called with pass by value option)
I_ZBNKL -
Data type: REGUH_BF-UBNKLOptional: No
Call by Reference: No ( called with pass by value option)
CHANGING Parameters details for FI_PAYMENT_BANK_CHAIN_SET
C_IBANK1 -
Data type: F110_KBANKOptional: Yes
Call by Reference: No ( called with pass by value option)
C_IBANK2 -
Data type: F110_KBANKOptional: Yes
Call by Reference: No ( called with pass by value option)
C_IBANK3 -
Data type: F110_KBANKOptional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
BANKCHAIN_ERROR -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
CONVERSION_ERROR -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for FI_PAYMENT_BANK_CHAIN_SET 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_ubnks | TYPE REGUH_BF-UBNKS, " | |||
| lv_c_ibank1 | TYPE F110_KBANK, " | |||
| lv_bankchain_error | TYPE F110_KBANK, " | |||
| lv_i_uzawe | TYPE REGUH_BF-UZAWE, " | |||
| lv_i_waers | TYPE REGUH_BF-WAERS, " | |||
| lv_i_xeinz | TYPE BOOLE-BOOLE, " | |||
| lv_i_proposal | TYPE BOOLE-BOOLE, " SPACE | |||
| lv_i_message_run | TYPE BOOLE-BOOLE, " SPACE | |||
| lv_i_message_prop | TYPE BOOLE-BOOLE, " SPACE | |||
| lv_i_ubnky | TYPE REGUH_BF-UBNKY, " | |||
| lv_c_ibank2 | TYPE F110_KBANK, " | |||
| lv_conversion_error | TYPE F110_KBANK, " | |||
| lv_i_ubknt | TYPE REGUH_BF-UBKNT, " | |||
| lv_c_ibank3 | TYPE F110_KBANK, " | |||
| lv_i_zbnks | TYPE REGUH_BF-UBNKS, " | |||
| lv_i_zbnky | TYPE REGUH_BF-UBNKY, " | |||
| lv_i_zbnkn | TYPE REGUH_BF-UBKNT, " | |||
| lv_i_zbkon | TYPE REGUH_BF-UBKON, " | |||
| lv_i_bkref | TYPE REGUH_BF-BKREF, " | |||
| lv_i_zbnkl | TYPE REGUH_BF-UBNKL. " |
|   CALL FUNCTION 'FI_PAYMENT_BANK_CHAIN_SET' " |
| EXPORTING | ||
| I_UBNKS | = lv_i_ubnks | |
| I_UZAWE | = lv_i_uzawe | |
| I_WAERS | = lv_i_waers | |
| I_XEINZ | = lv_i_xeinz | |
| I_PROPOSAL | = lv_i_proposal | |
| I_MESSAGE_RUN | = lv_i_message_run | |
| I_MESSAGE_PROP | = lv_i_message_prop | |
| I_UBNKY | = lv_i_ubnky | |
| I_UBKNT | = lv_i_ubknt | |
| I_ZBNKS | = lv_i_zbnks | |
| I_ZBNKY | = lv_i_zbnky | |
| I_ZBNKN | = lv_i_zbnkn | |
| I_ZBKON | = lv_i_zbkon | |
| I_BKREF | = lv_i_bkref | |
| I_ZBNKL | = lv_i_zbnkl | |
| CHANGING | ||
| C_IBANK1 | = lv_c_ibank1 | |
| C_IBANK2 | = lv_c_ibank2 | |
| C_IBANK3 | = lv_c_ibank3 | |
| EXCEPTIONS | ||
| BANKCHAIN_ERROR = 1 | ||
| CONVERSION_ERROR = 2 | ||
| . " FI_PAYMENT_BANK_CHAIN_SET | ||
ABAP code using 7.40 inline data declarations to call FM FI_PAYMENT_BANK_CHAIN_SET
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 UBNKS FROM REGUH_BF INTO @DATA(ld_i_ubnks). | ||||
| "SELECT single UZAWE FROM REGUH_BF INTO @DATA(ld_i_uzawe). | ||||
| "SELECT single WAERS FROM REGUH_BF INTO @DATA(ld_i_waers). | ||||
| "SELECT single BOOLE FROM BOOLE INTO @DATA(ld_i_xeinz). | ||||
| "SELECT single BOOLE FROM BOOLE INTO @DATA(ld_i_proposal). | ||||
| DATA(ld_i_proposal) | = ' '. | |||
| "SELECT single BOOLE FROM BOOLE INTO @DATA(ld_i_message_run). | ||||
| DATA(ld_i_message_run) | = ' '. | |||
| "SELECT single BOOLE FROM BOOLE INTO @DATA(ld_i_message_prop). | ||||
| DATA(ld_i_message_prop) | = ' '. | |||
| "SELECT single UBNKY FROM REGUH_BF INTO @DATA(ld_i_ubnky). | ||||
| "SELECT single UBKNT FROM REGUH_BF INTO @DATA(ld_i_ubknt). | ||||
| "SELECT single UBNKS FROM REGUH_BF INTO @DATA(ld_i_zbnks). | ||||
| "SELECT single UBNKY FROM REGUH_BF INTO @DATA(ld_i_zbnky). | ||||
| "SELECT single UBKNT FROM REGUH_BF INTO @DATA(ld_i_zbnkn). | ||||
| "SELECT single UBKON FROM REGUH_BF INTO @DATA(ld_i_zbkon). | ||||
| "SELECT single BKREF FROM REGUH_BF INTO @DATA(ld_i_bkref). | ||||
| "SELECT single UBNKL FROM REGUH_BF INTO @DATA(ld_i_zbnkl). | ||||
Search for further information about these or an SAP related objects