test your SQL statement before using it in your ABAP program

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.

local SAP WebIDE setup and configuration

Starting with new SAP development environment SAP Cloud WebIDE has a few drawbacks. First of all network performance problems can dramatically effect your development. Besides your company might not allow you using Cloud WebIDE because of securtiy reasons. For that purposes i highly recommend you to use The Personal Edition of WebIDE. You can download it from https://tools.hana.ondemand.com/#sapui5 . It has trial and productive usage versions. Untill productive usage we are using the Trial one with almost any problem. The only problem was in setup configuration phase. After downloading the files and extract files under C:\SAPWebIDE you also need to configure your destinations under C:\SAPWebIDE\eclipse\config_master\service.destinations\destinations folder.

change code inspector error types in other words message priorities

Code inspector provides a set of configuration which are customizable. You can either include or exclude any standard or custom check into your variant. By doing this you can prevent certaion types of checks in your ABAP programs. The only place to customize your variant is SCI. However there is a hidden customization where you can also set priority for the standard and custom checks. Go through the following steps to switch code inspector check priorities so that you could for example prevent a transport request to be released because it is consisted of an object with an error statused check.