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

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 ePersonality. The UPCAPERS program will be deprecated and may eventually become obsolete. The UPCAPERS program can still be used to produce reports
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 6 changed one line
To create the new XML format, the interface creation program UPCAPERSXML will now be used to generate the CalPERS file. The IDIF definition used for the previous UPPHF-based implementation is no longer used.
To create the new XML format, the interface creation program UPCAPERSXML will now be used to generate the CalPERS file. The [IDIF] definition used for the previous [UPPHF]-based implementation is no longer used.
At line 10 changed 3 lines
California PERS operates a number of different retirement systems.
At this time, only the Public Employees’ Retirement System (PERS) is supported.
There is no support provided for Judges’ Retirement Systems (JR1 and JR2), Legislators’ Retirement System (LRS) or the Supplemental Income Plan (SIP).
California PERS operates a number of different retirement systems. At this time, only the Public Employees’ Retirement System (PERS) is supported. There is no support provided for Judges’ Retirement Systems (JR1 and JR2), Legislators’ Retirement System (LRS) or the Supplemental Income Plan (SIP).
At line 39 changed 16 lines
|CALPERS_INTERFACE_TYPE|DED|This CalPERS ID is a new unique identifier, created by the new system. The CalPERS XML Schema names this item ‘Interface Type’ and most likely should contain ‘10006’ for regular Payroll.
|CALPERS_BP_ID|DED|If you are reporting your own payroll files the Business Partner ID is the same as the Employer CalPERS ID. If you use a third-party vendor then CalPERS will assign a unique identifier number once the third-party becomes an approved business partner
|CALPERS_EMPLOYER_ID|DED|This CalPERS ID is a new unique identifier, created by the new system. This replaces the CalPERS Employer Code and Unit Code used today. This CalPERS ID of the Employer who is submitting the payroll on behalf of all the employees in the file.
This may be the Employer where all the employees are working, but it may also be the Employer who is authorized to send payroll for other Employers’ employees
|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.
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|CalPERS-generated unique CalPERS ID for Participant
• The CalPERS ID will be 10 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 reporting employer, Appointment ID must be provided or the payroll record will error
|CALPERS_INTERFACE_TYPE|DED|This CalPERS ID is a new unique identifier, created by the new system. The CalPERS XML Schema names this item ‘Interface Type’ and most likely should contain ‘10006’ for regular pyroll.
|CALPERS_BP_ID|DED|If you are reporting your own payroll files, the Business Partner ID is the same as the Employer CalPERS ID. If you use a third-party vendor, then CalPERS will assign a unique identifier number once the third-party becomes an approved business partner.
|CALPERS_EMPLOYER_ID|DED|This CalPERS ID is a new unique identifier, created by the new system. This replaces the CalPERS Employer Code and Unit Code used today. This CalPERS ID is of the employer who is submitting the payroll on behalf of all the employees in the file.\\ \\This may be the employer where all the employees are working, but it may also be the employer who is authorized to send payroll for other employers’ employees.
|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 56 changed 2 lines
|PERSRPT SIP Type|DUD|This line reads from the Lexicon X_PERSRPT_SIP (created above) to return one of four values PERSRPT SIP1, PERSRPT SIP2, PERSRPT SIP3 or PERSRPT SIP4. Currently only PERSRPT SIP2 is supported for SIP reporting.
|Pers SIP Plan Id|DUD|Pers SIP Plan Id is the plan identification number supplied by CALPERS for the Unit that is being reported.
|PERSRPT SIP Type|DUD|This line reads from the lexicon [X_PERSRPT_SIP] (created above) to return one of four values PERSRPT SIP1, PERSRPT SIP2, PERSRPT SIP3 or PERSRPT SIP4. Currently only PERSRPT SIP2 is supported for SIP reporting.
|Pers SIP Plan Id|DUD|Pers SIP Plan Id is the plan identification number supplied by CALPERS for the unit that is being reported.