OK to install for San Diego.
It was noted by our ACT that there are some local system impacts and are working on the related project to accommodate the release.
Thanks,
Nini
-----Original Message-----
From: Barbara Vanden Borre [mailto:[log in to unmask]]
Sent: Sunday, November 21, 2004 11:01 PM
To: [log in to unmask]
Subject: payroll release 1607
Release 1607 is the second of four phases of Postdoc changes. In the first
phase, r1605, a new BELI code of 'P' was introduced for Postdocs, and also
the logic by which the system can derive it. This phase addresses insurance
benefits and assigned BELI.
- Postdocs are eligible for medical, dental, vision, supplemental disability,
UC-paid life insurance (includes AD&D), and UC-paid disability insurance.
- Postdoc insurance programs are given special plan codes and are given
separate GTN entries.
- R1607 modifies 3 CICS screen programs. Display of employer contribution
and employee deduction is suppressed on IINP and IINS when the assigned
BELI is 'P'. PPWEINS currently identifies the supplemental disability entry
for employees on the GTN table by looking for a benefit type of
'Z'. Because
the postdoc supplemental disability entriy will also have a type code of
'Z',
PPWEINS is modified to look up the GTN number in copymember
CPWSXIC2 (entry established in r1605).
- An incidental change in r1607 is a correction to the Delta Dental
contribution
GTN number coded in program PPEI199 which was inadvertently set to the
wrong value (117 instead of 065) in r1556. The release letter says that
Davis
is the only campus using a value of 117, but Hastings does also. We had
local mods in place for Riverside, SC, SB, and ASUCLA to address the
problem that now can be removed. However now that the number is being
standardized in the program, Davis and Hastings will need local mods.
- Two one-time programs are provided:
- PPO1607A - will create X1 transactions to set employee assigned BELI
codes to 'P' when the derived BELI codes are 'P'.
- PPO1607B - One of the 'invisible' aspects of open enrollment is that
carrier
data files are created to advise the carriers of enrollments for the
new year.
Postdocs were not included in open enrollment this year, so PPO1607B
is issued to create a carrier file similar to the one produced by
PPP560.
TABLE UPDATES
- system parameter - parameters 189 and 190 will contain rates for Postdoc
Life/AD&D and Postdoc disability insurance
- GTN - to add medical, dental, vision, and supplemental disability entries
for postdocs. These transactions require site-specific values.
- data element - to add new insurance plan codes, 'P' value for assigned
BELI, and trigger for edit program PPEG635
- message - to correct message text typos
- routine definition - to define new edit programs PPEC165 (Post benefits
conedit) and PPEG635 (prevents non-Postdocs from enrolling in Postdoc
supplemental disability insurance
- processing group - to add PPEC165 and PPEG635 to processing groups
08 and 12
IMPLEMENTATION
R1607 is date-mandated to be installed with very precise timing
requirements.
1 - The release itself, and its table updates, must be installed "after all
computes for November earnings are complete and immediately prior
to Monthly Maintenance to begin December".
2 - One-time program PPO1607A must be run immediately after Monthly
Maintenance.
3 - The release letter says that the X1 transactions generated by PPO1607A
must be processed immediately in an EDB update, however in conversation
with Base Payroll, we've learned that a few days won't hurt, which means
we may be able to take advantage of already-scheduled updates for some
sites.
4 - "Enrollment of postdoctoral scholars into the postdoc benefit plans
should take place as soon as the X1 transactions to set the Assigned
BELI (EDB 0360) are posted.
5 - Once all the Postdoc benefit enrollments are complete, PPO1607B
must be run.
As I think you'll see right away, accomplishing steps 1 and 2 on the
prescribed schedule will be a challenge because, for five of our seven
sites, the final compute of the month, monthly reporting, and monthly
maintenance all run on a single night. We'll have to shoe-horn in the
release processing on that night. Davis and San Diego run monthly
maintenance on the following work night, but their compute schedule
for November is such that we'll have to implement extra early.
Here's how steps 1 and 2 work out for each site, along with possible
dates for the EDB update for a couple of sites:
DV - final compute and MR on Wednesday 11/24. Installation of r1607
over the Thanksgiving holiday. MM and PPO1607A on Monday 11/29,
followed by a scheduled EDB update in which the X1 transactions
can be processed.
RV - final compute and MR on Thursday 12/2. Then, in this sequence:
installation of r1607, MM, and PPO1607A also on 12/2.
SD - final compute and MR on Wednesday 11/24. Installation of r1607
over the Thanksgiving holiday. MM and PPO1607A on Monday 11/29.
SC - final compute and MR on Thursday 12/2. Then, in this sequence:
installation of r1607, MM, and PPO1607A also on 12/2.
SB - final compute and MR on Wednesday 12/1. Then, in this sequence:
installation of r1607, MM, and PPO1607A also on 12/1. X1 trans
can be processed in the EDB update scheduled on 12/2.
AS - final compute and MR on Thursday 12/2. Then, in this sequence:
installation of r1607, MM, and PPO1607A also on 12/2.
HA - final compute and MR on Thursday 12/2. Then, in this sequence:
installation of r1607, MM, and PPO1607A also on 12/2.
May we have your ok to install r1607 on the schedules indicated above?
We'll also need your priority numbers for the GTN transactions, as well as
any special instructions for liability fau's. Scheduling of EDB updates
as well as PPO1607B can be worked out with Production Control and
Maintenance later.
bvb
|
