Prev
Next
Forums Lawson S3 Financials

GL security classes for LSF9 security

Sort:
You are not authorized to post a reply.
Author
Messages
dangus
New Member
Posts: 2
New Member
4/24/2013 7:08 PM
    We are in the process of switching to LSF9 security. We are in the early stages of defining the security classes for the General Ledger group and are just wanting to know what items we need to look out for in the set ups. Thank you.
    Georgette
    Veteran Member
    Posts: 52
    Veteran Member
    4/25/2013 10:01 AM
      Hi Dangus,
      I saw something in an earlier post on this site about an Activity field on the RQC Accounting which pulls from the AC10. Dependent on your policies, you may want to limit drill around on the AC tables to specific groups.
      Georgette
      Greg Moeller
      Veteran Member
      Posts: 1498
      Veteran Member
      4/25/2013 2:46 PM
        In my experience, DO NOT have any parent/child relationships ('Based on') in security classes or security roles. It's much easier to track down an issue if you don't have these defined and it's been a pain fixing ours to not have them.
        Georgette
        Veteran Member
        Posts: 52
        Veteran Member
        4/25/2013 3:08 PM
          Since security classes can be shared among different roles, best practice is to make sure the security class is focused on a single task if possible. For example create an APCheckPrint security class which includes all the forms and jobs needed for printing checks.

          However, avoid using the same form in different security classes (maintenance nightmare). For example, one Accountant had access to one of the forms needed for printing checks, so that form needed to be carved out and put in its own security class.
          You are not authorized to post a reply.