Data from different entities can be joined in an ad-hoc fashion and data can be aggregated for analytical queries. Ĭompared to the ODATA interface, the ODBC interface has the advantage that it allows unrestricted SQL access to all exposed ABAP CDS view entities. Full ABAP SQL semantics apply and even application-server-level buffering can be used as well as ABAP-level access control and read access logging. In this case, authentication and authorization is done using an ABAP user. ABAP-level security concepts are bypassed.Īll those problems go away when you treat the ABAP system itself as a database by accessing the ABAP system directly using ODBC. Database session variables are only set correctly if a view is accessed from the ABAP system. Typecasts might not be performed as expected, for example, NUMC data types might not be correctly padded, or currency data might not be correctly shifted. Names and internal structures in the ABAP database might not be stable because the lifecycle is managed by the ABAP system. Some of the problems are listed in SAP Note 2511210. Direct SQL read access to the underlying SAP HANA database of an ABAP system is not a good choice.
There are situations where you would like to have external SQL read access to CDS objects owned by the ABAP system. Open Database Connectivity (ODBC) is a standard API for accessing databases. In this blog post, we would like to show you how you can access CDS view entities in an ABAP system using SQL via ODBC.
0 kommentar(er)
