1 2 3 12 Previous Next

ABAP in Eclipse

178 Posts

In 1999, I started my professional career at a mid-sized German hospital. In 2000, we had succeeded in bringing our at-the-time already ageing patient management and billing system through the Y2K madness that was happening all around without too much effort. Then the news came – although the system was Y2K-proof, it wasn’t built to handle multiple currencies, and the vendor had decided to discontinue the product. Looking for a replacement, we finally ended up using the combination of FI, CO, IS-H for patient management, PM for our building services and maintenance department. A bit later, MM and especially i.s.h.med for the clinical aspects were added as well. At the time, one of my main tasks was to implement various forms and additional reports. I already knew several programming languages at the time and had some experience with Oracle, Interbase and other RDBMS, so taking a dive into ABAP development was a natural choice. This was back in release 4.6D. Since then, I’ve worked for a few years one of the companies that make i.s.h.med and which is nowadays part of the Siemens AG. During that time, I had the chance to learn a lot about ABAP development both in customer projects and for add-on and product development. Since 2009, I’m with one of Germany’s largest inpatient and rehab healthcare providers. Today, I’m responsible for the development team that extends and enhances i.s.h.med and connects it with surrounding systems – but since the team is small and I can’t resist it anyway, I still write quite a bit of ABAP applications.


I actually knew quite a bit about Eclipse, even in conjunction with ABAP systems, before ABAP in Eclipse emerged in its current form. For my bachelor’s thesis, I designed and explored a modeling solution to generate “stuff” (a common technical term) in the i.s.h.med system. During that project, I learned a lot about Eclipse and its flexibility and extensibility – not only as an IDE, but also as a starting point to develop your own applications. Sadly, the prototype was never developed into a full project. At the time, I used cheat sheets to guide first-time users through my application. Although simpler and a lot less interactive, cheat sheets and the ADT Feature Explorer follow a similar basic principle that has proven to be very valuable to support new users.


Since I’m rather familiar with the “traditional” ABAP development environment, there was no real incentive for me to explore the ADT in its first stages. I use data dictionary objects a lot, and most of our development is still screen-based (dynpros), which are both unsupported. For DDIC objects, that will change, for screens it probably won’t. Combine that with the fact that you were basically cut-off from the existing documentation (descriptions and documentation texts) in the early releases of the ADT, and I think it’s understandable that I decided to concentrate on other issues and give the ADT some time to mature. At this year’s TechEd && d-code in Berlin, I took the opportunity to visit the DEV165 session and familiarize myself with the current state. I’m still not using ADT for my day-to-day development, mostly because nobody else in my team is and we’d lose a lot by splitting up the toolkit right now, especially since a full two-way transfer of the documentation is not yet implemented. However, I will be presenting the ADT during our team meeting tomorrow, including Cristina Jitareanu, Graff Christian and a number of colleagues who unfortunately haven't yet found the time to use all aspects of the SCN. I would also recommend it to Daniel Sonnabend but I know that Daniel actually has had the opportunity to take a look at the ADT earlier than me, due to the fact that we have to support far lower releases.




i am working as abap developer from r/3 release 2.0 on (so about 20 years), as i am working with hana i am using ADT now and i think it's a must for all abap developers (@Rolf Fricker) after doing the realy nicely done beginners tour i continue to Play around:


i created an ALV using ADT and tested the new fiori style design called "Blue Crystal": nice :-)


good to see adt is also working with new sapgui 7.40



i am also impressed how fast it is, so once eclipse is started i can work with same Performance as in SE80

One of the major reasons of why Eclipse was chosen as a foundation for the new ABAP development environment is its extensibility. Almost every introduction to ADT I’ve seen so far stresses the additional value that can be gained by combining plug-ins from multiple sources. I’ve used Eclipse for some time now (starting with 3.2 or 3.3, I don’t exactly remember when), developed my own Eclipse-based tools and while I’m certainly not an expert, I know about the basics of implementing and extending Eclipse plug-ins.


