My Two Census

Formerly the non-partisan watchdog of the 2010 US Census, and currently an opinion blog that covers all things political, media, foreign policy, globalization, and culture…but sometimes returning to its census/demographics roots.

Rumor: Change in DAPPS Payroll Software?

Anyone have any knowledge about the following tip:

Subject: DAPPS payroll software change
Message Body:
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.

Tags: , , , , , , ,

4 Responses to “Rumor: Change in DAPPS Payroll Software?”

  1. nemo Says:

    It is essentially true, however it has nothing to do with the bug preventing recording working until midnight. That was fixed several weeks ago. It may well have reintroduced that bug however, no check has been made.

  2. A worker Says:

    This is true- we ran into errors when trying to enter night differential hours. This has nothing to do with the midnight aspect- there were no problems with people putting midnight as their ending time.

    Night differential starts at 6pm. Most people write something along the lines of 3:30-6, 6:8:30, 9-12am on their time sheets, it makes adding up the hours easier for them and for admin. In the system, the clerk needs to enter “3:30-8:30, 9-12am” instead. Not a big problem, just a minor headache, at least at my office.

  3. Admin OOS Says:

    Completely and 100 percent untrue and fabricated email.

    1 Pre-NRFU you had to end at 2345 (11:45pm) but since late April this has not been the case.

    2. “Such entries have been accepted up until now, and are *necessary* to properly record work across the midnight boundary”

    100% False. You CANNOT have a 308 go from one day to the next. If you start work at 6pm and get off at 3 am you have to do TWO 308′s. So this “issue” was never an issue. You can’t even have a 308 spanning two days.

    “Rumor has it that the change was made to stop somebody from getting extra pay by exploiting a bug in the system” Rumor from who? The voices in your head? This “exploit” never existed and has never even been possible to begin with. ALL 308′s stop at midninght, PERIOD.

    We had ZERO issues with payroll closing on 6/29 and actually haven’t had an issue in many months.

    It is obvious fake emails like this that destroy any shred of credibility SRM once had. An obvious scam artist who is only trying to fan the flames of a non-existent fire.

  4. Payroll Software Says:

    It also appears that a key diagnostic report regarding overlapping time is now, sometimes, “broken” in a way that masks existing errors.
    ___________
    James