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.
AKB_WHERE_USED_LIST is a function module in SAP repository served for finding where used list of a given object. I had employed it in a custom ABAP program which is reporting the given dictionary tables and the program libraries they are used in.
We take advantage of ABAP Test Cockpit in order to optimize our ABAP programs and other objects. We know that ATC can be done via SE80 with right clicking object and Check->ATC with option menu path. However if we want to control objects under a transport request and we dont want to check each object if there are many objects under the transport request, there are two alternatives for executing an ATC check over a transport request.
Discovering IDA recently i like the new interface of ALV with HANA support, however i faced many issues. Day by day i have overcome this issues and now want to share a few of my experiences. Firstly IDA is so fast that it directly reflects HANA experience. Moreoever it provides paging mechanism which divides database load into small pieces .And finally i can summarize that IDA is very useful when you have a CDS view or database view with restricted number of fields to display. Since HANA is column based you have to decrease the number of columns that you request from HANA server.
Strangely excel upload functions like TEXT_CONVERT_XLS_TO_SAP, ALSM_EXCEL_TO_INTERNAL_TABLE, KCD_EXCEL_OLE_TO_INT_CONVERT are not existing in CRM systems. Hence in order to upload excel files into CRM SAP system i had to use GUI_UPLOAD or CL_GUI_FRONTEND_SERVICES methods.
Yesterday we discovered a very popular problem by chance. After selection screen we were calling a dialog screen and then with ‘BACK’ button we tried to come back to selection screen. However the program goes to an empty list screen without any element. Soon after with an investigation i have found out that selection screen involves a list screen element which is SKIP n command. I guess this command is misused on behalf of SELECTION-SCREEN SKIP n command.
Therefore there is two alternative to solve this issue.