Skip to Content
Technical Articles

ABAP Development in VS Code | Setup Guide Video

Outside of ABAP I work almost exclusively in VS Code for all my other projects. It’s such a great tool for development! So when I heard you can now access ADT (ABAP Developer Tools) through it, I was incredibly excited πŸ™‚

 

Everything you need to know to setup up VS Code is outlined in a fantastic blog post by Leon Hassan and because I enjoy learning from YouTube videos I’ve made a short video myself essentially following those same steps.

 

In the video we go through how to easily setup up VS Code to work with your own SAP system. In my case I’m using the SAP ABAP Developer Trial version 7.52 SP04. We will be configuring the SAP system as well as installing the 4 required VS Code extensions. Then we’ll configure the frankly awesome ABAP remote file system extension written by Marcello Urbani which should then allow us to access our development objects.

 

If you run into any technical issues with the ABAP remote file system extension, I recommend you raise it in the extensions GitHub issues page.

 

Your experience may vary depending on the version of your SAP system so if you do run into any issues please leave a comment and I’ll help where I can.

 

Here’s the video link πŸ™‚

 

Thanks for reading!

 

2 Comments
You must be Logged on to comment or reply to a post.
  • Hi Brandon,

    Very happy to see this being possible now πŸ™‚

    However, I do believe that the way you set up your SICF service with your own user causes a massive security issue. If I am not mistaken, this basically skips authentication for anyone trying to access the service. As you are running the system over a network (judging from the URL where you said “whatever that means”). Anyone in your network could use the ADT service with your credentials. Your credentials should always be provided in the client as you actually did.

    Also, SSL/TLS is not in your case enabled. This needs to be done in the SICF service. The port would then probably be 44300 instead of 8000. The parameter you mentioned regards the certificate should be set to true if you trust the system. Normally you would say yes and make sure a valid certificate is installed on both the system and your pc (handled by basis normally).

    And also, in certain cases just taking the URL from the SICF service is a bad idea. It could be that you use a web dispatcher for load balancing or have certain DNS names that end users should use. Better ask your basis team for this data.

    Best regards from a Basis guy πŸ˜‰

    • Hi Fabian Brakowski,

      Thank you very much for this very useful information! You can clearly see I am not a Basis guy and so I very much appreciate the tips πŸ™‚ The system you see there is my own local one which only runs when I need it, which is the reason why the security is a bit crap πŸ˜…

      I now understand it’s a bad idea to setup the ICF node with my own user credentials and so will be stopping that immediately! Also I’m going to try switch the ICF node to SSL and see if I can get the certificates installed because frankly you are right, there is no excuse to not be running over SSL even on a test system!

      I’ll also have a chat to our Basis guy at the office about the web dispatcher πŸ™‚

      Thanks again for the advice!