DX_SYNTAX_CHECK_SXDA SAP Function module

DX_SYNTAX_CHECK_SXDA is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name DX_SYNTAX_CHECK_SXDA into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: SXDA
Released Date: Not Released
Processing type: Normal fucntion module

Pattern for FM DX_SYNTAX_CHECK_SXDA - DX SYNTAX CHECK SXDA

CALL FUNCTION 'DX_SYNTAX_CHECK_SXDA' "
  EXPORTING
    dxobj =                     " sxda1-dxobj
    subdx =                     " sxda1-subdx
    loadfile =                  " dxfile-filename  Complete file name
*   max_no_errors = '0'         " dxattrib-maxerror  Maximum Number of Errors Before Program Terminates
  TABLES
    syntax_errors =             " edids
  EXCEPTIONS
    MAX_NO_ERRORS_REACHED = 1   "               Maximum Number of Tolerable Errors Reached
    ERROR_HANDLING_LOADFILE = 2  "
    DXOBJ_READ_FAILED = 3       "
    NO_AUTHORITY = 4            "
    .  "  DX_SYNTAX_CHECK_SXDA

ABAP code example for Function Module DX_SYNTAX_CHECK_SXDA

The ABAP code below is a full code listing to execute function module DX_SYNTAX_CHECK_SXDA including all data declarations. The code uses 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 original method of declaring data variables up front. 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).

DATA:
it_syntax_errors  
 
 TYPE STANDARD TABLE OF EDIDS,"TABLES PARAM
wa_syntax_errors
 
 LIKE LINE OF it_syntax_errors
.

 

SELECT single DXOBJ 
  FROM SXDA1 
  INTO @DATA(ld_dxobj).

 

SELECT single SUBDX 
  FROM SXDA1 
  INTO @DATA(ld_subdx).

 

SELECT single FILENAME 
  FROM DXFILE 
  INTO @DATA(ld_loadfile).

 

SELECT single MAXERROR 
  FROM DXATTRIB 
  INTO @DATA(ld_max_no_errors).

 

"populate fields of struture and append to itab
append wa_syntax_errors to it_syntax_errors.
.

CALL FUNCTION 'DX_SYNTAX_CHECK_SXDA'
  EXPORTING
    dxobj =                      ld_dxobj
    subdx =                      ld_subdx
    loadfile =                   ld_loadfile
*   max_no_errors =              ld_max_no_errors
  TABLES
    syntax_errors =              it_syntax_errors
  EXCEPTIONS
    MAX_NO_ERRORS_REACHED =      1
    ERROR_HANDLING_LOADFILE =    2
    DXOBJ_READ_FAILED =          3
    NO_AUTHORITY =               4
    .  "  DX_SYNTAX_CHECK_SXDA

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 2. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 3. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 4. "Exception
  "Add code for exception here
ENDIF.

ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:

ld_dxobj
 
 TYPE SXDA1-DXOBJ ,
it_syntax_errors
 
 TYPE STANDARD TABLE OF EDIDS ,
wa_syntax_errors
 
 LIKE LINE OF it_syntax_errors,
ld_subdx
 
 TYPE SXDA1-SUBDX ,
ld_loadfile
 
 TYPE DXFILE-FILENAME ,
ld_max_no_errors
 
 TYPE DXATTRIB-MAXERROR .



SELECT single DXOBJ 
  FROM SXDA1 
  INTO ld_dxobj.
 

"populate fields of struture and append to itab
append wa_syntax_errors to it_syntax_errors.

SELECT single SUBDX 
  FROM SXDA1 
  INTO ld_subdx.


SELECT single FILENAME 
  FROM DXFILE 
  INTO ld_loadfile.


SELECT single MAXERROR 
  FROM DXATTRIB 
  INTO ld_max_no_errors.