Skip to content

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.40, SP05

Other versions: 7.31 | 7.40 | 7.54

Conditions for the Strict Mode

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

  • Listings of operands as comma-separated lists
  • SQL expressions except for columns specified individually or aggregate expressions specified individually.
  • ON conditions without a column from a database table or view specified on the right side as an operand.
  • Multiple consecutive joins where a join expression (and not a database table or view) is on the right side of a join expression.
  • Fields from the right side specified in LEFT OUTER JOIN or from the left side in RIGHT OUTER JOIN in the WHERE condition.

Rules for the Strict Mode

The strict mode of the syntax in Release 7.40, SP05 checks whether the following additional rules are followed:

  • Any errors that would normally be displayed as syntax warnings are reported as syntax errors.
  • All lists of operands must be comma-separated lists. This affects the following:
  • In the statement UPDATE, change expressions specified after SET.
  • If an explicit comma-separated list is specified without the addition DISTINCT in the SELECT list, all columns of the results set defined here must exist as identically named components in a structure or table specified after INTO CORRESPONDING FIELDS.
  • The addition CLIENT SPECIFIED can only be used for client-specific database tables or views.
  • If the addition FOR ALL ENTRIES is used, no database fields of the built-in types STRING, RAWSTRING, and GEOM_EWKB plus LCHR and LRAW can occur in the SELECT list.
  • If database views with the same number of key fields and view fields are accessed in a dynamic FROM clause combined with the addition ORDER BY PRIMARY KEY, the exception CX_SY_DYNAMIC_OSQL_SEMANTICS is raised.

Comma-separated lists of operands and the escape character @ can only be used in programs in which the program attribute fixed point arithmetic is activated.