SAP SQL_CHECK Function Module for









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

Function Group: SFSG_TEST_VALIDATION
Program Name: SAPLSFSG_TEST_VALIDATION
Main Program:
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function SQL_CHECK 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 'SQL_CHECK'"
EXPORTING
I_NAMEFIRST = "
I_NAMELAST = "
I_MNR = "
I_BIRTHDT = "
I_MODE = "

IMPORTING
E_TESTPARS = "
.



IMPORTING Parameters details for SQL_CHECK

I_NAMEFIRST -

Data type: STRING
Optional: No
Call by Reference: Yes

I_NAMELAST -

Data type: STRING
Optional: No
Call by Reference: Yes

I_MNR -

Data type: STRING
Optional: No
Call by Reference: Yes

I_BIRTHDT -

Data type: STRING
Optional: No
Call by Reference: Yes

I_MODE -

Data type: C
Optional: No
Call by Reference: Yes

EXPORTING Parameters details for SQL_CHECK

E_TESTPARS -

Data type: SFSG_TESTPARS_S
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for SQL_CHECK 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_e_testpars  TYPE SFSG_TESTPARS_S, "   
lv_i_namefirst  TYPE STRING, "   
lv_i_namelast  TYPE STRING, "   
lv_i_mnr  TYPE STRING, "   
lv_i_birthdt  TYPE STRING, "   
lv_i_mode  TYPE C. "   

  CALL FUNCTION 'SQL_CHECK'  "
    EXPORTING
         I_NAMEFIRST = lv_i_namefirst
         I_NAMELAST = lv_i_namelast
         I_MNR = lv_i_mnr
         I_BIRTHDT = lv_i_birthdt
         I_MODE = lv_i_mode
    IMPORTING
         E_TESTPARS = lv_e_testpars
. " SQL_CHECK




ABAP code using 7.40 inline data declarations to call FM SQL_CHECK

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!