Why we need to define the security:
Security is important to define user's scope (the perimeter of data user can see), specially in order to avoid conflict of 2 users being able to see/modify the same scope.
For ex: 2 Sales Employees of a given GBU will have access (see) a different set of DFUs, so that they can input the "Sales team Forecast" without blocking one another.
Where (which Master Table) should we define the Security : the real answer is that it depends on the user and what is the screen he's supposed to see. To make it simple, the user should have his Security defined in the dimensions (Master tables) of the datafields shown in his screen.
In Solvay DP Context, most of DFs have the Material:Shipto@DC dimension, so the Security would need to be defined at least in this Master Table (in most cases).
Ex1: in the following grid view, all the DFs have Horizon + Material:Shipto@DC dimensions => user should have the right Security defined at Material:Shipto@DC (note: we don't define Security in Horizon)
Ex2: in the following cases, even though there are several splits of Material:Shipto@DC (Soldto, Country,...), we still just have to define the Security in the root (before split) Master table: Material:Shipto@DC
Ex3: in the following cases, we have to define the Security in Sales Employee ID table,
What do we need to do a Security: to define the Security, we need a condition (True / False). Most users of DP are Sales employee, each of them having a Sales employee condition associated.
For ex: for a Sales Employee of a given GBU
| # | Description | Screenshot |
|---|---|---|
| 1 | right click the master table Sales Employee ID, then click Security In the Advanced security tab, for each user group, associate the conditions to the corresponding user groups, |
|
| 2 | right click the master table Material:shipto@DC, click Security In the Advanced security tab, for each user group, associate the conditions to the corresponding user groups, |
|
ex, QSM-285899
| # | Description | Screenshot | Reference view |
|---|---|---|---|
Problem! | |||
| 1 | user SANTOSMA all black view while open the work space, |
|
|
Trouble Shooting! | |||
| 2 | The grid view has a split on dimension MAterial:Shipto@DC into
|
| |
| 3 | If you connect as the user into the rich client and right click => configure on the view, you can check which one is empty (the one with /) : | ||
| 4 | The problem is on Material : the view has a filter on Material, on condition 'GBU - TS: Yes & Planned Material | TS : Yes' : | ||
| 5 | User belongs to those groups : | ||
| 6 | The only group having a security configured on the master table 'MAterial' is TS - US / MArcio Santos, with the visibility condition 'GBU - SA&D' Finally, a right click => hierarchy view (with a super user account) on the master table 'Material' shows that there is no intersection bewteen the combination of the conditions used to filter the grid and the condition of visibility : | ||
| 7 | select here the 3 conditions (pressing control key allows to multiple select them) : | ||
| 8 | |||
| 9 | |||
| 10 | |||
,
,
