Technology Blogs by Members
Explore a vibrant mix of technical expertise, industry insights, and tech buzz in member blogs covering SAP products, technology, and events. Get in the mix!
Showing results for 
Search instead for 
Did you mean: 
Active Contributor
Beta planned for summer, GA is planned for SAP TechEd

The legal disclaimer applies, that things in the future are subject to change.

Source: SAP

Cloud service, cloud native service, managed by SAP

Uses HANA database in the cloud

Existing customers, this is meant to extend on premise use cases to the cloud

connect and extend with cloud data warehouse

Or new use case such as new data marts

Cloud native datawarehouse from scratch

New solution, independent of cloud

For IT and business users

Source: SAP

Designed to be easy to access and use

It is a managed service

It is an "agile solution"

"fast time to value"

Open SQL interface, SQL scripting

scale up and down

Figure 4: Source: SAP

Architecture level; at bottom it is an open solution, connect to SAP and non-SAP data sources, either on premise or cloud

3rd Data ingestion tools

Connectivity to data lakes

Virtual or federated access

It is based on the HANA cloud offering - 4 services - repository services, modeling services, data warehousing services, governance services

Consumption layer for analytics tools, such as SAP Analytics Cloud

Source: SAP

Lower left, data layer with components to generate tables, views, data flows, connection management to on premise or cloud systems, and enhancement to the data store object

Separating semantic layer from data layer

Semantic layer is a virtual layer to create models, entities, facts, dimensions, hierarchies

The business can create objects - e.g. invoice, order, deliver - map from semantic layer to data layer or reverse

Goal is to generate semantic layer, virtual, based on nature of the objects, for line of business users to find way to integrate data

Business catalog will have predefined objects; open to be enhanced, include documentation objects such as data lineage, versioning

Source: SAP

Attributes related to layers

Data layer - how access, how provisioned, could be virtual, no need to load data to data warehouse cloud

Could also persist data in data warehouse cloud

Top - semantic layer, describe the virtual business entities and related KPI's

Provide business model

Focus semantic layer on stable, connected layer, closely to SAP Analytics Cloud, strong connection to semantic model

Source: SAP

Concept of spaces

Data layer integrated with spaces

Integration with data lake spaces (IQ in the cloud)

Data layer is based on different spaces

On the left, IT managed operational systems, such as S/4HANA, C4/HANA - golden color. Move to the right - marketing, finance, sales, blue part - managed by business to create model, generate virtual tables

Spaces help you manage data, locate the data

On the right, blue only, business maintained

Source: SAP

Watch the replay for demos; it is here

Source: SAP

This was part of the demo


Q: Migration tools/BW/4HANA

A: conversion path from BW/4HANA

Q: would you put CDW next to BW/4HANA?

A: hybrid scenario, if put it on top

Could have BW/4 provide data or virtual access

Q: advanced engines from HANA from modeling process

A: will be made available, can't tell you now

Q: virtual connection

A: done by virtual table, federated access by source system, not by BICS

Q: based on neo or cf

A: based on Cloud Foundry

Part 1 of this blog is here  - what is SAP Data Warehouse Cloud


What do you think?  Will business users use it?
Labels in this area