SAP BKK_CONDITION_MAINTAIN Function Module for Edit Condition
BKK_CONDITION_MAINTAIN is a standard bkk condition maintain SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Edit Condition 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 condition maintain FM, simply by entering the name BKK_CONDITION_MAINTAIN into the relevant SAP transaction such as SE37 or SE38.
Function Group: FB83
Program Name: SAPLFB83
Main Program: SAPLFB83
Appliation area: F
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function BKK_CONDITION_MAINTAIN 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_CONDITION_MAINTAIN'"Edit Condition.
EXPORTING
I_FLG_DISPLAY = "One-Character Indicator
I_MODUS = "One-Character Indicator
I_CONDTIME = "
I_RELEASE = "
I_HEADER = "
I_CONDGR_CAT = "
IMPORTING
E_FLG_CHANGE = "One-Character Indicator
TABLES
T_ACT_CONDITION = "
T_ALL_CONDITION = "
T_POSITION = "
* T_ATTRIBUTE = "
IMPORTING Parameters details for BKK_CONDITION_MAINTAIN
I_FLG_DISPLAY - One-Character Indicator
Data type: CHAR1Optional: No
Call by Reference: Yes
I_MODUS - One-Character Indicator
Data type: CHAR1Optional: No
Call by Reference: Yes
I_CONDTIME -
Data type: TBKK80BAS-XCONDTIME1Optional: No
Call by Reference: Yes
I_RELEASE -
Data type: TBKK80BAS-XRELEASEOptional: No
Call by Reference: Yes
I_HEADER -
Data type: IBKK99Optional: No
Call by Reference: Yes
I_CONDGR_CAT -
Data type: IBKK91-CONDGR_CATOptional: No
Call by Reference: Yes
EXPORTING Parameters details for BKK_CONDITION_MAINTAIN
E_FLG_CHANGE - One-Character Indicator
Data type: CHAR1Optional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for BKK_CONDITION_MAINTAIN
T_ACT_CONDITION -
Data type: IBKK91Optional: No
Call by Reference: No ( called with pass by value option)
T_ALL_CONDITION -
Data type: IBKK91Optional: No
Call by Reference: No ( called with pass by value option)
T_POSITION -
Data type: IBKK92Optional: No
Call by Reference: No ( called with pass by value option)
T_ATTRIBUTE -
Data type: IBKK9DOptional: Yes
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for BKK_CONDITION_MAINTAIN 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_e_flg_change | TYPE CHAR1, " | |||
| lv_i_flg_display | TYPE CHAR1, " | |||
| lt_t_act_condition | TYPE STANDARD TABLE OF IBKK91, " | |||
| lv_i_modus | TYPE CHAR1, " | |||
| lt_t_all_condition | TYPE STANDARD TABLE OF IBKK91, " | |||
| lv_i_condtime | TYPE TBKK80BAS-XCONDTIME1, " | |||
| lt_t_position | TYPE STANDARD TABLE OF IBKK92, " | |||
| lv_i_release | TYPE TBKK80BAS-XRELEASE, " | |||
| lt_t_attribute | TYPE STANDARD TABLE OF IBKK9D, " | |||
| lv_i_header | TYPE IBKK99, " | |||
| lv_i_condgr_cat | TYPE IBKK91-CONDGR_CAT. " |
|   CALL FUNCTION 'BKK_CONDITION_MAINTAIN' "Edit Condition |
| EXPORTING | ||
| I_FLG_DISPLAY | = lv_i_flg_display | |
| I_MODUS | = lv_i_modus | |
| I_CONDTIME | = lv_i_condtime | |
| I_RELEASE | = lv_i_release | |
| I_HEADER | = lv_i_header | |
| I_CONDGR_CAT | = lv_i_condgr_cat | |
| IMPORTING | ||
| E_FLG_CHANGE | = lv_e_flg_change | |
| TABLES | ||
| T_ACT_CONDITION | = lt_t_act_condition | |
| T_ALL_CONDITION | = lt_t_all_condition | |
| T_POSITION | = lt_t_position | |
| T_ATTRIBUTE | = lt_t_attribute | |
| . " BKK_CONDITION_MAINTAIN | ||
ABAP code using 7.40 inline data declarations to call FM BKK_CONDITION_MAINTAIN
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 XCONDTIME1 FROM TBKK80BAS INTO @DATA(ld_i_condtime). | ||||
| "SELECT single XRELEASE FROM TBKK80BAS INTO @DATA(ld_i_release). | ||||
| "SELECT single CONDGR_CAT FROM IBKK91 INTO @DATA(ld_i_condgr_cat). | ||||
Search for further information about these or an SAP related objects