onedevatlasBeta
Browse the atlas
AllCAPUI5ABAPBTP
NewSAP Business Technology Platform, also named SAP Business AI Platform

New in BTP/BAIP

7 days30 days90 daysAll time
All time
31added to the atlas78new pieces of content87revisions
Change: Revised
Kind
Origin
Domain: Data & Persistence
Clear all
87 changes
DayCapability
Change RevisedDomain Data & Persistence

Today
4 changes
Attachmentscoverage by ecosystem, coverage by flavor revisedReassessed against the graph (check:capabilities): drops a count-like contrast with a plugin the flavor does not have.Capability,
Cataloguing and lineagecore coverage revisedReassessed against the graph (check:capabilities): a newer community server publishes Delta shares as data products in Business Data Cloud, a kind the text did not name.Capability,
Database connectorscoverage by ecosystem revisedReassessed against the graph (check:capabilities): the note counted one entry behind the door; it now names the driver and SAP HANA, which now provides the capability on this door. State unchanged.Capability,
Loading a warehousecore coverage, coverage by ecosystem revisedReassessed against the graph (check:capabilities): ERPL is a provider the text never named, and it loads from ABAP systems outside BW routines. State unchanged.Capability,
Sat 24
2 changes
SAP HANA Cloudprovides revisedThe capability was added on 2026-10-24 for administering a database instance; SAP HANA Cloud ships its administration tools, so it is the core answer on BTP.Service,
SAP-samples/hana-developer-cli-tool-exampleprovides, serves ecosystems, domain, provides revisedIts performance analysis, privilege grants and backup and recovery commands had no capability to sit under; Database administration was added for them the same day.CLI,
Fri 23
3 changes
SAP Analytics Cloudlinks revisedSAP moved the What's New entries for SAP Business Data Cloud, SAP Datasphere and SAP Analytics Cloud to the Business Data Cloud feed; the old BTP feed had stopped carrying them.Service,
SAP Business Data Cloudlinks revisedSAP publishes the What's New entries for SAP Business Data Cloud on its own feed; the entry linked none before.Service,
SAP Dataspherelinks revisedSAP moved the What's New entries for SAP Business Data Cloud, SAP Datasphere and SAP Analytics Cloud to the Business Data Cloud feed; the old BTP feed had stopped carrying them.Service,
Sat 17
43 changes
[BTP HANA Cloud Database] : How to access HANA Cloud Database & HDI Container in BTPexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
2024/01最新版！Productivity Toolsを使ったCAPバックエンド開発②~HANA Cloud編~explains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
Agentic memory: Knowledge graph engine and recall in SAP HANA Cloudexplains revisedDoor scope derived from the artifacts this piece also explains, so a door page lists it only where it holds (docs/concepts/content-on-doors.md).Talk,
Agentic SAP BW modernization: Your path to SAP Business Data Cloudexplains revisedDoor scope derived from the artifacts this piece also explains, so a door page lists it only where it holds (docs/concepts/content-on-doors.md).Talk,
Show 39 more
Analyze and optimize ABAP Cloud model apps built on core data servicesexplains revisedDoor scope derived from the artifacts this piece also explains, so a door page lists it only where it holds (docs/concepts/content-on-doors.md).Talk,
Building a CAP App with Fiori Integration – Part 1: Environment & HANA Cloud Setupexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
Building agentic applications with SAP HANA Cloudexplains revisedDoor scope derived from the artifacts this piece also explains, so a door page lists it only where it holds (docs/concepts/content-on-doors.md).Talk,
Building an SAP BTP Agent Architecture from Scratch: Python + CAP + HANAexplains revisedDoor scope derived from the artifacts this piece also explains, so a door page lists it only where it holds (docs/concepts/content-on-doors.md).Blog,
Cachingdescription revisedKeep the default capability wording neutral; preserve the previous wording in framing_by_ecosystem.cap. Maintainer-requested scope audit.Capability,
Configure an SAP CAP Application to Connect to an SAP HANA Cloud Database in Another Global Account or Subaccountexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
Connect SAP CAP (Node.js) to On-Premise/Private PostgreSQL using SAP Cloud Connectorexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
Create a CAP Application with SAP HANA Cloud from Scratch and Deploy to Cloud Foundryexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
Database connectorsdescription revisedKeep the default capability wording neutral; preserve the previous wording in framing_by_ecosystem.cap. Maintainer-requested scope audit.Capability,
Deploying CAP services with the in-memory SQLite databaseexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
Distributed Resiliency of SAP CAP applications using SAP HANA Cloud (Multi-Zone Replication)explains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
Enhancing agentic AI with trusted business dataexplains revisedDoor scope derived from the artifacts this piece also explains, so a door page lists it only where it holds (docs/concepts/content-on-doors.md).Talk,
Explore your Hyperscaler data with SAP Business Data Cloudexplains revisedDoor scope derived from the artifacts this piece also explains, so a door page lists it only where it holds (docs/concepts/content-on-doors.md).Reference architecture,
Extend SAP SuccessFactors on SAP BTP with CAP - Deploy to SAP HANA Cloudexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
Extend Upload Set to Fiori Elements and utilize Document Management Serviceexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
Flexible analytics at speed: Calculation views in SAP Business Data Cloudexplains revisedDoor scope derived from the artifacts this piece also explains, so a door page lists it only where it holds (docs/concepts/content-on-doors.md).Talk,
Fullstack CAP Application with HANA Cloud (Decoupled Architecture) [Part-3]explains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
Fullstack CAP Application with HANA Cloud (Decoupled Architecture) [Part-4]explains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
Graph, spatial and document datadescription revisedKeep the default capability wording neutral; preserve the previous wording in framing_by_ecosystem.btp. Maintainer-requested scope audit.Capability,
How to create an API to run a HANA Cloud Stored Procedure in Cloud Foundryexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
Hybrid testing using PostgreSQL on SAP BTP, hyperscaler optionexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
Knowledge graph and agent memory: Build an agent that remembersexplains revisedDoor scope derived from the artifacts this piece also explains, so a door page lists it only where it holds (docs/concepts/content-on-doors.md).Talk,
Lets Deep dive into CAPM and HANA Cloud --> HANACapexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
Loading a warehousedescription revisedKeep the default capability wording neutral; preserve the previous wording in framing_by_ecosystem.btp. Maintainer-requested scope audit.Capability,
Medallion Reference Architecture for Big Data Processing in SAP HANA Cloudexplains revisedDoor scope derived from the artifacts this piece also explains, so a door page lists it only where it holds (docs/concepts/content-on-doors.md).Reference architecture,
Modernize your database landscape with SAP HANA Cloudexplains revisedDoor scope derived from the artifacts this piece also explains, so a door page lists it only where it holds (docs/concepts/content-on-doors.md).Talk,
Part 1: Creating and Deploying a SAP CAP Application with SAP HANA on SAP BTP (Cloud Foundry)explains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
Run and Deploy SAP CAP (Java) with PostgreSQL on SAP BTP Cloud Foundryexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
Run and Deploy SAP CAP (Node.js or Java) with PostgreSQL on SAP BTP Cloud Foundryexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
SAP BTP Showcase - Use SAP Cloud Application Programming to do Native Development on HANA Cloudexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
SAP CAP Lessons Learned: Run a CAP app using SQLite on SAP BTP - Cloud Foundryexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
SAP Datasphere Integration Patterns: Lessons Learned from Two Years of Implementationsexplains revisedDoor scope derived from the artifacts this piece also explains, so a door page lists it only where it holds (docs/concepts/content-on-doors.md).Blog,
Setting Up PostgreSQL for SAP BTP Development: A Practical Guideexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
SFSFとHANA Cloudを使用するCAPのアプリケーション開発explains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
Sharing SAP HANA Cloud instance to multiple subaccounts and creating HDI containersexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
Simple steps to deploy your CAP project to HANA cloudexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
SQLite as database for a multi-target (/productive) CAP Applicationexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
Stop guessing, start counting: How generative AI fixed an inventory messexplains revisedDoor scope derived from the artifacts this piece also explains, so a door page lists it only where it holds (docs/concepts/content-on-doors.md).Talk,
Unlocking Efficiency: Leveraging SAP BTP Document Management Service in Fiori Applications # 2explains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
Wed 14
1 change
Attachmentscoverage by ecosystem revisedThe five citations and four links to FileUploader.ts and UploadCollection.ts used the organisation the project has left, which now answers only as a redirect. Both files were opened at the new address on 2026-10-14 and carry the sentences quoted here, so every claim and every quote stands as written and only the addresses and their titles moved; the checked dates stay at the day each quote was last read in full.Capability,

