Maintaining table entries

Editing the rows of a custom or customising table through a generic or generated screen, with value helps, checks and a transport for what changed, so that no maintenance application is written per table. Looking at what a table holds is browsing table data, even where one transaction does both.

Overview

SAP SHIPS

SM30 and SM31 edit tables through maintenance dialogs created in SE54. In ABAP for Cloud Development the Generate ABAP Repository Objects wizard builds a draft-enabled RAP business object from a table, whose entries are edited in the Custom Business Configurations app with changes recorded on a customising transport.

Not covered: Both are generated per table. SE54 writes a dialog for one table, and the wizard accepts only client-dependent tables of delivery class C and cannot overwrite objects it has already created.

How the generated dialogs and the community editors came to be present side by side has not been assessed.

THE COMMUNITY ADDS

Editors that open a table without a generation step, some adding change documents and per-table extensions, one that runs in the browser on classic and cloud releases alike (table-maintenance), and a low-footprint one served over HTTP for a single table named in its code (open-table-maintenance).

Artifacts4

4 of 4 artifacts
ArtifactSignals
Apps3
cuteCustom Table Editor editing table rows in an editable ALV grid
Signals
Quiet
table-maintenanceBrowser-based table maintenance UI built on abap2UI5
Signals
Functional boundary
ZABAP_TABLE_EDITGeneric ABAP table editor writing its own change documents
Signals
none
Packages1
open-table-maintenanceTable maintenance over HTTP for a table fixed in code
Signals
Functional boundary

Details