SAP BAL_LOG_MSG_ADD_FREE_TEXT Function Module for Application Log: Log: Message: Insert as free text









BAL_LOG_MSG_ADD_FREE_TEXT is a standard bal log msg add free text 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: Insert as free text 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 free text FM, simply by entering the name BAL_LOG_MSG_ADD_FREE_TEXT 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_FREE_TEXT 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_FREE_TEXT'"Application Log: Log: Message: Insert as free text
EXPORTING
* I_LOG_HANDLE = "Log handle
I_MSGTY = "Message type (A, E, W, I, S)
* I_PROBCLASS = '4' "Problem class (1, 2, 3, 4)
I_TEXT = "Message data
* I_S_CONTEXT = "Context information for free text message
* I_S_PARAMS = "Parameter set for free text message

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_FREE_TEXT

I_LOG_HANDLE - Log handle

Data type: BALLOGHNDL
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_MSGTY - Message type (A, E, W, I, S)

Data type: SYMSGTY
Optional: No
Call by Reference: Yes

I_PROBCLASS - Problem class (1, 2, 3, 4)

Data type: BALPROBCL
Default: '4'
Optional: Yes
Call by Reference: Yes

I_TEXT - Message data

Data type: C
Optional: No
Call by Reference: Yes

I_S_CONTEXT - Context information for free text message

Data type: BAL_S_CONT
Optional: Yes
Call by Reference: Yes

I_S_PARAMS - Parameter set for free text message

Data type: BAL_S_PARM
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for BAL_LOG_MSG_ADD_FREE_TEXT

E_S_MSG_HANDLE - Message handle

Data type: BALMSGHNDL
Optional: No
Call by Reference: No ( called with pass by value option)

E_MSG_WAS_LOGGED - Message collected

Data type: BOOLEAN
Optional: No
Call by Reference: No ( called with pass by value option)

E_MSG_WAS_DISPLAYED - Message output

Data type: BOOLEAN
Optional: 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_FREE_TEXT 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_msgty  TYPE SYMSGTY, "   
lv_e_msg_was_logged  TYPE BOOLEAN, "   
lv_msg_inconsistent  TYPE BOOLEAN, "   
lv_i_probclass  TYPE BALPROBCL, "   '4'
lv_log_is_full  TYPE BALPROBCL, "   
lv_e_msg_was_displayed  TYPE BOOLEAN, "   
lv_i_text  TYPE C, "   
lv_i_s_context  TYPE BAL_S_CONT, "   
lv_i_s_params  TYPE BAL_S_PARM. "   

  CALL FUNCTION 'BAL_LOG_MSG_ADD_FREE_TEXT'  "Application Log: Log: Message: Insert as free text
    EXPORTING
         I_LOG_HANDLE = lv_i_log_handle
         I_MSGTY = lv_i_msgty
         I_PROBCLASS = lv_i_probclass
         I_TEXT = lv_i_text
         I_S_CONTEXT = lv_i_s_context
         I_S_PARAMS = lv_i_s_params
    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_FREE_TEXT




ABAP code using 7.40 inline data declarations to call FM BAL_LOG_MSG_ADD_FREE_TEXT

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_probclass) = '4'.
 
 
 
 
 
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!