What does it do? Untyped literals in ABAP SQL correspond to general ABAP literals and the same rules apply. In AB-SQL , untyped literals can be specified in read positions of AB-SQL statements where host variables are possible. The following applies, depending on the operand position:
If an untyped literal is specified in an operand position in which it is handled like an elementary SQL expression, the corresponding rules apply and the untyped literal is mapped to a dictionary type and evaluated accordingly on the database.
If an untyped literal is specified in an operand position in which it is not handled like an SQL expression, it is handled like a host variable. If necessary, an ABAP specific type conversion takes place and a lossless assignment to the data type required in the operand position must be possible. Non-matching untyped literals produce, BEGIN_SECTION VERSION 5 OUT depending on the syntax check mode, syntax warnings or END_SECTION VERSION 5 OUT syntax errors.
Latest notes:
While general ABAP supports untyped literals only, ABAP SQL also supports typed literals which should be preferred.
In some operand positions in which untyped literals are allowed and host expressions are forbidden, an untyped literal can be specified with the syntax @( literal ) and is handled as an untyped literal and not as an expression. NON_V5_HINTS ABAP_HINT_END
ABAP_EXAMPLE_VX5 Reading of data from the DDIC database table SPFLI using AB-SQL . The read rows are specified as untyped text literals in the WHERE condition. After UP TO, an untyped numeric literal specifies the maximum number of rows to read. ABEXA 00807 ABAP_EXAMPLE_END
