2014 Nov 25 5:13 AM
Hi all,
Not sure if any comments needed for this question. Does anyone know (and can tell) what is the real reason why we can't edit classes in SE24/SE80 once you add the AMDP marker interface?
It's not because of SQLscript syntax check (might have been in the past, not anymore).
I can't find any explanation other than "because SAP wants you to use ADT".
Cheers,
Custodio
2014 Nov 25 7:53 AM
Hi Custodio,
SQL Script is not integrated in the ABAP language natively. That means we do not have the infrastructure in ABAP to fulfill editor requirements like syntax-coloring, code completion etc.
As this infrastructure is already available in the HANA studio for HANA-native procedures we decided to support AMDPs only in the eclipse editor. The ABAP class editor in SAP GUI is not capable of managing non-ABAP code. We had to spend quite some effort to at least support the read-only mode in SE24. Supporting the edit mode even without providing standard features like syntax-coloring and code completion was not possible within the given timeframe. Upcoming features like the AMDP debugger for example will also be provided in eclipse only.
Since NW Release 7.40 we clearly state that all new investments concerning the ABAP development tools are only be done in eclipse. Especially for all HANA related topics it makes sense to switch to eclipse because of the integration with the HANA studio. There are other examples like the CDS editor, the SQL console and the data preview in eclipse. These tools are also eclipse-only.
THE FUTURE OF ABAP DEVELOPMENT IS IN ECLIPSE AND IT ALREADY STARTED.
Kind Regards,
Thomas.
2014 Nov 25 6:12 AM
I can't find any explanation other than "because SAP wants you to use ADT".
2014 Nov 25 7:53 AM
Hi Custodio,
SQL Script is not integrated in the ABAP language natively. That means we do not have the infrastructure in ABAP to fulfill editor requirements like syntax-coloring, code completion etc.
As this infrastructure is already available in the HANA studio for HANA-native procedures we decided to support AMDPs only in the eclipse editor. The ABAP class editor in SAP GUI is not capable of managing non-ABAP code. We had to spend quite some effort to at least support the read-only mode in SE24. Supporting the edit mode even without providing standard features like syntax-coloring and code completion was not possible within the given timeframe. Upcoming features like the AMDP debugger for example will also be provided in eclipse only.
Since NW Release 7.40 we clearly state that all new investments concerning the ABAP development tools are only be done in eclipse. Especially for all HANA related topics it makes sense to switch to eclipse because of the integration with the HANA studio. There are other examples like the CDS editor, the SQL console and the data preview in eclipse. These tools are also eclipse-only.
THE FUTURE OF ABAP DEVELOPMENT IS IN ECLIPSE AND IT ALREADY STARTED.
Kind Regards,
Thomas.
2021 May 27 11:14 AM
Unfortunately, as usual, SAP is very active in starting the future, but never really cares to finish it up... For example the itab viewer in the debugger is still way behind the ABAP debugger and renders eclipse unusable for any debugging with big data tables.
2021 May 27 12:41 PM
2021 May 27 11:18 AM
To answer the original question, if you set user parameter SEO_SOURCEBASED_AMDP to X, you can edit it in SE24...
2021 May 27 11:36 AM
Wow, this is very good information - a bit late, but still good 🙂
Thanks!
2021 May 27 6:40 PM
Maybe it works in a given version, but not in ABAP 7.52 SP 0 (in S/4HANA). I don't even see any logic for that. (method IF_OO_ACCESS_PERMISSION~ACCESS_FOR_MODIFY of CL_OO_ABSTRACT_CLASS_TOOL)
2021 May 27 7:01 PM