RMMAIN_Change scope option

[Former Member]

Dear friends,

I am working in Sol man 4.0. In t.code RMMAIN, under "Edit" option, we are having"Change scope" option. I wants to restrict this based on the user. Because, the project manager sets the scope for the consultants. But the consultants changes the scope.

How to restrict this option for users? Is any authorization object related to this option?

your help will be very much appreciated.

Senthil

[DoreenBaseler · Accepted solution]

Hello Senthil,

you may check out the following object:

AI_RMGEN = Authorization object to perform various implementation and development roadmap functions.

Defined fields

PROJECT_ID: Name of the project

ROADMAP: id of the roadmap

RM_FUNCT: roadmap functions. Currently:

• SCOP Using scope function to hide nodes from structure

I believe it to be this way that for all project-specific roadmaps you can user-specifically control if you want the user to allow scoping or not (SCOP).

I hope this helps.

Best regards,

Doreen

[Former Member · Accepted solution]

Hi Doreen,

Thnaks for your reply. I have tried in authorization object AI_RMGEN as per your instruction. I have maintained my Project & roadmap id but in RM_FUNCT, the system is not proposing value like "SCOP" if i press F4 . So i have inputed the value of " * " . After assigning that role to the user, still the "Change scope" option is active for all user. i could not restrict that option.

<b>My requirement is:

If any consultants, selects that option "Change scope", he should get a message that "You are not authorised to change the scope" But only Project manager can authorised to do.</b>

I am trying in one more authorization object namely "AI_RMMAIN"...sytem is telling this object is obsolete.

Plz...guide me

Thanks

Senthil

[DoreenBaseler · Accepted solution]

Hello Senthil,

Authorization works the other way around:

For the respective user who should <u>not</u> be able to scope: This user should not have SCOP (because assigning SCOP means "allow to scope").

I just checked out the following: When you set the whole authorization object AI_RMGEN to inactive regenerate the profile and log on again you will see that the user is not able to scope because the <i>Edit -> Change Scope</i> menu is greyed out in this case.

So you do not receive a respective message as you required but a greyed out menu for scoping, which, however, should bring the same result: The respective user is now no longer able to scope.

Good look and best regards,

Doreen

[Former Member · Accepted solution]

Dear Doreen,

Thanks. It is working.

Senthil