Everything in the atlas
Type
Domain
Origin
Signals: 2
Content
More
Group by: Capability
Monorepo of CAP's SQL database services
Placeholder package under a CAP annotations name, no annotations
The manifest calls it a dummy library exposing custom CDS annotations, but the published contents are a one-line README, a single exported barrier() whose body is throw Error("not yet implemented"), and no .cds file at all — there is nothing to import and nothing to annotate with. No repository, one release, May 2025.
Cloud Foundry topology cache for the other @saptools packages
Scaffolded UI5 TypeScript app consuming the JSX runtime
It shows the wiring and a converted view pair, not the runtime's API surface; the directives, the plugin SPI and the binding forms are demonstrated in [@ui5-community/jsx-runtime-showcase](artifact:ui5-community-jsx-runtime-showcase) instead.
Showcase and documentation app of @ui5-community/jsx-runtime
Its views are not a template for application code: every showcase view overrides `getController()` to return itself so a sample stays readable in one file, and the gotchas page says not to ship that in production, where a view keeps a separate `*.controller.ts`. Routing from a sample, an `ODataModel` v2 or v4, `sap.ui.mdc.Table`, forms and custom control authoring in TSX are absent by decision and documented as deferred.
129 abap2UI5 sample apps, one ABAP class each
A sample that needs something the system provides is not here — the samples-stack repository holds the OData, RAP, WebSocket and launchpad demos, and samples-controls the rebuilds of the UI5 Demo Kit originals. Every class in `src/` keeps to controls and properties available since UI5 1.71 and not deprecated, apart from two clipboard samples marked `(UI5 1.119+)`, so a newer control is not demonstrated here. Numbers are handed out per repository and reused across the three, so `493` alone does not name a sample: `Z2UI5_CL_SMP_APP_493` is the Hello World here.
Eleven abap2UI5 apps, one per open-source ABAP library
Not on ABAP Cloud: most of the libraries use APIs that are not released there, and the repository has no ABAP Cloud gate yet. Not beyond a development system without authorisation checks added first — the samples carry none of their own, the abap-fm-logger sample reads the log table `ZAFL_LOG` with whatever the logged calls received and returned, and the abap_fm_json sample calls function modules, limited to a hard-coded whitelist.
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.
abap2UI5 apps in front of OData, RAP, events and other technology
Not the place to learn abap2UI5 itself: every package starts from a technology the system already provides, and the framework basics and the control gallery are the other two sample repositories, abap2UI5/samples and abap2UI5/samples-controls. Three packages are out of reach on ABAP Cloud, and `05` needs the 2021 release that carries RAP business events.
GUI controls for ABAP transpiled to JavaScript
Concurrent and cross-session locking for open-abap on PostgreSQL
Neither the package manifest nor the repository tree declares a licence.
Template pairing a FastAPI service with ABAP reports that call it
CAP agent writing reports into a shared SDM document workspace
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.
Docker Compose IoT edge stack that connects to SAP BTP
Release and repository quiet for 36 months.
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.
Demo CAP bookshop with server-rendered UI5 views
No license Neither the package manifest nor the repository tree declares a licence.
Functional boundary As a deployment template it stops at the service: the `mta.yaml` has one module, `gen/srv` on the Node.js buildpack, and no HTML5 repository or router module for the app.
npm library parsing SAPUI5 and project UI5 class metadata
A project nested inside another is not parsed: its README says nested projects are not supported any more. A library installed from npm is read only when it ships its `-dbg.js` files and `manifest.json`.
