With the new code constructs in ABAP 7.2 and ABAP 7.4 we have the ability to create ABAP code with fewer statements for the same functionality, without compromising readability of the code. METHOD CHAINING can make our code shorter, easier to read, and easier to maintain. INLINE DECLARATIONS can help us avoid TYPE MISMATCH errors. And using a CONSTRUCTOR OPERATOR can save us time by eliminating lines of code while increasing the readability of our code.
HANA
With the new string options like String Templates, Chaining of strings, and embedded expression string functions, we have the ability to create ABAP code with fewer statements for the same functionality, without compromising readability of the code. If you’re working on a ABAP 7.02 – 7.04 based system, I would start using new ABAP coding because they will improve your speed of development and make your programs better maintainable.
As time has gone by, more and more commands and constructs have been added to the ABAP language. While many changes came as a result of the introduction of SAP NetWeaver 7.02, that is nothing compared to the deluge of change that came with version 7.4. Inline ABAP DATA declarations are a new concept introduced in release 7.4 which allows you to declare your internal table variables or work areas within the code that uses them. This is done simply by adding the DATA(wa_data) or @DATA(it_data) statements.
As time has gone by, more and more commands and constructs have been added to the ABAP language. While nothing has been taken away, this is to ensure backward compatibility, the rate of change seems to be accelerating. While many changes came as a result of the introduction of SAP NetWeaver 7.02, that is nothing compared to the deluge of change that came with version 7.4.