This release is the first phase of the Master Record Keeper (MRK)
project, which transfers responsibility for administration of UC's
defined contribution plans from UCOP HR/Benefits to Fidelity.
This phase includes modifications to provide additional demographic
data to Fidelity and to automate loan processing. (See release
documents and service request for details.)
Key features include:
- A person-level 'without salary' field is added to the PER table of
the EDB and will be displayed on the IGEN screen.
- A "Distribution Eligibility Date' to 'identify employees who are not
separated but are otherwise eligible for distributions' is added to
the benefits tables (BEN and HBN) in both the EDB and HDB.
It is added to the IRTR, HPER, and IBN1 screens.
- New program PPEM108, which will run during monthly periodic
maintenance, will derive values for both new fields. It sets the person
level WOS indicator to 'Y' if all of the appointment level WOS values
are 'Y', and it sets the distribution eligibility date to the first of
the new
month for employees who had no payroll activity in the month just
ended. Then, during the month, if daily employment status derivation
changes an employee's status to 'A'ctive, the distribution eligibility
date will be re-initialized to 01/01/0001.
- The two new fields are added to the monthly MEM740 UCRS interface file.
They also are added to the nightly -outgoing- IVR file, along with a
General Purpose Loan ID, a Primary Residence Loan ID, and an
indicator to identify 'safety' employees. Identification of 'safety'
employees is based on their title codes having a retirement code 2
value of '2' in the TCT. Our understanding is that ASUCLA has no
police or fire title codes and that although Hastings does, they are
not eligible for the UCRP safety classification. The two loan id's
correspond to existing GTN numbers 243 and 253 respectively.
- Loan transactions will flow from Fidelity to PPS via the nightly 'IVR'
transaction feed, on the 5th and the 20th of each month, per the
release letter. I assume there will be some slight adjustment in timing
if those dates should fall on a holiday or weekend.
- Seven new GTN entries are added:
730 - Tax-Deferred 403(b) Flat
731 - Tax-Deferred 403(b) %
732 - NTD DCP
733 - DCP Regular
734 - DCP Casual
735 - DCP Summer Salary - Deduction
736 - DCP Summer Salary - Contribution
Note that a future phase of the MRK project will involve switching
employees from the current GTN entries that are specific to the type
of investment (savings, equity, etc) to these generic entries. R1635
is just doing some advance setup.
- Three one-time programs are issued in this release. Each produces
only a tiny control report.
PPO1635A will derive values for the new person level WOS indicator.
PPO1635B will initialize the WOS indicator to N and the distribution
eligibility date to 000000 in the UCRS history file.
Some background: Each month the PPI740 program creates
a MEM740 file for UCRS consisting of changes to
demographic
data since the last month. It knows what has
changed because
it compares the contents of the current EDB with a
historical
file of data previously sent to UCRS. We don't
want to send
a record for every single employee when we add new
fields
to the MEM740 file, so we back fill last month's
history file
with 'turned off', 'neutral' values such as the N
and 000000
noted above, so that only employees whose WOS indicator
or distribution eligibility date are switched on
this month will be
perceived has having changed.
PPO1635C will initialize the WOS indicator, distribution eligibility
date,
and safety indicator in the IVR employee history
file in a
similar manner so it won't appear that every single
employee
has had a change, only those with real activity.
TABLE UPDATES
- The new fields are added to the data element table.
- Seven GTN table entries are added. You can view the template
transactions at http://www.ucop.edu/payroll/REL2005/R1635/gtnprod.pdf
- The text of one message is tweaked.
- New program PPEM108 is added to the routine definition and
processing group tables.
IMPLEMENTATION
This is a date-mandated release that must be installed no later than
April 18th, which doesn't give us a lot of time, given the DB2 structure
changes. My hope is to install for some sites on weekends (either this
weekend or the next - sooner would be better), but I think some will
have to be on weeknights, working around production batch scheduling.
We would appreciate receiving an ok to install from you at your earliest
convenience, along with the priority numbers to code for each of the
new GTN numbers. For Davis, Riverside, and San Diego, please also
provide us with the local liability FAU values you'd like to use. For other
sites we will specify the account number given in the template transactions
unless you tell us otherwise.
bvb
|