Ques:
You’re asked to create a reusable data product containing customer order history for various analytics use cases. How would you model and expose this data product in SAP Datasphere’s business layer?
Ans:
In order to create a reusable data product for customer order history in the business layer, we can follow a semantically rich modelling approach, which should use both the business builder and the data builder.
Here’s the goal: to create a consumption-ready product that should support multiple analytics use cases.
By step-by-step guide involves:
– Prepare the data in the technical layer or the data builder. Here you can cleanse or integrate the data from relevant source tables such as customer, sales order, order items, returns, etc.
– Create one or more graphical or SQL views and apply all the filters, joins, and calculations.
– In the business builder, we can create the business entities and add the associated dimensions, if required.
– Now define all the KPIs and the calculated measures in the business builder, such as total order value, average order size, order frequency, and repeat purchase rate. These KPIs will become part of the data product and can be reused across stories, dashboards, and planning models.
– Apply the governance and reusability standards by exposing the business entity through consumption models. Apply analysis authorizations wherever restricted is required.
– Expose the data product to the consumers and share the consumption model with SAP SAC and other spaces. This will be the single source of truth for customer order history across all analytical use cases.
Thus, this way, a reusable customer order history data product can be created in SAP Datasphere, which can support multiple analytical products.
For More Such QnA on Datasphere for Quick Revision, you can check out: https://topmate.io/vartika_gupta11/1639897