Opera3 VFP - Emailing of Payslips

Morning all,

I probably know the answer to this, but just wanted to run it past as everyone is always so helpful.

I have a site whereby they emailed the payslips this week for their Week 4, however 1 employee has reported (could have been others but nobody else has raised it and not even sure how we could check), but the employee received their Week49 payslip from previous tax year and not the Week4 payslip?

I've checked the PAYIMAGE and PSSIMAGE folder, and the Week04 payslip is in there.
Also checked the Historical Payslip report and there is no error showing for that employee....

I've got their IT people onto it, but we are continually having permission issues on the site with "Read Only" issues to the reports folder, so I'm guessing this could be partly to blame.

It is concerning as I'm afraid that another employee could get someone else's payslip - so any advice is very welcome.

Regards

Claire

Ford GTL.pdf

Find more posts tagged with

Pegasus - Partner General Discussions

Accepted answers

All comments

kerryh

Hi Claire

Note sure if the same problem but we had a very similar thing a while back, an employee went to payroll department and said they kept getting the same payslip - it was their own but a prior period and had been happening for a few weeks

We amended the email address to us and sent the payslip for the current period and it came through with the correct payslip for the correct period. We did the same for the payroll clerk so she could see that it was sending
eceiving the correct one but sending to the employee still opened the prior one

Not sure what was causing the problem but in the end it was put down to her phoneemails especially as tried changing the password and she started getting 'invalid password' when trying to open - it was thought somehow still locating an old one. The employee gave a different email address and the payslip was sent again to this and on opening was correct

Hope this may be of some help

Kerry

claire-craig

Hi Kerry

Many many thanks for this - as it is only one employee at the moment this could be the same so will give that a go as they are about to process week5 payroll so we'll see what happens.

Really appreciate you coming back.

Regards

Claire

tcyprys

Hi Claire

I had this a while back and it was the zpubhist table I think that appeared to be the cause; can't quite remember if I just removed the week 49 entry(in your case) in zpubhist for that EEs payslip record or renamed it in some way or reset a flag - but it was that table/record that appeared to be the cause/resolved it for me.

Regards

Tony

claire-craig

Many thanks Tony, wasn't even aware of that table but I am now and will definitely have a look at that if we have a repeat in Week5 :-)

Really appreciate you taking the time to help out.

Regards

Claire

Steve Loader

Hi, Claire,

The zpubhist table, as its name suggests, contains a history of published documents, such as payslips.

The records, for any given, customer or employee, are not necessarily consecutive, and so are chained.

If, somehow, that chain breaks, or a record in the chain is missing, then you would experience the error that your customer has experienced.

As Tony suggested, just examine the zpubhist table, locate the start record for the employee/payslip concerned, and follow the chain to determine if it has broken. If it has theh it should be relatively straight forward to fix it.

I hope that helps

Steve

claire-craig

Hi Steve,

Many thanks for coming back to me couple of months ago about the zpubhist table - unfortunately just had another occurrence with our customer of employee getting payslip for a previous period, so I'm now starting to look at this table which it has data in it going back to 2016.....

Do you know is it ok to do a purge on this table? What's the risks?

Regards

Claire

claire-craig

Hi Tony

Got another occurrence of employee getting a payslip for week 50 of previous year when it should have been week 11 of current year so as per your and Steve's advice I'm looking into the zpubhist table and hoping you could keep me right....

For this particular employee they only started in week50 of 23/24 (so not too much data to look at)
The last line of data in the table is the Week 11 she should have got and the only thing I can see different is the publisher status of "R" and wondering do you know what this means?

Also the record for the P60 with the Failed status, is this a concern?

Any help or advice would be greatly appreciated.

Regards

Claire

claire-craig

Hi all,

Just wanted to give you an update with regards to the latest issue I had with email payslips in case anyone ever comes across something similar. It turns out that it was the mobile device when opening the attached payslip was the issue.

We sent the payslip to the employee but then also added the payroll administrator into one of the email address fields, and when the payroll administrator opened the payslip using outlook it was the correct one however when the employee opened it on their mobile phone is was the incorrect payslip, so the mobile devices pdf reader was either corrupt or the phone was opening an old pdf.

We also did do a purge of the zpubhist.dbf. The customer has had 2 server moves since email payslips was implemented back in 2015 however the PegScheduler database wasn't restored from the previous SQL version so the message items database and the zpubhist were completely out of sync so as a precaution cleared this down in line with what was in the message items and batch database (obviously taking a backup and putting it away somewhere safe in case ever needing a historic payslip)

Regards
Claire

Copyright © 2025 Infor. All rights reserved.