Data federation
Reading data that lives in another system as if it were local — by federating the query, by copying the rows, or by caching what was read. Three different answers to one question, and the choice is about how stale you can afford to be.
Overview
cds-federation-synonyms An experimental CAP plugin for CAP-to-CAP data federation over SAP HANA synonyms, so one project reads another's tables without the rows being copied.
@sap/cds Shows service-level replication as application code in the Data Federation guide: about forty lines in the xtravels sample that turn each @federated entity into a table, schedule a replicate handler with the runtime's scheduling API and upsert the rows newer than the local maximum of modifiedAt. The runtime supplies the annotation, the scheduling and the remote query; the loop is the application's own.
Not covered: At the pattern. The guide's replication is code the application owns, published as a sample and not as a runtime feature, and the integration overview names HANA virtual tables and SAP data products without a page for them yet. Delta beyond one timestamp, retries, run history and tenant-aware replicas are what the entries here add.
On BTP this is SAP Master Data IntegrationSAP Master Data IntegrationA multi-tenant cloud service that replicates master data between two or more clients, giving a hybrid landscape a consistent view of it, with filters set through SAP Business Data Orchestration service.sap official, btp: copying master data, not transactional rows, between two or more clients so a hybrid landscape has one consistent version of it, with which records move set by filters rather than written into the application.
SAP Master Data IntegrationSAP Master Data IntegrationA multi-tenant cloud service that replicates master data between two or more clients, giving a hybrid landscape a consistent view of it, with filters set through SAP Business Data Orchestration service.sap official, btp replicates master data between two or more clients across a hybrid landscape, giving them a consistent view of it; which records move is set by filters configured through SAP Business Data Orchestration service, and the replicated objects can be extended with a project's own fields and entities.
Not covered: At master data moving between clients your account already reaches: filtering what replicates is done through SAP Business Data Orchestration service rather than in this service itself.
The one provider behind this door is SAP-official, so core-only is a assessment of the corpus rather than a quote from the core.
No community artifact is documented here.
Licence
LicenceSAP Developer License Agreement 3.2 CAP§ 1AlwaysReplication by a covered CAP application moves data from an SAP product into a non-SAP product.
- § 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.
Section 1 restricts mass extraction to a non-SAP product and states a scoped interoperability exception. That boundary is central to a replication design and must be checked against the actual use.
SAP Developer License Agreement 3.2 CAP →Artifacts
Content
Seen working
Neither the package manifest nor the repository tree declares a licence.
Details
Coverage
Comparison properties
These are the questions used to compare what the artifacts do. Values come from their documentation and may apply to a particular ecosystem or runtime. Each recorded value in the comparison opens its statement and sources.
For your agent
- Ref
capability:replication- JSON
- /capabilities/replication.json
- MCP
- Connecting an agent