Analytical models

Marking up a CDS model so an analytical front end can read it as a cube rather than as a list of rows, and serving it over the protocol that front end speaks. Separate from Analytical queries, which is the query shape an OData client issues against the same service: here the question is what the service declares itself to be.

Overview

SAP SHIPS
Node.js →

@sap/cds-analytics CDS plugin that adds embedded analytics to a CAP project, so a service view can be annotated as an analytical cube for SAP Analytics Cloud.

Not covered: At the CAP side of the wire. The package documents the annotations a view carries, the dependency an mtx/sidecar needs in a multitenant project and a debug variable; what SAP Analytics Cloud is then modelled to do with the cube is not part of it.

Assessed from the package's own npm entry rather than from capire: the CAP Plugins page lists nineteen plugins and this is not among them, so no page in the core documentation states an intent here.

THE COMMUNITY ADDS

No community artifact is documented here.

Artifacts1

1 of 1 artifacts
ArtifactSignals
CDS plugins1
@sap/cds-analyticsCDS plugin adding embedded analytics to CAP for SAP Analytics Cloud
Signals
Functional boundary

Details

Coverage
For your agent
Ref
capability:analytical-models
JSON
/capabilities/analytical-models.json
MCP
Connecting an agent