Are there any technical or usage benefits of work areas over header lines -- e.g. speed, space or maintainability? Perhaps future SAP releases will be removing the option of header lines?
Classic ABAP tables with header lines will remain -- not only since ranges and select-options and function modules use them, but it would also be far too much work to rewrite all SAP and customer programs. In ABAP Objects, however, which is becoming increasingly important, tables with header lines are forbidden, and you must use a work area.
The usage benefits of work areas apply to the maintainability of tables. When you use a table with a header line, t_table could refer to either the table or its header line. This is ambiguous outside of context, and ambiguity is not good for maintainability.
Dig Deeper on SAP ABAP
Related Q&A from Matthew Billingham
An SAP user is trying to run a report in an SAP ALV Grid online and wants to know how to get the data in the report to appear along with the header. Continue Reading
An SAP user needs to transfer customer purchase order spreadsheet data to SAP VA01 to create a new sales order. Continue Reading
An SAP user needs information on how to change the password on several SAP user accounts from a central location. Continue Reading