Hello Venkat,
it depends on your definition of a "good ABAPer".
In my opinion there are 2 types of ABAPer:
1) The "functional" ABAPer
These guys can extend, add, maintain and develop code/functions combined with a huge module know-how for the business needs, but they use a database just as a data store without knowing the "power" and "possibilities" of it.
2) The "technical" ABAPer
These guys can extend, add, maintain and develop code/functions with less module know-how. So the functional development would take much more time than by a "functional" one. The written code is high-performance and is designed to handle the amount data smoothly regarding to performance, memory usage, etc.
In my ABAP times (round about 9 years ago .. oh man i am getting old), i was one of the "functional ABAPer" and used the database just as a data store.
Today i think you should have one "functional" ABAPer and one experienced dba with ABAP (and DBSL) know-how in your team to get the best result. It is nearly impossible to be up-to-date on oracle database level for a ABAPer, because it changes so fast (optimizer behavior, new features, etc.).
I listen to discussions of ABAPers who think they can tune SQL code with their "old database" know-how. (a classic one is still the order of tables in a sql statement to get a "good" execution plan - if these guys would know that the RULE based optimizer isn't in the game anymore)
Regards
Stefan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.