SAP BDL_READ_LOG Function Module for Read message log according to given selection criteria









BDL_READ_LOG is a standard bdl read log SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Read message log according to given selection criteria 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 bdl read log FM, simply by entering the name BDL_READ_LOG into the relevant SAP transaction such as SE37 or SE38.

Function Group: BDL3
Program Name: SAPLBDL3
Main Program: SAPLBDL3
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function BDL_READ_LOG 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 'BDL_READ_LOG'"Read message log according to given selection criteria
  EXPORTING
*  SESSIONNR = '*' "
*  MANDANT = '*' "
*  STARTDATE = '19990801' "
*  STARTTIME = '000000' "
*  ENDDATE = '99991231' "
*  ENDTIME = '235959' "
*  SEVERITY = 'I' "
*  SHOWUNSPECIFIC = 'X' "

TABLES
   MSGLOG =  "
.



IMPORTING Parameters details for BDL_READ_LOG

SESSIONNR -

Data type: BDLMSGLOG-SESSIONNR
Default: '*'
Optional: Yes
Call by Reference: No ( called with pass by value option)

MANDANT -

Data type: BDLMSGLOG-MANDANT
Default: '*'
Optional: Yes
Call by Reference: No ( called with pass by value option)

STARTDATE -

Data type: SY-DATUM
Default: '19990801'
Optional: Yes
Call by Reference: No ( called with pass by value option)

STARTTIME -

Data type: SY-UZEIT
Default: '000000'
Optional: Yes
Call by Reference: No ( called with pass by value option)

ENDDATE -

Data type: SY-DATUM
Default: '99991231'
Optional: Yes
Call by Reference: No ( called with pass by value option)

ENDTIME -

Data type: SY-UZEIT
Default: '235959'
Optional: Yes
Call by Reference: No ( called with pass by value option)

SEVERITY -

Data type: BDLMSGLOG-SEVERITY
Default: 'I'
Optional: Yes
Call by Reference: No ( called with pass by value option)

SHOWUNSPECIFIC -

Data type: SY-DEBUG
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for BDL_READ_LOG

MSGLOG -

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

Copy and paste ABAP code example for BDL_READ_LOG 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:
lt_msglog  TYPE STANDARD TABLE OF BDLMSGLOG, "   
lv_sessionnr  TYPE BDLMSGLOG-SESSIONNR, "   '*'
lv_mandant  TYPE BDLMSGLOG-MANDANT, "   '*'
lv_startdate  TYPE SY-DATUM, "   '19990801'
lv_starttime  TYPE SY-UZEIT, "   '000000'
lv_enddate  TYPE SY-DATUM, "   '99991231'
lv_endtime  TYPE SY-UZEIT, "   '235959'
lv_severity  TYPE BDLMSGLOG-SEVERITY, "   'I'
lv_showunspecific  TYPE SY-DEBUG. "   'X'

  CALL FUNCTION 'BDL_READ_LOG'  "Read message log according to given selection criteria
    EXPORTING
         SESSIONNR = lv_sessionnr
         MANDANT = lv_mandant
         STARTDATE = lv_startdate
         STARTTIME = lv_starttime
         ENDDATE = lv_enddate
         ENDTIME = lv_endtime
         SEVERITY = lv_severity
         SHOWUNSPECIFIC = lv_showunspecific
    TABLES
         MSGLOG = lt_msglog
. " BDL_READ_LOG




ABAP code using 7.40 inline data declarations to call FM BDL_READ_LOG

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.

 
"SELECT single SESSIONNR FROM BDLMSGLOG INTO @DATA(ld_sessionnr).
DATA(ld_sessionnr) = '*'.
 
"SELECT single MANDANT FROM BDLMSGLOG INTO @DATA(ld_mandant).
DATA(ld_mandant) = '*'.
 
"SELECT single DATUM FROM SY INTO @DATA(ld_startdate).
DATA(ld_startdate) = '19990801'.
 
"SELECT single UZEIT FROM SY INTO @DATA(ld_starttime).
DATA(ld_starttime) = '000000'.
 
"SELECT single DATUM FROM SY INTO @DATA(ld_enddate).
DATA(ld_enddate) = '99991231'.
 
"SELECT single UZEIT FROM SY INTO @DATA(ld_endtime).
DATA(ld_endtime) = '235959'.
 
"SELECT single SEVERITY FROM BDLMSGLOG INTO @DATA(ld_severity).
DATA(ld_severity) = 'I'.
 
"SELECT single DEBUG FROM SY INTO @DATA(ld_showunspecific).
DATA(ld_showunspecific) = 'X'.
 


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!