cancel
Showing results for 
Search instead for 
Did you mean: 

Portal Roles

Former Member
0 Kudos

Hello,

We want to controll roles access to user at workset level (subtab) and assign everyone one major roles e.g "BI Reporting" and then assign roles which they have access to..

Here is the examples

1) User A can see GL and AP reports

BI Reporting (main Tab)

GL Reports (Sub Tab)

AP Reports (Sub Tab)

2) User B can see only GL

BI Reporting (main tab)

GL Reports (sub tab)

I created 3 roles and made BI Reporting role as Entry Point and assigned "GL and AP" roles to BI Reporting roles.. but when I assign BI Reporting roles, users B can still see AP roles.. Can someone please help me on how this should be controlled without creating multiple roles...

thanks,

Deepak

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hello Deepak,

I had similar requirement and this is what I did.

Create 2 roles BI_GL_reports and BI_AP_Reports with Entry points No.

Create a workset BI reporting with some MergeID (say BIREPORTING) and make the entry point yes in the workset properties.

Open the role BI_GL_reports and add the workset BI reporting as a delta link and then add the GL report iview under BI reporting workset.

open the role BI_AP_Reports and add the workset BIReporting as a delat link and then add the AP report iview under BI reporting wokset.

Let me know if you still face any issue.

Thanks,

Naresh Agarwal

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi Deepak,

As you have already mentioned, you have assigned roles GL and AP to your BI role. Thus any user with BI role will automatically see both the GL and AP workset. My suggestion for your situation is below.

Why not try using MergeID. Below is the sample setup which we use for our portal with merge ID.

http://help.sap.com/saphelp_nw70/helpdata/EN/53/89503ede925441e10000000a114084/frameset.htm

Note that I only use merge ID on the top level navigation with the name of the role identical but with a different ID. I will use your situation stated above as example setup below.

BI (Role set with Entry Point and MergeID "BI". Role ID is BI_GLRep)

GL Reports (Workset)

GL Reports (Page)

GL Reports (Iviews)

BI (Role set with Entry Point with MergeID "BI".Role ID is BI_APRep)

AP Reports (Workset)

AP Reports (Page)

AP Reports (Iviews)

*Note that the Workset, Page and Iviews setup above is up to your preference.

The result we got (if a user has been assigned with the 2 above roles) was that on top level navigation, all user see only one tab (BI). On the second level navigation, they will see what you have assign them to see.

If a user have 2 roles, then he will see BI as the TLN and GL Reports and AP Reports as second lvl navigation. If only 1 role is assign, then he/she will see BI as TLN and either GL Reports or AP Reports (depending on which role you give).

This approach help you to manage your Navigations, largely your TLN (so your user do not have too many tabs on the TLN) and also possibly your second lvl navigation as well (via mergeID on workset).

Hope that can assist in your design for mergeID. I hear that its possible to merge at a lower level but I did not try that as the above concept works perfect for me at this moment.

Ray