Speak Your Voice; New ABAP Editor for Older Releases
Speak Your Mind
I have received an amazing response to New ABAP Editor; too good to wait for.. In fact based upon the number of page views and emails I have received, I would say there is huge interest in this new editor.
It seems a shame that SAP is only going to release this new editor as part of WebAS 7.0 (Netweaver 04S). For most of us that means that working in this editor could still be 5 years or more in the future.
Even if you would have access to 7.0 via a standalone WebAS or BW system, many of us still do the majority of our ABAP coding in an R/3 system. Most businesses are hesitant to upgrade their core business system too often, not wanting to incur cost and disruption. From talking to people, I would say that it is not uncommon for a company to wait 4-5 years in between R/3 upgrades (supported further by SAP’s 5/2/1 support policy). I doubt that most development teams could approach upper management and justify an R/3 upgrade just so they could get access to a better development tool.
Take my company for instance. We are currently on 46C (and have been for almost 5 years). We are planning our upgrade to ERP2004 later this year. ERP2004 will still only put us on a WebAS 640 system. Then there are the thousands of customers who have already upgraded to R/3 Enterprise (a WebAS 620 based system). For many of us a 7.0 system with the new ABAP editor is still a far off dream.
This is where we have an opportunity to have our voices heard via SDN. For the first time the ABAP developer community has a loud unified voice here on SDN. Perhaps if we can gather enough response, SAP will see that there is customer demand and value for back-porting the new editor and integrating it into the ABAP workbench in older WebAS releases.
What I would like to suggest is that everyone interested, please go to the following forum posting:
Back-porting the New ABAP Editor to older WebAS Releases
Reply to this posting, simply stating what release you would like to see the new editor back-ported to. Please be realistic (no 3.0F is not realistic). What version of the WebAS do you really think you will be developing on for the next few years.
Henning
BTW, thanks to your other blog about the new ABAP editor.
It will be wonderful if the new AB4 editor can be compatible 4.6C onwards.
SAP R/3 Enterprise 4.7 with
- SAP_BASIS 620
- SAP_ABA 620
- SAP_APPL 470
- Kernel 6.40
Jürgen
>...the message is indeed more important than the means...
What does everybody think of making SDN an offical institution for addressing development requests to SAP (like DSAG, ASUG, etc.)?
Is there already a discussion/statement regarding this idea? (Shall i create a new forum-post or weblog? Maybe Craig or Mark are the right persons to turn to...)
Comments welcome...
Best regards
Jürgen
Most of the installations are on 4.6C or SAP_ABA 620. Enterprise 4.7 is still based on ABAP 620 and 4.7 is under mainstream maintenance at least another 4 years.
So, it will be really nice to have this new editor backported starting atleast ABAP 620.
BTW: Thomas, thanks a lot for your weblog. looking forward to your latest findings 🙂
Cheers !!
Satya.
as my previous poster said: A backport to 6.20 would be perfect.
Regards
Gregor
Even if we could convince SAP to back-port the editor to older releases it is unlikely that they will go back to 46C because of this Unicode setup.
WAS 6.20 is a MUST, but 4.6c would be great.
regards from BCN,
David R.
Peter
Since we seem to have drummed up a nice amount of interest in just a day's time, perhaps we can approach one of the SDN community managers and see if there is an outlet to take this discussion to SAP. That way we could find out if our dream can become reality.
So let's definately go back to 6.20!
currently I'm developing most time on 4.6C and I don't think, that this would change within the next 2 years.
So it would be nice to have the editor for this release (and 6.20 of course).
Regards
Olli
"Join a Grassroots Effort to Render the New ABAP Editor Backwards Compatible"
🙂
Peter
I think we should have it backwards compatible to WebAS 6.20 .
Leonardo Araujo
But I want more: Couldn't find any info about a new and improved DEBUGGER!
How often do you find yourself wanting to display more than 4 variables at once? Or even track more than 8 at the time?
How about using the whole screen? On me screen, only 50% is used, most of it to display code. A smal part at the bottom is for debugging information. I know; this can be "inverted", but still most of my screen is unused.
I want:
- floating windows where I can display how many variables I want. It should be possible to collaps them, not only minimize.
- evaluation of logical statements. I want to see the result of a (complex) AND/OR/NOT statement in the debugger!
-to preserve the display of local variables when returning to a form. When I exit the form; hide them till next time.
Found something here:
-----------------------------
The New ABAP Debugger
The New ABAP Debugger
-----------------------------
Thanx to Boris Gebhardt
regards
nicola
Developers using other programming languages are enjoying a much friendlier development environment.
Why don't we ?
please make it possible for us too
benny
in my opinion syntax highlighting is a must have feature. Because of so many ABAP devs will be developing on 6.20 systems, please port it back to 6.20!!!!
PS: Don't forget the code assitent feature 🙂
Thanks