When several lines must be inserted/updated into an internal table, instead of doing those changes line by line, mass operations should be used because they offer better performance by design.
This rule raises an issue when a single line operation like ``++APPEND++``, ``++CONCATENATE++``, and ``++INSERT++`` is performed on an internal table in a loop.
Not really sure of what to do with this rule in fact.
Here the example are not equivalent in functional terms : compliant copy STRUC into ITAB and non compliant iterate through a table to do a write statement.
\[~ann.campbell.2] Maybe, you can provide some reference where the rule originated ?
=== on 30 Apr 2014, 15:53:32 Nicolas Peru wrote:
Rule originated from \http://www.dsag.de/fileadmin/media/Leitfaeden/Leitfaden_Best_Practice_Guide_eng/files/assets/basic-html/page20.html