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, 19 Aug 2005 12:42:28 -0700
Content-Type:
text/plain
Parts/Attachments:
text/plain (43 lines)
<ASUCLA and Hastings - you can skip this release as it consists solely of
one-time code for the EX unit.>

Release 1659 provides support for a contract agreement entered into by the
University and AFSCME on behalf of employees in the EX (Patient Care
Technical) unit.  These employees are to be given an across-the-board (ATB)
4% base-building salary increase effective September 1st (August 28th for
biweekly employees), and because payroll sites did not feel quite ready to
use the Web Merit application for this purpose, Base has issued a one-time
program to do the job.

As in similar past releases, the one-time program, PPOT1659, is modeled on
the PPP910 range adjustment program and is intended to be run in PRLM1 and
FINAL modes.  PRLM1 will identify the eligible population, and FINAL will
generate EDB file maintenance and costing transactions.  Notes:

- Eligibility criteria are listed in the release letter.
- An action code of 55 (signifying an ATB increase) will be assigned
   to costing transactions.
- We will call the one-time jobs PP*1659A and PP*1659B.
- A later release will provide additional reporting for the EX ATB salary
increases.

The release letter not only designates r1659 as date-mandated, it
explicitly cites the computes in which the new rates should take effect:

· the September 21, 2005 check for the BW pay period beginning 08/28/05
· the September 30, 2005 check for the MO pay period beginning 09/01/05.

The implications are that we need to implement very quickly (keep
timesheets and online rosters in mind) and that retroactive processing is
not expected.  Biweekly sites clearly have the biggest time crunch.

Would you please facilitate this process by:
- letting us know if you need a different costing action code
- approving installation of the release
- providing us with the target date on which you would like to update
   the EDB with file maintenance transactions generated by PPOT1659

Thanks, everyone!

   bvb

ATOM RSS1 RSS2