SAP BAL_LOG_MSG_ADD Function Module for Application Log: Log: Message: Add
BAL_LOG_MSG_ADD is a standard bal log msg add SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Application Log: Log: Message: Add 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 bal log msg add FM, simply by entering the name BAL_LOG_MSG_ADD into the relevant SAP transaction such as SE37 or SE38.
Function Group: SBAL
Program Name: SAPLSBAL
Main Program: SAPLSBAL
Appliation area: S
Release date: 26-Apr-1999
Mode(Normal, Remote etc): Normal Function Module
Update:
Function BAL_LOG_MSG_ADD 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_LOG_MSG_ADD'"Application Log: Log: Message: Add.
EXPORTING
* I_LOG_HANDLE = "Log handle
I_S_MSG = "Notification data
IMPORTING
E_S_MSG_HANDLE = "Message handle
E_MSG_WAS_LOGGED = "Message collected
E_MSG_WAS_DISPLAYED = "Message output
EXCEPTIONS
LOG_NOT_FOUND = 1 MSG_INCONSISTENT = 2 LOG_IS_FULL = 3
IMPORTING Parameters details for BAL_LOG_MSG_ADD
I_LOG_HANDLE - Log handle
Data type: BALLOGHNDLOptional: Yes
Call by Reference: No ( called with pass by value option)
I_S_MSG - Notification data
Data type: BAL_S_MSGOptional: No
Call by Reference: Yes
EXPORTING Parameters details for BAL_LOG_MSG_ADD
E_S_MSG_HANDLE - Message handle
Data type: BALMSGHNDLOptional: No
Call by Reference: No ( called with pass by value option)
E_MSG_WAS_LOGGED - Message collected
Data type: BOOLEANOptional: No
Call by Reference: No ( called with pass by value option)
E_MSG_WAS_DISPLAYED - Message output
Data type: BOOLEANOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
LOG_NOT_FOUND - Log not found
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
MSG_INCONSISTENT - Message inconsistent
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
LOG_IS_FULL - Message number 999999 reached. Log is full
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for BAL_LOG_MSG_ADD 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_log_handle | TYPE BALLOGHNDL, " | |||
lv_log_not_found | TYPE BALLOGHNDL, " | |||
lv_e_s_msg_handle | TYPE BALMSGHNDL, " | |||
lv_i_s_msg | TYPE BAL_S_MSG, " | |||
lv_e_msg_was_logged | TYPE BOOLEAN, " | |||
lv_msg_inconsistent | TYPE BOOLEAN, " | |||
lv_log_is_full | TYPE BOOLEAN, " | |||
lv_e_msg_was_displayed | TYPE BOOLEAN. " |
  CALL FUNCTION 'BAL_LOG_MSG_ADD' "Application Log: Log: Message: Add |
EXPORTING | ||
I_LOG_HANDLE | = lv_i_log_handle | |
I_S_MSG | = lv_i_s_msg | |
IMPORTING | ||
E_S_MSG_HANDLE | = lv_e_s_msg_handle | |
E_MSG_WAS_LOGGED | = lv_e_msg_was_logged | |
E_MSG_WAS_DISPLAYED | = lv_e_msg_was_displayed | |
EXCEPTIONS | ||
LOG_NOT_FOUND = 1 | ||
MSG_INCONSISTENT = 2 | ||
LOG_IS_FULL = 3 | ||
. " BAL_LOG_MSG_ADD |
ABAP code using 7.40 inline data declarations to call FM BAL_LOG_MSG_ADD
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