SAP SVMCRT_LGV_LOGREADER Function Module for









SVMCRT_LGV_LOGREADER is a standard svmcrt lgv logreader SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 svmcrt lgv logreader FM, simply by entering the name SVMCRT_LGV_LOGREADER into the relevant SAP transaction such as SE37 or SE38.

Function Group: SVMCRT_LOGVIEWER_JAVA
Program Name: SAPLSVMCRT_LOGVIEWER_JAVA
Main Program: SAPLSVMCRT_LOGVIEWER_JAVA
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled JAVA Module
Update:



Function SVMCRT_LGV_LOGREADER 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 'SVMCRT_LGV_LOGREADER'"
  EXPORTING
   OFFSET = 0 "
*  THREAD_NAME =  "
*  LOGCONTR_NAME =  "
*  FROM_DATE =  "
*  FROM_TIME =  "
*  UNTIL_DATE =  "
*  UNTIL_TIME =  "
*  MAX_COUNT = 100 "
*  LOG_NAMES =  "
*  EXCLUDE_NAMES =  "
   UPDATE_SELECTION =  "
*  MIN_SEVERITY = 0 "
*  USER_NAME =  "
*  CLIENT_ID =  "
*  SESSION_ID =  "

 IMPORTING
   IF_RESULT =  "
   SIZE =  "
   LAST_INDEX =  "
.



IMPORTING Parameters details for SVMCRT_LGV_LOGREADER

OFFSET -

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

THREAD_NAME -

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

LOGCONTR_NAME -

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

FROM_DATE -

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

FROM_TIME -

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

UNTIL_DATE -

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

UNTIL_TIME -

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

MAX_COUNT -

Data type: INT4
Default: 100
Optional: No
Call by Reference: No ( called with pass by value option)

LOG_NAMES -

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

EXCLUDE_NAMES -

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

UPDATE_SELECTION -

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

MIN_SEVERITY -

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

USER_NAME -

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

CLIENT_ID -

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

SESSION_ID -

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

EXPORTING Parameters details for SVMCRT_LGV_LOGREADER

IF_RESULT -

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

SIZE -

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

LAST_INDEX -

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

Copy and paste ABAP code example for SVMCRT_LGV_LOGREADER 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_offset  TYPE INT4, "   0
lv_if_result  TYPE SVMCRT_LGV_RECORDTAB, "   
lv_thread_name  TYPE SVMCRT_LGV_THREAD, "   
lv_logcontr_name  TYPE SVMCRT_LGV_LOGCONTRNAME, "   
lv_from_date  TYPE D, "   
lv_from_time  TYPE T, "   
lv_until_date  TYPE D, "   
lv_until_time  TYPE T, "   
lv_size  TYPE INT4, "   
lv_max_count  TYPE INT4, "   100
lv_log_names  TYPE STRINGTAB, "   
lv_last_index  TYPE INT4, "   
lv_exclude_names  TYPE STRINGTAB, "   
lv_update_selection  TYPE XFLAG, "   
lv_min_severity  TYPE SVMCRT_LGV_SEVERITY, "   0
lv_user_name  TYPE SYUNAME, "   
lv_client_id  TYPE SYMANDT, "   
lv_session_id  TYPE SVMCRT_LGV_SESSION. "   

  CALL FUNCTION 'SVMCRT_LGV_LOGREADER'  "
    EXPORTING
         OFFSET = lv_offset
         THREAD_NAME = lv_thread_name
         LOGCONTR_NAME = lv_logcontr_name
         FROM_DATE = lv_from_date
         FROM_TIME = lv_from_time
         UNTIL_DATE = lv_until_date
         UNTIL_TIME = lv_until_time
         MAX_COUNT = lv_max_count
         LOG_NAMES = lv_log_names
         EXCLUDE_NAMES = lv_exclude_names
         UPDATE_SELECTION = lv_update_selection
         MIN_SEVERITY = lv_min_severity
         USER_NAME = lv_user_name
         CLIENT_ID = lv_client_id
         SESSION_ID = lv_session_id
    IMPORTING
         IF_RESULT = lv_if_result
         SIZE = lv_size
         LAST_INDEX = lv_last_index
. " SVMCRT_LGV_LOGREADER




ABAP code using 7.40 inline data declarations to call FM SVMCRT_LGV_LOGREADER

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_max_count) = 100.
 
 
 
 
 
 
 
 
 


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!