Hi,
I would like to ask for the better solution for my problem.
I have a employee hierarchy, so I have Area Managers, District Managers and Territory managers. My sales fact table has the data at territory level, so I get the sales of a District Manager as the sum of the sales of all territories in his/her district, and the sales of an area Manager as the sum of all his/her districts.
All the employees has a login_id in Business Objects. I have create a report that has 3 sections. One for the Area Managers, another for the District Managers and the last for the Territory Managers. What I want to get is that when a users login in the system and open this reports only could see the information of his/her hierrarchy level and the information of the employees below his/her level.
Could you give me some suggestions about how develop this. I have several ideas in my mind by I think that they are very complicated and Iâm thinking that perhaps there are better solutions and I donât know them.
I would propose creating of a profile table in database and linking the profile table to your sales fact table.
Maintain the BO user id in the profile table.
You can then use supervisor level restrictions and make use of @BOUSER.
Iâm getting a PowerPoint slide show uploaded that shows several methods for doing this. In the meantime, search tech supportâs knowledge base for âMiami&Securityâ and youâll see a similar set of slides.
Steve,
you mention âBusiness Objects passwords must be in synch with database passwordsâ as a disadvantage for a âprivate viewâ. Have you ever used âOS Authenticationâ on a OracleDB? It works fine and no password checking on the database is needed.
I have applied row level security using ârestrictionsâ option in Unverse. When I migrate from Dev to QA, the restrictions I have applied is not getting migrated. Is there anything that I have do specifically to get my restrictions also migrated?