CMPPAY-L Archives

UC Payroll Release Distribution Notes

CMPPAY-L@LISTSERV.UCOP.EDU

Options: Use Forum View

Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Barbara Vanden Borre <[log in to unmask]>
Reply To:
UC Payroll Release Distribution Notes <[log in to unmask]>
Date:
Fri, 1 Jul 2005 13:17:19 -0700
Content-Type:
text/plain
Parts/Attachments:
text/plain (39 lines)
Release 1651 introduces a new means by which employees/
dependents who do not meet the eligibility rules as set forth in
the Group Insurance Regulations Supplement 6 can be
de-enrolled from health and welfare plans.  Currently, when
UCOP HR&B identifies ineligible family members, 'a report is
sent to campus and laboratory locations where the ineligible
dependents are manually de-enrolled.'  The new, more automated,
process has two PPS components:

1 - HR&B will create X1 transactions with a de-enrollment indicator
     of 'Y' that will flow through the daily IVRNH/benefits/web update
     process that we run in the evening after production CICS
     comes down.  That special PPP130 update is restricted to
     processing only certain data elements, and in r1651 is
     modified to 'add 'X1' transaction processing for medical,
     dental, vision, and legal de-enrollment indicator fields ...
     and post to the EDB.'

2 - Monthly periodic maintenance will perform the actual
     de-enrollment and will treat the 'Y' code just like the existing
     'X' code except that a reason code of 'AD' (Administrative
     De-enrollment) will be assigned.

TABLE UPDATES
    Transactions are provided with which to update:
- the data element table, to add the 'AD' code
- the code translation table, to add the 'AD' code and also to
   change the description for 'XD' from simply 'De-enrolled' to
   'Deenrolled-suspension of Premiums or ineligible dependent'

IMPLEMENTATION
   Installation is date-mandated to occur by July 15th.  Although
the release documents don't explicitly say so, I assume that is
when the new transactions will begin to flow through to PPS.

May we have your ok to install?

   bvb

ATOM RSS1 RSS2