Application Development Blog Posts
Learn and share on deeper, cross technology development topics such as integration and connectivity, automation, cloud extensibility, developing at scale, and security.
Showing results for 
Search instead for 
Did you mean: 
Product and Topic Expert
Product and Topic Expert

Hi community,

do you know this situation? You just saw a presentation about the really cool new ABAP language features and can't wait until you can use them. Fortunately you have a brand new 7.40 system in your landscape and you write you first modern ABAP report. For sure you are using ABAP in Eclipse and you look very proud on your new piece of code like in this example with a bunch of inline declarations:

Woh, that's really nice. But .........DAMN.  :mad:

You forgot that your product owner told you that you have to deliver your code also for older releases.

[Remark: All the developers in the ABAP in Eclipse team know this situation :wink: ]

So you can't use the new feature because in older releases the code will not run. But how can you do that?

The syntax check does not tell when you are using statements that are not available in older releases.

You first have to downport your code and do the syntax check there. This is horrible !

How cool would be the world if your IDE is doing the following: 


You can do a remote syntax check in your system by using the code inspector and I will tell you now what you have to do:

First you have to define a code inspector variant (or you add the remote check in your existing variant) by using transaction SCI:

In the tree of available checks you find under 'Syntax Check/Generation' an item called 'Syntax Check in Remote System'.

Select this check and press the green/yellow icon because you have to enter additional attributes:

On the popup you have to enter the name of the RFC connection that you want to use for the remote check. Additionally you can enter the name of a transport object set. These are the objects that are transported virtually in the remote system before the check is triggered. Via this object set the dependent objects that you need for the check are defined. The object set is defined via an code inspector object set. In my example I just picked the ABAP package of my report:


That is more or less what you have to. The code inspector variant is ready to go.

Very nice is the integration of this feature with ABAP in Eclipse via the ABAP test cockpit. You can use the variant in your eclipse project to do the remote syntax-check directly from your IDE. Just specify in your project properties the name of the code inspector variant under the ATC settings:


Now you can trigger the check via the eclipse project explorer just by choosing the context menu item RunAs...ABAP Test Cockpit on the object that you want to check.The result will look like the picture above. 

Find more information about the ABAP test cockpit in general in this nice blog from olga.dolinskajaABAP Test Cockpit (ATC) for Developers in Eclipse or watch the video that is linked within that blog.

Have fun with the ABAP test cockpit and the remote syntax-check.

This feature is available on following releases:

7.02 SP14  

7.31 SP09

7.40 SP03

Kind Regards,


Labels in this area