Learning & Reference
What to read before writing code: the documentation, the conventions, and the reference applications that show a whole thing working.
Capabilities
Compare the concerns mapped here and open an ecosystem for its assessment. Artifact counts show providers; content counts show items linked directly to the capability.
Each ecosystem hexagon shows its own coverage assessment. Coverage is never combined across ecosystems.
Artifacts
Providers, examples and other artifacts mapped to this domain, from SAP and the community. Each artifact appears once.
The tools are documented as meant for AI models and not a stable API, so anything built to parse `cds-mcp` output rather than to feed a model can break between releases. Its corpus is the CAP documentation, so Fiori elements, BTP service or ABAP questions are not in what `search_docs` indexes.
It answers from documentation and never opens your project, so it cannot tell you whether the component you are asking about is the one your application already uses. Node.js v20.17 or v22.9 and above; on Windows the command needs a `cmd /c` prefix.
Not reachable since 2026-10-20.
The Markdown is a snapshot of whatever help.sap.com served when the pipeline last ran, and the Standard library is scraped from the `latest` index, so which release a page describes follows from the scrape date rather than from anything the corpus states. `package.json` states ISC and the repository carries no LICENSE file, so what the copied SAP documentation may be used for is not stated in it.
A `SELECT` from a business table has nothing to select from: the database in the page holds the framework's own tables, and nothing can reach outside the browser, so an app that reads a system's data cannot be tried here. Only the UI5 libraries built in are available and a control from anywhere else will not load; what the transpiler cannot compile is reported in the output panel rather than run. State lives in the tab — a reload, and a press of Run, starts over on a fresh database.
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.
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.
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.
No published releases; repository quiet for 31 months.
Neither the package manifest nor the repository tree declares a licence.
Neither the package manifest nor the repository tree declares a licence.
It calls the OpenAI API directly with a key in the environment. It was written in early 2023 and last touched in May 2023, which is before SAP AI Core and the CAP LLM plugins existed — so read it for the shape of the application, not for how a CAP service should reach a model today.
Last released April 2024.
Not reachable Not reachable since 2026-10-20.
Functional boundary The Level A–D grade merges SAP's two published files in the tool's own engine: it is an orientation rather than an ATC result and is left out of the signed audit pack, and the repository documents state by state where the grade is expected to differ from what the clean core ATC check reports. Nothing here runs ABAP Unit — on the RAP track that result is recorded from your own SAP system, and generated CAP tests run against mocks in an isolated runner rather than in a real SAP S/4HANA system. Tenants, organisation accounts, single sign-on, a self-hosted edition and write access through an API are deliberately not built, and one account has five analysis runs before a Gemini API key of its own is needed.
This is the legacy edition, for on-premise systems from SAP_BASIS 7.40. On ABAP Cloud, [the Cloud Edition](artifact:sap-code-pal-for-abap-cloud) is the one that runs.
No published releases; repository quiet for 67 months.
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.
Neither the package manifest nor the repository tree declares a licence.
The maintainer states it is unofficial, not endorsed by SAP, and that it uses authenticated Hub web and catalogue endpoints and browser session cookies in ways SAP's terms of service, SAP account terms or an organisation's own policies may restrict. The same README asks the reader not to use it for production, broad distribution or shared access without explicit approval, and says that installing it grants no permission to automate SAP services.
Neither the package manifest nor the repository tree declares a licence.
It needs an S-user with SAP Support Portal access, so there is nothing to search without a support contract behind the login. The maintainer states it uses private SAP APIs behind authentication, asks the reader to check whether that use breaches SAP's terms of service, and disclaims both liability and any guarantee that it keeps working. MFA is handled only by typing the code into a visible browser, so a headless deployment cannot complete a login that demands one.
What it returns is planning material, not a commitment, and the monorepo labels the server's role "future/planned features (planning only)". The maintainer also states it is unofficial, not endorsed by SAP, and that it uses authenticated Road Map Explorer web endpoints and browser session cookies in ways SAP's terms of service or an organisation's policies may restrict, with production, broad distribution and shared access called out as needing explicit approval. An account that requires MFA has to be bootstrapped once through a visible browser.
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.
Neither the package manifest nor the repository tree declares a licence.
No license Neither the package manifest nor the repository tree declares a licence.
Functional boundary It reports what the change log says, not what your application uses, so it cannot tell you which of the listed changes touches your code. The repository carries no licence file, which leaves the code itself with no grant attached even though the hosted app is open to use.
Content
Content includes reference architectures. Each item appears once; filter by type to narrow the list.
Recent changes
- Clean code conventionscore coverage revised
Reassessed against the graph (check:capabilities): FORMfactor, an independent ABAP generator, provides this capability, so the community is present on the door.
- Documentationcore coverage revised
Reassessed against the graph (check:capabilities): the note counted providers and said what_core_does was empty, which it no longer is; a provider that documents a custom program changes the shape of the community answer.
- Documentationcoverage by ecosystem revised
Reassessed against the graph (check:capabilities): independent providers sit on this door (ui5-lib-diff, vscode-ui5-api-reference, and mcp-sap-docs, which serves ui5), so the stated core-only contradicted the providers.
- Documentationcoverage by ecosystem revised
Reassessed against the graph (check:capabilities): servers over the API Business Accelerator Hub, SAP Notes and the roadmap arrived, so "each points at one repository" and "both providers" were no longer true.
- Documentationcoverage by ecosystem revised
Reassessed against the graph (check:capabilities): community providers arrived that the note never named. The state stays core-and-community, because the core is the platform and the block states the ADT ABAP Doc export with its source.
- Documentationcore coverage revised
Package pass 2026-09-27: the capability had no paragraph and no source at all.
- Reference appscore coverage revised
The note asked to be corrected once an official sample was entered, and SAP-samples repositories are now entered. They demonstrate rather than provide (VISION §5), so the state stays community-only; the note and where_it_stops said the indexed samples were all independent, which stopped being true.
- Reference appsecosystems revised
Two SAP-samples repositories in this batch are whole applications on other doors: hana-shine-xsa, SHINE for XS Advanced on SAP HANA, and btp-abap-cna, a RAP side-by-side extension on SAP BTP ABAP Environment. Both are samples, so each door opens unmapped.
- Documentationecosystems revised
Two documentation servers over BTP and AI Core corpora entered from the sap-ai-mcp-servers sweep.
- Documentationecosystems revised
Artifacts that answer this concern sat behind the ABAP door with no tile to appear under, so browse counted them and rendered nothing. The concern is one a ABAP developer actually decides there, which is the test for opening a door rather than trimming a serves claim.