PackagePackagetypeA library you install and call yourself.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-common-content

ISO-standard content for CAP's common definitions — countries, languages, currencies and timezones — so a project does not seed those tables itself.

Facts

Latestv3.2.0ReleasedLicenceSAP DEVELOPER LICENSE AGREEMENT 3.2 CAP

Where it sits

Lives in
Provides
Data modellingCAPData modellingcapabilityDefining the shape of data before anything serves it: entities and their types, how they relate, and the projections and views that services and applications consume.Seed dataCAPSeed datacapabilityGetting realistic data into a service so it can be developed and demonstrated — initial data, per-tenant content, and believable volumes for testing.Service compositionCAPService compositioncapabilityBuilding one solution out of parts other projects published: a reuse package brings its models, code, initial data and texts into your project through npm or Maven, you serve what you reference and extend what you import, and the same modules deploy as one application or as several on a shared database. Distinct from [service integration](capability:service-integration), which reaches a service that stays deployed elsewhere, and from [tenant extensibility](capability:tenant-extensibility), which is a subscriber extending a running SaaS.
Flavors
Requires
@sap/cds≥ 7.7.0@sap/cdsartifactThe peer range, as published.

What it declares

Every artifact

Type
Package
Origin
By SAP

As a package

Declared for
>=7.7.0
Where it runs
Inside its host
Distributed through
npm

Connections3

Install

npm add @sap/cds-common-content

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

README

quoted from @sap/cds-common-content@3.2.0, read
@sap/cds-common-content@3.2.0/README.mdOn npm

CDS Common Content

This package holds default content based on the ISO specification for the following CDS common definitions:

The codes names and descriptions are translated into the most important SAP supported languages.

excerpt, SAP DEVELOPER LICENSE AGREEMENT 3.2 CAP, read licencethe rest, on npm

History

Latest

v3.2.0

Changed 1

  1. v3.1.0

    Changed 1

  2. v3.0.1

    Changed 1

  3. v2.1.0

    Features 1

  4. v2.0.0dated in the atlas

    Removed 1

  5. v1.4.0

    Features 1, Changed 1

  6. v1.3.1

    Fixes 1

  7. v1.3.0

    Changed 1

  8. v1.2.0

    Features 1

  9. v1.1.0

    Changed 1

  10. v1.0.1

    Fixes 1

  11. v1.0.0

    Fixes 1

  12. v0.2.0

    Features 1

  13. v0.1.1

    Fixes 2

  14. v0.1.0

    Features 1

4,227downloads per week, npm
Weekly downloads for @sap/cds-common-content26 complete calendar weeks from 2026-04-20 to 2026-10-18; the latest total is 4227.20 Apr – 26 Apr: 7,11727 Apr – 3 May: 6,0144 May – 10 May: 6,80211 May – 17 May: 7,14018 May – 24 May: 7,75425 May – 31 May: 7,8321 Jun – 7 Jun: 6,1088 Jun – 14 Jun: 8,52615 Jun – 21 Jun: 9,25922 Jun – 28 Jun: 7,77929 Jun – 5 Jul: 6,9026 Jul – 12 Jul: 6,77913 Jul – 19 Jul: 8,72120 Jul – 26 Jul: 9,34527 Jul – 2 Aug: 8,7853 Aug – 9 Aug: 8,76410 Aug – 16 Aug: 7,64217 Aug – 23 Aug: 9,33224 Aug – 30 Aug: 9,61831 Aug – 6 Sept: 8,9337 Sept – 13 Sept: 5,88914 Sept – 20 Sept: 5,88021 Sept – 27 Sept: 7,59828 Sept – 4 Oct: 8,9225 Oct – 11 Oct: 7,58212 Oct – 18 Oct: 4,227

Others providing12

Data modelling
  1. ABAP CDSModelling layer of ABAP Cloud above database tablesfrom ABAP
  2. cds-numberrange-pluginFills a CDS element from a database-backed number rangefrom CAP
  3. cdsanalyserMaps database tables and fields to the CDS views exposing themfrom ABAP
  4. com.sap.cds:cds-services-bomMaven bill of materials pinning CAP Java module versionsfrom CAP
  5. @sap/cds-compilerCompiler from CDS models to CSN, EDMX and database schemasfrom CAP
  6. @sap/cdsCAP Node.js runtimefrom CAP
  7. cap-user-infoUser details and quickview links for createdBy and modifiedByfrom CAP
  8. CDS Field MappingMaps classic dictionary tables and fields to CDS entities and fieldsfrom ABAP
Seed data
  1. @animb1996/cds-data-driftCompares a CAP project's CSV data with its database rowsfrom CAP
  2. cap-js-mockdataCSV seed data generated from @Mockdata annotations with Fakerfrom CAP
  3. @sap/cdsCAP Node.js runtimefrom CAP
  4. abapFakerFake data generator for ABAPfrom ABAP
  5. cap-mock-generatorFills db/data with relationally consistent CSV from a .cds schemafrom CAP
Service composition
  1. com.sap.cds:cds-services-bomMaven bill of materials pinning CAP Java module versionsfrom CAP
  2. @sap/cdsCAP Node.js runtimefrom CAP

Details

Sources4
npm registrydiscovered herechecked
The discovery passdiscovered herechecked
npm registry, @sap/cds-common-contentversion, 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
declared for>=7.7.0
latestv3.2.0
first release
releases and cadence11, ~136d median
discovered vianpm registry, The discovery pass
first seen in the atlas
ecosystem and domaincap, data-and-persistence
Flavors1
Node.js
“Install this module in your CDS Node.js project:” — @sap/cds-common-content — npm READMEchecked
History in the atlas4
  1. A CAP package was pointing at the ABAP data-modelling capability because it was the only one named Data modelling — the CAP one did not exist. Repointed when it did. The mis-edge is the clearest evidence the gap was real.
  2. Typed cds-plugin by placement, which defaults every candidate to that. It is not one.
  3. ISO-standard content for CAP's common definitions — countries, languages, currencies and timezones — so a project does not seed those tables itself.
  4. First seen.
For your agent
Ref
artifact:sap-cds-common-content
JSON
/artifacts/sap-cds-common-content.json
MCP
Connecting an agent