Concept card

SAC Custom Widgets

As of 2026-07-23

Edited by Cédric-Olivier Mâry, sole editor and publication director — 27 years in the SAP ecosystem. How these pages are produced, and where automation is used.

What is SAC Custom Widgets?

SAC Custom Widgets are worth building only when a visualisation gap is real and recurring across many Stories — a self-contained Web Component a typical developer ships in 2-3 days, but each SAC release can break.

What it is

SAC Custom Widgets are the developer-grade extensibility surface that lets a consultant ship visualisations and interactive components SAC does not provide out of the box — Sankey diagrams, custom maps with non-standard projections, third-party charting libraries (Highcharts, AmCharts), animation-rich displays, or specialised input forms. They are the answer to 'the standard SAC chart doesn't do what we need' without abandoning SAC and rebuilding the application elsewhere.

What a Custom Widget actually is. Technically it is a self-contained JavaScript bundle, packaged as a Web Component, that SAC loads at runtime into Analytic Applications. The widget exposes properties (configurable in the SAC Application Designer like any standard widget), events (firable to scripting code), and methods (callable from scripting code). It receives data from SAC via a defined contract — bound to a dataset or model — and renders into its allotted canvas region. Authentication, data fetching, and lifecycle are all SAC-managed; the widget only owns its render.

Why it matters

The widget only owns rendering — authentication, data fetching, and lifecycle stay SAC-managed via a defined properties/events/methods contract.
For a one-off visualisation, an R-Visualization or a static image embed is cheaper than building and maintaining a custom widget.
A fleet of custom widgets is a real maintenance liability, since every SAC release can potentially break them — factor that into the build-vs-buy decision.

Key points

Web-Component-based — self-contained JS bundle SAC loads at runtime into Analytic Applications; framework-agnostic (vanilla JS, React via wrapper, Lit).
Three surfaces — Properties (designer-configurable), Events (firable to scripting), Methods (callable from scripting); same contract as any SAC widget.
SDK + CLI — SAP-provided templates, build tool, local-preview server; first widget 2-3 days end-to-end for a competent JS developer.
Tenant-level deployment — uploaded once to the Custom Widget repository; available to every Analytic Application in the tenant.
Maintenance burden — every SAC release can break the widget; budget for regression testing per release.
SAC Custom Widgets is mastered only when it changes a named buyer decision.
Start with the semantic contract and control model before demonstrating the tool.
Use current SAP, analyst, study, KG, and news signals as evidence, not decoration.
Separate verified facts from directional trends and modeled assumptions.
Define owner, metric, threshold, support path, and rollback before scaling.

Terms used on this page

Custom Widget: A SAC extensibility surface — a Web-Component-packaged JS bundle that SAC loads at runtime into Analytic Applications; lets developers ship visualisations and components SAC does not provide natively.
Web Component: A W3C standard for self-contained UI components — Custom Elements + Shadow DOM + HTML Templates; the technical foundation of SAC Custom Widgets.
Custom Widget SDK: The SAP-provided developer kit — templates, CLI tool, local preview server, debugging utilities; the official path for building widgets that meet SAC's runtime contract.
Tenant repository: The SAC tenant-level store of uploaded Custom Widgets; once a widget is in the repository, it is available to every Analytic Application designer in the tenant.
Decision owner: The accountable person who accepts the trade-off and funds the next action.
Semantic contract: The shared definition of business terms, metrics, entities, and access rules used by tools and teams.
Control plane: The layer that applies policy, access, lineage, monitoring, and escalation across the operating model.
Evidence grade: A label that separates verified fact, directional signal, modeled assumption, and field observation.

Sources

Full card available to members. What the full card adds: the full decision framework · the SAP vs Snowflake / Databricks / Fabric comparison · the common pitfalls and their fix · the cheat sheet · the architecture schemas · the code blocks.

Open in the app →