SAP FKK_BANK_SELECTION_GET_VALUES Function Module for
FKK_BANK_SELECTION_GET_VALUES is a standard fkk bank selection get values 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 fkk bank selection get values FM, simply by entering the name FKK_BANK_SELECTION_GET_VALUES into the relevant SAP transaction such as SE37 or SE38.
Function Group: FKPG
Program Name: SAPLFKPG
Main Program: SAPLFKPG
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FKK_BANK_SELECTION_GET_VALUES 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 'FKK_BANK_SELECTION_GET_VALUES'".
EXPORTING
I_BSLID = "ID for Bank Selection in Payment Run
TABLES
T_VALUES = "Payment Program: Bank Selection
EXCEPTIONS
ID_INVALID = 1
IMPORTING Parameters details for FKK_BANK_SELECTION_GET_VALUES
I_BSLID - ID for Bank Selection in Payment Run
Data type: TFK042AX-BSLIDOptional: No
Call by Reference: Yes
TABLES Parameters details for FKK_BANK_SELECTION_GET_VALUES
T_VALUES - Payment Program: Bank Selection
Data type: TFK042AOptional: No
Call by Reference: Yes
EXCEPTIONS details
ID_INVALID - Invalid ID
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for FKK_BANK_SELECTION_GET_VALUES 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_bslid | TYPE TFK042AX-BSLID, " | |||
| lt_t_values | TYPE STANDARD TABLE OF TFK042A, " | |||
| lv_id_invalid | TYPE TFK042A. " |
|   CALL FUNCTION 'FKK_BANK_SELECTION_GET_VALUES' " |
| EXPORTING | ||
| I_BSLID | = lv_i_bslid | |
| TABLES | ||
| T_VALUES | = lt_t_values | |
| EXCEPTIONS | ||
| ID_INVALID = 1 | ||
| . " FKK_BANK_SELECTION_GET_VALUES | ||
ABAP code using 7.40 inline data declarations to call FM FKK_BANK_SELECTION_GET_VALUES
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 BSLID FROM TFK042AX INTO @DATA(ld_i_bslid). | ||||
Search for further information about these or an SAP related objects