Subject: | |
From: | |
Reply To: | |
Date: | Sun, 17 Aug 2003 23:13:15 -0700 |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
Release 1507 issues a one-time program similar to the one in r1355,
issued two years ago. Because the intent of the program is to
determine eligibility and calculate across-the-board pay increases for
open-range employees in the TX unit, this release can be skipped for
ASUCLA and Hastings.
One-time program PPOT1507 is similar to program PPP910, even using
PPP910 spec cards, and operates much like a conventional range adjustment
process. Differences are:
- Eligibility criteria based on the collective bargaining agreement. See the
release documents for specifics. The criteria for the TX unit are a little
different than those for RX, e.g., tests for specific title codes, which
accounts for this separate program. Aside from that, r1507 is very
similar to r1506.
- TCS will not provide a payscale file. Instead I'll manufacture a dummy
payscale file containing only a header. The effective date is 10/01/02,
and for Davis, the header will also identify a biweekly effective date of
09/29/02.
- The one-time program is intended to be run in only PRLM1 and FINAL
modes.
- The costing transactions that are generated will have an action code of
'43' instead of the usual '28'. Whatever action you choose for handling
the costing action code for r1506 can apply to r1507 as well.
The release installation document includes a section that describes how
the retro process for RX open range employees is to be run. A key point
is that even though there will be only one step/sequence, it must be run as
a 'multi' process. Additionally, when running program PPP684 (job PP*RRA),
error code overrides must be specified. Information about the meaning of the
various error codes is given in the release letter.
IMPLEMENTATION
First, we'll need your approval to install the release. Additionally, we'd
appreciate it if you would let us know:
- Dates when you'd like us to run the PRLM1 and FINAL phases of
program PPOT1507. I suggest that they be on different dates, so
we don't run into problems with report files being overlaid.
- Your instructions regarding the costing action code.
- When you would like us to process the generated EDB file maintenance
and costing transactions.
- The timeframe in which you anticipate having us run the retro process.
- The retro error code override values.
- Your target for retro payments.
Thanks!
bvb
|
|
|