Best Practice for PR12

Mary, there is no table (e.g. HRHISTORY) in v9 holding the history for the ACH distributions; only automated solution I have seen for this is similar to tracking history for employee dependents, which is to use Smart Notifications (LSN) to monitor data changes on the table. Since this table (EMACHDEPST) does have effective start/end dates, I think it is safe/sufficient to use those to track changes, thereby keeping a full history. Only caveat required is to change the default flag to 'N' when changing the default account for an employee. Hope that helps, and anyone with other ideas, please chime in...

Once you get to version 10 and it could be one of the newer point releases, that history will be available on a more granular level.

It was presented at Inforum.

You think I'd have remembered that, since I reported an issue with the v10 upgrade documentation having incorrect instructions for loading those tables (PADICT, etc.) not adding the v10 records for HR10...

Well that's cool to know it's out there. I think we are two years away from 10 my boss wants to wait until you all get all of the bugs worked out for us ;)
But at least we'll get to 9.1.9 this summer. Thanks Margie and John!

Mary, we are one of the companies "working out the bugs" for you....   We are in the process of migrating to V10.   I just changed data on PR12 and it looks like it is doing much better with the change history dating.   version - 10.0.2

I'm sure the answer to this is NO, but, I thought I'd ask anyway. If payroll deletes a record entirely, is there anywhere to look to see who deleted it?

You are correct, Mary - unless your organization uses some kind of server auditing tool that captures all activity)

Thanks Stephanie. We are remote hosted so I'll ask them.