Anybody have exprience providing Total Compensation Reports?

I've done them stitching together data from tables like PRTIME, BENEFIT, and different TA tables like TAEEMASTR. Now you'd have to use the LP equivalent. It's not that hard.

Using the BENEFIT table was a lot more work than just going straight to the QUARTDED table.  Believe me, that's what I tried first too.  Mainly because different benefit plans store their company cost and employee cost in different fields within the database tables (like flex plans vs. others).

I'm lazy, I didn't want to worry about those differences, and I always like making things flexibile to handle other situations so I just pull the particular deduction codes right from QUARTDED, I have way higher confidence doing that compared to piecing together a benefits history.  This ties me directly to what the employee paid, instead of hoping there are no errors in our BN32 entries and history.

Also has the advantage of not caring if there are 8 types of Medical plans of one flavor, they can all go to the same deduction code on BN15 setup.

I just followed the money, right to QUARTWAGE and QUARTDED, so I could just look right at the deduction codes for Company and Employee both.  That way I didn't need to hunt and peck for information in PTO usage, Benefits, and Work hours in all their separate tables.  They all funnel back to those tables.  And I can handle any adjustments seamlessly because they show up too.

Jeremy Zerr
St. Luke's Regional Medical Center
Boise, ID
Lawson Reporting
Exercise log

The problem with the QUART tables, as you probably know, is that you can't run it for the middle of a quarter. In other words, if you run the rpt on 3/15/08 for 2/15/08 pay, then you can't pull that out. Of course, the performance will be superior since those records have considerably fewer records than PAYDEDUCTN and PRTIME.

I created Total Compensation Statements last year and will do it again this year. I pulled data from Lawson into an access database and then worked with a local printing company (Econoprint) to print and mail the statements. They took a while to pull together but it was MUCH more cost effective than using a statement vendor.

I pulled as much as I could into one table in Access but a couple items I just pulled new tables with Employee number and then everything just linked based on the employee number. It really was not too difficult.

I'm curious ... how did your custom versions compare to BN242? Was something missing? Was it the formatting, etc.? I have used Crystal to "pretty-up" BN245 before, and was wondering if a similar tactic would work for BN242. In other words, if the logic's all there, that's a good starting point, right?

Just looked at that BN242 report, displays current benefits fine, but it also only displays current benefits and the yearly contribution with that benefit, but I found it necessary to properly handle someone who changed in the middle of a year to a different plan, to try and be as accurate as possible.  This was one of the main reasons that drove me to use the Deductions taken from QUARTDED.

Also, for the wages part of it, because we are a hospital, we would like to break out the different type of hours worked so that employees see how much shift differential and overtime they get.  This is what drove me to use the Wages from QUARTWAGE so I could separate out those pay groups.

Since we really only want to report Total Comp at most once a quarter, I figured I could get away with using the QUARTWAGE and QUARTDED tables instead of the PRTIME and such.

Also as you said, the report is not very nice looking at all, we are trying to design something a little more professional.  Figured I might as well just do it all outside of Lawson instead of have little bits and pieces of Lawson reports to rely on.  Don't know for certain, but will probably change when we upgrade to 9.0 anyways.

Jeremy Zerr

I have created a crystal report that creates total comp statements we have been using it for the past two years and have good luck with it.we take the pdf output file and send it to a postal presort company and they print and stuff the envelopes for us. I am using the prtime and deduction tables as the basis. last year we added a personalized letter also. It took about a month to create. I have to spend a few hours each year making sure it has been updated to include any new pay or deduction codes. It can be done if you can dedicate the time.

When you use the PRTIME and Deduction tables are you compensaton reports giving info for the previous year since the PRTIME and deductions are actuals not future?  How would you do it, if you wanted to project what what the earnings would be for the current year?

I would prorate totals.  If you wanted to forecast employee earnings on July 1, for example, then you could simply double the amount of money from PRTIME from Jan 1 to June 30, for example.  Obvious considerations include:

• employee hire date
• overtime (hard to project)
• year end bonuses

I'm doing this now, and since we don't use Lawson Payroll, I created a file using both Lawson and our Payroll system to provide earnings, bonus, benefit elections/accruals etc. Once the file was done, I did one big merge in MS word and it worked fine, I am now in the process of verifying the data and we will deliver via mail to the locations to distribute or to employee's home address (were still deciding). The process wasn't that difficult, but I wanted to do something custom based on the direction I was given.