LS security rule for journal entries (GL40 or GL45): users should be able to maintain their own JEs

Can anyone share an example of a security rule for GL40 or GL45 that limits users to their own journal entries? In other words, a user should be able to add/maintain their own journal entries, even release/quickpost them on GL45 - but they should NOT be able to do anything to anyone else's JE's on GL40 or GL45. Anyone have a rule that you can share, or can point me in the right direction?

Find more posts tagged with

Infor Lawson Technology Group - Discussion

Accepted answers

All comments

Derick Safarian

Here is an example. In this example, ficclaw81 is the name of the Identity Service, and you may need to adjust this name to reflect the name of your specific Identity Service.

(getIdentityAttribute('ficclaw81','LOGIN',user.getRDId())==trim(getDBField('GLCONTROL','OPERATOR',form.GLC_COMPANY,form.GLC_FISCAL_YEAR,form.GLC_ACCT_PERIOD,form.GLC_SYSTEM,form.GLC_JE_TYPE,form.GLC_CONTROL_GROUP,form.GLC_JE_SEQUENCE)))

unknown

Yay!! Thank you Derick, that works great on GL40. In fact, I have already been able to use it on a few other screens as well. Question though...if I build a new rule for something else...say an HR form for example, how do I know what fields go on the righthand side of the equation? For example, I would not have though that year, period, etc. would be used on the GL40 rule.

Derick Safarian

The right side of the equation uses the getDBField function, which relies on the index sets of the specific table you are referencing in your rule. To obtain the index sets, use the MS Add-Ins query tool, and this will display the index sets you need to reference in your rule. Then, use the form or table fields to fill in those index sets in the rule. In the example above, I am trying to use the OPERATOR field from the GLCONTROL table. The index set for the GLCONTROL table uses the fields Company, Fiscal Year, Acct Period, System, JE Type, Control Group, and JE Sequence. I have used the fields from the GL40.1 form to fill them in my rule.

unknown

Got it. That helped me get over the hump. Those fields are still required to do the same kind of security in GL45, but the form itself doesn't have those fields so I was getting an error in SecAdmin when trying to save the rule. Instead, the fields are on each individual line on GL45, so I applied the same rule to GL45.1 LINE-FC, and now it works like a champ. Thank you very much for the assist on this.

Copyright © 2025 Infor. All rights reserved.