Btw I never use the function builder for anything else than testing RFCs and BAPIs. I only use it to read documentation and as a shortcut helper to the function builder where I can perform tests. I recognise the fact that a lot of ABAP’ers love and cherish the new features, so if you’re a highlighting completion lover, stay clear of Java GUI 🙂 The bapi transactionĪs stated earlier, the BAPI transaction works beautifully. I don’t see this as a loss as the ABAP code completion doesn’t really complete anything for me, and the syntax highlighting almost none existent when compared to Eclipse in which i used to work. When running the Java version of Gui, you won’t be able to use the new ABAP code editor with code-completion and syntax highlighting. Remember to substitute what is between the with something from reality.Īfter this I was able to connect just perfectly. and write a connection string in the textarea like what I’ve done below. It should look something like this:Ĭlick the advanced tab and check the check-box saying user expert…. Here is hvat you need to do:Īfter installing Gui for Java, run it and click the New button. Things work a little different than in the WinGui. Once downloaded I ran the installer and it created a Mac-ified application which integrates with the Mac OS X just perfectly.Īnd then the problems started to kick in, not that there is anything wrong with the software, it just appears that I don’t know how to configure it. I went to the SWDC and downloaded a installer packed as a jar file. Seriously, installing the SAP Gui for Java is a breeze. This of course can related to the fact I’ve set Safari as the default browser and Safari isn’t supported by the Web Dynpro framework. These glitches is mostly regarding context menus and the initial layout of property inspectors and tables. I have recently discovered that there are some minor glitches in the Java gui regarding the WD4A extension to SE80. The I of course use the gui a bit more intensive. One exception is when I’m developing Web Dynpro ABAP (WD4A). In fact I’ll rather use the Java version as it seems a little faster than the WinGUI. Transactions SE37 and BAPI work terrific in SAP Gui for Java. I primarily do Web Dynpro Java development and hence does not need to use the SAP Gui for much other than fetching RFC and BAPI specs and of course the occasional test drive of the two. I my opinion, the Mac is a superior platform in every way, and since it can run a virtualised MS Windows installation simultaneously by the help from VMWare, I decided that lacking support from SAP was not going to prevent me from using the best platform ever. To set the record straight, I have to say I had been warned a lot against choosing the Mac platform because of the lacking platform support from SAP.
0 kommentar(er)
