Hi All,
Iam facing one problem regarding user rights. I created one role like purchase order posting with user rights setup objects. I did transaction. Then permissions was created accordingly. After that when i assign that role to perticular user he was not able to post the PO? they are getting 'You dont have permission to read xx table'. why the permissions are not created properly by using of the user rights setup objects. Is there any bug on this objects?
Thanks & Regards,
Kishore...
0
Comments
Are you sure the user posts in the same way that you did?
Are you sure you used all purchase order data the user entered?
Remaining two points are same.They are posting the same way.
Is there any problem by using the developer license to create roles. because user right setup objects having IDs 70000 onwards. Thats why i used developer license. Customer license does not support those range.
Regards,
kishore...
Other issue could be where did this guy create and test permissions did they use developers license in customers DB? if so it may have posted to a table the customer has no access to under their license and now that table must be cleansed before user can post again.
Without knowing which objects are involved hard to say.
Doing the same process with code coverage during a test usualyy shows you what is involved in each step.
You are quite right in what you have said einstein :thumbsup:
Its not possible for us to know what the exact issue is without knowing the process followed and objects system wants access to EG customer sites could have addons or custom tables and user role could have been created in cronus
](*,) ](*,) ](*,) ](*,) ](*,) ](*,) ](*,) ](*,) ](*,) ](*,) ](*,)
Someone once said "if you can't say anything nice, then don't say anything at all", well I think best in this case that I just don't say anything at all.
#-o
Please share your valuable ideas.
Regards,
kishore...
Why would the customer have objects ranging from 70000 and up if their license doesn't have access to these objects? Sounds like there has been copied some functionality between 2 databases where the second one doesn't have access to the customisations.
If you have modified the posting routine to put data into some table (i.e. 70002) the customer license has to have access to that table. Making user rights that have access will do absolutely nothing if the license doesn't have access to it.