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.
I admit that the header of this post is complicated enough. I will try to simplify it. Recently one of my friend was getting an error message from an external webservice because he was calling the service but some of…
I know the post header does not make enough sense. However this is an expalantion for the solution of a problem that i come across recently, and i believe it will be very useful for such cases.
As far as i have discovered new commands coming with ABAP 7.4 (COND,SWITCH), i realized that they have some superiority over the old predecessors considering code repetition. Lately i have started to make use of COND command very often. The reason for that is SWITCH has same usage with CASE but has less code. Likewise COND provides declaring free conditions and accordingly assign a field value therefore has less code than IF. Below i have written very simple sample code for you to easily compare each of these commands.
In consume REST oauth service from ABAP – get access token in order to call main webservice – part 1 post, i had tried to explain how a key required by REST services can be obtained. In this step i will make use of this generated key so that i can call my real service. Here all i have to do is creating the body part of my JSON data, the rest is again using right methods of cl_http_client. After consuming service the response from the server will be processed and siutable message will be returned.
I have heard many things about REST, oauth, JSON and all these things. Finally i have to meet these terms this week. There was a third party tool which is provding a REST service and i have to consume it with ABAP. Interestingly i learnt that there is not any Enterprise Service infrastructure in order to call REST services. Therefore i had to use HTTP service objects within ABAP program library. cl_http_client is the main class for REST services. Calling a REST service is consist of two parts. In this post i will focust on the first part. It is getting access token which is required to successfully make main webservice and this is the second poart of REST service.