ABAP is also for me not the only one language. And you would do the same in all of them - imagine one single common thing some of your programs should do with a table.
E.g. running the conversion exits on all the fields with some exceptions. I believe you would create some kind of encapsulation for this function (either a FM or a method). When creating you know more programs will need this and all of them have a different table-structure. What will you do? You could e.g. pass the field-catalog to the function that does the job, but still your parameter have to be generic. Wouldn't it be nicer if I could just pass anything there and leave all the process to the logic inside? RTTS / RTTI is a very nice approach for this.
Don't take this wrong - but not accepting dynamics is the approach of the people that started working with ABAP long time back.
One more note - the user will be happy always once the system works fine. It can be working fine even if it was writen in Whitespace. But we do not want to be working that way, do we Image may be NSFW.
Clik here to view.
.
