If you are building a Customer-Managed Data Product (CMDP) in SAP Business Data Cloud and your data source is an existing Datasphere VIEW joining multiple tables in the HANA relational space (not a direct S/4HANA CDS view), you will encounter a storage pattern that looks like multiple copies of your data on the SAP side before it ever reaches Databricks. This post explains exactly why that happens, what your options are, and what “zero copy” actually guarantees in this context. This is not in the official blogs yet. I lived it with a real enterprise implementation, had it validated by SAP Product Engineering, and I am publishing it so other customers and partners do not have to discover it the hard way.
If you are building a Customer-Managed Data Product (CMDP) in SAP Business Data Cloud and your data source is an existing Datasphere VIEW joining multiple tables in the HANA relational space (not a direct S/4HANA CDS view), you will encounter a storage pattern that looks like multiple copies of your data on the SAP side before it ever reaches Databricks. This post explains exactly why that happens, what your options are, and what “zero copy” actually guarantees in this context. This is not in the official blogs yet. I lived it with a real enterprise implementation, had it validated by SAP Product Engineering, and I am publishing it so other customers and partners do not have to discover it the hard way. Read More Technology Blog Posts by SAP articles
#SAP
#SAPTechnologyblog
