SAP FIS_EVENT_GET_CUST_DATA Function Module for Provides User Customizing for Log Category









FIS_EVENT_GET_CUST_DATA is a standard fis event get cust data SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Provides User Customizing for Log Category 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 get cust data FM, simply by entering the name FIS_EVENT_GET_CUST_DATA 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): Normal Function Module
Update:



Function FIS_EVENT_GET_CUST_DATA 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_GET_CUST_DATA'"Provides User Customizing for Log Category
EXPORTING
CATEGORYNAME = "Name of Log Category
* BUKRS = "Company Code

IMPORTING
ACTIVE = "Indicator: Category Active?
DAYSTOKEEP = "Number of Days a Log Entry Stays in System
AGGREGATION = "Aggregation Behavior of Log Entry
.



IMPORTING Parameters details for FIS_EVENT_GET_CUST_DATA

CATEGORYNAME - Name of Log Category

Data type: CATEGORYNAME_FIS
Optional: No
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)

EXPORTING Parameters details for FIS_EVENT_GET_CUST_DATA

ACTIVE - Indicator: Category Active?

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

DAYSTOKEEP - Number of Days a Log Entry Stays in System

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

AGGREGATION - Aggregation Behavior of Log Entry

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

Copy and paste ABAP code example for FIS_EVENT_GET_CUST_DATA 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_active  TYPE CATEGORYACTIVE_FIS, "   
lv_categoryname  TYPE CATEGORYNAME_FIS, "   
lv_bukrs  TYPE BUKRS, "   
lv_daystokeep  TYPE DAYSTOKEEP_FIS, "   
lv_aggregation  TYPE EVENTAGGREGATION_FIS. "   

  CALL FUNCTION 'FIS_EVENT_GET_CUST_DATA'  "Provides User Customizing for Log Category
    EXPORTING
         CATEGORYNAME = lv_categoryname
         BUKRS = lv_bukrs
    IMPORTING
         ACTIVE = lv_active
         DAYSTOKEEP = lv_daystokeep
         AGGREGATION = lv_aggregation
. " FIS_EVENT_GET_CUST_DATA




ABAP code using 7.40 inline data declarations to call FM FIS_EVENT_GET_CUST_DATA

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



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!