SAP TOKENIZATION - Obsolete

Get Example source ABAP code based on a different SAP table
  SAP Help

Obsolete Statement Structuring
The following syntax forms are obsolete. They are forbidden within ABAP Objects and produce syntax check warnings outside of classes:

Outside of classes, separators (blanks, commas, colons periods, or the end of a line) after literals or offset/length specifications can be omitted.

Outside of classes, the operators for offset and length can be omitted in offset/length specifications. A single plus sign directly after a field name, a plus sign that is followed directly by a parenthetical expression, or an empty parenthetical expression after a plus sign, an offset value, or a field name, are interpreted as non-existent.
BEGIN_SECTION SAP_INTERNAL_HINT
A further undocumented obsolete syntax form is possible for functional method calls, calls of built-in functions, arithmetic or logical expressions in parentheses, or in non-strict ABAP SQL. Inside the parentheses, spaces before the closing and sometimes after the opening bracket can be omitted if the last or the first actual parameters are text literals within quotes.
END_SECTION SAP_INTERNAL_HINT
BEGIN_SECTION SAP_INTERNAL_HINT
Another undocumented obsolete syntax form is the fact, that between a token and a string or text literal no blank is needed.
END_SECTION SAP_INTERNAL_HINT