• Search Forums
    Advanced Search Topics Posts
Prev
Next
Forums Financial Management Lawson S3 Financials

GL Maintenance Tracking / Statistics

 5 Replies
 1 Subscribed to this topic
 43 Subscribed to this forum
Sort:
Author
Messages
yabrahiem
New Member Send Private Message
Posts: 0
New Member
8/30/2007 2:20 PM
I'm new to Lawson, so please forgive me if this doesn’t make sense, or I'm leaving out information.

I'm looking for a table that contains audit information on what account changes were made via GL20, GL00, GL30.

One of the Accounting managers would like a count of every GL record update that is made to Lawson, preferably by the form updated, and which user updated it. He's just looking for a way to track how much work his people are doing.

He specifically mentioned:
Account inactivations, activations updates via GL20 screens
Account adds/changes/deletes via GL00
Views, lists, attributes, values, RC's etc

What's the best way to capture this information from Lawson?
John Henley
Send Private Message
Posts: 3351
8/31/2007 1:07 AM
Lawson's audit trail in GL is mostly non-existent (HR is really the only module that has any decent tables). So the info you're looking for really doesn't exist, at least "out of the box". There are a few ways you can add this capability to Lawson, such as via user exits, database triggers, as well as using the new LSF9 security auditing capability (assuming you're using LSF9 and Portal--not LID). Also Machensoft's ESBus product has some audit capabilities.
Thanks for using the LawsonGuru.com forums!
John
yabrahiem
New Member Send Private Message
Posts: 0
New Member
8/31/2007 12:59 PM
Thanks for the reply. Unfortunately, we're still on 8.0.3, but we're migrating to LSF9 & Portal by July 31st of next year(the environment decommission date). I will look into this then.
k-rock
Veteran Member Send Private Message
Posts: 142
Veteran Member
9/19/2007 11:43 AM
Look into Machensoft from Kinsey & Kinsey
Deleted User
New Member Send Private Message
Posts: 0
New Member
9/21/2007 8:27 PM
Hi. I am trying to create a database trigger on the GLNAMES table for audit purposes. We could have user exits on GL20, but we're also using GL161 to interface some from JDA. So, database triggers is a better option. For some reason, I get a variable not defined or not usable error when I try to create an insert trigger.

Has anyone else had a problem with creating triggers on lawson tables for iSeries? Does anyone have an example of one that works?

Deleted User
New Member Send Private Message
Posts: 0
New Member
9/24/2007 2:44 PM
I found the answer!!! On the iSeries, the SQL Long name must be referenced, not the AS400 fieldname. So, instead of using NEW.DGLNACCUNT for the accounting unit, you need to reference it by NEW.ACCT_UNIT.