Modelling Approach SAP Data Warehouse Cloud & SAP BW Bridge
A classic modeling approach in the context of SAP BW was always LSA/LSA++.
Within the public cloud, however, there are completely new possibilities and a rethinking of the modelling is required.
As mentioned above, SAP BW bridge is a Staging Layer with all the modeling capabilities from SAP BW/4HANA.
You should follow the same Layered modeling appr.
,
SAP BW Bridge – Architected Data Mart –> Moved to SAP Data Warehouse Cloud CORE
In the LSA++, the system initially always tries to satisfy the requirements based on the Propagation Layer and the Virtual Data Mart Layer.
A persistent architected data mart layer is only built if the service level and/or business requirements cannot be fulfilled.
,
SAP BW Bridge – Propagation & Harmonization
The data propagation layer serves the persistent architected data marts and is a basis for the Virtual Data Mart Layer.
The data is saved and consolidated in standard DataStore objects (advanced) and in InfoObjects.
,
SAP Data Warehouse Cloud – Data Builder Artefacts
Remote Tablesare the inbound artefact in SAP Data Warehouse Cloud which offers federated as well as replicated access to the source.
With SAP BW bridge, you can use federated access if the performance works well.
If your report on top of SAP Data Warehouse Cloud is not performant, you should replicate the data.
Analytical DataSetis used to leverage.
