onedevatlasBeta
Browse the atlas
AllCAPUI5ABAPBTP
All CAPNode.jsJava
CapabilityData & PersistenceNode.js, read from its artifacts

Native SAP HANA artifacts

Using a database object CDS did not generate from the model, an existing table, a view with parameters, a table function, a calculation view or a table in another HDI container, and shipping the design-time files CDS cannot express, an index, a synonym, a native clause, in the same deployment. Distinct from database connectors, which is which database the model runs on, and from schema evolution, which is getting a model change into data that already exists.

Showing artifacts, examples and content with confirmed Node.js applicability. View All CAP

Overview

SAP SHIPS
cds-federation-synonyms

Generates the SAP HANA synonyms and the role that let one CAP application's schema read another's tables and views in place, for the CAP-to-CAP case, with the synonyms switchable between connected and local mock tables.

Sourcecds-federation-synonyms — READMEchecked
@sap/cds-dk

cds build copies the native design-time files under db/src, an .hdbtable, .hdbsynonym or .hdbindex, untouched into gen/db/src beside the generated HDI artifacts, so they deploy in the same container.

SourceUsing Native HANA Artifacts — capirechecked
@sap/cds

Treats an entity annotated @cds.persistence.exists as a facade for a database object it does not generate, renders a user-defined function or calculation view call from the matching hint, and inserts @sql.prepend and @sql.append snippets into the generated DDL unevaluated.

SourceUsing Native HANA Artifacts — capirechecked
@sap/hdi-deploy

Deploys the design-time files of a database module, generated and native alike, into the HDI container, as the delta of added and modified files.

Source@sap/hdi-deploy — READMEchecked

A Node.js coverage assessment has not been written. View all flavors

THE COMMUNITY ADDS

No community artifact is confirmed here for Node.js.

A Node.js coverage assessment has not been written. View all flavors

Artifacts5

5 of 5 artifacts
ArtifactSignals
CDS plugins1
cds-federation-synonymsCAP-to-CAP data federation over SAP HANA synonyms
Signals
Functional boundary
CLI tools2
@sap/cds-dkCommand line client and development toolkit for CAP
Signals
none
SAP-samples/hana-developer-cli-tool-exampleDeveloper-centric command line for SAP HANA
Signals
none
Packages2
@sap/cdsCAP Node.js runtime
Signals
none
@sap/hdi-deployNode.js deployer for SAP HANA Deployment Infrastructure containers
Signals
none

Details

What changed — and what it makes stale1
@sap/cds 9.0.2, CAP, Node.js

CDS associations are no longer reflected as native SAP HANA associations (the WITH ASSOCIATIONS clause) in generated tables and views by default, because CAP does not need them and their validation slowed HDI deployments and introduced indirect dependencies between objects. Dated from the first 9.0 release published on npm, 9.0.2.

Makes stale:

Native HANA code, a calculation view or an SQLScript procedure, that navigated a CDS association on the database through the native association and expects it to still be there after an upgrade.

SourceUsing SAP HANA Cloud for Production — capirechecked
Coverage
statecore only, CAP, Node.js, derived
domainData & Persistence
For your agent
Ref
capability:hana-native-artifacts
JSON
/capabilities/hana-native-artifacts.json
MCP
Connecting an agent