Converting laua to LS9

we are getting ready to start the conversion of laua to Lawson Security 9. For those that have already completed this or are already underway, are there any lessons learned that you would like to share? Thanks, for any input.

Find more posts tagged with

Comments

bob-heitzman

When our team started this effort the concensus was that doing cleanup of unused security classes was worth the time investment since it would help "un-clutter" what would need to be analyzed and converted.

Legacy Contributor

1) Setup access to Forms/Fields by Job Process not necessarily Job Function (multiple Roles may make a Job Function); be as granular as possible. Confirm each Job Function with Data Owner. Try and standardise your Job Functions (Profiles), therefore Roles.
2) Setup individual File accesses for each Application, bearing inn mind you may need multiple accesses for critical/secure data (e.g. HR).
3) Ensure you have a procedure in place to confirm/deny access by Data Owner.
4) Make available to your Super Users access to clarify which Security Classes/Roles access what Forms/Files (easy to read format).

Legacy Contributor

Also be aware, do NOT under-estimate the resource required by Users to complete this process.
It takes a long time to phase this in, presumably by Application/Department.
People don't like change, even though this is merely a front end to the SAME programs/processes.
Don't just emulate your LAUA access, review what is required by each business process.

Legacy Contributor

In laua, you can define at any system code that it is inquiry only. In LS9, it looks like it can only be done at the token level.

So, if I want to setup a security class where the role will have all the AM forms/tokens as inquiry only, do I have to assign it at each individual token or is there another way of doing these?

Thanks...

Legacy Contributor

We have setup a separate Attribute called 'CompanyLimited', then you are able to distinguish who has access to Companies for full Update (enter Companies in the Company Attribute), and those Companies where Users only have Inquiry access (enter those Companies for Inquiry access).

Of course you will then need to create a rule on the Security Class to accommodate ALL_ACCESS for CompanyControl, ALL_INQUIRIES/I for CompanyLimited, and NO_ACCESS for the rest.

Copyright © 2025 Infor. All rights reserved.