ADT, just have to do the coding part yourself (which is a plus point for me) and you need to know how exception classes and T100 messages work. If you create a new global class and inherit from one of the exception bases classes some work is already done for you.
For T100 messages there is a template available (called textIdExceptionClass).
For new exception classes I made a custom template for me. You can find it here: https://blogs.sap.com/2017/01/16/additional-adt-code-templates/
Also you need to tell your colleagues not to edit your exception classes in SE24. There you cannot edit the constructor of exception classes at all while in eclipse you can. So if you added some custom functionality in the constructor and someone accidentally regenerates the constructor in SE24 (by adding a new T100 message for example) things won't work anymore. This is also the case if you use naming conventions for the import parameters that differ from the ones SE24 uses. On newer releases there is a pragma available which I assume addresses these issues in some way (##ADT_SUPPRESS_GENERATION), not sure what exactly it does though.
All in all not an ideal situation if you have developers using both ADT and SE80.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.