onedevatlasBeta
Browse the atlas
AllCAPUI5ABAPBTP
CDS pluginCDS plugintypeInstalls into a CAP project and extends the runtime. CAP loads it through cds.requires or the plugin hook.See every one →What this type is →by SAPby SAPoriginPublished by SAP itself. A visible facet, never an input to a reading — a dormant official plugin reads exactly like a dormant independent one.See every one →

@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.

A CAP service view is a list of rows, and an analytical front end wants a cube with measures and dimensions it can name. This plugin is what SAP publishes for that: npm add @sap/cds-analytics puts what its README calls built-in support for embedded analytics in the project, and the one example it gives annotates a service @protocol: 'ina' and its view @ObjectModel.modelingPattern: #ANALYTICAL_CUBE and @ObjectModel.supportedCapabilities: [#ANALYTICAL_PROVIDER]. The README names the integration with SAP Analytics Cloud and stops at those annotations; for a multi-tenant scenario with extensibility it adds that the package is listed again in the package.json inside the mtx/sidecar directory. The package ships no repository and its licence is the LICENSE file inside it, so the npm entry is the whole of the documentation, down to CDS_ANALYTICS_DEBUG set to TRUE as the way to produce a log for SAP support.

npm10/wk

Facts

Latestv1.0.1ReleasedLicenceSAP DEVELOPER LICENSE AGREEMENT 3.2

Where it sits

