SAP BKK_HY_DYNPRO_CONTROL_D40 Function Module for Account Hierarchy: Control of Interval Change (Screen 40)
BKK_HY_DYNPRO_CONTROL_D40 is a standard bkk hy dynpro control d40 SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Account Hierarchy: Control of Interval Change (Screen 40) 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 bkk hy dynpro control d40 FM, simply by entering the name BKK_HY_DYNPRO_CONTROL_D40 into the relevant SAP transaction such as SE37 or SE38.
Function Group: FBH1
Program Name: SAPLFBH1
Main Program: SAPLFBH1
Appliation area: F
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function BKK_HY_DYNPRO_CONTROL_D40 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 'BKK_HY_DYNPRO_CONTROL_D40'"Account Hierarchy: Control of Interval Change (Screen 40).
EXPORTING
* I_NO_CHANGE = "
IMPORTING
E_FLG_INTERV_CHANGED = "
CHANGING
* C_FLG_CHANGE = '0' "Change Indicator: 0-False, 1-True
TABLES
T_BKK610 = "-> Current Entry; <- Updated Entry
T_BKK615 = "
T_BKK600 = "-> Current Entries; <- Updated Entries
EXCEPTIONS
E_WRONG_INTERFACE = 1 E_WRONG_CODING = 2
IMPORTING Parameters details for BKK_HY_DYNPRO_CONTROL_D40
I_NO_CHANGE -
Data type: SY-SUBRCOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for BKK_HY_DYNPRO_CONTROL_D40
E_FLG_INTERV_CHANGED -
Data type: BKK_XFELDOptional: No
Call by Reference: No ( called with pass by value option)
CHANGING Parameters details for BKK_HY_DYNPRO_CONTROL_D40
C_FLG_CHANGE - Change Indicator: 0-False, 1-True
Data type: IBKK6S4-CHAR1Default: '0'
Optional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for BKK_HY_DYNPRO_CONTROL_D40
T_BKK610 - -> Current Entry; <- Updated Entry
Data type: BKK610Optional: No
Call by Reference: No ( called with pass by value option)
T_BKK615 -
Data type: BKK615Optional: No
Call by Reference: No ( called with pass by value option)
T_BKK600 - -> Current Entries; <- Updated Entries
Data type: BKK600Optional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
E_WRONG_INTERFACE -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
E_WRONG_CODING -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for BKK_HY_DYNPRO_CONTROL_D40 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_bkk610 | TYPE STANDARD TABLE OF BKK610, " | |||
| lv_i_no_change | TYPE SY-SUBRC, " | |||
| lv_c_flg_change | TYPE IBKK6S4-CHAR1, " '0' | |||
| lv_e_wrong_interface | TYPE IBKK6S4, " | |||
| lv_e_flg_interv_changed | TYPE BKK_XFELD, " | |||
| lt_t_bkk615 | TYPE STANDARD TABLE OF BKK615, " | |||
| lv_e_wrong_coding | TYPE BKK615, " | |||
| lt_t_bkk600 | TYPE STANDARD TABLE OF BKK600. " |
|   CALL FUNCTION 'BKK_HY_DYNPRO_CONTROL_D40' "Account Hierarchy: Control of Interval Change (Screen 40) |
| EXPORTING | ||
| I_NO_CHANGE | = lv_i_no_change | |
| IMPORTING | ||
| E_FLG_INTERV_CHANGED | = lv_e_flg_interv_changed | |
| CHANGING | ||
| C_FLG_CHANGE | = lv_c_flg_change | |
| TABLES | ||
| T_BKK610 | = lt_t_bkk610 | |
| T_BKK615 | = lt_t_bkk615 | |
| T_BKK600 | = lt_t_bkk600 | |
| EXCEPTIONS | ||
| E_WRONG_INTERFACE = 1 | ||
| E_WRONG_CODING = 2 | ||
| . " BKK_HY_DYNPRO_CONTROL_D40 | ||
ABAP code using 7.40 inline data declarations to call FM BKK_HY_DYNPRO_CONTROL_D40
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 SUBRC FROM SY INTO @DATA(ld_i_no_change). | ||||
| "SELECT single CHAR1 FROM IBKK6S4 INTO @DATA(ld_c_flg_change). | ||||
| DATA(ld_c_flg_change) | = '0'. | |||
Search for further information about these or an SAP related objects