Release 1458 provides the code for a new interface to the SHPS vendor
who is managing DepCare and HCRA.  All payroll sites will run new
batch program PPP466, which is issued in this release, twice a month
to write files that will be consolidated at UCOP for handoff to the vendor.

Two types of data will be included in the interface:
- enrollment information taken from the EDB is always sent
- DepCare and HCRA deduction activity taken from the DB2 PAR
   **that has not previously been sent**

A small control report, PPP4661, is produced.

Selection of data from the DB2 PAR presented quite a design challenge
because the twice-a-month reporting schedule doesn't synchronize with
any payroll site's computes, and there has to be a way to mark cycles
of data as already having been processed so that duplicate deduction
activity won't be sent to SHPS.  The solution is a brand new table in
the DB2 PAR called - you guessed it! - PPPSHP.  It's a very simple
standalone table containing only 5 fields:  the pay period begin and
end dates, check date, compute type, and a Y/N processed-or-not
indicator.  Note that the end date and compute type comprise the
key, which is another reason why we must be careful to use different
pay period end dates for XX computes in months in which more than
one XX compute is run.

One thing leads to another:   the existing PPP465 program that is
used to load sequential PAR data into the DB2 PAR database is
modified in r1458 to also insert a row for each cycle of data that is
processed into the new PPPSHP table with the indicator set to N.
Additionally, we need to insert rows into the table for past computes,
which we will do with the PPOT1458 one-time program that is provided.

TABLE UPDATES
   Message table transactions are provided.

IMPLEMENTATION
   This is one of those situations where we need the release installed
yesterday, and Base Payroll does apologize for the extremely short
implementation time.  My understanding is that, as a startup measure,
Jerry has made DepCare and HCRA enrollment information based on
Open Enrollment available to the vendor, however SHPS does not yet
have any deduction information.

Bruce issued the FTP specs last week after a naming convention
with cycle codes like those used for New Employee Registry was
agreed upon.  Like the NER file, the new SHPS interface file is due
on the 2nd and 17th of each month, therefore we will simply add the
new program to our existing PP*IFC jobs and no additional
scheduling will be required.  The initial files are due by 1/27, but if
we would do it sooner, that would be good.  May we have your
approval to install?

   bvb