Data Level security

 2 Replies
 0 Subscribed to this topic
 27 Subscribed to this forum
Sort:
Author
Messages
golfer24
Advanced Member
Posts: 46
Advanced Member

    Has anyone applied data level security on a system code, like Billing, where you restricted a user from creating invoices for a particular process level?  In our billing system we have 2 companies and 6 process levels for each company.  I've set this up to where a user has 'Inquiry only' for one of those process levels, and I have one user who has an issue.  For some reason, she cannot drill into an invoice in BL80 and look at the AR transaction.  Does this seem weird or odd to anyone?  I don't understand as to why this new layer of security prevents her from seeing.  When I take away the data level security, she can see the AR transaction information just fine when she drills into BL80.  By the way, we are on LSF 9, ESP 6, MSP 4 and LAUA security.  Any thoughts would be appreciative.  Thanks.

    MattM
    Veteran Member
    Posts: 82
    Veteran Member
      Ensure any "process level" or "company" restrictions written on an element are very specific as to system code, etc... Lawson ALWAYS looks to see if there are any restrictions on Process Level or Company and will apply the restrictions even though there are no rules on the token/file. This is the 700/900 level security Lawson has always used. Is this LAUA or LS security?
      golfer24
      Advanced Member
      Posts: 46
      Advanced Member
        This is LAUA security.