• Search Forums
    Advanced Search Topics Posts
Prev
Next
Forums Infor / Lawson Platforms S3 Security

LAUA GL account security

 3 Replies
 0 Subscribed to this topic
 18 Subscribed to this forum
Sort:
Author
Messages
riegerj
Veteran Member
Posts: 44
Veteran Member
10/6/2009 5:05 PM
We are using LAUA security and received a request to lock down user access to specific accounts (not accounting units).  The only way I know of to do this is to apply record level security to each table that has account number in it for each security class.  Has anyone done something like this and know of a better way to do this?  Thanks!
John Henley
Posts: 3364
New Poster
New Poster
Congrats on posting!
Engaged Reader
Engaged Reader
You are an engaged reader!
Avid Reader
Avid Reader
Avid Reader art thou!
10/6/2009 5:30 PM
There are several pieces to this -- can the user view transactions/forms vs. enter that account on forms vs. drill-around, etc. .
How soon are you going to migrate to LSF9 and implement Lawson 9 security? If it's fairly soon, you can do it via easier-to-implement rules.
If you really want to do it with LAUA, the only way I know is to use data security, and "fake" the account to look like an accounting unit (it ain't pretty).
Thanks for using the LawsonGuru.com forums!
John
riegerj
Veteran Member
Posts: 44
Veteran Member
10/6/2009 5:38 PM
Thanks John.
We are on LSF9 but there are no plans to move ahead with Lawson 9 security, we can't get all users to portal for a couple of years probably. We want to complete lock down the user so they would only be able to view and enter on specific accounts. Would we want to create accounting units for each account or were you talking about another method with the accounting units?
riegerj
Veteran Member
Posts: 44
Veteran Member
10/27/2009 2:58 PM
Just an update, I spoke to soon and we have decided to make those users go to LSF9 security. We are implementing now for the users that will affect. Thanks for responding though.