SAP BAL_CNTL_CREATE Function Module for
BAL_CNTL_CREATE is a standard bal cntl create 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 bal cntl create FM, simply by entering the name BAL_CNTL_CREATE into the relevant SAP transaction such as SE37 or SE38.
Function Group: SBAL_CNTL
Program Name: SAPLSBAL_CNTL
Main Program: SAPLSBAL_CNTL
Appliation area: S
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 BAL_CNTL_CREATE 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 'BAL_CNTL_CREATE'".
EXPORTING
I_CONTAINER = "
* I_S_DISPLAY_PROFILE = "Display Profile
* I_T_LOG_HANDLE = "Restrict display by log handle
* I_T_MSG_HANDLE = "Restrict display by message handle
* I_S_LOG_FILTER = "Restrict display by log filter
* I_S_MSG_FILTER = "Restrict display by message filter
* I_T_LOG_CONTEXT_FILTER = "Restrict display by log context filter
* I_T_MSG_CONTEXT_FILTER = "Restrict display by message context filter
* I_SRT_BY_TIMSTMP = ' ' "
IMPORTING
E_CONTROL_HANDLE = "Application Log: Control Display Handle
E_NO_DATA_AVAILABLE = "
E_NO_AUTHORITY = "
EXCEPTIONS
PROFILE_INCONSISTENT = 1 INTERNAL_ERROR = 2
IMPORTING Parameters details for BAL_CNTL_CREATE
I_CONTAINER -
Data type: CL_GUI_CONTAINEROptional: No
Call by Reference: Yes
I_S_DISPLAY_PROFILE - Display Profile
Data type: BAL_S_PROFOptional: Yes
Call by Reference: Yes
I_T_LOG_HANDLE - Restrict display by log handle
Data type: BAL_T_LOGHOptional: Yes
Call by Reference: Yes
I_T_MSG_HANDLE - Restrict display by message handle
Data type: BAL_T_MSGHOptional: Yes
Call by Reference: Yes
I_S_LOG_FILTER - Restrict display by log filter
Data type: BAL_S_LFILOptional: Yes
Call by Reference: Yes
I_S_MSG_FILTER - Restrict display by message filter
Data type: BAL_S_MFILOptional: Yes
Call by Reference: Yes
I_T_LOG_CONTEXT_FILTER - Restrict display by log context filter
Data type: BAL_T_CFILOptional: Yes
Call by Reference: Yes
I_T_MSG_CONTEXT_FILTER - Restrict display by message context filter
Data type: BAL_T_CFILOptional: Yes
Call by Reference: Yes
I_SRT_BY_TIMSTMP -
Data type: BOOLEANDefault: SPACE
Optional: Yes
Call by Reference: Yes
EXPORTING Parameters details for BAL_CNTL_CREATE
E_CONTROL_HANDLE - Application Log: Control Display Handle
Data type: BALCNTHNDLOptional: No
Call by Reference: Yes
E_NO_DATA_AVAILABLE -
Data type: BOOLEANOptional: No
Call by Reference: Yes
E_NO_AUTHORITY -
Data type: BOOLEANOptional: No
Call by Reference: Yes
EXCEPTIONS details
PROFILE_INCONSISTENT - Inconsistent display profile
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
INTERNAL_ERROR - Internal Error
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for BAL_CNTL_CREATE 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_container | TYPE CL_GUI_CONTAINER, " | |||
lv_e_control_handle | TYPE BALCNTHNDL, " | |||
lv_profile_inconsistent | TYPE BALCNTHNDL, " | |||
lv_internal_error | TYPE BALCNTHNDL, " | |||
lv_e_no_data_available | TYPE BOOLEAN, " | |||
lv_i_s_display_profile | TYPE BAL_S_PROF, " | |||
lv_e_no_authority | TYPE BOOLEAN, " | |||
lv_i_t_log_handle | TYPE BAL_T_LOGH, " | |||
lv_i_t_msg_handle | TYPE BAL_T_MSGH, " | |||
lv_i_s_log_filter | TYPE BAL_S_LFIL, " | |||
lv_i_s_msg_filter | TYPE BAL_S_MFIL, " | |||
lv_i_t_log_context_filter | TYPE BAL_T_CFIL, " | |||
lv_i_t_msg_context_filter | TYPE BAL_T_CFIL, " | |||
lv_i_srt_by_timstmp | TYPE BOOLEAN. " SPACE |
  CALL FUNCTION 'BAL_CNTL_CREATE' " |
EXPORTING | ||
I_CONTAINER | = lv_i_container | |
I_S_DISPLAY_PROFILE | = lv_i_s_display_profile | |
I_T_LOG_HANDLE | = lv_i_t_log_handle | |
I_T_MSG_HANDLE | = lv_i_t_msg_handle | |
I_S_LOG_FILTER | = lv_i_s_log_filter | |
I_S_MSG_FILTER | = lv_i_s_msg_filter | |
I_T_LOG_CONTEXT_FILTER | = lv_i_t_log_context_filter | |
I_T_MSG_CONTEXT_FILTER | = lv_i_t_msg_context_filter | |
I_SRT_BY_TIMSTMP | = lv_i_srt_by_timstmp | |
IMPORTING | ||
E_CONTROL_HANDLE | = lv_e_control_handle | |
E_NO_DATA_AVAILABLE | = lv_e_no_data_available | |
E_NO_AUTHORITY | = lv_e_no_authority | |
EXCEPTIONS | ||
PROFILE_INCONSISTENT = 1 | ||
INTERNAL_ERROR = 2 | ||
. " BAL_CNTL_CREATE |
ABAP code using 7.40 inline data declarations to call FM BAL_CNTL_CREATE
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_srt_by_timstmp) | = ' '. | |||
Search for further information about these or an SAP related objects