Better SM30

Edit any table. Create change document automatically. Extend basic functionality if needed.

Via https://github.com/abapGit/abapGit. Requires https://github.com/Kaszub09/ZABAP_SALV_REPORT. Written in ABAP 7.50.

To streamline the process of making table available for edit and tracking changes.

With SM30:

• Every time you change table, you need to regenerate maintenance module. No more!
• Only way to add change document to SM30 is via editing maintenance module. That and any other edits are lost after recreating maintenace module, and you must implement them again (that is if you remembered copying them before regenerating module - otherwise you need to write them again from scratch). No more!
• Table and column on generated screen are really narrow and usually needs to be manually widened. No more!

With ZSM30

• Any changes to table are automatically reflected in transaction. Generating maintenance module is not needed.
• No code is ever lost
• Change document is implemented automatically - you can decide, whether to use it or not
• Change document can be generated even for fields not marked as such
• Transaction can be easily extended with custom logic per table (additional fields with description, make some fields non-editable, add additional validation, add new commands, edit entries before save etc. ) - instead of creating maintenance view or editing maintenance modules
• It's possible to save default layout, so every time you open table for edit columns width/layout will be perfect! the same

See examples package. Either call transaction ZABAP_TABLE_EDIT only with table name, or with name of class implementing interface ZIF_ZABAP_TABLE_EDIT.

• Some version of function module 'CHANGEDOCUMENT_MULTIPLE_CASE2' require change indicator field to be named 'KZ', causing shortdump otherwise - you can fix it by implementing SAP notes Kaszub09#2 (comment)