Lives in
CAP
Provides
Analytical modelsCAPAnalytical modelscapabilityMarking 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](capability: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.
Flavors
Node.js
Requires
@sap/cds≥ 8@sap/cdsartifactThe peer range, as published.

Who is behind it

SAP SE

Before choosing this

Conditions

LicenceSAP Developer License Agreement 3.2 CAP§ 1, 2, 3A cds-plugin is used with SAP CAP materials, or an artifact is explicitly identified as a CAP plugin or application.
  • § 1 License. Productive customer applications are limited to SAP BTP or another SAP-licensed platform, and mass extraction to a non-SAP product is restricted except where solely required for SAP interoperability.
  • § 2 Intellectual Property. The agreement retains SAP's rights in the covered materials and limits making APIs, tools or software available to third parties, while preserving ownership of customer applications subject to SAP's underlying rights.
  • § 3 Artificial Intelligence Training. The agreement prohibits use of the covered materials and customer applications for training artificial-intelligence models or systems.
SAP Developer License Agreement 3.2 CAP →
PracticalFunctional boundary

Not in a project on CAP 7 or earlier: the package declares @sap/cds >=8 and @sap/cds-compiler >=5 as peer dependencies.

What it declares

Every artifact

Type
CDS plugin
Origin
By SAP
Runtime
Node.js

As a CDS plugin

Declared for
>=8
Distributed through
npm

Connections2

Download
@sap/cds-analytics connections@sap/cds-analyticsPROVIDES→ provides1provides stated Adds embedded analytics to a CAP project: a service view carries the annotations that mark it an analytical cube and an analytical provider, as the plugin's own example shows. @sap/cds-analytics — npm registry document, Usage: https://registry.npmjs.org/@sap/cds-analytics @sap/cds-analytics — npm registry document, Usage example: https://registry.npmjs.org/@sap/cds-analyticsAnalytical modelsNEEDS→ connects to1connects to stated The integration the plugin's own description names: the annotated service view is marked an analytical cube and an analytical provider for it. @sap/cds-analytics — npm registry document, README: https://registry.npmjs.org/@sap/cds-analytics @sap/cds-analytics — npm registry document, Usage example: https://registry.npmjs.org/@sap/cds-analyticsSAP Analytics Cloud

Install

npm add @sap/cds-analytics

Derived from the package name. No recipe recorded; the README has the configuration.

Where it sits in your app

Download
Your CAP applicationYour SAP BTP subaccount@sap/cds-analytics — npm registry document, README, checked 2026-10-19: “The `@sap/cds-analytics` package is a [CDS plugin](https://cap.cloud.sap/docs/node.js/cds-plugins#cds-plugin-packages) that enhances the SAP Cloud Application Programming Model (CAP) with built-in support for embedded analytics, enabling seamless integration with SAP Analytics Cloud.”connects@sap/cds-analytics, module@sap/cds-analyticsSAP Analytics Cloud, service instanceSAP AnalyticsCloud
SAPnot SAP's, or the project's ownstated in the document

README

quoted from @sap/cds-analytics@1.0.1 under SEE LICENSE IN LICENSE, read
@sap/cds-analytics@1.0.1/README.MDOn npm

CDS Enterprise Analytics Plugin

The @sap/cds-analytics package is a CDS plugin that enhances the SAP Cloud Application Programming Model (CAP) with built-in support for embedded analytics, enabling seamless integration with SAP Analytics Cloud.

Table of Contents

Setup

Install the plugin in your project:

npm add @sap/cds-analytics
Dependency added to package.json 
{
  // ...
  "dependencies": {
    // ...
    "@sap/cds-analytics": "^X.X.X"
  }
}

For multi-tenant scenarios with extensibility, ensure that @sap/cds-analytics is also listed as a dependency in the package.json within your mtx/sidecar directory.

Usage

To leverage the analytics features, annotate your CDS service views with the required properties. Example:

@protocol: 'ina'
@restrict: [{ grant: '*', to: 'authenticated-user' } ]
service FlightService {
  @ObjectModel.modelingPattern: #ANALYTICAL_CUBE
  @ObjectModel.supportedCapabilities: [#ANALYTICAL_PROVIDER]
  view FlightByAirport as select from my.Flight {
    // ...
  }
}

Support

If you experience issues with @sap/cds-analytics plugin, enable debug logging by setting the environment variable CDS_ANALYTICS_DEBUG to TRUE. Redirect the build output to a file and provide it to SAP support for troubleshooting and resolution.

Licensing

Copyright 2024 SAP SE or an SAP affiliate company and contributors. See LICENSE for details.

SAP DEVELOPER LICENSE AGREEMENT 3.2, read licence

History

Latest

v1.0.1

15downloads per week, npm
Weekly downloads for @sap/cds-analytics26 complete calendar weeks from 2026-04-20 to 2026-10-18; the latest total is 15.20 Apr – 26 Apr: 1427 Apr – 3 May: 134 May – 10 May: 1311 May – 17 May: 1018 May – 24 May: 125 May – 31 May: 71 Jun – 7 Jun: 98 Jun – 14 Jun: 715 Jun – 21 Jun: 622 Jun – 28 Jun: 729 Jun – 5 Jul: 46 Jul – 12 Jul: 513 Jul – 19 Jul: 820 Jul – 26 Jul: 1827 Jul – 2 Aug: 103 Aug – 9 Aug: 1810 Aug – 16 Aug: 2617 Aug – 23 Aug: 2024 Aug – 30 Aug: 2031 Aug – 6 Sept: 67 Sept – 13 Sept: 314 Sept – 20 Sept: 921 Sept – 27 Sept: 728 Sept – 4 Oct: 45 Oct – 11 Oct: 2112 Oct – 18 Oct: 15

Details

Sources3
npm registrydiscovered herechecked
npm registry, @sap/cds-analyticsversion, releases, installschecked
README.MDquoted, and what the entry declareschecked

Sources are graph entities: the same page may back several entries, and an unreachable source flags every row that rests on it.

Compatibility and provenance
runtimesnode
declared for>=8
latestv1.0.1
first release
releases and cadence1
discovered vianpm registry
first seen in the atlas
ecosystem and domaincap, protocols-and-apis
Flavors1
Node.js
“Install the plugin in your project: ```sh npm add @sap/cds-analytics ```” — @sap/cds-analytics — npm registry document, Setupchecked
History in the atlas1
  1. First seen.
For your agent
Ref
artifact:sap-cds-analytics
JSON
/artifacts/sap-cds-analytics.json
MCP
Connecting an agent