Hi gurus,
I'm working on a project in which we are publishing BW reports in SAP Netweaver Portal (prior to this, we were using SAP Bex Browser) organizing it by Department (workset, 2nd lvl of navigation), Business Processes (workset, 3rd lvl of navigation) and "iview types" (transactions, queries, dashboards and so on). On 1st level we have a workset simply called "Reports".
For each PFCG role we have on BW (ABAP Server), we created a portal role and defined which of the higher navigation tiers is visible to users (delta-linking the top level navigation worksets to the portal role and setting visible accordingly) and then we assigned Portal roles to the appropriated Group (PFCG role) so all users that have access to certain PFCG role can have access to the corresponding Portal role.
For example:
In BW (ABAP) we have a PFCG Role: Sales PMR Analysis - Administrator, which grants access to Sales Infoproviders, queries and data for PMR analysis. The user that have access to it, should be able to see:
|Reports|
|Sales Administration|
v PMR Analysis
> Web Queries
> Transactions
> Dashboards
> Workbooks
In Portal we create a workset that has: "Reports" and under it, all Departments (Sales Administration, Financial, Services, Human Resources and so on) set as "not visible". We create a Portal role called PMR Analysis and add the Report/Departments workset, set Sales Administration as visible and add worksets/folders named PMR Analysis, Web queries, Transactions, etc, and all the corresponding iviews under it.
If we assign this new Portal role to the Group of the corresponding PFCG role, the user will see exactly as the example from above.
Pros: The users have a clean view of the reports he/she has access.
Cons: The users doesn't have a clear view of what is available in BW so he can request access. There might be some useful report lost in on of the hundreds of BW roles that he doesn't know it exist.
One of the options would be to grant visibility to ALL departments, business processes and iviews in Portal and let PFCG security roles control user access, but that might be confusing to have an overwhelming amount of links, making it hard to find what the user needs, specially during first access. Not to mention possible security breaches.
So, I'd like to know how other consultants are defining this kind of folder structure and report publishing strategy in Portal. Ideally we would like to be able to have:
- Visibility of all existant reports even those that the user does not have acess (so he can learn that it exist and request access)
- Clean view of reports, segmented by department and business processes.
- Possibility to search for reports, even for those that the user does not have access.
I'd appreciate if you guys can share your experience on this.
Thanks in advance.
Leandro
The tool provides a way to:
