Soooo, is there a way to secure the output of a report with LS?

I know how to secure the report itself. and I know how to secure parameters on the report. But to secure the output of say GL290 to only show certain Accounting Units has proven to be a real challenge.

It seems like this program much like a lot of others uses what is called "Programmatic Security" for COMPANY and ACCT-UNIT.

This means that I have to build a rule for Element Group containing both company and acct-unit. Well, in GL accounting Unit is process-level (the element).

SO I tried doing that, it works and it doesn't work.

It turns out that (I think) GL290 does a FIND-NLT and if you have restricted the very first one it finds then it just stops right there. SO if I say do only

COMPANY==10
ACCT-UNIT==2000

I get nothing since the first ACCT-UNIT is say 1000

But if I say

COMPANY=10
ACCT-UNIT<=2000

It works (for the reason I stated above). But that's not what I want. It's all very frustrating as it seems a lot of how LS was designed was an after-thought and most of the "Programmatic Security" basically turns into what is better describe as a bug.

Any other thoughts on how to secure report outputs would be greatly appreciated. Otherwise I just might have to patch GL290 myslef.

Anyone know how to debug batch programs in 9.0 ? :(

Trezai:

You wrote:

Works the same as in Lawson 8, 7, 6, .... because it's the same COBOL as before! :D The only tricky part (as I'm sure you know) is that starting in 8.1 the location of the pdlib's and wslib's was moved. I was poking around in GL290 in Apps 9 last week, and it looked really familiar.

Well I got Lawson to admit that GL290 isn't working properly with the Element Group rule for the reason that I had speculated.

quote from gsc :

"I wrote up PT177404 for this issue and have assigned it a priority of 2"

so hopefully we'll get something soon.