SAP SCI_REMOTE_SQL_STMNTS_ANALYZE Function Module for









SCI_REMOTE_SQL_STMNTS_ANALYZE is a standard sci remote sql stmnts analyze 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 sci remote sql stmnts analyze FM, simply by entering the name SCI_REMOTE_SQL_STMNTS_ANALYZE into the relevant SAP transaction such as SE37 or SE38.

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



Function SCI_REMOTE_SQL_STMNTS_ANALYZE 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 'SCI_REMOTE_SQL_STMNTS_ANALYZE'"
EXPORTING
* P_DEST = "
* P_TRACE_USER = "
* P_PERSIST = '' "
* P_DELDATE = "
* P_DISPLAY_STAT = '' "
* P_DISPLAY_SQL = '' "
* P_SQL_CHECK = '' "
* P_STAT_PROG_CHECK = '' "
* P_SCI_CHKV_STAT = "
* P_SCI_USER_STAT = "
* P_WITH_RESULT_LIST = '' "
* P_SNAME = "
* P_CALLED_FROM_ST05 = '' "
* P_STMNTS = "
* P_SCI_CHKV_SQL = "
* P_SCI_USER_SQL = "
* P_START_DATE = "
* P_START_TIME = "
* P_END_DATE = "
* P_END_TIME = "

IMPORTING
P_INSP_STAT = "
P_INSP_SQL = "
P_RESULT_STAT = "
P_RESULT_SQL = "
P_PERF_CHKLST = "
P_RESULT_LIST = "

TABLES
* PT_PERF_CHKLSTF = "

EXCEPTIONS
ILLEGAL_INPUT = 1 FUNCTION_NOT_EXISTS = 2 INVALID_VARIANT_SQL = 3 CHECK_ERROR_SQL = 4 ERROR_READING_TRACE = 5 INTERNAL_ERROR = 6 CHECK_ERROR_STAT = 7 INVALID_VARIANT_STAT = 8
.



IMPORTING Parameters details for SCI_REMOTE_SQL_STMNTS_ANALYZE

P_DEST -

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

P_TRACE_USER -

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

P_PERSIST -

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

P_DELDATE -

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

P_DISPLAY_STAT -

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

P_DISPLAY_SQL -

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

P_SQL_CHECK -

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

P_STAT_PROG_CHECK -

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

P_SCI_CHKV_STAT -

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

P_SCI_USER_STAT -

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

P_WITH_RESULT_LIST -

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

P_SNAME -

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

P_CALLED_FROM_ST05 -

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

P_STMNTS -

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

P_SCI_CHKV_SQL -

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

P_SCI_USER_SQL -

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

P_START_DATE -

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

P_START_TIME -

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

P_END_DATE -

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

P_END_TIME -

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

EXPORTING Parameters details for SCI_REMOTE_SQL_STMNTS_ANALYZE

P_INSP_STAT -

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

P_INSP_SQL -

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

P_RESULT_STAT -

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

P_RESULT_SQL -

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

P_PERF_CHKLST -

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

P_RESULT_LIST -

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

TABLES Parameters details for SCI_REMOTE_SQL_STMNTS_ANALYZE

PT_PERF_CHKLSTF -

Data type: SCIT_PERF_CHKLSTF
Optional: Yes
Call by Reference: Yes

EXCEPTIONS details

ILLEGAL_INPUT -

Data type:
Optional: No
Call by Reference: Yes

FUNCTION_NOT_EXISTS -

Data type:
Optional: No
Call by Reference: Yes

INVALID_VARIANT_SQL -

Data type:
Optional: No
Call by Reference: Yes

CHECK_ERROR_SQL -

Data type:
Optional: No
Call by Reference: Yes

ERROR_READING_TRACE -

Data type:
Optional: No
Call by Reference: Yes

INTERNAL_ERROR -

Data type:
Optional: No
Call by Reference: Yes

CHECK_ERROR_STAT -

Data type:
Optional: No
Call by Reference: Yes

