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:
Mon, 11 Oct 2004 17:25:34 -0700
Content-Type:
text/plain
Parts/Attachments:
text/plain (68 lines)
As is the case with many collective bargaining agreements,
not only is a special one-time program required to simulate a
conventional range adjustment, with special eligibility requirements
folded in, but there is also a reporting component.

In the case of the EX Patient Care unit pay increases effective
January 1, 2004, a one-time program was issued in release 1597
for across-the-board (ATB) increases.  Per diem rate increases
for the same population were handled via the issuance of a
payscale file from the Corporate Title Code System, to be
processed in a normal range adjustment.

R1601 addresses the reporting phase by providing another
one-time program, PPOT1601, to produce paper reports:

- POT16011 - a control report
- POT16012 - central office report.  The installation document
   indicates that multiple copies are required, one of which is to be
   sent by HR to AFSCME and another to UCOP Labor Relations.
- POT16013 - departmental report

and also a data file to be named  FTPUSR*.PUT.EXWAGES.Y2004

There are one or two input files, depending on the site:
- the workfile from one-time program PPOT1597
- the PPP910 workfile produced when the EX per diem range
   adjustment was run.  Among our sites, only Davis and San Diego
   were provided per diem payscale files, and thus a per diem range
   adjustment was not run for the others.

WHO AND WHAT

- ASUCLA and Hastings have no EX unit employees, so this
   release can be skipped entirely for them.

- Riverside and Santa Barbara:  R1601 must be installed.
   Input will be from only PPOT1597.

- San Diego:  R1601 must be installed.  Input will be from both
   PPOT1597 and the EX per diem range adjustment.

- Santa Cruz:  Opted to implement ATB increases manually
   and did not have a per diem payscale file, therefore it has
   no input files for PPOT1601 and we expect to skip the release.
   Note, however, that the campus still must meet the reporting
   requirements for the union and UCOP Labor Relations.

- Davis: Also opted to implement ATB increases manually,
   and must comply with union and Labor Relations reporting
   requirements locally.  We're uncertain what the plan is for per
   diem rates, i.e., whether that also will be handled manually.

Additional notes for Davis and SC:

- Without having run PPOT1597, we also don't have the basis
   for running the ATB retro's.
- For now we're assuming that we will not install r1601 for you,
   however you might find it easier to satisfy the reporting
   requirements by locally building the input data for PPOT1601
   and giving it to us to process rather than writing the entire thing
   yourself.  PPOT1601 will do all the formatting and will take care
   of miscellaneous things like sorting and organizing the data and
   filling in such things as hire date and home department code.

Ok to install?  (for those sites where it's relevant....)

   bvb

ATOM RSS1 RSS2