Release 1611 enhances PPS by providing the means to capture HCRA and
DepCare (sometimes referred to as DCRA) information in the History Database
(HDB) and display it on the IBN1 screen.  HCRA and DepCare information also
is added to IDOC benefits text.  (See the sample contained in the service
request document.)

 From a technical perspective, r1611 requires DB2 structure changes to the
HBN table, to add fields in which to store the new data.  Functionally, the
intent is to build a repository of HCRA and DepCare data that can easily be
accessed when SHPS or others request historical information regarding
enrollments or deductions.

The way that data capture in the HDB works is that, first, fields in one or
more DB2 tables are defined in which to store the data.  Next, entries are
made in the history data element (HDE) table to define the new data
elements and identify which table(s) they are a part of.  Some data values
are collected as of a point in time, e.g., on a monthly or annual basis,
and others are collected each time they change, and this, too, is specified
in the HDE.  HCRA and DepCare information will be collected on an ongoing
basis each time the values change.

In the normal course of events for the 'ongoing' approach, whenever an
add-on to historical data is implemented, collection of data commences from
that point onward, gradually, as individual employee data is
modified.  R1611 is a little different in this respect.  Instead of saying,
well, when we get around to installing, we'll begin collecting data,

- It's date-mandated to be installed before running calendar year periodic
   maintenance.  The significance of CY processing is that it will zero out/
   terminate nearly all HCRA/DepCare enrollments.

- And, r1611 provides a one-time program to facilitate a mass capture of
   HCRA/DepCare information for all employees currently enrolled.  Thus
   we'll have a picture of how things look right now before we wipe it all out
   in CY.  It's a clever approach:  one time program PPOT1611 reads through
   the EDB and generates an EDBCHG file containing information about all
   existing HCRA/DepCare information, without updating anything.  We then,
   in the same job, will run PPP742 to process that EDBCHG file and populate
   the history database with initial entries.  Thereafter, updates will
occur on an
   incremental basis.

TABLE UPDATES
   There are no conventional control table updates.  There are CICS Help
updates and history data element table updates to be applied by Maintenance.

IMPLEMENTATION
   As noted above, r1611 must be installed - and the one-time program must be
run - prior to calendar year periodic maintenance.  Testing is complete and
we're ready to proceed for nearly all sites once we receive your approval.

   bvb