INVALID_VARIANT_STAT -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for SCI_REMOTE_SQL_STMNTS_ANALYZE 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_p_dest  TYPE RFCDEST, "   
lv_p_insp_stat  TYPE SCIINS_INF, "   
lv_illegal_input  TYPE SCIINS_INF, "   
lt_pt_perf_chklstf  TYPE STANDARD TABLE OF SCIT_PERF_CHKLSTF, "   
lv_p_trace_user  TYPE SY-UNAME, "   
lv_p_persist  TYPE FLAG, "   ''
lv_p_deldate  TYPE SY-DATUM, "   
lv_p_display_stat  TYPE FLAG, "   ''
lv_p_display_sql  TYPE FLAG, "   ''
lv_p_sql_check  TYPE FLAG, "   ''
lv_p_stat_prog_check  TYPE FLAG, "   ''
lv_p_sci_chkv_stat  TYPE SCI_CHKV, "   
lv_p_sci_user_stat  TYPE SCI_USER, "   
lv_p_with_result_list  TYPE FLAG, "   ''
lv_p_sname  TYPE MSNAME2, "   
lv_p_insp_sql  TYPE SCIINS_INF, "   
lv_function_not_exists  TYPE SCIINS_INF, "   
lv_p_called_from_st05  TYPE FLAG, "   ''
lv_p_stmnts  TYPE SCIT_SQL_ANALYZE, "   
lv_p_result_stat  TYPE SCIREST_AGGR1, "   
lv_invalid_variant_sql  TYPE SCIREST_AGGR1, "   
lv_p_result_sql  TYPE SCIREST_AGGR, "   
lv_p_sci_chkv_sql  TYPE SCI_CHKV, "   
lv_check_error_sql  TYPE SCI_CHKV, "   
lv_p_perf_chklst  TYPE SCI_PERF_CHKLST, "   
lv_p_sci_user_sql  TYPE SCI_USER, "   
lv_error_reading_trace  TYPE SCI_USER, "   
lv_p_start_date  TYPE SYSTDATLO, "   
lv_p_result_list  TYPE SCIT_ALVLISTN, "   
lv_internal_error  TYPE SCIT_ALVLISTN, "   
lv_p_start_time  TYPE SYSTTIMLO, "   
lv_check_error_stat  TYPE SYSTTIMLO, "   
lv_p_end_date  TYPE SYSTDATLO, "   
lv_invalid_variant_stat  TYPE SYSTDATLO, "   
lv_p_end_time  TYPE SYSTTIMLO. "   

  CALL FUNCTION 'SCI_REMOTE_SQL_STMNTS_ANALYZE'  "
    EXPORTING
         P_DEST = lv_p_dest
         P_TRACE_USER = lv_p_trace_user
         P_PERSIST = lv_p_persist
         P_DELDATE = lv_p_deldate
         P_DISPLAY_STAT = lv_p_display_stat
         P_DISPLAY_SQL = lv_p_display_sql
         P_SQL_CHECK = lv_p_sql_check
         P_STAT_PROG_CHECK = lv_p_stat_prog_check
         P_SCI_CHKV_STAT = lv_p_sci_chkv_stat
         P_SCI_USER_STAT = lv_p_sci_user_stat
         P_WITH_RESULT_LIST = lv_p_with_result_list
         P_SNAME = lv_p_sname
         P_CALLED_FROM_ST05 = lv_p_called_from_st05
         P_STMNTS = lv_p_stmnts
         P_SCI_CHKV_SQL = lv_p_sci_chkv_sql
         P_SCI_USER_SQL = lv_p_sci_user_sql
         P_START_DATE = lv_p_start_date
         P_START_TIME = lv_p_start_time
         P_END_DATE = lv_p_end_date
         P_END_TIME = lv_p_end_time
    IMPORTING
         P_INSP_STAT = lv_p_insp_stat
         P_INSP_SQL = lv_p_insp_sql
         P_RESULT_STAT = lv_p_result_stat
         P_RESULT_SQL = lv_p_result_sql
         P_PERF_CHKLST = lv_p_perf_chklst
         P_RESULT_LIST = lv_p_result_list
    TABLES
         PT_PERF_CHKLSTF = lt_pt_perf_chklstf
    EXCEPTIONS
        ILLEGAL_INPUT = 1
        FUNCTION_NOT_EXISTS = 2
        INVALID_VARIANT_SQL = 3
        CHECK_ERROR_SQL = 4
        ERROR_READING_TRACE = 5
        INTERNAL_ERROR = 6
        CHECK_ERROR_STAT = 7
        INVALID_VARIANT_STAT = 8
. " SCI_REMOTE_SQL_STMNTS_ANALYZE




ABAP code using 7.40 inline data declarations to call FM SCI_REMOTE_SQL_STMNTS_ANALYZE

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 UNAME FROM SY INTO @DATA(ld_p_trace_user).
 
DATA(ld_p_persist) = ''.
 
"SELECT single DATUM FROM SY INTO @DATA(ld_p_deldate).
 
DATA(ld_p_display_stat) = ''.
 
DATA(ld_p_display_sql) = ''.
 
DATA(ld_p_sql_check) = ''.
 
DATA(ld_p_stat_prog_check) = ''.
 
 
 
DATA(ld_p_with_result_list) = ''.
 
 
 
 
DATA(ld_p_called_from_st05) = ''.
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 


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!