fiori-table-maintenance
The CAP service and freestyle UI5 app behind Simple Table Maintenance in SAP Fiori Using UI5 Smart ControlsSimple Table Maintenance in SAP Fiori Using UI5 Smart ControlsStarts from SM30 and the table maintenance dialog it generated with almost no code, then asks what the equivalent is now. That framing is the value: a maintenance screen for a custom table was a solved problem in SAP GUI and is not an obviously solved one on Fiori, and the post works through what smart controls give you towards it.published 2025-02-11, where a SmartTable edits rows in place rather than through a draft.
SM30 generated a maintenance screen for a custom table with almost no code, and this works out what the same screen costs on Fiori, where nothing generates it. Two CDS entities, StarWarsFighter and FighterStatus, are served as OData V2 through @cap-js-community/odata-v2-adapter@cap-js-community/odata-v2-adapterExposes a CAP service as OData V2 for clients that cannot move to V4.community org, cap, and one XML view puts a SmartFilterBar and a SmartTable over them with editable and editTogglable set, variant management and export. The columns and the read-only fields are Fiori annotationsFiori annotationsDescribing a service so a Fiori client can render it without hand-written UI code — titles, value helps, hierarchies and visibility expressed as model annotations rather than screen logic.SAP and community, unassessed in app/annotations.cds, so the controller holds little more than onFieldChange calling model.submitChanges() as a field is left. It stops at one table and one app: the view names its entity set, the annotations name its fields, and a second table means writing both again.
Facts
Where it sits
Who is behind it
In the atlas: maintains 35, contributes to 86, wrote 25@marianfoomaintainer
Before choosing this
Signals
LicenceNo licenseNeither the package manifest nor the repository tree declares a licence
Without a licence the default is all rights reserved. Ask the maintainer, or check for terms stated elsewhere, before depending on it.
What it declares
Every artifact
- Type
- Sample
- Origin
- Independently maintained
As a sample
- Form
- A tutorial's companion code
Connections
Keeping a control and a model in step in both directions
Describing a service so a Fiori client renders it without UI code
Exposing data and operations through OData
Exposes a CAP service as OData V2
Download
README
quoted from marianfoo/fiori-table-maintenance, readGetting Started
This was documented in this blog post:
https://community.sap.com/t5/technology-blogs-by-members/simple-table-maintenance-in-sap-fiori-using-ui5-smart-controls/ba-p/14014547
Welcome to your new project.
It contains these folders and files, following our recommended project layout:
| File or Folder | Purpose |
|---|---|
app/ | content for UI frontends goes here |
db/ | your domain models and data go here |
srv/ | your service models and code go here |
package.json | project metadata and configuration |
readme.md | this getting started guide |
Details
Sources
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
Flavors
“By using CAP/RAP Backend, a freestyle UI5 app, and OData V2 (plus UI annotations), you can quickly set up a user-friendly, fully responsive table maintenance application.” — Simple Table Maintenance in SAP Fiori Using UI5 Smart Controls — SAP Community
History in the atlas
- First seen.
For your agent
- Ref
artifact:marianfoo-fiori-table-maintenance- JSON
- /artifacts/marianfoo-fiori-table-maintenance.json
- MCP
- Connecting an agent