Suppose you work for a company that sells goods to customers. You have recorded transactional data for all sales orders, and master data for all customers in different sources. You want to combine them, then aggregate the sum of all order amounts in the enterprise's currency and all quantities per customer and display each customer with its name. Following the data integration scenario using SAP Business Warehouse Bridge, you wonder what type of objects you have to create.
SAP Business Warehouse Bridge uses the same objects that you may already know from SAP BW/4HANA. If not, please see the following video to learn the required terminology.
Note that SAP Business Warehouse Bridge is mainly used for physical data storage. Instead of using the SAP BW/4HANA federation options in SAP Business Warehouse Bridge, you instead use the federation options in the SAP Datasphere core tenant. Therefore, the following SAP BW/4HANA object types are rarely used or cannot be used directly:
- An Open ODS view accesses data from an external source or BW object. It cannot be defined in SAP BW bridge.
- A BAdI Provider processes ABAP code at runtime. It cannot be defined in SAP BW bridge.
- An InfoSource allows splitting a transformation into parts that are executed in sequence. It can be defined.
- A Semantic Group is a collection of ADSOs (advanced DataStore Objects) that are combined in one CompositeProvider. It can be defined.
- A BW Query is a predefined choice of filter values, columns, and rows for data Analysis, which can be changed at runtime. I can exist, but can only be used as a source object for model transfer with certain limits, for example a query with two structures cannot be transferred to a datasphere view.
So, you mainly maintain InfoObjects to manage master data and ADSOs for transactional data. In this course, you will see a data acquisition scenario.
In SAP Datasphere core tenant, there are other objects with similar purpose. Take a look at the following slide to see the object types.
Before we start creating these objects, let's consider in more detail how the data is delivered from SAP sources.