
Hello All,
Welcome back to my other blog post on an exciting feature available in SAP Datasphere: the data access control in Data Builder and the authorization scenario in Business Builder. This blog post will explain this concept with an example and demo.
In this blog post, I am not going to discuss what data access control in data builder is and what the authorization scenario in business builder is. You can go to the official documentation of SAP and can understand the concept.
We will develop a business case in this blog post, which can also assist you in developing your scenario for a real-time project. Now, straight away, let us get into the demo and understand in detail.
First, let us create a product category hierarchy table, as in this post I will explain DAC based on hierarchy, and then we will move into creating a DAC based on a table and then an authorization scenario in Business Builder.
Now let us go to the dataset of this table.
So my hierarchy table is created, and it is ready.
To further implement DAC, we need a control table that will control the access; in short, we are going to create a permission table. This is a must when we create DAC, as it is going to control the activity and will provide row-level access to users who actually want to view the data. you can read more about permission table and its usage.
Now let us create a permission table.
Business Name : Permission Entity Product Category
Technical Name: PE_ProductCategory
So now our control table or permission table is created.
Now we are set to create our data access control object, which we are going to apply to a final view. So let us create a data access control. Go to data builder and create a new DAC.
So we are all set with our data access control now. Now let us create a view and apply the DAC to the view.
So, I have created a view with the name Sales View Fact, and I have a product table. Kindly see below.
we are going to join this 2 tables with Product ID
Now let us apply the data access control to the final view. Please follow the image below.
Now let us view the data in the Sales View Fact table.
So, we have successfully implemented the data access control based on a parent-child hierarchy. Similarly, we can maintain many user ids as per requirement and can view the data applying data access control to users.
Please visit the next blogpost for DAC in data builder and new authorization scenario in bsuiness builder.
Thank You.
Narasingha.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
9 | |
8 | |
6 | |
5 | |
4 | |
4 | |
3 | |
3 | |
3 | |
3 |