Until now, I have more or less ignored ADT – mostly because our ABAP environments were too outdated to use ADT. This is slowly changing, so I took the opportunity and visited the introductory DEV165 session at this year’s SAP TechEd && d-code in Berlin. Back at home, I wanted to put the claim of extensibility to the test. My aim was to create a plug-in that takes an existing interface and generates a pre-fabricated implementation class according to some rules. The details are not of importance here – I’ll probably write about it later when there is something to be seen.


My idea was to extend the Project Explorer view so that you could right-click the interface and start some kind of wizard that creates a class for the interface. Extending the Project Explorer is a frequent task in the Eclipse world, so there are a number of tutorials available. If you want to code along, I’d recommend using this tutorial to get a starting point.


The next step would be to place a restriction on the menu extension so that the context menu entry only appears for interfaces. This is fairly easy, you just need to add a condition to the extension. In this case, I figured that an instanceof condition should do the trick, so I used the Plug-in Spy provided by the PDE to find out more about the interface entries in the Project Explorer (select an interface in the project explorer, then press Alt+Shift+F1).




Among other information, you can see that the current selection (which is what matters most here) is a TreeSelection that contains an AbapRepositoryInterfaceNode. Using this information, it is possible to limit the popup menu entry to Interfaces:




In the command handler, you would usually use the central selection service to find out what objects the command should work on. There’s a basic example in the tutorial I mentioned above; it involves examining the selection and then casting the selected object to a suitable class or interface variable. This is where the trouble really starts…


If you try to look up the class AbapRepositoryInterfaceNode in the ADT SDK documentation, you’ll be out of luck – as the fully qualified class name com.sap.adt.oo.ui.internal.interfaces.projectexplorer.AbapRepositoryInterfaceNode suggests, this is an internal implementation class, and most of the object-specific classes aren’t documented anyway. This is not good – while it is still possible to plough on, it makes things a lot harder for wannabe contributors.


Using some dirty tricks, it is possible to put together an inheritance tree of AbapRepositoryInterfaceNode. However, it doesn’t look too promising:




Using the documented API, you can find out which project the interface belongs to, and that’s about it. Now for the average Eclipse plug-in that would be annoying, but not too uncommon – there are loads of plug-ins with a similar level of (un)documentation. At this point, you would start to dig into the source code to find out about the structure of AbapRepositoryInterfaceNode and its superclasses and interfaces, other classes that use it, perhaps some service implementations, and usually within a reasonable amount of time, you would have gained an understanding of the inner workings. That’s not possible in this case, simply because the source code is not available publicly. We’ll have to continue guessing, which in this case is easy: A TreeNode has a generic means to attach a value to the node. A quick look with the debugger reveals that this is indeed the way the node keeps track of the object it represents:




So, a RepositoryObjectListItem, let’s look that up in the SDK – whoops, internal stuff again. This class implements IRepositoryObject, which is undocumented as well, but at least gives you basic information about the selected interface:




Fine so far, but now you might want to be interested in the contents of the interface. At this point, you would probably use the References in Workspace (Ctrl+Shift+G) function to try and find out where the interface is used and what you might do with it – but again, this only applies to open source projects where you have the source code at your disposal.




At the moment, this looks like the end of the road – if you want to continue your journey, you have to put on a hard hat, break out the heavy machinery and probably violate a few terms of the licensing agreement in the process.


I would have liked to blog about something else today, something a bit closer to an implementation, but that wasn’t to be. A few key takeaways from my point of view:


  1. Extensibility doesn’t come automatically with the platform, it has to be considered in the architecture and implementation of each and every aspect of the product. An Eclipse plug-in can be as segregated and hard to extend as any other commercial application.
  2. Extensibility of other products largely comprises of the ability to examine the existing stuff. This applies not only to Eclipse, but likewise to the SAP NetWeaver platform and the applications built on top of it. Imagine having to implement a BAdI without access to the application around it…
  3. Documentation is no substitute for access to the source code unless it is really comprehensive and well-maintained.
  4. Likewise, access to the source code is no real substitute for documentation – it tells you how things are built, but not why.

If you need to connect to any system, you have to create a Project.


Project can be created based on the type of implementation Eclipse will be used.


In our case, since we are connecting to SAP system , I am going to create an ABAP project.






Specify the connection details of the system.

You can either select the details from SAP Logon pad or you can define them manually. You can enable or disable the SNC connection.


