Restricting department access in LSA

We are currently using LSA and would also like to restrict users to certain departments. Is there a simple rule we could use to exclude one department?

Find more posts tagged with

Comments

Legacy Contributor

We were never able to get Accounting Unit selection to work.
You can do it via Company access, or Process Levels in HR, but other than that, I am unable to suggest anything else.

0712131256598360.doc

todd-brown

I think with the element group security when you use company and process level for GL type access, the process level is actually accounting unit.

Legacy Contributor

Good call!
I think you are right, but you still should be able to fileter by A/U, and that I just couldn't get to work.

Legacy Contributor

Has anyone been able to restrict HR department access?

todd-brown

I have a rule that looks similar to this. This restricts people to only certain accounting units for a company

if(isNumInRange(lztrim(COMPANY),4000,4199))
'ALL_ACCESS,'
else
if(lztrim(COMPANY)==1000&&((match(trim(PROCESS_LEVEL),'601130|603160|609010|609030|609040|609050|610010|610030|614100|614110|614120|621120|633200|633220|633610|633630|633640|633650|633660|633670|633900|639600|640400|642420|642140|642460|655100|655610|655630|655660|655680|655690|655900|655960|655980|655990'))||trim(PROCESS_LEVEL)=='PR'))
'I,'
else
'NO_ACCESS,'

productmodeling

We defined a custom attribute and used the match function. The attribute contained the values to include and were expressed using explicity values, ranges, or wildcards, etc. that is valid for a 'regular expression'. By having as an attribute, it allowed the security group to maintain the values w/o getting into the rule builder.

Legacy Contributor

Andrew, can you send me an example of your custom attribute. I would like to setup this option instead of using the rule builder.

Copyright © 2025 Infor. All rights reserved.