Introduction

Based on the explanations in the previous document Starting with ADT SDK is easy – Pt.1 I want to share how you can easily extend your ABAP in Eclipse environment with a simple transaction call. This could be useful just to put a shortcut (otherwise you have to use Alt + F8 and hope that your object is displayed in the history) or even custom transactions (like in Z- or Y-namespace).

How to start?

Just start as mentioned in the document above. Create a new “Eclipse Plug-In Project” and use the “Hello World Command” template. After generating the artefacts we have to take a closer look into the plugin.xml file. You can use your project generated during Pt. 1 as well.

Plugin.xml

At first we have to reference some predelivered ADT packages. Proceed to the “Dependencies” tab and add the following packages:

/wp-content/uploads/2014/06/dependencies_001_472985.png

We have to declare the usage of this packages because we need some classes later within our implementation.

Implement the transaction call

As the handler class has been generated we just have to implement the execute() method (you can click on the screenshot in order to enlarge it). Please consider that the imported Java packages are only available if the dependencies in plugin.xml were maintained correctly. Have a look at the comments in the coding and just try it out 🙂

/wp-content/uploads/2014/06/implementation_001_473033.png
You can also refer the attached coding “implementation_001.txt”.

Result

Finally a new SAP GUI window should be opened within your Eclipse installation with called transaction SE80:

/wp-content/uploads/2014/06/se80_473035.png

Of course you must have access to a running SAP backend system to do this. For pure development purposes no backend is needed.

What’s next?

As next step we will try to implement a “right mouse click” scenario for objects in the project tree and pass the object name to the transaction. This will follow in Pt. 3.

Maybe you’ve got some ideas by yourself – just try it out and perhaps you find the time to write a blog about it 🙂

To report this post you need to login first.

9 Comments

You must be Logged on to comment or reply to a post.

    1. Martin Steinberg Post author

      Hi Christian,

      thanks for your feedback. It’s right, it seems to be the half way – but especially after our hangout concerning the SAPlink plugin yesterday I see a lot of potential using the SDK, and I hope to leverage that step by step. 😎

      Martin

      (0) 
            1. Martin Steinberg Post author

              Hi Luis,

              to help the Web UI Client developers Christian and I planned to integrate it as Christian mentioned above. If you like you can join us, of course 🙂

              At the moment we are having a closer look at the SAPlink plugin for Eclipse (Gregor Wolf is supporting us) because there are some issues to be fixed and it’s a good starting point for working with ADT SDK as well (but quite more complex than the example showed in this blog).

              Afterwards we will have to discuss how a solution for the WebUI could look like. Be sure that we will inform and envolve you on any ongoing activities concerning this topic (by private scn message).

              Martin

              (0) 
  1. Florian Henninger

    Hi Martin.

    this is very cool. I love the unlimited possibilities now with having ADT right now. I need to take some time to rebuild your explained stuff here. Hope I will find some time the next weeks.

    I’m thinking about some quality-functions such as a nicely made informative header and an generated changelog-line…

    ~Florian

    (0) 

Leave a Reply