@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
Where it sits
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
Connections
Defining entities, their relations and the views services consume
Getting realistic data into a service for development and demos
Building one solution from reuse packages other projects published
Download
Install
npm add @sap/cds-common-contentDerived from the package name. No recipe recorded; the README has the configuration.
README
quoted from @sap/cds-common-content@3.2.0, readCDS 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.
History
Others providing
- ABAP CDSABAP CDSThe modelling layer of ABAP Cloud — view entities, projections and annotations defined above database tables, delivered with the platform rather than installed.sap official, abapModelling layer of ABAP Cloud above database tablesfrom ABAP
- cds-numberrange-plugincds-numberrange-pluginA CAP plugin that fills an annotated CDS element with the next number from a named range, optionally with prefix, suffix and padding, keeping the counter in a database entity it adds to the model.independent, capFills a CDS element from a database-backed number rangefrom CAP
- cdsanalysercdsanalyserA search tool that maps SAP database tables and fields to the CDS view entities that expose them, and back, from an index a background job builds, for SAP S/4HANA on-premise or private cloud.independent, abapMaps database tables and fields to the CDS views exposing themfrom ABAP
- com.sap.cds:cds-services-bomcom.sap.cds:cds-services-bomThe Maven bill of materials for CAP Java, pinning every com.sap.cds module in a release, from the API and core runtime to the Spring Boot starters and the CQN engine, to the same version.sap official, capMaven bill of materials pinning CAP Java module versionsfrom CAP
- @sap/cds-compiler@sap/cds-compilerCompiles CDS models to CSN, EDMX and database schemas.sap official, capCompiler from CDS models to CSN, EDMX and database schemasfrom CAP
- @sap/cds@sap/cdsThe CAP Node.js runtime, which compiles the CDS model, serves the services declared in it, answers generic requests before any handler runs, and loads every cds-plugin.sap official, capCAP Node.js runtimefrom CAP
- cap-user-infocap-user-infoResolves the createdBy and modifiedBy of a managed entity to a stored user record of email, given name and family name, and renders the two fields as links with a quickview.independent, capUser details and quickview links for createdBy and modifiedByfrom CAP
- CDS Field MappingCDS Field MappingLooks up which Core Data Services entity and field a classic dictionary table and field map to, filterable by whether the target CDS view is released.independent, abapMaps classic dictionary tables and fields to CDS entities and fieldsfrom ABAP
- @animb1996/cds-data-drift@animb1996/cds-data-driftCompares the CSV files under a CAP project's db/data with the rows in the database bound as its db service, and reports where the two have diverged without writing to either.independent, capCompares a CAP project's CSV data with its database rowsfrom CAP
- cap-js-mockdatacap-js-mockdataA cds add command that generates CSV seed files into db/data from @Mockdata annotations on your entities, filling each column with values from the Faker module the annotation names.independent, capCSV seed data generated from @Mockdata annotations with Fakerfrom CAP
- @sap/cds@sap/cdsThe CAP Node.js runtime, which compiles the CDS model, serves the services declared in it, answers generic requests before any handler runs, and loads every cds-plugin.sap official, capCAP Node.js runtimefrom CAP
- abapFakerabapFakerGenerates fake data in ABAP, for bootstrapping a database, creating XML documents, stress-testing a persistence layer or anonymising data taken from a production service.independent, abapFake data generator for ABAPfrom ABAP
- cap-mock-generatorcap-mock-generatorParses the .cds schema and fills db/data with relationally consistent CSV — through an LLM layer where one is configured, or a local engine where none is.independent, capFills db/data with relationally consistent CSV from a .cds schemafrom CAP
- com.sap.cds:cds-services-bomcom.sap.cds:cds-services-bomThe Maven bill of materials for CAP Java, pinning every com.sap.cds module in a release, from the API and core runtime to the Spring Boot starters and the CQN engine, to the same version.sap official, capMaven bill of materials pinning CAP Java module versionsfrom CAP
- @sap/cds@sap/cdsThe CAP Node.js runtime, which compiles the CDS model, serves the services declared in it, answers generic requests before any handler runs, and loads every cds-plugin.sap official, capCAP Node.js runtimefrom CAP
Details
Sources
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
Flavors
“Install this module in your CDS Node.js project:” — @sap/cds-common-content — npm README
History in the atlas
- 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.
- Typed cds-plugin by placement, which defaults every candidate to that. It is not one.
- ISO-standard content for CAP's common definitions — countries, languages, currencies and timezones — so a project does not seed those tables itself.
- First seen.
For your agent
- Ref
artifact:sap-cds-common-content- JSON
- /artifacts/sap-cds-common-content.json
- MCP
- Connecting an agent