Lawson Security (LSF) and unable to Secure Cash Ledger Module (CB)

Is there a trick to securing the Cash Ledger module (CB). Our I/S Analyst has tried to specifically exclude access to the CB module but has been unable to get it to work. We aren't even talking about data level security at this point. Just excluding access to CB. He has written the code to specifically say "CB" [No Access] and written code that says something similiar to "If GL" [All Access] Else [No Access] but neither stop access to CB. Any thoughts would be greatly appreciated.

Find more posts tagged with

Comments

Legacy Contributor

The first thing I would check is to see if the CB module has been granted access under a different Role/security class. If a user has one role or security class that has no access for CB, but another role or security class has grant access to CB - then the grant access takes precident.

Legacy Contributor

Please find below the Rule which works for us.
We Have created an additional Attribute called CompanyLimited to accommodate just Inquiry access, but should work directly against the Company Attribute I think. The Rule has been used against the Company/CompanyLimited Attribute, Element Group COMPANY:

if(((SystemCode='AP'||'PO'||'CB'||'RQ'||'IF'||'WO'||'WH'||'IC'||'MA'||'AM'||'AC'||'TX'||'TE'||'AR'||'GL')&&user.attributeContains('CompanyControl',lztrim(COMPANY))))
'ALL_ACCESS,'
else
if(((SystemCode='AP'||'PO'||'CB'||'RQ'||'IF'||'WO'||'WH'||'IC'||'MA'||'AM'||'AC'||'TX'||'TE'||'AR'||'GL')&&user.attributeContains('CompanyLimited',lztrim(COMPANY))))
'ALL_INQUIRES,'
else
'NO_ACCESS,'

Legacy Contributor

Good point by Richard about SAecurity conflicts. Many times I have noticed that higher level access overrides what I am trying to process.
Excellent thought.

Copyright © 2025 Infor. All rights reserved.