BAL_LOG_MSG_READ is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.
See here to view full function module documentation and code listing, simply by entering the name BAL_LOG_MSG_READ into the relevant SAP transaction such as SE37 or SE80.
Associated Function Group:
SBAL
Released Date:
26.04.1999
Processing type: Normal fucntion module
CALL FUNCTION 'BAL_LOG_MSG_READ' "Application Log: Log: Message: Read data and texts
EXPORTING
i_s_msg_handle = " balmsghndl Message handle
* i_langu = SY-LANGU " sylangu Language
IMPORTING
e_s_msg = " bal_s_msg Message data
e_exists_on_db = " boolean Message already exists in the database
e_txt_msgty = " c Error type text
e_txt_msgid = " c Application area text
e_txt_detlevel = " c Level of detail text
e_txt_probclass = " c Problem class text
e_txt_msg = " c Message text (formatted)
e_warning_text_not_found = " boolean At least one text not found
EXCEPTIONS
LOG_NOT_FOUND = 1 " Log not found
MSG_NOT_FOUND = 2 " Message not found
. " BAL_LOG_MSG_READ
The ABAP code below is a full code listing to execute function module BAL_LOG_MSG_READ including all data declarations. The code uses 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 original method of declaring data variables up front. 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).
| ld_e_s_msg | TYPE BAL_S_MSG , |
| ld_e_exists_on_db | TYPE BOOLEAN , |
| ld_e_txt_msgty | TYPE C , |
| ld_e_txt_msgid | TYPE C , |
| ld_e_txt_detlevel | TYPE C , |
| ld_e_txt_probclass | TYPE C , |
| ld_e_txt_msg | TYPE C , |
| ld_e_warning_text_not_found | TYPE BOOLEAN . |
The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.
DATA:
| ld_e_s_msg | TYPE BAL_S_MSG , |
| ld_i_s_msg_handle | TYPE BALMSGHNDL , |
| ld_e_exists_on_db | TYPE BOOLEAN , |
| ld_i_langu | TYPE SYLANGU , |
| ld_e_txt_msgty | TYPE C , |
| ld_e_txt_msgid | TYPE C , |
| ld_e_txt_detlevel | TYPE C , |
| ld_e_txt_probclass | TYPE C , |
| ld_e_txt_msg | TYPE C , |
| ld_e_warning_text_not_found | TYPE BOOLEAN . |
INCLUDE BAL_GENERAL_LINK OBJECT DOKU ID TX.
...See here for full SAP fm documentation
Please help keep this info upto date and use the comments section below to add useful hints, tips and information specific to this SAP function. This will then be available for you and other users to easily find by simply searching on the object name BAL_LOG_MSG_READ or its description.
BAL_LOG_MSG_READ - Application Log: Log: Message: Read data and texts BAL_LOG_MSG_EXIST - Application Log: Log: Message: Check existence (in memory) BAL_LOG_MSG_DELETE_ALL - Application Log: Log: Message: Delete All Messages BAL_LOG_MSG_DELETE - Application Log: Log: Message: Delete BAL_LOG_MSG_CUMULATE - Application Log: Log: Message: Add Cumulatively BAL_LOG_MSG_CHECK - Application Log: Log: Message: Check