SAP Datasphere Transformation

See how we help a client to accellerate its vision to tap into SAP Data Products and the rich business content sitting in S/4 HANA on premise in a meaningful way with DataSphere

ABOUT THE CLIENT

Client going through a major S/4 HANA ERP transformation programme, in parallel building up its SAP Data Product strategy to allow surrounding platforms, including its Enterprise Data Platform and Data Hubs to consume SAP Data Products from its wider S/4 HANA landscape.

Challenge

Client is transforming its ERP landscape into one comprised of numerous larger S/4 HANA on premise but also some smaller ERPs on S/4 HANA Cloud versions. Challenge to be addressed is how to consume and tap into SAP Data Products and the rich business content sitting in S/4 HANA on premise in a meaningful way, i.e. initially exploring that business content via Data Catalog, then via a Data Contract gain access to the data and last but not least ensure Data is read or transferred in a way that protects the underlying SAP platforms, both its S/4 HANA private instances as as well as SAP DataSphere as a proxy. 

Approach

ONE together with the client decided to run a PoC in two phases (due to still some key SAP DataSphere features under development), and in combination with SAP DataSphere Product Management and SAP Strategic Customer Analytics team evaluate SAP DataSphere’s: 1) General Maturity and Readiness for use, 2) Ability to support S/4 HANA private instances as an ’extended’ embedded S4 reporting platform, 3) Deliver and integrate SAP Data Products into Enterprise Data Platform - Data Lake, DataBricks and Enterprise Data Content via Collibra and 4) Host on-prem native HANA and BW solutions running out of support.

Results

SAP Product Management rectifying in record turn-around time infant issues in the Semantic Onboarding / Import Entity meta data read of ABAP CDS view annotations (now able to fetch all relevant ABAP CDS view types)

+ CORE

SAP Product Management rectifying in record turn-around time infant issues in the Semantic Onboarding / Import Entity as artefact types created in DataSphere; initially as local tables, now as remote tables as expected

+ SPEEDUP

Concrete dialog on how to advance the launch date for the ABAP SQL adapter (via SDA) to replace the current ABAP Adapter (via DP agent) to allow better performing remote querying (via join and filter push down)

++ SPEEDUP

Concrete dialog on how to allow import of not just main ABAP CDS views but also its associations in CSN files, for subsequent execution

+ EXTEND

Concrete dialog on how to allow replication of not just main ABAP CDS views but also its associations as part of replication flow execution

++ EXTEND

Improvements to speeding up modelling in SAP DataSphere when refactoring and changing source CDS views (column data lineage) and use of versioning

+ MATURITY

Conclusion

SAP DataSphere has seen tremendous improvement after its rebranding in Mar/Apr 2023 and is rapidly moving closer to soon act as a data mesh concept on top of S/4 HANA private (note the distinguishment from S/4 HANA Cloud) that can act as 1) an extend to analytics scenarios difficult to model in ABAP CDS and 2) as an extended proxy to S/4 HANA private to deliver and integrate SAP Data Products with surrounding data platforms and 3) as a bridge for existing on-prem BW and Native HANA solutions being out-of-support soon.