BrowseAll ecosystems
Everything in the atlas
3 of 2362
Domain
Signals: 2
Content
More: 2
Group by: Capability
EntryBySignalsLast activity
The Full Picture: Federating, Replicating, and Caching Remote Data in CAP — Part 1The Full Picture: Federating, Replicating, and Caching Remote Data in CAP — Part 1Part one of two, and the concepts half: terminology, what CAP already does, and what a project still has to write. It fixes a vocabulary — federation is the umbrella for making remote data part of your model, delegation forwards each request to the remote at query time, replication is a scheduled copy into the local database, and caching is an option on either rather than a third strategy — which collides with CAP's own, since what this series calls replication is what the CAP-level Data Federation guide calls federation. From the ground the Service Integration guide covers, it lists what is left to hand-write: cross-service $expand, navigation filters across the boundary, write forwarding, timeouts and retries, then scheduling, delta detection, backoff, a guard for two app instances sharing one schedule, idempotent writes, and knowing whether the last run succeeded. That list is why the edge to cds-data-federation holds: the second half maps it onto @federation.delegate and @federation.replicate and says which package carries which part — annotations in cds-data-federation, the scheduled engine in cds-data-pipeline, response caching through cds-caching — so it is the design rationale for the annotations, not the API reference. The gap list and the plugins answering it come from the same person who maintains them; cap-replication-demo and SAP's xtravels sample are cited as the hand-written form of the same work. Part 2 is announced as a walkthrough of a demo application and is not covered here.
SAP Table to CDS Mapper - New Version thanks to AI-supported DevelopmentSAP Table to CDS Mapper - New Version thanks to AI-supported DevelopmentThe author ran a table-to-CDS field analysis across a whole SAP S/4HANA 2025 FPS01 system and published the result as one HTML report, SAP Table to CDS Mapper, that ranks candidate CDS objects for a classic table or field. The post states what the snapshot holds, how the official successor, C1 release and direct coverage are ranked, and that each candidate is a lead to validate before relying on it. It credits cdsanalyser as the idea and implementation it builds on, and offers a classification import for Project Kernseife.LBretschneider, published 2026-10-26
SAP Table to CDS Mapper - New Version thanks to AI-supported DevelopmentSAP Table to CDS Mapper - New Version thanks to AI-supported DevelopmentThe author ran a table-to-CDS field analysis across a whole SAP S/4HANA 2025 FPS01 system and published the result as one HTML report, SAP Table to CDS Mapper, that ranks candidate CDS objects for a classic table or field. The post states what the snapshot holds, how the official successor, C1 release and direct coverage are ranked, and that each candidate is a lead to validate before relying on it. It credits cdsanalyser as the idea and implementation it builds on, and offers a classification import for Project Kernseife.LBretschneider, published 2026-10-26
Under no capability
API Policy - FAQAPI Policy - FAQSAP’s June 2026 FAQ, version 1.3, explains the scope and use conditions of the SAP API Policy, including published and non-published APIs, ADT developer access, AI-driven usage and third-party MCP servers. It also addresses data extraction and the responsibilities of customers and partners. The FAQ is informational: it does not modify contracts, and applicable agreements and product documentation prevail if they conflict with it.
