SAP BAL_LOG_MSG_READ Function Module for Application Log: Log: Message: Read data and texts

Search SAP Function Modules

BAL_LOG_MSG_READ is a standard bal log msg read 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: Read data and texts 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 read FM, simply by entering the name BAL_LOG_MSG_READ 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_READ 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_READ'"Application Log: Log: Message: Read data and texts
  EXPORTING
   I_S_MSG_HANDLE =  "Message handle
*  I_LANGU = SY-LANGU "Language

 IMPORTING
   E_S_MSG =  "Message data
   E_EXISTS_ON_DB =  "Message already exists in the database
   E_TXT_MSGTY =  "Error type text
   E_TXT_MSGID =  "Application area text
   E_TXT_DETLEVEL =  "Level of detail text
   E_TXT_PROBCLASS =  "Problem class text
   E_TXT_MSG =  "Message text (formatted)
   E_WARNING_TEXT_NOT_FOUND =  "At least one text not found

EXCEPTIONS
   LOG_NOT_FOUND = 1    MSG_NOT_FOUND = 2 

.

IMPORTING Parameters details for BAL_LOG_MSG_READ

I_S_MSG_HANDLE - Message handle

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

I_LANGU - Language

Data type: SYLANGU
Default: SY-LANGU
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for BAL_LOG_MSG_READ

E_S_MSG - Message data

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

E_EXISTS_ON_DB - Message already exists in the database

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

E_TXT_MSGTY - Error type text

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

E_TXT_MSGID - Application area text

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

E_TXT_DETLEVEL - Level of detail text

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

E_TXT_PROBCLASS - Problem class text

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

E_TXT_MSG - Message text (formatted)

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

E_WARNING_TEXT_NOT_FOUND - At least one text not found

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

EXCEPTIONS details

LOG_NOT_FOUND - Log not found

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

MSG_NOT_FOUND - Message not found

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

Copy and paste ABAP code example for BAL_LOG_MSG_READ 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.

ABAP code using 7.40 inline data declarations to call FM BAL_LOG_MSG_READ

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