BlogBlogA post on somebody's own site or a community platform. Nobody edits it after publication, so it dates from the day it was written.See every one →SAP Community
Connecting Two SAP CAP Projects Without Duplicating Your Data
Cross-container HDI synonyms, argued from the alternatives rather than presented as a recipe: copying the table, standing up an API, or hard-coding the values are the three things the author reports seeing teams do, and each is named as working but unclean. With synonyms in place the consuming project queries the owner's HANA tables through ordinary SQL and ordinary CAP service code, with no replication and nothing to drift between environments. Covers the same ground as Mio YasutakeMio Yasutakemaintains 47 entries, wrote 10 posts, contributed to 47 entriesindependent's 2021 post from a different angle — that one enumerates four topologies, this one argues for one of them.
Where it sits
Explains
Native SAP HANA artifactsCAPNative SAP HANA artifactsUsing native SAP HANA database objects alongside an application’s generated data model, including objects and database features the modelling layer cannot express. Choosing a database is [database connectors](capability:database-connectors); changing an existing schema is [schema evolution](capability:schema-evolution).
Source
reachable
Who is behind it
Inderpreetauthor
Properties
About this work
What was found on the page
Prose
1,013 words
Code blocks
4
Group by
Piece, what it offersStill applies
How to share tables across different CAP projectsHow to share tables across different CAP projectsFour scenarios for reading one CAP project's table from another, worked out as a matrix of what each one needs: the same HDI container and namespace, the same container under a different namespace, a different container, and a different Cloud Foundry space. The mechanics change with each step — @cds.persistence.exists on the reused entity throughout, an .hdbsynonym once namespaces diverge, .hdbrole and .hdbgrants once containers do, and a user-provided service built from the grantor's credentials once spaces do. The author flags the caveat themselves: these are learning scenarios, and consuming the OData service is often the better answer than reaching into another project's database. Dated corrections from twelve days after publication sit inline — synonyms need only the name because the configuration comes from .hdbsynonymconfig, SERVICE_REPLACEMENTS in mta.yaml removes the hard-coded service name, and the reused container need not be bound to the srv module.published 2021-10-03
Details
Graph
Source
Type
blog
Published on
Host
community.sap.com
Discovered via
First seen
History
- Entered the atlasDiscovered via SAP Community · cap-group.
For your agent
- Ref
content:connecting-two-sap-cap-projects-without-duplicating-your-data- JSON
- /content/connecting-two-sap-cap-projects-without-duplicating-your-data.json
- MCP
- Connecting an agent