Sun 27
3 changes
Attachmentscore coverage revisedThe paragraph opened with SAP's packages and never said that the runtime serves a @Core.MediaType element with nothing installed. capire's Serving Media Data page is that built-in layer, cited by pagination-and-streaming and not here. Two deliveries, said apart (docs/concepts/sap-ships-and-documents.md).Capability,
Data federationfacets, core coverage, name revisedThe concern this node holds is what capire calls data federation: making data that lives in another system available as if it were local, by federating the query, by copying the rows, or by caching what was read. Replication is one of the three strategies, and the facets declared on 2026-09-27 compare the options on exactly that axis, so a node named after one strategy read as if the other two were elsewhere. The id stays, as the 2026-09-13 rename kept it: it is the stable ref every record, edge and link carries. BTP keeps its own framing name, Master data integration. Proposed by the capire audit of 2026-09-27; decided by the maintainer.Capability,
Database connectorscore coverage revisedcapire audit 2026-09-27, link-only pass: a page this capability owns was cited nowhere.Capability,
Fri 18
1 change
Database connectorscoverage by ecosystem revisedhdb, SAP's pure-JavaScript HANA driver for Node.js, entered in the same batch, so the note counted two entries where there are now three. The assessment is unchanged: the driver is SAP's own, so core-only still holds.Capability,
Thu 17
4 changes
Attachmentscore coverage revisedReplace unsupported migration/UI boundary with sourced implementation limits; keep community additions separate. Add four CAP-scoped comparison questions and preserve other ecosystems/flavors.Capability,
Cachingcore coverage, framing by ecosystem, core coverage revisedUser requires SAP ships to describe only core behavior and limits. Provider guidance belongs under The community adds. The broad tenant-key prescription is omitted; sourced tenant conditions remain on provider edges. Redis remains the served BTP option.Capability,
Object Store on SAP BTPprovides revisedPlace the service under its direct job of object storage. CAP attachment integration remains represented by existing dependency edges from the attachment plugins.Service,
SAP Document Management service, integration optionserves ecosystems revisedAdd CAP to served ecosystems from documented CAP integration; preserve the existing BTP/UI5 contribution and source dates. CAP plugin restrictions do not apply to the service itself.Service,
Tue 15
2 changes
Attachmentsecosystems, coverage by ecosystem, framing by ecosystem revisedOn BTP the concern is answered by a repository service with folders and versions, which differs from the CAP, UI5 and ABAP framings of a file stored against an entity or a business object.Capability,
Cachingecosystems, core coverage revisedThe sentence was cut off mid-word. Rewritten to name the two CAP plugins by their entries, and the multitenancy warning moved here as core_coverage.note: node-cache leaves the graph because its own documentation names no SAP stack, and the lesson it carried is about every hand-wired general-purpose cache, not about one library.Capability,
Mon 14
6 changes
Analytic modellingecosystems revisedteched2023-DT187v builds an analytical ABAP CDS model in ABAP Cloud and hana-cloud-modeling-learning-journey carries the files for SAP's calculation view course, both SAP-samples; MBT Logical Object Lister and MBT Listcube read BW's object models and cubes from an ABAP-based BW system.Capability,
Attachmentscoverage by flavor, framing by flavor, coverage by ecosystem, ecosystems, framing by ecosystem revisedThe ABAP door opened with Generic Object Services and AttachmentCommentODataService, and what the concern is there differs from the CAP and UI5 framings: the file belongs to a business object in the system rather than to an entity a service defines.Capability,
Cachingecosystems revisedABAP-CACHE-BOX in this batch generates singleton cache classes over hashed tables for ABAP programs, which is application-level memoisation on the ABAP door.Capability,
Database connectorsecosystems revisedSAP-samples' hana-hdbext-promisfied-example wraps the HANA client drivers for Node.js, Go and Python, hxe-hibernate-google-app-engine reaches HANA through Hibernate's dialect, and odbc-driver-for-abap-examples connects to an ABAP system through the ODBC driver for ABAP, which widens the node from CAP's database choice to the driver question.Capability,
Show 2 more
Loading a warehouseecosystems revisedpawelwiejkut's bw_remove_characters and bw_trfn_pocketknife answer the concern inside SAP BW transformation routines on ABAP, and SAP-samples' dbt-sap-hana-cloud answers it on HANA Cloud with a dbt adapter that transforms and loads data there.Capability,
SAP HANA Cloudprovides revisedRAG on CDS reads that HANA Cloud supplies the vector column and the similarity function, and the capability opened to the BTP door on 2026-09-14, yet the service carried no edge to it; the store the CAP-door pipelines write into is now an option on the capability.Service,
Sun 13
2 changes
Attachmentsname revisedThe map draws every capability as one tile, and a name that spells out its second half ran to three lines at a size nobody could read. The id already carried the short name; the name now matches it. The concern is unchanged: the description and the coverage say what it spans.Capability,
Data federationname revisedThe map draws every capability as one tile, and a name that spells out its second half ran to three lines at a size nobody could read. The id already carried the short name; the name now matches it. The concern is unchanged: the description and the coverage say what it spans.Capability,
Thu 10
10 changes
Analytic modellingentry, core coverage revisedThe note said the core side of this reading was prose with a citation because SAP's products were not entries. They are now, so the admission is retired rather than left standing as a stale caveat.Capability,
Attachmentsecosystems revisedArtifacts that answer this concern sat behind the UI5 door with no tile to appear under, so browse counted them and rendered nothing. The concern is one a UI5 developer actually decides there, which is the test for opening a door rather than trimming a serves claim.Capability,
Cataloguing and lineageentry, core coverage revisedThe note said the core side of this reading was prose with a citation because SAP's products were not entries. They are now, so the admission is retired rather than left standing as a stale caveat.Capability,
Database connectorsecosystems revisedHANA Cloud and the PostgreSQL hyperscaler option are both BTP services answering which database you run on, and the capability existed on the CAP door alone — so both sat behind the BTP door with no tile to appear under.Capability,
Show 6 more
Loading a warehouseentry, core coverage revisedThe note said the core side of this reading was prose with a citation because SAP's products were not entries. They are now, so the admission is retired rather than left standing as a stale caveat.Capability,
PostgreSQL on SAP BTP, hyperscaler optionprovides revisedEntered with a delivers edge and no provides, so it was behind the BTP door with nothing to group under. database-connectors gained the BTP door the same day.Service,
SAP Analytics Cloudentry, serves ecosystems revisedAdded by me the day it was entered, and it did not hold: the data and analytics capabilities are on the BTP door only, so on CAP this was counted behind the door and grouped under nothing. A CAP service reaches it through a destination, which is the BTP door's concern.Service,
SAP Business Data Cloudentry revisedEntered so the data and analytics capabilities have SAP's answer as an artifact rather than as a paragraph with a citation — the asymmetry every one of those three coverage notes admitted to. Written from SAP Help, read today, which is what the checked date means.Service,
SAP Datasphereentry, serves ecosystems revisedAdded by me the day it was entered, and it did not hold: the data and analytics capabilities are on the BTP door only, so on CAP this was counted behind the door and grouped under nothing. A CAP service reaches it through a destination, which is the BTP door's concern.Service,
SAP HANA Cloudentry, serves ecosystems revisedAdded by me the day it was entered, and it did not hold: an ABAP developer does not choose the database — S/4 runs on HANA — so database-connectors is not a decision made on the ABAP door.Service,
Tue 8
1 change
Cachingcore coverage revisedcap.cloud.sap.com does not resolve — the domain is cap.cloud.sap. Found by the first run of the link checker; the citation had carried a checked date since it was written, which is what a date alone is worth.Capability,
Mon 7
1 change
Cachinggap revisedSeed text. It claimed nothing credible existed for invalidation driven by CDS change events, which cds-caching answers, so the note described the corpus before that entry rather than the ecosystem.Capability,

Mon 31
4 changes
Attachmentscore coverage revisedStates renamed to describe who is present rather than to interpret intent. left-open-on-purpose asserted a motive; core-and-community states a fact, with relationship carrying the intent separately.Capability,
Cachingcore coverage revisednarrow-by-design requires saying what the core does and where it stops. With the unsourced core claim removed there is no basis for either, and 'narrow by design' asserts an intent we cannot evidence. Unassessed is the honest state until someone checks.Capability,
Data federationcore coverage revisedStates renamed to describe who is present rather than to interpret intent. left-open-on-purpose asserted a motive; core-and-community states a fact, with relationship carrying the intent separately.Capability,
Database connectorscore coverage revisedStates renamed to describe who is present rather than to interpret intent. left-open-on-purpose asserted a motive; core-and-community states a fact, with relationship carrying the intent separately.Capability,
Everything the feed holds.
AtomJSON