abap2UI5 frontend-webcomponent
An alternative abap2UI5abap2UI5One ABAP class implementing z2ui5_if_app is the whole app: the browser loads a generic UI5 shell once, and every interaction after that is an HTTP roundtrip back into ABAP.community org, abap frontend: one ES module registering <abap2ui5-app>, which renders the views an unchanged abap2UI5 app class sends with UI5 Web Components@ui5/webcomponentsSAP's UI elements as standard custom elements, ui5-button among them, implementing SAP Fiori design and usable from plain HTML, React, Angular or Vue.sap official, ui5 and no UI5 core.
abap2UI5 apps are reached through the project's UI5 single-page app, which loads the UI5 core. This frontend speaks the same JSON protocol and renders the same views out of UI5 Web Components instead, so the app class stays as it is and the bundle is 1265 kB raw, 263 kB gzip, with the 62 components its mappers create and nothing else. It ships as one custom element: dist/index.html is the standalone start page with ?app_start=<CLASS>, and the same element goes into a React, Vue, Angular or plain-HTML page, where it renders into its own shadow root, keeps its own backend session and reports what happens as DOM events. It implements the core protocol in full (app start, events with their model delta, the sap-contextid session, the five view slots, the app stack and the URL hash) and the protocol's portable view profile v1 for rendering, 65 of 65 controls mapped, 42 full and 23 basic. Embedded, the element never reads or writes location: it emits an abap2ui5-route event per hash the app would write and takes one back through navigate(hash), so the host keeps its own routing.
Facts
Where it sits
Who is behind it
In the atlas: maintains 18@abap2UI5maintaineroblomov-devContributes to this
In the atlas: maintains 4, contributes to 44@oblomov-dev1 contributor
Before choosing this
Conditions
PracticalFunctional boundary
Not for views built from controls outside the portable profile: sap.ui.table, sap.f, sap.uxap, sap.ui.comp and z2ui5.cc custom controls render as a visible unsupported-control box and are listed in the diagnostics, and CONTROL_BY_ID and BINDING_CALL stay unsupported. Nine frontend actions the profile allows, DOWNLOAD_B64_FILE and SYSTEM_LOGOUT among them, are skipped and reported rather than run, and formatters other than the profile's Formatter.Date* render a placeholder.
What it declares
Every artifact
- Type
- Package
- Origin
- By a community org
As a package
- Where it runs
- does not say
- Distributed through
- does not say
Connections
Producing a web user interface from ABAP code
Using standards-based custom elements inside an app
UI5 apps written as one ABAP class, rendered by a generic shell
SAP's UI elements as standard custom elements
UI5 apps written as one ABAP class, rendered by a generic shell
Download
README
quoted from abap2UI5/frontend-webcomponent under MIT, readabap2UI5 frontend - UI5 Web Components
An alternative frontend for abap2UI5:
it speaks the same JSON protocol as the official UI5 SPA and renders the
views an unchanged abap2UI5 app class sends - with
UI5 Web Components
(@ui5/webcomponents, @ui5/webcomponents-fiori 2.27), without the UI5
core. One ES module, one custom element:
<script type="module" src="abap2ui5-wc.js"></script>
<abap2ui5-app endpoint="/sap/bc/z2ui5" app="Z2UI5_CL_MY_APP"></abap2ui5-app>- standalone -
dist/index.htmlis the equivalent of the UI5 SPA's start page:?app_start=<CLASS>; - embedded - in any web app (React, Vue, Angular, plain HTML): the element renders into its own shadow root, keeps its own backend session and reports what happens as DOM events.
What it implements
The abap2UI5 protocol is layered:
| Layer | Here |
|---|---|
| Core protocol (transport, request/response, sessions, navigation, errors) | all of it: app start, events with T_EVENT_ARG, the model delta of the edited paths (__delta rows), the draft id, the sap-contextid session, the CSRF token handshake, the five view slots (MAIN, NEST, NEST2, POPUP, POPOVER), the app stack (nav_app_call / nav_app_leave / the back button), the URL hash (ROUTER action: KEEP/FRESH routes, browser Back/Forward restores, the app-state hash, app-owned hashes with their listener event, HASH_BACK; see The URL hash), PROTOCOL check, the error body of a failed roundtrip shown verbatim as text |
Portable view profile v1 (61 controls + 4 tolerated elements, profile/portable-v1.json) | 65 of 65 mapped - table below |
| full UI5 view profile | no - a control outside the portable profile renders as a visible unsupported control box (its children are still rendered) and is listed in the diagnostics |
| semantic profile (agent snapshot) | no - that is the MCP server's agent client |
Frontend actions (T_CUSTOM / .eF wires): MESSAGE_TOAST, MESSAGE_BOX
(types, details, custom actions, onClose event), CONTROL_GLOBAL
(message toast/box incl. client-composed {0} texts, VIEW_SLOTS destroy =
popup/popover close, BUSY_INDICATOR, THEMING, INVISIBLE_MESSAGE announce), SET_TITLE, START_TIMER, SET_FOCUS, CLIPBOARD_COPY,
OPEN_NEW_TAB / LOCATION_RELOAD (same origin only), URLHELPER REDIRECT
(http(s) only), HASH_BACK (with its fallback route), and the navigation
family under its client-API names (SET_PUSH_STATE, HASH_REPLACE,
HASH_ATTACH_CHANGED, SET_NAV_ROUTING, SET_APP_STATE_ACTIVE - a backend
folds them into the ROUTER system action; as an .eF wire they reach the
router as the same options). CONTROL_BY_ID and BINDING_CALL are excluded
from the portable profile and stay unsupported. Everything else is skipped,
logged and listed in the diagnostics - never thrown.
Bindings: absolute and relative paths, list bindings with one template
(sorter, length, startIndex), element binding (binding="{/X}"),
two-way binding of every value-like property (the edit goes into the model
and the next event's delta, exactly as the UI5 frontend sends it), typed
bindings for display (sap.ui.model.type / odata.type Integer, Float,
Decimal, Date, Time, DateTime, Currency with formatOptions such as
decimals, pattern, source.pattern) and back (numbers stay numbers,
read with the symbols of the locale they are shown in: 1.234,56 in a
German browser),
expression bindings in the profile's grammar (${...}, operators, ? :,
.length, Math.max/min/abs/round/floor/ceil, toUpperCase/toLowerCase/ trim/indexOf/includes/startsWith/endsWith) evaluated by a small parser - no
eval -, composite text and parts, the device> model, and the profile's frontend
formatters Formatter.DateCreateObject, Formatter.DateAbapDateToDateObject
and Formatter.DateAbapDateTimeToDateObject (ABAP DATS/TIMS or ISO strings
to dates, e.g. for DatePicker.dateValue, minDate, maxDate; same names and
behaviour as the UI5 frontend's model/formatter.js). Any other formatter
renders a visible [formatter name] placeholder and is reported. Tables and
lists grow: growing / growingThreshold / growingTriggerText /
growingScrollToLoad render the first rows and a "More" trigger.
Embedding
The bundle registers <abap2ui5-app>; give the element a height.
<!-- plain HTML -->
<script type="module" src="/assets/abap2ui5-wc.js"></script>
<abap2ui5-app endpoint="/sap/bc/z2ui5" app="Z2UI5_CL_MY_APP" style="height: 600px"></abap2ui5-app>
<script>
document.querySelector('abap2ui5-app')
.addEventListener('abap2ui5-message', (e) => console.log(e.detail));
</script>// React 19 (custom elements are first-class; React 18: addEventListener in a ref effect)
import '@abap2ui5/frontend-webcomponent';
export const Abap2UI5 = ({ app }) => (
<abap2ui5-app endpoint="/sap/bc/z2ui5" app={app} style={{ display: 'block', height: 600 }} />
);<!-- Vue 3 - compilerOptions.isCustomElement: (t) => t === 'abap2ui5-app' -->
<script setup>import '@abap2ui5/frontend-webcomponent';</script>
<template>
<abap2ui5-app endpoint="/sap/bc/z2ui5" :app="app" style="display:block;height:600px"
@abap2ui5-message="onMessage" />
</template>Angular: add CUSTOM_ELEMENTS_SCHEMA to the component and import the module
once. examples/plain.html runs two apps side by side
(the demo server serves it at /examples/plain.html),
examples/react.jsx and
examples/vue.vue are the snippets above in full.
| Attribute | |
|---|---|
endpoint | the abap2UI5 HTTP service (/sap/bc/z2ui5, or an absolute URL) |
app | the app class; changing it restarts the element with that app |
params | extra start parameters, a=1&b=2 (they travel in SEARCH) |
theme | a UI5 Web Components theme: sap_horizon (default), sap_horizon_dark, sap_horizon_hcb, sap_fiori_3, ... |
credentials | fetch credentials: same-origin (default), include (a backend on another origin, cookie auth), omit |
csrf | auto (default: fetch a token when a token layer answers 403 X-CSRF-Token: Required, re-send once), fetch (before the first POST), none, or a token |
diagnostics | off hides the diagnostics panel (the console and the events still report) |
document-title | SET_TITLE also sets document.title (always on in the standalone page) |
standalone | the element owns the page: the URL hash is the app's (routes, app state, Back/Forward) and travels with every request |
routing | the URL hash: hash (read and write the page's hash - the default with standalone), events (never touch the host's URL, emit abap2ui5-route - the default embedded), off |
language | the language of the frontend's own texts (message box buttons and titles, "No data", the error dialog - English and German built in, defineTexts() adds one) and of the web components; default: the page's lang, else the browser's. The standalone page takes ?sap-language= |
endpoint, app, params, credentials, csrf, routing, standalone
and language restart the element when changed; theme, diagnostics and
document-title apply at once.
Properties: headers (extra request headers - Authorization, sap-client;
a new object assigned later is used from the next request on),
transport (your own { roundtrip(body), endSession() } - set before the
element connects), session, diagnostics; methods restart(),
navigate(hash). Events (bubbling, composed): abap2ui5-response,
abap2ui5-request, abap2ui5-message, abap2ui5-title, abap2ui5-error
(detail.retry says whether the error dialog offers Retry),
abap2ui5-diagnostic, abap2ui5-route. TypeScript hosts get the element,
its event map and the exports typed from types/index.d.ts.
The URL hash
abap2UI5 apps can keep their state in the URL hash
(spec/navigation.md):
hash routing (#/app/<CLASS>/<DRAFT> in mode KEEP, #/app/<CLASS> in
FRESH; a nav_app_call pushes a history entry, the browser Back button
restores the caller's draft), the app-state hash
(#/z2ui5-xapp-state=<DRAFT>: reload and bookmarks restore the state), and
app-owned hashes (hash_set / hash_replace with a listener event raised
on Back/Forward, HASH_BACK with a fallback route). The backend sends what
the URL has to reflect as the ROUTER system action; this frontend applies
it once per response, as the UI5 frontend's router does.
- Standalone (
dist/index.html, orrouting="hash"): the page's hash is the app's. It is written with the History API, a browser Back/Forward or a manual edit sends the app-start-shaped restore request (noID, the newHASH), and every request carries the hash asS_FRONT.HASH. Inside the SAP Fiori launchpad the shell part before&/is kept. - Embedded (the default without
standalone): the hash is the host's. The element never reads or writeslocation, sends noHASH, and tells the host instead - anabap2ui5-routeevent per hash the app would write,{ action: 'push' | 'replace', hash, app, id }, and{ action: 'back' }forHASH_BACK. A host that routes itself can record those hashes and, on its own Back button or a deep link, hand one back withelement.navigate(hash): a route then restores that draft, an app-owned hash raises the app's listener event - and that one request carries the hash.routing="off"ignores theROUTERaction altogether.
The protocol client, the renderer and the control registry are exported too
(Session, createFetchTransport, Renderer, defineControl, ...), and
defineControl('z2ui5.cc.MyControl', mapper) adds a mapper of your own.
Run the demo
The demo backend is abap2UI5 itself, transpiled to Node -
@abap2ui5/node-runtime
1.146.0 - with 16 real sample apps of
abap2UI5/samples transpiled on top,
exactly as the package's README describes for your own apps.
npm ci
npm run demo:build # open-abap-core at the runtime's commit, transpile demo/abap, abap2ui5-own-apps
npm run build # dist/abap2ui5-wc.js, dist/index.html
npm run demo:serve # http://127.0.0.1:4300/?app_start=Z2UI5_CL_SMP_APP_494The same server answers the official UI5 SPA at
http://127.0.0.1:4300/sap/bc/z2ui5/?app_start=Z2UI5_CL_SMP_APP_494 - one
backend, two frontends.
| Demo app | Status | |
|---|---|---|
| Z2UI5_CL_SMP_APP_493 | Hello World - Shell, Page, MessageStrip, Title | runs fully |
| Z2UI5_CL_SMP_APP_494 | Data binding - two-way binding, delta, MessageBox | runs fully |
| Z2UI5_CL_SMP_APP_381 | MessageToast via the global object - Select, CheckBox, toast options, onClose event, client-composed toast | runs fully (toast position options are not applied) |
| Z2UI5_CL_SMP_APP_382 | MessageBox types, details, custom actions | runs fully |
| Z2UI5_CL_SMP_APP_011 | Table - edit mode, cell inputs, MultiSelect, delete and add rows | runs fully |
| Z2UI5_CL_SMP_APP_019 | Table selection modes - SegmentedButton, selection read in ABAP | runs fully |
| Z2UI5_CL_SMP_APP_048 | List - StandardListItem, ${ROW} args on detailPress, selectionChange | runs fully |
| Z2UI5_CL_SMP_APP_012 (+020) | Popups - dialog over the page, popup closed on the client, popup app via nav_app_call | runs fully |
| Z2UI5_CL_SMP_APP_026 | Popover at its opener, input and footer | runs fully |
| Z2UI5_CL_SMP_APP_024 (+025) | Navigation - call another app, return data, back button | runs fully |
| Z2UI5_CL_SMP_APP_445 | Device model - device> bindings, expressions, IconTabBar, popup | runs fully |
| Z2UI5_CL_SMP_APP_125 | Set the tab title (SET_TITLE) | runs fully |
| Z2UI5_CL_SMP_APP_027 | Expression binding, types, composite parts | partial: the RegExp(...) expression is outside the profile - reported, the button stays disabled |
| Z2UI5_CL_SMP_APP_453 | ObjectStatus, ObjectNumber in a table | runs fully |
| Z2UI5_CL_SMP_APP_480 (+469) | Hash routing (KEEP) - #/app/<CLASS>/<DRAFT>, nav_app_call pushes, browser Back/Forward restore the drafts | runs fully |
| Z2UI5_CL_SMP_APP_498 | App state in the URL - #/z2ui5-xapp-state=<DRAFT>, a reload restores the state | runs fully (the share link is the backend's) |
All screenshots: docs/screenshots/.
Tests
npm run lint
npm test # node:test - bindings, expressions, types, the protocol client
# (delta, slots, errors, busy queue), transport (contextid, CSRF),
# the URL hash router, frontend actions (both shapes of the
# profile's action list), formatters, the renderer on happy-dom over the recorded
# views of every demo app, the vendored-file hashes, profile coverage
npm run e2e # Playwright - every demo app in the web-components frontend,
# DOM + backend state, and the same interaction in the UI5 SPA
# with the request bodies / models compared; embedding; errors
npm run screenshots # docs/screenshots/The e2e cross-check drives the official UI5 SPA through the UI5 control API
(setValue + fireChange, firePress, ...) and compares what both
frontends sent (EVENT, T_EVENT_ARG, MODEL) and what the backend answered.
UI5 itself comes from sdk.openui5.org; OPENUI5_DIR=<node_modules/@openui5>
serves it from local packages instead (offline sandboxes), CROSS_CHECK=0
skips the UI5 half. Chromium: CHROMIUM_BIN, else /opt/pw-browsers/chromium
when present, else Playwright's own.
Architecture
src/core/ the protocol client - no DOM
session.js start / fire / closeSlot, response adoption (vendored applyResponse),
delta (vendored buildDelta), app stack, APP-change popup teardown, busy queue,
route restore, the error body verbatim
transport.js fetch POST { value }, sap-contextid, CSRF handshake, terminate HEAD
router.js the URL hash: ROUTER sync, routes, app-state hash, app-owned hashes,
HASH_BACK - on the page's hash or as abap2ui5-route events (embedded)
actions.js T_CUSTOM / eF frontend actions
src/bindings/ model.js (long-lived models, edited paths, device>), binding.js (property and
list bindings), expression.js (profile grammar), types.js (typed display),
formatters.js (the profile's Formatter.Date*), objectsyntax.js
src/render/ renderer.js (XML -> elements, scopes, two-way, wires), wires.js (event args),
registry.js + controls/*.js (one mapper per UI5 control), webcomponents.js (imports)
src/ui/ app.js (slots, popups, toast/box, busy, errors, diagnostics), styles.js
src/element.js <abap2ui5-app>
src/vendor/agent/ viewxml.mjs, snapshot.mjs, appclient.mjs of abap2UI5/mcp-server, unchanged
The XML parser, the wire parser, the response bookkeeping and the delta
builder are the MCP server's agent client modules, vendored unchanged at
a recorded commit (scripts/vendor-agent.mjs, src/vendor/agent/source.json,
hash test) - the same code that already speaks the protocol for agents;
the bundler drops what the browser does not call.
Bundle (npm run build): dist/abap2ui5-wc.js 1265 kB raw / 263 kB gzip
loaded up front (the 62 web components used, nothing else); on demand, in
dist/chunks/: the SAP icon collection (248 kB gzip, on the first icon),
popover internals, the CLDR data of the user's locale, extra themes.
Control coverage
Portable profile v1: 65 of 65 controls mapped (42 full, 23 basic).
| UI5 control (profile v1) | rendered as | status | basic: what is left out |
|---|---|---|---|
| sap.m.Page | ui5-page + ui5-bar header/footer | full | |
| sap.m.Shell | HTML/CSS | full | |
| sap.m.VBox | HTML/CSS | full | CSS flexbox: direction, alignItems, justifyContent, wrap, fitContainer; FlexItemData grow/shrink/base |
| sap.ui.layout.form.SimpleForm | CSS grid + ui5-title | basic | label/field grid with group titles; layout, columns and breakpoints are not modelled |
| sap.m.HBox | HTML/CSS | full | CSS flexbox: direction, alignItems, justifyContent, wrap, fitContainer; FlexItemData grow/shrink/base |
| sap.m.Panel | ui5-panel | full | |
| sap.ui.layout.Grid | HTML/CSS | basic | defaultSpan and GridData span (XL/L/M/S); no indent |
| sap.m.FlexBox | HTML/CSS | full | CSS flexbox: direction, alignItems, justifyContent, wrap, fitContainer; FlexItemData grow/shrink/base |
| sap.m.ScrollContainer | HTML/CSS | full | |
| sap.m.IconTabFilter | ui5-tab | full | |
| sap.m.IconTabBar | ui5-tabcontainer + ui5-tab | basic | tabs with text, icon, count, iconColor and content; selectedKey, select; no expand/collapse event, no drag & drop |
| sap.ui.layout.VerticalLayout | HTML/CSS | basic | a column of its content; width/spacing not modelled |
| sap.ui.core.Title | ui5-title | basic | icon not shown |
| sap.ui.layout.HorizontalLayout | HTML/CSS | basic | an inline row of its content; allowWrapping always on |
| sap.m.OverflowToolbar | ui5-toolbar (+ ui5-toolbar-button, -item, -spacer, -separator) | full | |
| sap.m.ToolbarSpacer | ui5-toolbar-spacer | full | |
| sap.m.Toolbar | ui5-toolbar (+ ui5-toolbar-button, -item, -spacer, -separator) | full | |
| sap.m.Bar | ui5-bar | full | |
| sap.m.OverflowToolbarButton | ui5-button | basic | icon button with the text as tooltip (the overflow text is the toolbar's) |
| sap.m.Text | ui5-text | full | |
| sap.m.Label | ui5-label | full | |
| sap.m.Title | ui5-title | full | |
| sap.m.ObjectStatus | styled <span> + ui5-icon | basic | icon, title, text, state, inverted, active; no stateAnnouncementText |
| sap.m.Link | ui5-link | full | |
| sap.m.ObjectIdentifier | HTML (+ ui5-link when titleActive) | basic | title, text, titleActive/titlePress |
| sap.ui.core.HTML | HTML/CSS | basic | content sanitized: no script, no style element, no event handlers |
| sap.ui.core.Icon | ui5-icon | full | |
| sap.m.ObjectNumber | HTML/CSS | basic | number, unit, state, emphasized |
| sap.tnt.InfoLabel | ui5-tag + ui5-icon | full | |
| sap.m.ProgressIndicator | ui5-progress-indicator | full | |
| sap.m.Image | HTML <img> | full | |
| sap.m.Input | ui5-input + ui5-icon | full | |
| sap.m.TextArea | ui5-textarea | full | |
| sap.ui.core.Item | ui5-option + ui5-cb-item + ui5-mcb-item | full | |
| sap.m.CheckBox | ui5-checkbox | full | |
| sap.m.Switch | ui5-switch | full | |
| sap.m.SegmentedButton | ui5-segmented-button | full | |
| sap.m.SegmentedButtonItem | ui5-segmented-button-item | full | |
| sap.m.Select | ui5-select | full | |
| sap.m.DatePicker | ui5-date-picker | basic | value (two-way), valueFormat, displayFormat, minDate/maxDate; dateValue one-way (from a frontend formatter) |
| sap.m.SearchField | ui5-input + ui5-icon | full | |
| sap.m.ComboBox | ui5-combobox | full | |
| sap.m.MultiInput | ui5-multi-input | basic | tokens are shown; a token delete fires tokenUpdate but is not written back into the bound token table (UI5 needs z2ui5.cc.MultiInputExt for that too) |
| sap.m.Token | ui5-token | basic | text, key, selected |
| sap.m.MultiComboBox | ui5-multi-combobox | full | |
| sap.m.StepInput | ui5-step-input | full | |
| sap.ui.core.ListItem | ui5-option + ui5-cb-item + ui5-mcb-item | full | |
| sap.m.DateTimePicker | ui5-datetime-picker | basic | value (two-way), valueFormat, displayFormat, minDate/maxDate; dateValue one-way (from a frontend formatter) |
| sap.m.Button | ui5-button (ui5-toolbar-button in a toolbar) | full | |
| sap.m.ToggleButton | ui5-toggle-button | full | |
| sap.m.Column | ui5-table-header-cell | basic | header, width, hAlign, minScreenWidth; no demandPopin/footer |
| sap.m.ColumnListItem | ui5-table-row + ui5-table-cell | basic | cells, type (interactive rows), selected, press; highlight not shown |
| sap.m.Table | ui5-table (+ header row/cells, ui5-table-selection-multi/-single) | basic | columns, items (bound or static), header toolbar, noDataText, MultiSelect/SingleSelect via the selected binding, itemPress, selectionChange, growing (threshold, trigger text, scroll to load); no Delete mode, no grouping |
| sap.m.List | ui5-list | basic | items (bound or static), headerText, mode, itemPress, selectionChange, delete, growing (threshold, trigger text, scroll to load); no grouping |
| sap.m.StandardListItem | ui5-li | basic | title, description, icon, info, infoState, highlight, type, selected; no counter/avatar |
| sap.m.CustomListItem | ui5-li-custom | full | |
| sap.m.Tree | ui5-tree | basic | nested array binding (sorter, length, startIndex at the top level), headerText, mode, headerToolbar, toggleOpenState/itemPress/selectionChange |
| sap.m.StandardTreeItem | ui5-tree-item | full | |
| sap.m.Dialog | ui5-dialog + ui5-bar footer | basic | title, icon, state, content size, buttons/begin/endButton/footer, custom header, afterClose; type Message not distinguished |
| sap.m.Popover | ui5-popover | basic | title, placement, modal, content size, footer, afterClose |
| sap.m.MessageStrip | ui5-message-strip | full | |
| sap.ui.core.CustomData (tolerated) | none (no UI) | full | tolerated, no UI |
| sap.m.FlexItemData (tolerated) | none (no UI) | full | applied to the parent control as CSS flex |
| sap.ui.layout.GridData (tolerated) | none (no UI) | full | applied to the parent control as grid span |
| sap.m.OverflowToolbarLayoutData (tolerated) | none (no UI) | full | tolerated, no UI |
Beyond v1 (31):
| UI5 control | rendered as | status | basic: what is left out |
|---|---|---|---|
| sap.m.ActionListItem | ui5-li | full | |
| sap.m.App | HTML/CSS | full | |
| sap.m.Avatar | ui5-avatar | basic | |
| sap.m.BusyIndicator | ui5-busy-indicator | full | |
| sap.m.DateRangeSelection | ui5-daterange-picker | basic | value only (no dateValue/secondDateValue) |
| sap.m.DisplayListItem | ui5-li | full | |
| sap.m.FormattedText | HTML/CSS | basic | sanitized HTML; no controls aggregation |
| sap.m.GenericTag | ui5-tag | basic | |
| sap.m.GroupHeaderListItem | ui5-li | basic | |
| sap.m.IconTabSeparator | ui5-tab-separator | full | |
| sap.m.MaskInput | ui5-input | basic | a plain input: the mask is shown as placeholder, not enforced |
| sap.m.NavContainer | HTML/CSS | basic | shows the initial (or first) page; to() by CONTROL_BY_ID is not supported |
| sap.m.ObjectAttribute | ui5-link | basic | |
| sap.m.ObjectHeader | ui5-title | basic | title, number, attributes and statuses; no intro, icon, markers |
| sap.m.ObjectListItem | ui5-li | basic | title, intro, number, icon; attributes and statuses are not shown |
| sap.m.RadioButton | ui5-radio-button | full | |
| sap.m.RadioButtonGroup | HTML/CSS | full | |
| sap.m.RatingIndicator | ui5-rating-indicator | full | |
| sap.m.ResponsivePopover | ui5-popover | basic | as Popover (no phone-fullscreen variant) |
| sap.m.Slider | ui5-slider | full | |
| sap.m.SuggestionItem | HTML/CSS | basic | |
| sap.m.TimePicker | ui5-time-picker | basic | |
| sap.m.ToolbarSeparator | ui5-toolbar-separator | full | |
| sap.ui.core.FragmentDefinition | HTML/CSS | full | |
| sap.ui.core.InvisibleText | none (no UI) | full | |
| sap.ui.core.SeparatorItem | ui5-option | basic | |
| sap.ui.core.mvc.View | HTML/CSS | full | |
| sap.ui.core.mvc.XMLView | HTML/CSS | full | |
| sap.ui.layout.form.Form | CSS grid + ui5-title | basic | |
| sap.ui.layout.form.FormContainer | ui5-title | basic | |
| sap.ui.layout.form.FormElement | ui5-label | basic |
"basic" = the members listed are rendered; any other property of the control
is accepted, ignored and logged (property: in the console), as the profile
requires.
Limits
- Not rendered: controls outside the portable profile (sap.ui.table,
sap.f, sap.uxap, sap.ui.comp, z2ui5.cc custom controls, ...) - visible box +
diagnostics; formatter functions other than the profile's
Formatter.Date*; named models other thandevice>; XML templating (template:repeat);CONTROL_BY_IDcalls andBINDING_CALL(excluded from the portable profile);prevent_default_expr; expressions outside the profile grammar (RegExp,odata.*). - Frontend actions the profile allows but this frontend does not run yet
(skipped and reported):
DOWNLOAD_B64_FILE,SCROLL_TO,SCROLL_INTO_VIEW,SET_FAVICON,SYSTEM_LOGOUT,STORE_DATA,KEYBOARD_SHORTCUT,PLAY_AUDIO,SET_SIZE_LIMIT(the last one MAY be a no-op). - Deviations from the UI5 rendering: SimpleForm is a two-column CSS grid
(Label opens a row, Title opens a group) rather than
ui5-form; MessageToast position options are ignored;DatePicker.dateValueis one-way (a formatter binding, as in UI5 - the edit travels throughvalue); growing renders on the client (all rows are in the model, as with UI5's JSON model). - NEST/NEST2 (profile v1.1) are rendered into the MAIN control the display names, appended to its content.
- Backend concurrency: the e2e tests run with one worker - the transpiled
framework in
@abap2ui5/node-runtimekeeps request state in static attributes, and two roundtrips interleaving in one Node process were seen to read each other's app data.
Development
npm run vendor -- /path/to/mcp-server [--ref <sha>]re-vendors the agent modules;npm run vendor:checkverifies them.node scripts/vendor-profile.mjs /path/to/protocol [--ref <rev>]re-copiesprofile/portable-v1.json(defaultorigin/main) and records the commit inprofile/source.json.node scripts/vendor-samples.mjs /path/to/samplesre-copies the demo apps listed indemo/apps.json;node scripts/record-fixtures.mjsre-records the views the renderer unit tests render.node scripts/generate-coverage.mjsregenerates the table above (npm testfails when it is stale).
See AGENTS.md for the repository rules and CHANGELOG.md for the history.
License
MIT
History
Other 6
Notes
First version.
- Core protocol client (
src/core/): app start with location andS_DEVICE, events withT_EVENT_ARGand the model delta of the edited paths (__deltarows for table cells), the draft id, the five view slots (response bookkeeping by the vendoredapplyResponse), POPUP/POPOVER torn down on anAPPchange, the app stack followed throughS_FRONT.APP, thePROTOCOLcheck, error texts of failed roundtrips with Restart, one roundtrip at a time with the queue-last and no-busy wire flags; fetch transport withsap-contextid, the CSRF token handshake, credentials and extra headers. - Renderer (
src/render/): view XML to UI5 Web Components through a control registry - all 65 controls of portable profile v1 plus 31 more; unknown controls as a visible box with their children still rendered, and a diagnostics panel / console /abap2ui5-diagnosticevent. - Bindings: paths, list bindings with templates, element binding,
two-way binding of value-like properties, typed display formatting,
expression bindings in the profile grammar (own parser, no eval),
composite parts, the
device>model; formatters as visible placeholders. - Frontend actions: message toast and box (incl. client-composed texts,
custom actions,
onClose), popup/popover close,SET_TITLE,START_TIMER,SET_FOCUS, clipboard, URL actions with the UI5 frontend's URL rules, theming, busy indicator. - Packaging:
dist/abap2ui5-wc.js(registers<abap2ui5-app>),dist/index.html(standalone start,?app_start=), on-demand chunks for icons, CLDR data and themes; embedding examples. - Demo and tests: 14 sample apps of abap2UI5/samples on
@abap2ui5/node-runtime1.146.0; Playwright tests of every app with a cross-check of the request bodies and models against the official UI5 SPA served by the same backend; unit tests on node:test and happy-dom; screenshots indocs/screenshots/; CI.
Others providing
- abap2UI5-localabap2UI5-localThe whole abap2UI5 framework folded into the local classes of one HTTP handler, so an app runs without the framework installed as a package.community org, abapabap2UI5 folded into the local classes of one HTTP handlerfrom ABAP
- abap2UI5abap2UI5One ABAP class implementing z2ui5_if_app is the whole app: the browser loads a generic UI5 shell once, and every interaction after that is an HTTP roundtrip back into ABAP.community org, abapUI5 apps written as one ABAP class, rendered by a generic shellfrom ABAP
- abap-cloud-guiabap-cloud-guiA report-style programming model for abap2UI5: one class produces a selection screen with a WRITE list or an ALV grid, running as a UI5 app on ABAP Cloud as well as on NetWeaver 7.02.independent, abapReport-style programming model for abap2UI5 on ABAP Cloudfrom ABAP
- custom-controlscustom-controlsThirteen custom controls for abap2UI5, a signature pad and a scanner that reads several barcodes at once among them, each one an ABAP builder class with a single render( ) method and all of them shipped in a BSP of their own.community org, abapThirteen custom UI5 controls for abap2UI5 appsfrom ABAP
- http-connectorhttp-connectorAn add-on that makes the abap2UI5 apps of one ABAP system reachable through another: a thin ICF handler on the consumer system forwards every roundtrip to the source system through an SM59 destination.community org, abapForwards abap2UI5 roundtrips to another system over HTTPfrom ABAP
- layout-managementlayout-managementAn abap2UI5 addon that renders an internal table or a structure as a UI5 table or form with a settings popup, where the user lays it out and saves the result as a layout variant.independent, abapTable and form layouts with saved variants for abap2UI5from ABAP
- abap2UI5 for Excelabap2UI5 for ExcelAn Office add-in that runs an abap2UI5 app in Excel's task pane, where the app reads and writes the workbook through the z2ui5.cc.ExcelBridge control.community org, abapOffice add-in running an abap2UI5 app in Excel's task panefrom ABAP
- abap2UI5-addons/popupsabap2UI5-addons/popupsReady-made dialogs for an abap2UI5 app: confirm, inform, select from a list, file up- and download, table, text edit, PDF, HTML, messages, range, value help and search help, each opened with one factory( ) call.community org, abapReady-made dialogs for abap2UI5 appsfrom ABAP
- rap-extrap-extFloorplan classes that read a CDS entity's UI annotations at runtime and render a list report, worklist, tree, object page, overview page, value help or action dialog as an abap2UI5 app.community org, abapFloorplans rendered from CDS UI annotations as abap2UI5 appsfrom ABAP
- selection-screenselection-screenSelect-options with saved variants for an abap2UI5 app, built from a database table name or from an internal table the app passes in.independent, abapSelect-options with saved variants for abap2UI5 appsfrom ABAP
- abap2UI5 frontendabap2UI5 frontendThe abap2UI5 frontend as installable ABAP artefacts: per system type one generated branch carrying the BSP or HTTP service with its handler, pulled into the system with abapGit.community org, abapabap2UI5 frontend as ABAP artefacts installed with abapGitfrom ABAP
- abap2UI5 Layout Editorabap2UI5 Layout EditorA browser editor that lays out a UI5 view by drag and drop and writes it out as one abap2UI5 app class, pulled into the system with abapGit.community org, abapDrag-and-drop UI5 view editor that writes an abap2UI5 app classfrom ABAP
- abap2UI5 protocolabap2UI5 protocolThe abap2UI5 roundtrip written down: a versioned specification of the wire between frontends and backends, JSON Schemas for its messages, and two conformance suites that test either side.community org, abapVersioned specification of the abap2UI5 roundtrip protocolfrom ABAP
- ZFPM_TOOLSZFPM_TOOLSA report that shows the development objects of an FPM hierarchy in one view and edits, copies, deletes, imports and exports the hierarchy as a whole rather than one object at a time.independent, abapEdits, copies and transports a whole FPM hierarchy at oncefrom ABAP
- ZWD_CALENDAR_VHZWD_CALENDAR_VHA value help for date fields in Web Dynpro ABAP screens that shows a calendar view, so the user picks a day from it instead of typing the date.independent, abapWeb Dynpro ABAP calendar value help for date fieldsfrom ABAP
- abap_mustacheabap_mustacheA Mustache template engine for ABAP, rendering logic-less templates into HTML or any other text from a structure or table of any type, with partials and a separate Steampunk-compatible branch.independent, abapMustache template engine for ABAPfrom ABAP
- @openui5/sap.ui.core@openui5/sap.ui.coreThe OpenUI5 core: the module loader, the MVC runtime, data binding, routing, theming and the test stack, which is everything a UI5 app does before a single community package is added.sap official, ui5Framework core: module loader, MVC runtime, binding, routing, themingfrom UI5
- ui5-webcomponents-bundleui5-webcomponents-bundleA custom bundle of UI5 Web Components built from the old playground's bundle definitions, served from GitHub Pages and loaded with one script tag.community org, ui5Custom UI5 Web Components bundle loaded with one script tagfrom UI5
- @ui5/tooling-webc@ui5/tooling-webcDeprecated UI5 Tooling extensions that generate UI5 library wrapper projects for UI5 Web Components and serve them during development; the README points to ui5-tooling-modules instead.sap official, ui5Deprecated UI5 Tooling extensions for UI5 Web Components wrappersfrom UI5
- @ui5/webcomponents@ui5/webcomponentsSAP's UI elements as standard custom elements, ui5-button among them, implementing SAP Fiori design and usable from plain HTML, React, Angular or Vue.sap official, ui5SAP's UI elements as standard custom elementsfrom UI5
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
“Frontend with UI5 Web Components – no UI5 core, one embeddable custom element” — abap2UI5/frontend-webcomponent — README
Contributors
History in the atlas
- First seen.
For your agent
- Ref
artifact:abap2ui5-frontend-webcomponent- JSON
- /artifacts/abap2ui5-frontend-webcomponent.json
- MCP
- Connecting an agent