Anyone have any knowledge about the following tip:
Subject: DAPPS payroll software change
It appears that the following occurred on either 6/27 or 6/28. A change to D-308 timesheet editing rules in DAPPS was implemented which no longer permits timesheets to include entries for which one entry ends at the same time as the next begins. Such entries have been accepted up until now, and are *necessary* to properly record work across the midnight boundary. Rumor has it that the change was made to stop somebody from getting extra pay by exploiting a bug in the system.
It is not clear what the details are, for example how multiple task codes affect the results, but it is known for certain that work across the midnight boundary is affected, and that the new edit rules can cause errors between timesheets and batches. Washington I.T. support apparently is telling people they have to shift their time 1/4 hour away from midnight (trivially, falsifying their timesheets). My LCO discovered that payroll batches which had been entered without errors for the previous week, if re-opened and re-saved for any reason, generated NEW errors. It also appears that a key diagnostic report regarding overlapping time is now, sometimes, “broken” in a way that masks existing errors.
If my understanding of DAPPS is correct, it is *possible* that MANY LCOs experienced errors when payroll was transmitted 6/29.
The change was made the day before payroll had to be wrapped up and transmitted, and there was NOT SO MUCH AS AN E-MAIL NOTIFICATION. We can’t be the only ones who got burned; HQ I.T. support confirmed the situation and provided the workaround.
I would love to know how much of a problem this has caused, and/or whether the change had to be backed out of the code. As of Tuesday afternoon 6/29 the change was still in place.