SAP Support Radar

SAP Support Radar

🚀 Try it out: open the app

Check the support/maintenance status of the SAP products and versions you actually use against the official SAP Product Availability Matrix (PAM) — no backend, nothing uploaded leaves your browser.

Built with OpenUI5 and TypeScript. Full documentation, architecture, and Architecture Decision Records live in the docs site (built with VitePress — run npm run docs:dev locally, or see the deployed site once published, per ADR 0011).

Why not just use SAP Solution Manager or SAP for Me?

SAP already offers this for your own products via SAP Solution Manager or SAP for Me. The SAP Support Radar fills a narrower gap instead.

What it does

• Load the full SAP PAM export (your own CSV, converted locally — see below) into the browser.
• Mark a subset of entries as your own product landscape.
• View a dedicated "Support status of my products" page, filtered to just those, with visual highlighting of approaching end-of-mainstream-maintenance/end-of-maintenance dates.
• Drill into any product's full lifecycle, from "restricted available" to "end of maintenance".
• Query the same data from an LLM client via the bundled pam-mcp-server MCP server.

See docs/index.md for the full project goal, and docs/workflow.md for a page-by-page tour with screenshots.

Screencast

A quick walkthrough: search for a product, add it to your own landscape, then check its support status — see tests/screencast.md for the exact steps.

From zero to a running app

Assumes a fresh checkout — no webapp/model/PAM.json yet, just a pv CSV export (SAP's PAM export format) in the repository root. See docs/index.md § Download the PAM export from SAP for how to obtain that file from the SAP Support Portal if you don't have one yet.

# 1. Install dependencies
npm install

# 2. Convert the CSV export into the JSON the app reads (pv -> webapp/model/PAM.json)
npm run pam:import

# 3. Static checks: eslint, ui5lint, and type-checking (app + scripts/)
npm run lint

# 4. Build the app -> dist/
npm run build

# 5. Unit tests for scripts/ (type-checks scripts/ again first)
npm run test:scripts

# 6. One-time: install the Playwright browser used by the e2e suite
npx playwright install --with-deps chromium

# 7. End-to-end tests + code coverage report (coverage/)
npm run test:e2e:coverage

# 8. Remaining reports: SBOM (sbom-report.dev.html / sbom-report.prod.html) and Allure (allure-report/)
npm run sbom:report
npm run test:e2e:allure:generate

# 9. Start the app
npm start                  # dev server with live reload, http://localhost:8080/index.html
# or, to serve the dist/ build from step 4 instead:
npm run start:dist

Optional: regenerate the e2e visual-regression screenshots

Only needed after a change that affects what the app visibly renders (see Build toolchain → Linux baselines (for CI) for why both platforms are needed):

npm run test:e2e:update-snapshots          # macOS/local-OS baselines (tests/e2e/*-darwin.png)
npm run test:e2e:update-snapshots:linux     # Linux baselines via Docker/Podman (tests/e2e/*-linux.png)

See docs/build-toolchain.md for what each of these commands actually does and the full list of available scripts.

Project layout

License

Apache License 2.0 — see LICENSE.