R1639 is an urgent fixit to the PPIIVR program that every payroll site runs
Monday through Friday evenings to create an extract file of data for the 'IVR'
database that supports UCFY, Risk Management, and so on.  I got involved
in this one when Base Payroll approached me to ask about unusual spikes
in the numbers of records being sent for most if not all sites since r1635
was installed.

Normally PPIIVR operates in the same manner as the monthly MEM740
process, generating files of incremental changes based on a comparison
of current EDB data with history files of previously sent data from the last
run.  Somewhat larger than normal files might be sent after running
monthly periodic maintenance, but throughout the rest of the month
the numbers are generally fairly stable.

Base Payroll observed abrupt, large increases in the record counts for the
IVR employee file, but not the appointment, deduction, or dependent files,
with numbers high enough to suggest that at times data for all employees
was being sent instead of only those with activity.  First we ruled out any
connection between the increases and scheduled production processes.
Then, by comparing IVR history files for some of our sites from one day to
the next, it became clear that the volume of EDB data changes was normal,
and that PPIIVR was simply not accurately determining when a change had
occurred.  That's what this release fixes.

R1635 added two new fields (without salary indicator and distribution
eligibility
date) to the IVR employee interface, and because the comparison of distribution
eligibility date in the current EDB and the previous day's history file weren't
using the same format, PPIIVR thought there were more changes than there
actually were.  The correction required only 3 lines of code to make the
date formats the same.

Per the release letter, r1639 'must be installed immediately to prevent the
production of large number of unnecessary IVR Employee Change records.'
May we have your ok to implement asap?

   bvb