SAP FIS_EVENT_READ Function Module for Read Log Entries
FIS_EVENT_READ is a standard fis event 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 Read Log Entries 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 fis event read FM, simply by entering the name FIS_EVENT_READ into the relevant SAP transaction such as SE37 or SE38.
Function Group: FIS_EVENTLOG
Program Name: SAPLFIS_EVENTLOG
Main Program: SAPLFIS_EVENTLOG
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:
Function FIS_EVENT_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 'FIS_EVENT_READ'"Read Log Entries.
EXPORTING
* IM_CATEGORYNAME = "Name of Log Category
* IM_OBJKEY = "Object Key
* IM_OBJTYPE = "Object Category
* IM_LOGSYS = "Logical System
* IM_REFERENCE = "
* IM_LANGUAGE = SY-LANGU "SAP R/3 System, Current Language
* IM_MAXROWS = 200 "Maximum Number of Entries Returned
* IM_USERID = "User ID in FSCM
* IM_BP_ID = "Business Partner in FSCM
* IM_BP_TYPE = "Type of Business Partner
* IM_FDATE = '00010101' "From Date
* IM_TDATE = '99991231' "To Date
* IM_FTIME = '000000' "From Time
* IM_TTIME = '235959' "To Time
* IM_BUKRS = "Company Code
TABLES
T_EVENT = "Reporting Structure for Log Entries
IMPORTING Parameters details for FIS_EVENT_READ
IM_CATEGORYNAME - Name of Log Category
Data type: TFISEVENTLOG-CATEGORYNAMEOptional: Yes
Call by Reference: No ( called with pass by value option)
IM_OBJKEY - Object Key
Data type: TFISEVENTLOG-OBJKEYOptional: Yes
Call by Reference: No ( called with pass by value option)
IM_OBJTYPE - Object Category
Data type: TFISEVENTLOG-OBJTYPEOptional: Yes
Call by Reference: No ( called with pass by value option)
IM_LOGSYS - Logical System
Data type: TFISEVENTLOG-LOGSYSOptional: Yes
Call by Reference: No ( called with pass by value option)
IM_REFERENCE -
Data type: TFISEVENTLOG-REFERENCEOptional: Yes
Call by Reference: No ( called with pass by value option)
IM_LANGUAGE - SAP R/3 System, Current Language
Data type: SY-LANGUDefault: SY-LANGU
Optional: Yes
Call by Reference: No ( called with pass by value option)
IM_MAXROWS - Maximum Number of Entries Returned
Data type: SY-TABIXDefault: 200
Optional: Yes
Call by Reference: No ( called with pass by value option)
IM_USERID - User ID in FSCM
Data type: TFISEVENTLOG-IDOptional: Yes
Call by Reference: No ( called with pass by value option)
IM_BP_ID - Business Partner in FSCM
Data type: TFISEVENTLOG-BP_IDOptional: Yes
Call by Reference: No ( called with pass by value option)
IM_BP_TYPE - Type of Business Partner
Data type: TFISEVENTLOG-BP_TYPEOptional: Yes
Call by Reference: No ( called with pass by value option)
IM_FDATE - From Date
Data type: TFISEVENTLOG-ADATEDefault: '00010101'
Optional: Yes
Call by Reference: No ( called with pass by value option)
IM_TDATE - To Date
Data type: TFISEVENTLOG-ADATEDefault: '99991231'
Optional: Yes
Call by Reference: No ( called with pass by value option)
IM_FTIME - From Time
Data type: TFISEVENTLOG-ATIMEDefault: '000000'
Optional: Yes
Call by Reference: No ( called with pass by value option)
IM_TTIME - To Time
Data type: TFISEVENTLOG-ATIMEDefault: '235959'
Optional: Yes
Call by Reference: No ( called with pass by value option)
IM_BUKRS - Company Code
Data type: TFISEVENTLOG-BUKRSOptional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for FIS_EVENT_READ
T_EVENT - Reporting Structure for Log Entries
Data type: EVENT_FISOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for FIS_EVENT_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: | ||||
| lt_t_event | TYPE STANDARD TABLE OF EVENT_FIS, " | |||
| lv_im_categoryname | TYPE TFISEVENTLOG-CATEGORYNAME, " | |||
| lv_im_objkey | TYPE TFISEVENTLOG-OBJKEY, " | |||
| lv_im_objtype | TYPE TFISEVENTLOG-OBJTYPE, " | |||
| lv_im_logsys | TYPE TFISEVENTLOG-LOGSYS, " | |||
| lv_im_reference | TYPE TFISEVENTLOG-REFERENCE, " | |||
| lv_im_language | TYPE SY-LANGU, " SY-LANGU | |||
| lv_im_maxrows | TYPE SY-TABIX, " 200 | |||
| lv_im_userid | TYPE TFISEVENTLOG-ID, " | |||
| lv_im_bp_id | TYPE TFISEVENTLOG-BP_ID, " | |||
| lv_im_bp_type | TYPE TFISEVENTLOG-BP_TYPE, " | |||
| lv_im_fdate | TYPE TFISEVENTLOG-ADATE, " '00010101' | |||
| lv_im_tdate | TYPE TFISEVENTLOG-ADATE, " '99991231' | |||
| lv_im_ftime | TYPE TFISEVENTLOG-ATIME, " '000000' | |||
| lv_im_ttime | TYPE TFISEVENTLOG-ATIME, " '235959' | |||
| lv_im_bukrs | TYPE TFISEVENTLOG-BUKRS. " |
| CALL FUNCTION 'FIS_EVENT_READ' "Read Log Entries |
| EXPORTING | ||
| IM_CATEGORYNAME | = lv_im_categoryname | |
| IM_OBJKEY | = lv_im_objkey | |
| IM_OBJTYPE | = lv_im_objtype | |
| IM_LOGSYS | = lv_im_logsys | |
| IM_REFERENCE | = lv_im_reference | |
| IM_LANGUAGE | = lv_im_language | |
| IM_MAXROWS | = lv_im_maxrows | |
| IM_USERID | = lv_im_userid | |
| IM_BP_ID | = lv_im_bp_id | |
| IM_BP_TYPE | = lv_im_bp_type | |
| IM_FDATE | = lv_im_fdate | |
| IM_TDATE | = lv_im_tdate | |
| IM_FTIME | = lv_im_ftime | |
| IM_TTIME | = lv_im_ttime | |
| IM_BUKRS | = lv_im_bukrs | |
| TABLES | ||
| T_EVENT | = lt_t_event | |
| . " FIS_EVENT_READ | ||
ABAP code using 7.40 inline data declarations to call FM FIS_EVENT_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.| "SELECT single CATEGORYNAME FROM TFISEVENTLOG INTO @DATA(ld_im_categoryname). | ||||
| "SELECT single OBJKEY FROM TFISEVENTLOG INTO @DATA(ld_im_objkey). | ||||
| "SELECT single OBJTYPE FROM TFISEVENTLOG INTO @DATA(ld_im_objtype). | ||||
| "SELECT single LOGSYS FROM TFISEVENTLOG INTO @DATA(ld_im_logsys). | ||||
| "SELECT single REFERENCE FROM TFISEVENTLOG INTO @DATA(ld_im_reference). | ||||
| "SELECT single LANGU FROM SY INTO @DATA(ld_im_language). | ||||
| DATA(ld_im_language) | = SY-LANGU. | |||
| "SELECT single TABIX FROM SY INTO @DATA(ld_im_maxrows). | ||||
| DATA(ld_im_maxrows) | = 200. | |||
| "SELECT single ID FROM TFISEVENTLOG INTO @DATA(ld_im_userid). | ||||
| "SELECT single BP_ID FROM TFISEVENTLOG INTO @DATA(ld_im_bp_id). | ||||
| "SELECT single BP_TYPE FROM TFISEVENTLOG INTO @DATA(ld_im_bp_type). | ||||
| "SELECT single ADATE FROM TFISEVENTLOG INTO @DATA(ld_im_fdate). | ||||
| DATA(ld_im_fdate) | = '00010101'. | |||
| "SELECT single ADATE FROM TFISEVENTLOG INTO @DATA(ld_im_tdate). | ||||
| DATA(ld_im_tdate) | = '99991231'. | |||
| "SELECT single ATIME FROM TFISEVENTLOG INTO @DATA(ld_im_ftime). | ||||
| DATA(ld_im_ftime) | = '000000'. | |||
| "SELECT single ATIME FROM TFISEVENTLOG INTO @DATA(ld_im_ttime). | ||||
| DATA(ld_im_ttime) | = '235959'. | |||
| "SELECT single BUKRS FROM TFISEVENTLOG INTO @DATA(ld_im_bukrs). | ||||
Search for further information about these or an SAP related objects