Everything in UI5 / Fiori elements
Type
Domain
Origin
Signals
Content
Fiori elements: Answers in Fiori elements
More
Group by: Type
Local ABAP server serving /IWBEP/ OData v2 without an SAP system
Not a system to run a business application on: there is no business application in it, and what it implements of the language, the dictionary and Gateway is a stated subset of each. It is a clean-room reimplementation of the `/IWBEP/` interfaces that bundles no SAP source and no standard DDIC, so a service that reads standard objects has nothing to read, and `ANORMALIES.md` records every place the runtime differs from SAP before any workaround is written.
Live reload middleware for the UI5 dev server
Playback-only SAP Companion (Help4) workarea served from CAP
Not behind a managed approuter: SAP Build Work Zone does not expose the `/$companion/**` routes, so Companion never reaches CAP, and the README names managed approuter and Work Zone as out of scope for v1. Not where help has to be authored in a browser, since the editor, the producer and writes are absent and content lives in files the plugin compiles.
Pro-code CLI for building and deploying Joule Studio solutions
UI5 Tooling command line for project setup, dev server and build
Groups npm audit findings by root dependency, with failing thresholds
It audits through npm: a project that resolves its dependencies with another package manager, or has no `package.json`, has nothing for it to run. What it reports is what `npm audit` knows, so a vulnerability outside the npm advisory data is not in its table.
Shows which feature branches reached which environment branch
A team that does not keep one long-lived branch per environment has no environment branches for it to compare feature branches against. What it reports is the merge state of branches in Git, so it says nothing about whether a merged change has been built or deployed to the environment.
Rust CLI and desktop app for exploring SAP OData services
Its README calls it early-stage — the core workflows run end-to-end against real systems and packaging, documentation and polish are stated as still evolving. A Rust binary rather than an npm install, so the platform build matters.
Local desktop workspace for AI conversations with SAP connectors
MCP server for creating and editing Fiori applications
MCP server for UI5 development with ten tools
It reads a UI5 project and the framework's own documentation, not a running system or a backend: a question about the service behind the app is answered somewhere else. Node.js v20.17 or v22.9 and above.
MCP server searching seventeen SAP documentation repositories
It reads documentation, never a system: nothing in it opens a package.json, a CDS model or an ABAP client, so a question about what your own project does has to be answered elsewhere. The offline half is only as fresh as the submodules the last build pinned, and the index answers where something is written down rather than which of two packages fits a task.
Hosted MCP server of developers.sap.com tutorials and missions
UI5 custom control that runs an abap2UI5 app inside a host app
The page and the [abap2UI5](artifact:abap2ui5-abap2ui5) service have to share an origin: an `endpoint` that resolves to another origin is refused, and abap2UI5 rejects a POST whose `Origin` names another host. A host that routes by the URL hash, such as a Fiori elements app or an app with a UI5 router, needs abap2UI5 1.146.0 or later, because 1.145.0 clears the host's hash after every roundtrip. One frontend per page: the first control that starts decides which endpoint the frontend comes from.
Writer module for changing a CAP project's configuration from code
There is nothing to run: it is published for a generator or a script to call, not for a developer to invoke in a project, and it declares Node.js 22 or later.
Writer of flexible programming model elements into Fiori elements apps
Thirteen custom UI5 controls for abap2UI5 apps
Needs Standard ABAP 7.50 or higher, and an abap2UI5 whose frontend reserves the resourceRoot `z2ui5_cci`: a frontend predating that rename reserves `z2ui5ccc` and cannot resolve the controls. Frontend artefacts only one company needs, such as an in-house reuse library, a corporate icon font or company CSS, are what [abap2UI5-addons/custom-controls-customer](https://github.com/abap2UI5-addons/custom-controls-customer) is for, the same mechanism under the second reserved root `z2ui5_ccc`. ExportSpreadsheet needs SAPUI5: under OpenUI5 `sap.ui.export` is missing and the button renders disabled.
Puts a number from an abap2UI5 app on a Fiori launchpad tile
There is nothing here for ABAP for Cloud: the requirements name Standard ABAP releases only, and a CDS/SADL based OData service for `ABAP for Cloud` compatibility stands under Limitations & Todo.
UI5 component adding a spreadsheet upload dialog to Fiori apps
UI5 control library of sized sap.m controls and touch inputs
UI5 control library for file upload and download in front of CAP
wdi5 selectors for locating controls in Fiori Elements apps
Archived The declared repository is archived.
No license Neither the package manifest nor the repository tree declares a licence.
End-to-end testing for UI5 on WebdriverIO with UI5 control selectors
Where the login cannot be completed by configuration. Its authentication page states that multi-factor authentication is not supported, because a media break between browser and phone cannot be managed out of the box.
Versioned specification of the abap2UI5 roundtrip protocol
Neither suite has been run against an ABAP system: the reference backends are the framework transpiled to Node and cap2UI5 on CAP, so what a check does on a real system is open. The portable profile is a subset of 61 controls, filled from a census of 247 core apps of which 64.8 % run unchanged, so an app outside it renders placeholders in the terminal and Adaptive Cards renderers.
UI5 Demo Kit samples rebuilt as abap2UI5 apps
The 221 ports under `src/02` need a UI5 runtime newer than 1.71: they install and activate on any release, and on an older UI5 the newer control does not render. The `src/03` collection is hand-written for SAPUI5-only controls and needs a SAPUI5 bootstrap. There are no per-library branches, so pulling the whole repository is the one way in and the activation takes a few minutes.
Showcase for dev-approuter in front of two UI5 apps
Template and mock runtime for S/4HANA Variant Configuration UIs
Samples for the six extension types of SAP Digital Manufacturing
Nothing here runs on its own: a plugin sample needs a Digital Manufacturing tenant to be uploaded into, and the integration samples need a Cloud Integration tenant plus an ERP system, or a mock server as the outbound example uses, before they do anything.
CAP and SAPUI5 demo of recovery from a supply disruption
No license Neither the package manifest nor the repository tree declares a licence.
Functional boundary The data is illustrative: availability is binary and backup capacity unlimited, and the model carries no inventory; nothing in it is forecast or priced. The recall half runs only against classic ABAP, because its openCypher trace goes through ADBC, which is not released for ABAP Cloud, and it expects an SSH tunnel to the A4H system it was built against. A plain `npm start` passes no model key, so the agent cannot be used on a server started that way.
Todo app with CAP and SAPUI5 in TypeScript over OData V4
Neither the package manifest nor the repository tree declares a licence.
Three Fiori apps wired to one cross-app navigation intent
Neither the package manifest nor the repository tree declares a licence.
CAP sample drawing a material BOM as a UI5 network graph
Neither the package manifest nor the repository tree declares a licence.
CAP bookshop showing UI5 development with cds-plugin-ui5
Template repository for own UI5 artefacts served to abap2UI5
Exercises building a Fiori elements app from Figma via MCP servers
TechEd 2022 workshop mixing SAPUI5 with Fiori elements building blocks
TechEd 2025 workshop driving a Fiori elements app from Figma via MCP
UI5con 2025 tutorial on SAPUI5 flexibility and key user adaptations
UI5con tutorial on Fiori elements apps with AI assistants and MCP
CAP Risks and Mitigations project with a Spreadsheet Upload button
Product-review screen consuming ui5-cap-ai-features on CAP
Neither the package manifest nor the repository tree declares a licence.
UI5 apps calling CAP OData actions and functions from custom code
Neither the package manifest nor the repository tree declares a licence.
Ten exercises on the Fiori elements mock server middleware
Neither the package manifest nor the repository tree declares a licence.
Session building a travel dashboard with Fiori elements and SAPUI5
Fiori Innovation Day session building a travel dashboard
Fiori Innovation Day exercises on Fiori elements with MCP servers
Joule's generative AI inside SAP Build Code
Managed hosting and routing for built frontends
SAP's own guidance is narrower than the service's reach: it names standalone, single-tenant applications that do not connect to other applications as the fit, and says to stay on [the HTML5 Application Repository](artifact:btp-html5-application-repository) and the application router where those meet your needs better. Four hard limits decide it before taste does — 300 requests per second per subaccount, ten retained versions per application, 100 MB per application and 400 MB for the deployment archive.
Development environment on BTP for UI5, Fiori, mobile and CAP
Role-based portal sites with pages, apps and widgets
Predefined CI/CD pipelines for SAP development projects
APIs and a UI5 component for document management in apps
Stores UI5 and HTML5 apps and serves them through the approuter
One inbox for tasks across SAP applications and BTP workflows
IDE service on SAP BTP for SAPUI5, Fiori and full-stack apps
Key-user adaptation and personalisation for UI5 apps on SAP BTP
Collection of 41 agent skills, 37 for SAP development tasks
SAP skills for the Kiro IDE
Host-specific: outside Kiro the automatic context activation is the part that does not come with it, and what remains is prose you would have to wire in yourself. Breadth over depth by design — thirty-five skills across six product areas is an orientation layer, not a substitute for the focused sets in each.
Agent skill built from the Fiori Design Guidelines
Forty SAP development plugins for coding agents
GPL-3.0, which is a licence to read before vendoring any of it into something you ship. Forty plugins is also a lot of always-available surface — the ledger is there because breadth and verification pull in opposite directions, and it does not resolve that so much as report it.
UI5 plugins for coding agents
Guidance, not access: these are instructions handed to an agent, and what the agent can then read of your project comes from [@ui5/mcp-server](artifact:ui5-mcp-server) or the editor. A modernisation workflow that runs autonomously across a codebase is also a thing to point at a branch rather than at main.