SAP FIS_EVENT_LOG Function Module for Save an Event to Database

Search SAP Function Modules

FIS_EVENT_LOG is a standard fis event 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 Save an Event to Database 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 log FM, simply by entering the name FIS_EVENT_LOG 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_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 'FIS_EVENT_LOG'"Save an Event to Database
  EXPORTING
   CATEGORYNAME =  "Name of Category of Event log
*  USER =  "User ID in FSCM
*  TIMESTAMP =  "Event Time Stamp
*  BUKRS =  "Company Code
*  DOCUMENTID =  "Object Relationship Service: BOR object identifier
*  MESSAGE =  "Transfer Structure with all Sy Fields for T100
*  REFERENCE =  "

 IMPORTING
   RETURN =  "Return Parameter(s)

.

IMPORTING Parameters details for FIS_EVENT_LOG

CATEGORYNAME - Name of Category of Event log

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

USER - User ID in FSCM

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

TIMESTAMP - Event Time Stamp

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

BUKRS - Company Code

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

DOCUMENTID - Object Relationship Service: BOR object identifier

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

MESSAGE - Transfer Structure with all Sy Fields for T100

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

REFERENCE -

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

EXPORTING Parameters details for FIS_EVENT_LOG

RETURN - Return Parameter(s)

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

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

ABAP code using 7.40 inline data declarations to call FM FIS_EVENT_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.

Search for further information about these or an SAP related objects