Login to the system with your User ID and Password.





Give a name to project. Since I am connecting to a CRM system, I have given the project name as CRM_<SID>_110


Since we are creating an ABAP project this will open a ABAP perspective. Perspective gives you an option to work in different areas of Eclipse.


Say "Yes"



Now you are ready with your project and connected to the CRM system.


Take a look into the displayed screen and you will notice all the software packages list on left hand side including the $TEMP package.


Click on the $TMP package which will launch SAP screen. In this screen you can enter any transaction you wish to execute.


I am using SE38 here since Eclipse will be mainly used for development activities.


If you just right click on your project , this will open a list of options available for you in Eclipse for your development. Interesting thing if you note, the options are similar to what we have in SE38.



Now, lets create a TEST program and see how it looks in Eclipse and SE38 Editor.




I am creating a new request for this TEST program.



Once you click on Finish, this is how you will see it in SE38 Editor.




Let's add few more lines in Eclipse and see how it looks again. Note the options marked in blue squares which are for Debugging, Executing etc for the program.






There are several other features available in Eclipse which you can explore by going to respective sections.


Help options :


Different Perspectives :








Navigation options :




Options for Running and Debugging the programs.





Options to set your Preferences.


That's it. Now you can start thinking about Eclipse and be ready to start your developments on Eclipse soon.

Welcome to ABAP Development !!!


As we all know that ABAP and SE38 has been a mainstay for SAP's code development and most of the companies run their businesses on SAP solutions written in ABAP. All these years ABAP development and SE38 has continuously evolved into what we see in latest and improved SE38 editor.


1990 - First ABAP Editor came

1999 - ABAP Workbench was introduced

2004 - Syntax coloring and Code compilation added


Since 2009, SAP has begun to move ABAP tools to the open Eclipse platform. And from 2011, switch to Eclipse changes everything.


Eclipse provides a great development experience with the Eclipse Client which is easy to install, use and understand, it can be used as single tool for developing everything (SAP HANA, SAPUI5, Java,....) and it works on major development platforms such as Windows, Linux and Mac, so we can develop everywhere. You can also use it as a central development tool by just connecting to your system from a single place.


So let's explore this new world of ABAP Development through Eclipse.


Welcome to Eclipse !!!


For Eclipse to work, you need either Eclipse Luna or Eclipse Kepler.


So starting point for your Eclipse experience is :





I have demonstrated this installation with Eclipse Luna, so you can get Eclipse Luna software from :






Download the Eclipse Luna R Package Standard 4.4







Select 32-bit or 64-bit depending on the operating system you plan to use for installation. The steps mentioned here are for Windows 64-bit.




Save it on your local desktop somewhere and extract the zip file. This will create a folder called "eclipse"




Eclipse needs a Java Runtime Environment (JRE) installed on your machine. You can download the suitable JRE and install it.









Copy the above "jre7" folder to your "eclipse" directory and rename it to "jre". If you keep the name as "jre7", the installer won't recognize it.



Click on "eclipse.exe" now to start the installation.




Specify the location of workspace which Eclipse will use.




Once installation is finished, you are ready to explore the world of Eclipse.









Ok...now this looks similar to NetWeaver Developer Studio (NWDS) which we use for Java Development. But for doing development using Eclipse we need to install the ABAP Development tools software.


Follow the steps given below :





Give a nice Name to Repository and Location as https://tools.hana.ondemand.com/luna



Now click on "Add..."










This will take some time and will populate the list of available software's for install.


Select ABAP Development Tools for NetWeaver from the list.














Accepted the license agreement and click "Finish"











Say "Yes".


Now Eclipse Luna is installed and it is ready for connection and your development in any system




Please refer my next blog "ABAP Development in Eclipse - Part 2" for further details.

Good news for ABAP Development Tools developers in Eclipse: ABAP Test Cockpit (ATC) is available in Eclipse with ADT 2.31. For those of you, who are not familiar with ABAP Test Cockpit, it is a toolset, which allows you to significantly improve the code quality during development process. With ATC you can detect the quality issues with regard to performance, security, programming conventions by regular executing static and dynamic (ABAP Unit) checks (of course you can reuse your Code Inspector backend check infrastructure). A very good general overview about ATC is given by Christopher Kaestner in the blog ABAP Test Cockpit – an Introduction to SAP’s new ABAP Quality Assurance Tool .


