topic Re: Different values for different users in Application Development and Automation Discussions

Different values for different users

Former Member — Fri, 08 Jun 2007 11:37:26 GMT

Hello All,

Well to start with, this is my first post in this Security Forum.

Our requirement is to store different Carrier ID's in different people's ID's.

1) I started with creating an Authorization Field say ZCARRID.

2) Then I created an Onject Class(ZTX_OC) in SU21 and then created an Authorization Object inside the Class. Lets say the Auth Obj. is named ZTX_AO1

3) Now I went to PFCG, and created a Role, ZTX_RL and went to Authorization Data, clicked on Changed Authorization data, and then manually added Auth. Obj. and then added specific Carrier ID values like AA, BB.

4) Now finally went to SU01 and added the ROLE to the users profile...

But if I have 150 different users with different values in each, then will I have to create 150 different ROLES for the same....

Can't I add localization data for the users ??

Please advise....

Thanks,

Tatvagna Shah

Message was edited by:

Tatvagna Shah

Re: Different values for different users

Former Member — Sat, 09 Jun 2007 07:33:43 GMT

just copy the existing role and just change the role name.and change the different values in each role.to assign that user.

Re: Different values for different users

Former Member — Mon, 11 Jun 2007 06:01:19 GMT

Hi,

In such case you do need to create 150 roles. Make use of CATT utility for this purpose. That should make it very simple.

Regards.

Ruchit.

Re: Different values for different users

Former Member — Mon, 11 Jun 2007 06:15:39 GMT

Hi Ruchit,

Actually, we spoke to our Client and then came down to a conclusion, that we will indeed create different Roles and one Auth Object. for the same.

Will check the CATT utility and let you know if any doubts...!

Thanks for you Answer.

Tatvagna.

Re: Different values for different users

Former Member — Thu, 19 Jul 2007 10:04:00 GMT

Hello All,

We have finally come down to a custom security solution.

Thanks.