This page (revision-26) was last changed on 31-Aug-2022 10:30 by Karen Parrott

This page was created on 26-Nov-2021 10:22 by jmyers

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Page revision history

Version Date Modified Size Author Changes ... Change note
26 31-Aug-2022 10:30 23 KB Karen Parrott to previous
25 26-Nov-2021 10:22 22 KB Meg McFarland to previous | to last
24 26-Nov-2021 10:22 22 KB ihowie to previous | to last
23 26-Nov-2021 10:22 22 KB kparrott to previous | to last
22 26-Nov-2021 10:22 22 KB kparrott to previous | to last
21 26-Nov-2021 10:22 22 KB kparrott to previous | to last

Page References

Incoming links Outgoing links
UPCAPERSXML
UPCAPERSXML

Version management

Difference between version and

At line 4 changed one line
The CalPERS organization has defined a new file format (XML) for submissions. This interface will replace that which was created by the [UPCAPERS] program in the application. [UPCAPERS] will be deprecated and may eventually become obsolete. [UPCAPERS] can still be used to produce reports. Note Nov 2017 UPCAPERS is not longer available in version 5.04.xx
The CalPERS organization has defined a new file format (XML) for submissions. This interface will replace that which was created by the [UPCAPERS] program in the application. [UPCAPERS] will be deprecated and may eventually become obsolete. [UPCAPERS] can still be used to produce reports
At line 15 removed 8 lines
!!Function Preference Setup
There is a new 'Function Preference' called [SCHED HRS ALIAS|SCHED HRS ALIAS(System_Preference)]. By default the regular 'Scheduled Hours' is taken from IEAS. If it should be taken from DJB or DPS then this preference can have a value of exactly 'DPS' or 'DJB'.
Scheduled Full Time Hours ( <n1:ScheduledFullTimeHoursPerWeek>) is now taken from one of three new columns (depending on the Preference setup).
It is taken in order by EASD.REPORT_HOURS_PER_WEEK if populated, then DPD.REPORT_HOURS_PER_WEEK, and then DJD.REPORT_HOURS_PER_WEEK.
This upgrade was primarily to handle Part Time Employees properly.
At line 39 removed 7 lines
|PERSADJ RSA EE|Employee Retro Earnings Contribution
|PERSADJ RSA ER|Employer Retro Earnings Contribution
|PERSADJ RSC EE|Employee Retro Special Compensation Earnings Contribution
|PERSADJ RSC ER|Employer Retro Special Compensation Earnings Contribution
|PERSRPT EE SIP2|(Optional) SIP2 Employer Contributions.457 Plan - This element should only be populated if the CalPERS Plan has 457 Supplemental Income associated with it.
|PERSRPT ER SIP2|(Optional) SIP2 Employer Contributions. 457 Plan - This element should only be populated if the CalPERS Plan has 457 Supplemental Income associated with it.
|PERSRPT LN SIP2|(Optional) SIP2 Loan
At line 50 removed 2 lines
Recent changes have allowed some of these fields to be instead referenced directly via database columns, but not all UDF's have been replaced at this time.
At line 57 changed 3 lines
|POSTED UPCAPERS|PPH|A flag that is used to indicate if the pay header has been posted to CalPERS or not. A value of “Y” means that it has and it will not be processed by subsequent UPCAPERSXML runs. A value of “N” or null means that it has not yet been processed and is eligible to be picked up.\\ \\%%information Note that this UDF has a space in the name not an underscore.%%\\ \\This is for compatibility with prior versions of CalPERS reporting. \\ \\This User Defined Field has been replaced by the database column POSTED_RETIREMENT as of the 4.10 release.
|CALPERS_ID|EID|the CalPERS-generated unique CalPERS ID for the participant\\ \\The CalPERS ID will be ten digits in length and used in place of a Social Security Number in contribution files. Prior to system “go-live”, CalPERS will send employers a file with the CalPERS ID for each of their existing employees. This is for compatibility with prior versions of CalPERS reporting. \\ \\This User Defined Field has been replaced by the database column EXTERNAL_RETIREMENT_ID as of the 4.10 release.
|APPOINTMENT_ID|EASD|The code representing the appointment into which the employee has been hired\\ \\Prior to system implementation, CalPERS will provide employers a list of their member’s Appointment IDs. After system implementation, employers can run a report online to generate a list of Appointment IDs.\\ \\If multiple appointments exists with the reporting employer, Appointment ID must be provided or the payroll record will error. \\ \\This User Defined Field has been replaced by the database column EXTERNAL_APPOINTMENT_ID as of the 4.10 release.
|POSTED UPCAPERS|PPH|A flag that is used to indicate if the pay header has been posted to CalPERS or not. A value of “Y” means that it has and it will not be processed by subsequent UPCAPERSXML runs. A value of “N” or null means that it has not yet been processed and is eligible to be picked up.\\ \\%%information Note that this UDF has a space in the name not an underscore.%%\\ \\This is for compatibility with prior versions of CalPERS reporting.
|CALPERS_ID|EID|the CalPERS-generated unique CalPERS ID for the participant\\ \\The CalPERS ID will be ten digits in length and used in place of a Social Security Number in contribution files. Prior to system “go-live”, CalPERS will send employers a file with the CalPERS ID for each of their existing employees.
|APPOINTMENT_ID|EASD|The code representing the appointment into which the employee has been hired\\ \\Prior to system implementation, CalPERS will provide employers a list of their member’s Appointment IDs. After system implementation, employers can run a report online to generate a list of Appointment IDs.\\ \\If multiple appointments exists with the reporting employer, Appointment ID must be provided or the payroll record will error.
At line 72 changed one line
Retired Annuitants may be identified either through their Employment Status (on [IEAS]) or via enrollment in a CALPERS plan. These employees will appear with a transaction type of "EPN" on the file.
Retired Annuitants may be identified either through their Employment Status (on [IEAS]) or via enrollment in a CALPERS plan.
At line 82 removed 8 lines
!!Transaction Types
Retroactive Pay (RSA) is determined by the 'Pay Category Type' of RETRO.
If the Pay is NOT RETRO then the Pay is considered a Current Period Contribution (EPR) if the Pay is in the Current Pay Period.
If the Pay is NOT RETRO then the Pay is considered a Prior Period Contribution (PPA) if the Pay dated before the Current Pay Period.
At line 91 changed one line
My CalPERS requires that any Retroactive Pay be reported in separate ‘Transaction Types’. To accommodate this, Retroactive Pay must be created with [UPRETRO] and be stored into a pay category that has the Pay Category type of ’07-Reto Pay’.
My|CalPERS requires that any Retroactive Pay be reported in separate ‘Transaction Types’. To accommodate this, Retroactive Pay must be created with [UPRETRO] and be stored into a pay category that has the Pay Category type of ’07-Reto Pay’.
At line 108 changed 5 lines
|(CPE) Pay Period|Mandatory, LOV available\\This identifies which Pay goes to the CPE (California Public Employees' Retirement System) Report.
|Beginning Pay Period|Mandatory, LOV available\\This identifies the starting pay period of the current CalPERS Reporting Cycle. Any transactions that are dated previous to the Period Begin date of this period are considered adjustments.
|Ending Pay Period|Mandatory, LOV available\\This identifies the ending pay period of the current CalPERS Reporting Cycle. Any transactions that are dated after the Period End date of this period are considered adjustments.
|Combine Start End PP|Optional\\If set to "Yes", report will combine Start and End Pay Periods.
|Incl RSA in ADJ|Optional\\If set to "Yes", report will include RSA (Retroactive Salary Adjustment) in ADJ report type.
|Pay Period|Mandatory, LOV available\\This identifies the pay period of the current CalPERS Reporting Cycle. Any transactions that are dated previous to the Period Begin date of this period are considered adjustments.
At line 127 changed one line
|Payrun Number|Optional, Multiple selections, LOV available\\This field limits the report to the payrun numbers specified.
|Payroll Number|Optional, Multiple selections, LOV available\\This field limits the report to the payroll numbers specified.
This page (revision-26) was last changed on 31-Aug-2022 10:30 by Karen ParrottTop