The ATC in Eclipse is tightly integrated with ABAP developer tools so that you can run ATC checks during development from the Project Explorer or editor and adjust the quality findings consequently by stepping to the relevant source code lines in the editor and correcting them one by one. You can also check with ATC your transport requests in the Transport Organizer before releasing them. And last but not least you can keep the eye on the central check results from your Q system and correct the reported quality findings.


The live demonstration (video) of the ABAP Test Cockpit tools in Eclipse is now on ABAP Channel in YouTube:




Let’s take a look at the brand new ATC tools in Eclipse in detail.



Check the quality of your source code


It’s quite simple. You can run ATC for a single object in the editor or select multiple objects or even packages using context menu
'Run As-> ABAP Test Cockpit'.




The tool of choice to analyse the quality issues is the ATC Problems View. It displays the worklist of ATC findings for you as developer to work on. By default the findings are grouped by priority: errors, warnings, information. Clicking on a finding displays its detailed information.The check variant is displayed in the breadcrumb (if required, change the variant in the project properties under ABAP Development).




In the breadcrumb you can filter the findings in the ATC Problems View and in this way restrict the view to the findings you need to focus on for correction. You can concentrate your correction work for example on the findings, belonging to the last check run (‘Last Check Run’ entry), package, transport request, or recheck of result from the central Q system. Every time you run ATC, the breadcrumb gets a new filter entry if required (e.g. if a new package is checked) and the findings will be added to your worklist.




As soon as you correct a finding, it disappears from your worklist after recheck.






There might be also such situations where a correction of the finding is not possible or not appropriate (e.g. the hard-corded text message, which is not relevant for translation). In such situations the ABAP Test Cockpit offers the possibility to create exemptions for the affected source code parts so that the findings will be hidden from the results. But you can still display them by using the display option ‚Include Exempted Findings’.




Create the exemption by right-clicking on the finding. You need to enter your quality expert (use content assist Ctrl + Space), reason for exemption and justification. As soon as your quality expert approves it, the finding will be marked accordingly in ATC results and will not appear in your worklist.



You can also customize the view on the findings in ATC Problems View and group the findings by priority, objects or checks for your convenience or configure the columns.



Ideally you should run ATC and correct the findings in the ATC Problems View on a regular base during your development process.




Check your transports before release


It is recommended to check regular with ATC your transport requests before release to catch erroneous situations and avoid transporting the source code with quality problems into quality and production systems. This can be done in the Transport Organizer View in Eclipse. There you can choose your transport request and run ATC using context menu ‘Run As->ABAP Test Cockpit’.




After execution of ATC checks you will be redirected to the ATC Problems View, where you can focus on the findings, reported for this transport request and get rid of all of them one by one (btw. the new filter entry for the selected transport request will be added to the breadcrumb).



Access ATC results from the central Q system


After your quality expert runs mass (regression) quality checks with the ATC, the results of these checks will be published to the development systems as the current, active ATC result. You as developer can use this central result to eliminate quality problems. You can access the ATC results from the central Q system in the ATC Result Browser (menu 'Window ->Show view->Other...->ATC Result Browser'). You can select the active ATC result on the left and display the findings of the result on the right.




You can also select the active check run and press 'Show Details' button to display its details.




You will get the same information as in the ATC Problems View. Of course you can customize the view by configuring the view columns or group the findings as in the ATC Problems View. Before you start to correct findings execute recheck to make sure they still are relevant.You can rerun ATC checks and consequently correct the remaining findings belonging to the check run result in the ATC Problems View (btw. the new filter entry for the result will be added to the breadcrumb) .


That’s it. Just try out the new ABAP Test Cockpit tools in Eclipse to increase the quality of your source code during development.


For quick and easy try copy & paste this ATC_EXAMPLE report into your system and run ATC for it.




parameters p_selall
abap_bool default 'X'.


class lcl_atc_example definition.


public section.

    methods run.




class lcl_atc_example implementation.


method run.


                lt_spfli    type spfli,

                lv_flight   type sflight.



" ATC ERROR:           Incompatible parameter in the function call

