SAP BAL_LOG_HDR_READ Function Module for Application Log: Log: Header Data: Read Data and Texts
BAL_LOG_HDR_READ is a standard bal log hdr 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: Header Data: 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 hdr read FM, simply by entering the name BAL_LOG_HDR_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_HDR_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_HDR_READ'"Application Log: Log: Header Data: Read Data and Texts.
EXPORTING
I_LOG_HANDLE = "Log handle
* I_LANGU = SY-LANGU "Language
IMPORTING
E_S_LOG = "Log header data
E_TXT_ALTCODE = "Transaction code text
E_TXT_ALMODE = "Operating mode text
E_TXT_ALSTATE = "Status text
E_TXT_PROBCLASS = "Problem class text
E_TXT_DEL_BEFORE = "'Delete before expiry' flag text
E_WARNING_TEXT_NOT_FOUND = "One or more texts not found
E_EXISTS_ON_DB = "Log already exists in the database
E_CREATED_IN_CLIENT = "Client in which the log was created
E_SAVED_IN_CLIENT = "Client in which the log was saved
E_IS_MODIFIED = "Log changed
E_LOGNUMBER = "Internal log number
E_STATISTICS = "Statistics (number of A, E, W, I and S messages)
E_TXT_OBJECT = "Application Log object text
E_TXT_SUBOBJECT = "Application Log subobject text
EXCEPTIONS
LOG_NOT_FOUND = 1
IMPORTING Parameters details for BAL_LOG_HDR_READ
I_LOG_HANDLE - Log handle
Data type: BALLOGHNDLOptional: No
Call by Reference: No ( called with pass by value option)
I_LANGU - Language
Data type: SYLANGUDefault: SY-LANGU
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for BAL_LOG_HDR_READ
E_S_LOG - Log header data
Data type: BAL_S_LOGOptional: No
Call by Reference: Yes
E_TXT_ALTCODE - Transaction code text
Data type: COptional: No
Call by Reference: Yes
E_TXT_ALMODE - Operating mode text
Data type: COptional: No
Call by Reference: Yes
E_TXT_ALSTATE - Status text
Data type: COptional: No
Call by Reference: Yes
E_TXT_PROBCLASS - Problem class text
Data type: COptional: No
Call by Reference: Yes
E_TXT_DEL_BEFORE - 'Delete before expiry' flag text
Data type: COptional: No
Call by Reference: Yes
E_WARNING_TEXT_NOT_FOUND - One or more texts not found
Data type: BOOLEANOptional: No
Call by Reference: Yes
E_EXISTS_ON_DB - Log already exists in the database
Data type: BOOLEANOptional: No
Call by Reference: Yes
E_CREATED_IN_CLIENT - Client in which the log was created
Data type: SY-MANDTOptional: No
Call by Reference: Yes
E_SAVED_IN_CLIENT - Client in which the log was saved
Data type: SY-MANDTOptional: No
Call by Reference: Yes
E_IS_MODIFIED - Log changed
Data type: BOOLEANOptional: No
Call by Reference: Yes
E_LOGNUMBER - Internal log number
Data type: BALOGNROptional: No
Call by Reference: Yes
E_STATISTICS - Statistics (number of A, E, W, I and S messages)
Data type: BAL_S_SCNTOptional: No
Call by Reference: Yes
E_TXT_OBJECT - Application Log object text
Data type: COptional: No
Call by Reference: Yes
E_TXT_SUBOBJECT - Application Log subobject text
Data type: COptional: 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)
Copy and paste ABAP code example for BAL_LOG_HDR_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.| DATA: | ||||
| lv_e_s_log | TYPE BAL_S_LOG, " | |||
| lv_i_log_handle | TYPE BALLOGHNDL, " | |||
| lv_log_not_found | TYPE BALLOGHNDL, " | |||
| lv_e_txt_altcode | TYPE C, " | |||
| lv_e_txt_almode | TYPE C, " | |||
| lv_e_txt_alstate | TYPE C, " | |||
| lv_e_txt_probclass | TYPE C, " | |||
| lv_e_txt_del_before | TYPE C, " | |||
| lv_e_warning_text_not_found | TYPE BOOLEAN, " | |||
| lv_i_langu | TYPE SYLANGU, " SY-LANGU | |||
| lv_e_exists_on_db | TYPE BOOLEAN, " | |||
| lv_e_created_in_client | TYPE SY-MANDT, " | |||
| lv_e_saved_in_client | TYPE SY-MANDT, " | |||
| lv_e_is_modified | TYPE BOOLEAN, " | |||
| lv_e_lognumber | TYPE BALOGNR, " | |||
| lv_e_statistics | TYPE BAL_S_SCNT, " | |||
| lv_e_txt_object | TYPE C, " | |||
| lv_e_txt_subobject | TYPE C. " |
|   CALL FUNCTION 'BAL_LOG_HDR_READ' "Application Log: Log: Header Data: Read Data and Texts |
| EXPORTING | ||
| I_LOG_HANDLE | = lv_i_log_handle | |
| I_LANGU | = lv_i_langu | |
| IMPORTING | ||
| E_S_LOG | = lv_e_s_log | |
| E_TXT_ALTCODE | = lv_e_txt_altcode | |
| E_TXT_ALMODE | = lv_e_txt_almode | |
| E_TXT_ALSTATE | = lv_e_txt_alstate | |
| E_TXT_PROBCLASS | = lv_e_txt_probclass | |
| E_TXT_DEL_BEFORE | = lv_e_txt_del_before | |
| E_WARNING_TEXT_NOT_FOUND | = lv_e_warning_text_not_found | |
| E_EXISTS_ON_DB | = lv_e_exists_on_db | |
| E_CREATED_IN_CLIENT | = lv_e_created_in_client | |
| E_SAVED_IN_CLIENT | = lv_e_saved_in_client | |
| E_IS_MODIFIED | = lv_e_is_modified | |
| E_LOGNUMBER | = lv_e_lognumber | |
| E_STATISTICS | = lv_e_statistics | |
| E_TXT_OBJECT | = lv_e_txt_object | |
| E_TXT_SUBOBJECT | = lv_e_txt_subobject | |
| EXCEPTIONS | ||
| LOG_NOT_FOUND = 1 | ||
| . " BAL_LOG_HDR_READ | ||
ABAP code using 7.40 inline data declarations to call FM BAL_LOG_HDR_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.| DATA(ld_i_langu) | = SY-LANGU. | |||
| "SELECT single MANDT FROM SY INTO @DATA(ld_e_created_in_client). | ||||
| "SELECT single MANDT FROM SY INTO @DATA(ld_e_saved_in_client). | ||||
Search for further information about these or an SAP related objects