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:
Sat, 6 Mar 2004 21:02:58 -0800
Content-Type:
text/plain
Parts/Attachments:
text/plain (41 lines)
Release 1553 enhances the system in response to a change in policy
"governing layoff, reduction in time, and severance pay that includes a
provision for a staff severance payment in the event of layoff or involuntary
reduction in time."

The key to the changes is new fields being added to the EDB layoff table:
- SEV_AMOUNT_PAID    (DE 0482  STAFF SEVERANCE AMOUNT PAID)
- SEV_PAY_NUM_DAYS  (DE 0483  STAFF SEVERANCE PAY NUMBER OF DAYS)
- SEV_PAYBACK_IND  (DE 0484  STAFF SEVERANCE PAYBACK INDICATOR)
- SEV_PAYBACK_AMOUNT  (DE 0485  STAFF SEVERANCE PAYBACK AMOUNT)

Corresponding fields are added to the HDB layoff table, and all four fields
are added to the ELOF, ILOF, IOFF, and HLOF screens.

For batch updating, the existing Layoff Administration Worksheet (UPAY
781, transaction 'LF) doesn't have enough room to add the new fields, so a
new Layoff Worksheet has been created (UPAY 917).  The new transaction
type is 'LX', and I expressed concern to Base Payroll that it could lead to
confusion with the 'LX' late pay compute transaction, but was told that the
users requested it.

Layoff status reporting is accomplished using program PPP862, to which
the new fields also are being added.  In preparing to write this cmppay-l
note, I tried running the pre-r1553 version and discovered a problem in that
it called a non-existent message handling routine, however the error surfaces
in only some runs, e.g., PPP862 abended for Davis but not for SB.
Base Payroll has now corrected that problem as an addendum to the release,
including updating the bind statements.  Fyi, we do not run PPP862 on a
scheduled basis for any of our sites, but it is available via on request job
PP*ONBB.

TABLE UPDATES   (All transactions are provided)
- data element
- messages
- data elements to screens
We'll also define the new fields for the history database.

May we have your approval to install when we complete our testing?

   bvb

ATOM RSS1 RSS2