"                      lt_spfli(type SPFLI) with the function signature

"                      parameter (type SPFLI_TAB)

" PROPOSED CORRECTION: replace in the DATA section TYPE spfli with spfli_tab.


if ( p_selall = abap_true ).

   call function 'READ_SPFLI_INTO_TABLE'


      id = 'AA'


      itab = lt_spfli.



" ATC ERROR:           Strings without text elements are not translated

" PROPOSED CORRECTION: Create text element using Quick Fix Ctrl + 1


message 'Display flight information' type 'I'.


" ATC ERROR:           Performance check SELECT accesses the non-buffered

"                      table SFLIGHT with WHERE condition,

"                      which doesn’t contain any key fields of the table.


"                      WHERE carrid = 'AA' AND seatsmax = 10.


select * from sflight into lv_flight where seatsmax = 10.








data example type ref to lcl_atc_example.


create object example.

     example->run( ).

Hi!!! I’m Hector (from Buenos Aires - Argentina). Since 1988 I work in ERP implementation (in different platforms S/36, AS/400, and PC Servers)

My first version Eclipse was Europa for Java Deployment.

I completed my certification in “ABAP Workbench” in July, 2000 (Release 4.0).


Now, I use Luna (4.4) version.

I fill comfortable using Eclipse + ABAP + Database Development.

I can work with my ABAP programs and use Database Development instance to dive into the data (without MANDT restriction).

Make a file.SQL, click the right button of the mouse and choose “Execute SQL File”.

If use Tcode SE16 only can see one MANDT records.

A simple example

ABAP Database Development.png   

My favorite features & Other functionality

Suggest keywords + Also suggest non-keywords.

Explain in http://scn.sap.com/community/abap/eclipse/blog/2014/03/28/abap-development-tools-version-224-available-now

Posted by @Thomas Fiedler


Finally, the Outline Windows.

This program is in ABAP Examples SoC (Separation of Concems)

It's easy follow each class in this windows.


Thank you for this tools

Hector Palo

Following the Become an ABAP in Eclipse Feature Explorer and earn the Explorer Badge Challenge, I took a look at the Feature Explorer...


Some missing Features / Issues I see with AiE:


  • Actually working Offline.
    Eclipse is an offline tool. But I cant save my changes without an online connection... Ther should at least be a "local save" variant.
    Maybe something like "sync down" (syncing a whole package to eclipse) or "sync up" (syncing up to the server). Activation would obviously require a "sync up".
    See e.g. SAPUI5 Team Provider...

  • Feature Split between AiE and SAP GUI
    Now we've got several features working ONLY in AiE (e.g. AMDP, CDS -- although both are "jsut plain files") and others working ONLY in SAP GUI (e.g. BSP. So the developer is kind of forced to use BOTH tools...


Some Answers for the Challenge:


Developing in ABAP: The standard way is SAP GUI. I love the "where used" feature. I hate the double-click-to-navigate feature (douple click is commonly used to select a single word for copy/paste)


Developing in Eclipse: I have a strong background developing in Eclipse (mainly, but not only Java). I love the Ctrl-Click-to-navigate feature (and double-click-tio-select)


Currently, I dont see the point of using Eclipse (apart of new ABAP features that are only available through eclipse), because you cant really work offline.


Use case: sync a few packages, work on a programm offline (be it on a train or from outside the intranet without open VPN connection) Once connected, activate and test/debug.

Finally, I have passed this "challenge"!


Well, you might say "That is not any challenge, it was easy for me...". And I agree, finally it was no such challenge, but took some time and effort time.


Firstly I would like to introduce myself shortly. I work as a SAP Basis administrator and I have really no experience with ABAP programming language. But I used Eclipse during my studies for programming using Java, JavaScript and Tcl (scripting language). I think I will never program in ABAP, but I had an idea to pass this mission, because it might have been helpful to understand ABAP language a little bit. Maybe it will help me in the future to solve some Basis issues connected with applications.


