Delete adjacent duplicates comparing all fields. S...
Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
If no explicit sort key is entered using the addition BY, the internal table itab is sorted by the primary table key.
It is best to specify an explicit sort key behind BY, if possible. An implicit sort behind the primary table key (which can itself, in standard tables, be defined implicitly as a standard key) makes a program difficult to understand and possibly unpredictable.
Documentation of primary table key:
either a self-defined key or the standard key
Documentation of standard key:
... whose key fields (if the row type is structured) are all table fields with character-like data types and byte-like data types.
If you use DELETE ADJACENT DUPLICATES FROM itab COMPARING ALL FIELDS, it can be preceded with SORT and the pseudo component table_line equivalent to ALL FIELDS (I can't find it in the documentation):
If no explicit sort key is entered using the addition BY, the internal table itab is sorted by the primary table key.
It is best to specify an explicit sort key behind BY, if possible. An implicit sort behind the primary table key (which can itself, in standard tables, be defined implicitly as a standard key) makes a program difficult to understand and possibly unpredictable.
Documentation of primary table key:
either a self-defined key or the standard key
Documentation of standard key:
... whose key fields (if the row type is structured) are all table fields with character-like data types and byte-like data types.
If you use DELETE ADJACENT DUPLICATES FROM itab COMPARING ALL FIELDS, it can be preceded with SORT and the pseudo component table_line equivalent to ALL FIELDS (I can't find it in the documentation):
Bluesky
