R1498 is the CX lump sum release. It can be skipped for ASUCLA
and Hastings.
The release issues a one-time program, PPOT1498, that generates
FT payment transactions using DOS code 'LSP' and a costing file
to accompany them. The transactions are separated by primary
pay schedule, so you'll have the option of making the payments on
employees' normal pay schedules, or you can pay them all in one
compute.
The eligible population of employees is defined in dataset
FTPUSRn.GET.CUEELIG.Y2003
That in turn is matched to DB2 PAR data for the months of
November 2001 through September 2002, immediately preceding
the range and merit increases that were effective October 1st, 2003.
You'll get a roster of payments (report OT14981) and a warning/
control report (OT14982) that will show the payment dollar totals
and will identify employees with no eligible earnings.
The intent is to charge these payments proportionately to current
distribution fau's if possible. If that's unsuccessful, there is an attempt
to locate distributions as of the contract effective date, May 12, 2003.
If all else fails, a default fau entered in the spec card will be used.
Here is the information we'll need:
- a batch number for the generated FT transactions. The same single
number will be used for all of the batches (MO, MA, and BW), and if
the batches are combined, either all but one batch cards should be
deleted or each batch should manually be given a unique number.
- there is an option to specify an action code other than '32' in the
costing transactions. Let us know if you're interested. (In the past
none of our sites have used this.)
- the default fau for the spec card.
The release letter strongly advocates that all sites make these
payments at the same time, i.e., in computes with check dates near
the end of July. They can be paid in regular MO, MA, or BW computes,
or they can be paid in an XX compute, but the target range of check
dates is still July 28 through August 8th.
May we have your ok to install r1498? Also, any information you can
provide about expected timing and target compute(s) will be appreciated.
bvb
|