I started my mission I think 2 month ago. Firstly I had to prepare my home computer and install all the environment. I mean SAP NetWeaver with database, SAP GUI, Eclipse and so on. I found a very useful blog How to install SAP NetWeaver Application Server ABAP 7.03 SP03 Trial – Ready for ABAP in Ecplipse (AiE). It served as a manual. I downloaded all the files and started the installation. Of course there were couple of problems and I had not so much time to solve them. So I had the installation in the middle and had to stop for couple of weeks. Then I returned to it, read some information, solved the problem and finished installation successfully. Then of course some problems with Eclipse, but not so hard. Couple of days ago I finally started the beginners tour.

And funny part is coming now. I passed first part and then decided to "clear the mess" in my PC. Unfortunately I did not realized Eclipse is not installed, but just unzipped. And of course I did not moved it anywhere else from my download directory. Yes, I deleted whole Eclipse in one shot! Well, no problem, just do again all the settings...at least it helped me to practice.  Then I finished my beginners tour today early in the morning. Here is the approval Ok, not so important, but I have nothing more...




Final conclusion is, that I found the tour very useful especially for me. It made mi to install SAP on Windows and I am really glad to have it on my home computer. Normally I work on Unix OS and it is interesting for me to see how it works on Windows OS. Of course I also have the newest SAP GUI 7.40. We don't have it even in my job yet. The beginners tour itself shows basics steps, but it is good to know about them, because probably  would not find all of them for a long time. And they are useful and they make the ABAP programming easier.


Thank you for reading and best regards next time


By the way, did you heard about I Care, I Gave, I Inspired. Even if so or not, check my personal challenge on my blog. Maybe you will find it interesting.

I am Anderson Balieiro and I'm from Brazil.




My journey started with SAP as an Functional CRM, however I always liked ABAP programming, and I'm improving very in this year.



I liked the experience with eclipse because this environment (Eclipse) is a very versatile.


I'm a new developer in the plataform Eclipse and this plataform improve my knowledge in geral.


Features described in this tour are new experience to me.



Thanks to you Thomas Fiedler to share this and all of involved with this great product.



Last Friday we had the SAP Code Jam event "ABAP on HANA" here in Munich. It took place in combination with the SAP Inside Track event on Saturday.

At the Code Jam event Thomas Alexander Ritter showed us a small little feature in ABAP in Eclipse tools, which was not known very well.


Restrict search for ABAP development objects to object-type


You can use the "Run ABAP application" (shortcut Alt + F8) or "Open ABAP development object" (shortcut Ctrl + Shift + A) functions for searching purpose.

Maybe you just want to search for a specific type of object, maybe a program, transaction, class, and so on...

If no object-type is specified your result list contains all kind of objects - often the max. result count of 50 items is reached and you possibly may not find the object you're searching for.



But there is a solution for that issue which I did not know.


Just type "type" behind your search term and use Ctrl + space (code completion) and you will receive a list of possible object-types (all ABAP repository object types available):





By starting tipping the list gets closer (Eclipse standard feature) and helps you to find your desired object-type faster. So finally you just have to select the object you had searched for.



Hi All,


I'm an ABAP developer for over 6 years, I started off as a HR ABAPer, then worked in BW, now I write BADI calculations in the BPC space.


I've heard about Eclipse during my varsity days, but never used it, this is my first time using Eclipse and I'm quite impressed.


I think the feature explorer is very helpful to on board new developers, it highlights most used shortcuts to jump start your coding, and in the same process it get you familiar with Eclipse.


My favorite features are ctrl+space, ctrl+o also the feature that list all the parameters for a class or function, it can speed up programming a lot.


Other features I like is that you can open sap transactions inside Eclipse, the looks and feel are like SAP GUI itself.


and I see SAP HANA development and admin console are in Eclipse as well, its good to know that SAP is behind Eclipse.


Can't wait to use Eclipse for my next development.


If you haven't tried Eclipse yet then you are missing out. Go on and give it a try.




I am a 10 years experienced SAP professional with 4 years of experience in ABAP and 6 years of experience as a functional consultant in SAP FICO. At the start of my career I was trained in JAVA and we used apache tomcat server and eclipse for all our developments back then. After I completed the training I was asked to learn SAP-ABAP. In the beginning I was a bit reluctant towards it, as I think, everyone is opposed to change. The thought process was; all the learning and hard work I had put in learning JAVA is going to go down the drain. But after spending 1 week in the training I felt right at home and I was totally comfortable with the ABAP editor. Since then I loved ABAP.


