SAP /SAPDS/SYNTAX_CHECK Function Module for DataServices: Allow DS generated abap to by checked in dev(!)
/SAPDS/SYNTAX_CHECK is a standard /sapds/syntax check SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for DataServices: Allow DS generated abap to by checked in dev(!) 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 /sapds/syntax check FM, simply by entering the name /SAPDS/SYNTAX_CHECK into the relevant SAP transaction such as SE37 or SE38.
Function Group: /SAPDS/RS_BASIS
Program Name: /SAPDS/SAPLRS_BASIS
Main Program: /SAPDS/SAPLRS_BASIS
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function /SAPDS/SYNTAX_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 '/SAPDS/SYNTAX_CHECK'"DataServices: Allow DS generated abap to by checked in dev(!).
IMPORTING
ERRORMESSAGE = "Message Variable
TABLES
PROGRAM = "ABAP/4 program (RFC SUBMIT)
EXPORTING Parameters details for /SAPDS/SYNTAX_CHECK
ERRORMESSAGE - Message Variable
Data type: SY-MSGV1Optional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for /SAPDS/SYNTAX_CHECK
PROGRAM - ABAP/4 program (RFC SUBMIT)
Data type: /SAPDS/PROGTABOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for /SAPDS/SYNTAX_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: | ||||
| lt_program | TYPE STANDARD TABLE OF /SAPDS/PROGTAB, " | |||
| lv_errormessage | TYPE SY-MSGV1. " |
|   CALL FUNCTION '/SAPDS/SYNTAX_CHECK' "DataServices: Allow DS generated abap to by checked in dev(!) |
| IMPORTING | ||
| ERRORMESSAGE | = lv_errormessage | |
| TABLES | ||
| PROGRAM | = lt_program | |
| . " /SAPDS/SYNTAX_CHECK | ||
ABAP code using 7.40 inline data declarations to call FM /SAPDS/SYNTAX_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.| "SELECT single MSGV1 FROM SY INTO @DATA(ld_errormessage). | ||||
Search for further information about these or an SAP related objects