Join 83 other subscribers
Thought-Provoking Commentary for the Lawson Software Community
If you haven’t discovered Ken Hamady, you need to check out his recent post on troubleshooting “duplicate records”. This is perhaps the most frustrating issue that report designers encounter when developing reports against Lawson tables.
If you don’t have a good grasp on the JOINs/relationships that are used in Lawson’s S3 databases, you can really get in trouble in a hurry. Some quick tips based on what I see quite often:
WHERE PRD.PRDSET5_SS_SW = 'Y'
AND PRD.ACTIVITY = ATN.ACTIVITY
AND PRD.COMPANY = ATN.COMPANY
AND PRD.ATN_OBJ_ID = ATN.OBJ_ID
Again, just a few tips to help you whip your reports into shape, and keep you out of trouble with your DBA!
The man knows his stuff. Very knowledgeable.
This is good information.
The link for –Deal with Lawson’s quirky way of storing “null dates” in the database– doesn’t work. I have used my own work-around, but would be interested in someone else’s take on the issue.
Thanks. I have updated the link.