There was a standard process in our system which sends a text as the body of a mail, after a certain operation is completed. For this program a change had been done so that the program could send a custom SMARTFORM as a PDF attachment beside to the text body. This change had been done as a repair in a program. So far so good, everything was working fine.
Let’s start with the long text of this runtime error caused by usage of a non-transparent table.
The current ABAP program attempted to execute an Open SQL statement containing a dynamic entry. The parser returned the following error: “If “CONNECTION” addition is used, the the table “CDPOS” must be transparent.
CDS view approach is maybe the safest approach while connecting to a secondary HANA database. If there is a safer approach it would be using directly OpenSQL. However there are cases where OpenSQL is not enough to cover all the states. So CDS technique becomes the only option to connect secondary HANA.
Another Top-Down approach of HANA usage is EXEC SQL method which you write SQL commands between EXEC SQL/ENDEXEC lines. Difficult side of this approach is you will be dependent to static special SQL statements which does not follow ABAP syntax.…
“ADBC is an API for the Native SQL interface of the AS ABAP that is based on ABAP Objects. The ADBC methods can be used to pass Native SQL statements to the database interface”. It was a definition from SAP Help. It is obvious that ADBC can be used ABAP on HANA systems. I think there are very few advantages of ADBC method but on the other hand many disadvantages that demotivates to use.
For a long time i thought that there is a missing SQL console feature integrated in SAP functionality. With ABAP 7.4 and usage of Eclipse as IDE, SAP succeded to fulfill this gap with new Eclipse SQL Console. Actually before this feature, there was a similar feature that we could use for the same aim. Therefore i wanted to write down both options so that you can pick one of the suitable one for you.