SAP FVD_BANK_DATA_UI_DISP_BNK_DATA Function Module for
FVD_BANK_DATA_UI_DISP_BNK_DATA is a standard fvd bank data ui disp bnk data 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 fvd bank data ui disp bnk data FM, simply by entering the name FVD_BANK_DATA_UI_DISP_BNK_DATA into the relevant SAP transaction such as SE37 or SE38.
Function Group: FVD_BANK_DATA_UI
Program Name: SAPLFVD_BANK_DATA_UI
Main Program: SAPLFVD_BANK_DATA_UI
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FVD_BANK_DATA_UI_DISP_BNK_DATA 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 'FVD_BANK_DATA_UI_DISP_BNK_DATA'".
EXPORTING
* I_DISPLAY = 'X' "
I_PARTNER = "
* I_OKCODE = "
* I_LOG_HANDLE = "
IMPORTING Parameters details for FVD_BANK_DATA_UI_DISP_BNK_DATA
I_DISPLAY -
Data type: CHAR1Default: 'X'
Optional: Yes
Call by Reference: Yes
I_PARTNER -
Data type: BP_PARTNR_NEWOptional: No
Call by Reference: Yes
I_OKCODE -
Data type: TBZ4-FCODEOptional: Yes
Call by Reference: Yes
I_LOG_HANDLE -
Data type: BALLOGHNDLOptional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for FVD_BANK_DATA_UI_DISP_BNK_DATA 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_display | TYPE CHAR1, " 'X' | |||
| lv_i_partner | TYPE BP_PARTNR_NEW, " | |||
| lv_i_okcode | TYPE TBZ4-FCODE, " | |||
| lv_i_log_handle | TYPE BALLOGHNDL. " |
|   CALL FUNCTION 'FVD_BANK_DATA_UI_DISP_BNK_DATA' " |
| EXPORTING | ||
| I_DISPLAY | = lv_i_display | |
| I_PARTNER | = lv_i_partner | |
| I_OKCODE | = lv_i_okcode | |
| I_LOG_HANDLE | = lv_i_log_handle | |
| . " FVD_BANK_DATA_UI_DISP_BNK_DATA | ||
ABAP code using 7.40 inline data declarations to call FM FVD_BANK_DATA_UI_DISP_BNK_DATA
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.| DATA(ld_i_display) | = 'X'. | |||
| "SELECT single FCODE FROM TBZ4 INTO @DATA(ld_i_okcode). | ||||
Search for further information about these or an SAP related objects