Working in Eclipse

As I knew Eclipse from my experiences as JAVA developer some years ago, I was really excited to see how ABAP in Eclipse will look. I knew the former problems with the right versions of the JAVA Plug-Ins and their dependencies, This was always a great trouble in the JAVA Projects. So this offer from SAP with a pre-installed development Environment in the cloud works perfect for me! You need nothing to do, just click and execute and everything works. You did a perfect Job, guys!

I might have to spend some time in getting a local installation of AIE in my laptop rather than using AWS cloud image. But i think with all the help availble on SCN it shouldn’t be a problem.


Eclipse feature explorer:


  1. Right at home - Once you are in the SAP HANA development perspective in eclipse, and open any ABAP object, you will feel that nothing has changed. You can still do a command based navigation, as well as menu based navigation.
  2. One stop place – Eclipse is known as one of the best integrated development environments available to date. Now i can code anything and everything in one place, test it, and deploy, be it, my java developments or ABAP. How cool is that!!
  3. Open SQL – Just got off from one of the openSAP courses about enhancements in open SQL and i am quite excited to experiment them on my own. Here is the link to the course.
  4. Debugger – I used the new debugger in eclipse and really liked the new capabilities in there like code editing while debugging. Now i can debug find out the issue and then align the code right then and there. Of course for the new code changes to take effect i have to activate it. I could not find some features like “Go to statement” and “memory analysis covering SAP and ABAP memory” in the new ABAP debugger in eclipse. May be i need to explore a bit more on it.
  5. Web Dynpro Developments – I need to say that this area needs some work. The user interface for all WD-ABAP developments in se80 is much much better than what we have in eclipse. Like if you need to create a node in the context, you have to explicitly click on the node and then rename it, as compared to se80 where the system intuitively asks for a node name. Same applies to the attributes. But i guess, the road forward is Fiori, so now would have to focus on that.
  6. Local editing – The inherent feature of eclipse is code check-in and check-out for all developments. My first thought when i came to know about ABAP in eclipse was yooohoooooo, now we can code locally while having lunch or while travelling back home, i and then sync back the code. But i must agree that i was a bit disappointed here.

Spread the word:

It is a must try for all ABAP developers. If you not tried it yet, please get a trial version on cloud or get a local installation to get your hand dirty. Here are some helpful links.


Getting development  System: http://scn.sap.com/docs/DOC-56314

Development Centre: http://scn.sap.com/community/developer-center

Getting Started: http://scn.sap.com/docs/DOC-31815

Good Blog: http://scn.sap.com/community/abap/eclipse/blog/2012/08/25/lets-see-what-this-aie-stuff-is-capable-of


With the new code-to-data paradigm approach together with the enhancements done in open SQL, the programming would just get more exciting.

I nominate Liew HanYean to share his experience in AIE.

I am Pavithra Jayasinghe from Sri Lanka, island in Indian Ocean. 

My journey started with SAP as an ABAP developer since 2013 ( new to ABAP and SAP ). Although time period is too short with ABAP

I like this experience so much...


Actually I don't know about Eclipse before  took this ABAP in Eclipse Explorer challenge because i'm new to ABAP.

I'm a new developer so the feature explorer is so interesting and helpful for me to improve my knowledge about Eclipse.


Features of this tour are new experience to me. I think new developers like me can get lot of knowledge from this tour and also by referring

documents from SCN and many more ways..

Thank u Thomas Fiedler to add this and all of who were involved with this great product ...






The series of SAP CodeJams on ABAP in Eclipse continues: One event will take place in Düsseldorf, Germany on October 24th, another event will take place in Oldenburg, Germany on November 28th.

What can you expect?


Both CodeJam events focus on the Eclipse-based ABAP tools and how they increase your developer productivity.

Since these are SAP CodeJams you can be sure that they will be highly interactive. You will have plenty of time to chat about ABAP in Eclipse and get hands-on experience.

How can you participate?


Just register yourself for one of the events:

The event is free, but space is limited.


Sign up, now! We are looking forward to see you there!



Filter Blog

By author:
By date:
By tag: