View Full Version: Lawson Is An X File ?

LawsonTalk > HR/Payroll > Lawson Is An X File ?


Title: Lawson Is An X File ?
Description: Missing records


cman13 - May 22, 2006 07:55 PM (GMT)
We are having difficulty "losing" records from the tables. Example, this morning, I identified 3 employees (2 termed and 1 active) that are missing from EMPLOYEE. I also found a REHIRE whose HRHISTORY was gone. Last week, found 8 employees (in a different, non benefit company) missing in PAEMPLOYEE, but in EMPLOYEE.

Has anyone experienced this behavior before? How was it resolved? Did you ever find out what the cause was??

Any and all advice appreciated, I have spent 4 days with Lawson Support trying to find and fix all the missing links.... :banghead:

trezaei - May 22, 2006 10:28 PM (GMT)
Hi Lisa,

I am betting you have some sort of custom program or interface which is not doing what it's supposed to. I have never seen a out-of-the-box Lawson program create orphan records as you've described.

It might also be worthwhile to check your ladb.log file and check for any DBRec type errors that may have happened recently.

You might also want to run an integ on your DB to make sure everything is in order. Not that it does a whole heck of a lot but I have found it useful in the past.

mthedford - May 23, 2006 06:07 PM (GMT)
Has someone accidentally hit the delete key/button on these records, not realizing what they did?

cBreeze - May 23, 2006 06:57 PM (GMT)
We had one situation (in 4+yrs) where All the history records for one employee, for one check, disappeared. The data was there after payroll close, b/c we just happened to copy Prod to test box, right after that payroll and the hist recs were in test. Approx, 2wks later they were no where to be found in Prod.. Also the Info for that check appeared on all of the rpts for that payprd as well... (That we save on a rpt archive system(ras).)
I would guess that someone deleted them from an sql or something, But I w/be the only one to do it.. & I didn't... Lawson couldn't find a reason either.
So I had to write many sql statements to update/insert into the necessary files. And from all the sql's I had to write, it would have taken some time to delete this one particular checkid from all of these files (& subtracting from the quarters..etc..)
Fortunately I had the recs from test to help with camparison.
Only oddity that may have caused the problem, is that the employee had a weird dept change during that pr run... Somehow it never fully closed in the payroll I suppose.

3monkeys - May 24, 2006 03:41 PM (GMT)
Aside from a wacky custom interface, could anyone have created some paint screens without your knowledge and used them to change/delete any records, even accidentaly? If somebody knows what they're doing they could also remove the edit checks from the paint screens.

The Upload Add In tool may also do something like this and the user might not even know they did it. Something to consider.

-GW



Hosted for free by InvisionFree