SAP BNK_UI_INSTRUCTION_CHANGE Function Module for Change instruction code
BNK_UI_INSTRUCTION_CHANGE is a standard bnk ui instruction change SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Change instruction code 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 bnk ui instruction change FM, simply by entering the name BNK_UI_INSTRUCTION_CHANGE into the relevant SAP transaction such as SE37 or SE38.
Function Group: BNK_UI_UTIL
Program Name: SAPLBNK_UI_UTIL
Main Program: SAPLBNK_UI_UTIL
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
![](https://www.se80.co.uk/training-education/wp-content/uploads/2019/07/normal-function-module.png)
Function BNK_UI_INSTRUCTION_CHANGE 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 'BNK_UI_INSTRUCTION_CHANGE'"Change instruction code.
IMPORTING
E_FLG_CHANGED = "Checkbox
E_URGENT = "
E_DTKVS = "Cost Allocation Key
TABLES
T_BTC_ITEM = "Batch Payment Item (for UI)
EXPORTING Parameters details for BNK_UI_INSTRUCTION_CHANGE
E_FLG_CHANGED - Checkbox
Data type: XFELDOptional: No
Call by Reference: No ( called with pass by value option)
E_URGENT -
Data type: DTURGOptional: No
Call by Reference: No ( called with pass by value option)
E_DTKVS - Cost Allocation Key
Data type: BNK_COM_COSTALLOCOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for BNK_UI_INSTRUCTION_CHANGE
T_BTC_ITEM - Batch Payment Item (for UI)
Data type: BNK_BTC_ITEM_UIOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for BNK_UI_INSTRUCTION_CHANGE 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: | ||||
lt_t_btc_item | TYPE STANDARD TABLE OF BNK_BTC_ITEM_UI, " | |||
lv_e_flg_changed | TYPE XFELD, " | |||
lv_e_urgent | TYPE DTURG, " | |||
lv_e_dtkvs | TYPE BNK_COM_COSTALLOC. " |
  CALL FUNCTION 'BNK_UI_INSTRUCTION_CHANGE' "Change instruction code |
IMPORTING | ||
E_FLG_CHANGED | = lv_e_flg_changed | |
E_URGENT | = lv_e_urgent | |
E_DTKVS | = lv_e_dtkvs | |
TABLES | ||
T_BTC_ITEM | = lt_t_btc_item | |
. " BNK_UI_INSTRUCTION_CHANGE |
ABAP code using 7.40 inline data declarations to call FM BNK_UI_INSTRUCTION_CHANGE
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