ABAP Keyword Documentation →  ABAP − Reference →  Processing External Data →  ABAP Database Access →  ABAP SQL →  ABAP SQL - Overview →  ABAP SQL - Release-Dependent Syntax Check Modes 

Strict Mode in Release 7.51

• Conditions for the Strict Mode

• Rules for the Strict Mode

Other versions: 7.31 | 7.40 | 7.54

Conditions for the Strict Mode

The strict mode of the syntax check in Release 7.51 applies to all ABAP SQL statements that use one of the following attributes introduced in Release 7.51:

• Statement WITH

• Cross join in the SELECT statement

• Use of new SQL functions:

• Numeric function DIVISION

• String functions LEFT, CONCAT_WITH_SPACE, INSTR, and RPAD, as well as LOWER and UPPER.

• Date functions DATS_IS_VALID, DATS_DAYS_BETWEEN, DATS_ADD_DAYS and DATS_ADD_MONTHS

• Use of the addition AS dtype in the aggregate function AVG

• Use of the addition EXTENDED RESULT in the INTO clause

• Use of OFFSET after the addition UP TO of the statement SELECT

• Use of the additions ORDER BY, OFFSET, and UP TO in the statement DELETE

• Inline declaration for dbcur in the statement OPEN CURSOR

Rules for the Strict Mode

The strict mode in Release 7.51 covers all rules of the strict mode in Release 7.50, plus the following rules:

• Only the data types b, s, i, and int8 are allowed for the operand n after the additions UP TO and PACKAGE SIZE of the statement SELECT A literal or a constant cannot have the value 0 here.

• In the statement OPEN CURSOR too, the additions grouped under additional_options must be specified at the end of the SELECT statement.

• The syntax of one of the database hints specified after %_HINTS is checked (if possible).

• If it is not possible to make a lossless read on a host constant, a syntax error occurs.