AppApptypeAn application you deploy and use, installed into a system or loaded into an application as a component, rather than a library whose functions you call.See every one →What this type is →independently maintainedindependently maintainedoriginPublished by one person or a small company outside SAP. Says nothing about quality; the readings say that.See every one →

ZABAP_TABLE_EDIT

A generic ABAP transaction that edits any table's rows and writes its own change documents, without generating an SM30 maintenance dialog, and is extended per table through an interface.

SM30 needs its maintenance module regenerated after every change to the table, and the only way to add a change document is by editing that generated module, an edit lost the next time it regenerates. ZABAP_TABLE_EDIT keeps table changes reflected in the transaction automatically, so no module needs regenerating, and implements the change document itself, for fields not marked for one as well. Transaction ZABAP_TABLE_EDIT is called with a table name alone, or with the name of a class implementing ZIF_ZABAP_TABLE_EDIT, which extends it per table: extra described fields, non-editable fields, validation, new commands and a saved default layout. It installs through abapGit; one known issue is that some versions of the change-document function module require the change indicator field to be named KZ, and shortdump otherwise.

Facts

Last pushLicenceMIT

Where it sits

Lives in
Provides
Maintaining table entriesABAPMaintaining table entriescapabilityEditing the rows of a data or configuration table through a generic or generated screen, with value helps, checks and a managed change package, so that no maintenance application is written per table. Looking at what a table holds is [browsing table data](capability:abap-data-browsing), even where one transaction does both.
Requires
abapGitabapGitartifactInstalls the repository into the ABAP system; the README gives abapGit as the install method.

Who is behind it

Marcin KaszubaMarcin KaszubaPersonMaintains this
In the atlas: maintains 6, contributes to 8
@Kaszub09
maintainerDaniel WegnerPersonContributes to this
In the atlas: maintains 3, contributes to 10
@WegnerDan
1 contributor

What it declares

Every artifact

Type
App
Origin
Independently maintained

As an app

Where it runs
Inside the system it serves
Distributed through
abapGit

Connections2

README

quoted from Kaszub09/ZABAP_TABLE_EDIT under MIT, read
Kaszub09/ZABAP_TABLE_EDIT/README.mdOn GitHub

ZABAP_TABLE_EDIT

Better SM30

FEATURES

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

INSTALATION

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

WHY

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

USAGE

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

CHANGELOG

v1.0.0 (9.06.2024)
  • Refactoring plus new extension
  • Support for text tables
  • Unit tests
v1.1.0 (30.07.2024)
  • Support for selection restriction
  • Utility interfaces (allows for easy combining of multiple interafces / check whether fields are filled / add additional fields with descriptions )
v1.2.0 (25.11.2024)
  • Added button to display documentation - either supplied in transaction, or default for table if exists.
v1.3.0 (06.05.2025)
  • Added support for technical display - whole table, as well as details, similar to SE16N obraz
(18.09.2025)
  • drop versioning
  • add new extensions - easy row statuss/colors, force allow edit
(10.11.2025)
  • add new extension - AMC channel broadcast. Can be used to react to changes in table content, e.g. in order to invalidate cache. Example
(17.02.2026)
  • add new extension (as option) - force edited entries to be transported.

Known issues

MIT, read
Maintaining table entries
  1. table-maintenanceBrowser-based table maintenance UI built on abap2UI5from ABAP
  2. open-table-maintenanceTable maintenance over HTTP for a table fixed in codefrom ABAP
  3. cuteCustom Table Editor editing table rows in an editable ALV gridfrom ABAP

Details

Sources3
Added by handdiscovered herechecked
github.com/Kaszub09/ZABAP_TABLE_EDITtree, pushes, contributors, CIchecked
README.mdquoted, and what the entry declareschecked

Sources are graph entities: the same page may back several entries, and an unreachable source flags every row that rests on it.

Compatibility and provenance
discovered viaAdded by hand
first seen in the atlas
ecosystem and domainabap, data-and-persistence
abaplint
issues under its own abaplint configuration12
lines6,308
statements4,780
objects85
files134
analysed, main
abaplint version2.120.84
Flavors1
Standard ABAP
“Written in ABAP 7.50.” — Kaszub09/ZABAP_TABLE_EDIT — README, INSTALATIONchecked
Contributors1

From the repository’s contributor list, .

History in the atlas1
  1. First seen.
For your agent
Ref
artifact:kaszub09-zabap-table-edit
JSON
/artifacts/kaszub09-zabap-table-edit.json
MCP
Connecting an agent