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
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
At line 12 changed 3 lines
!!!REPORT CALIFORNIA PERS
----
!!Report Parameters & Filters
!!Benefit Plan Changes - Setup
The Benefit Plan is still required, any values that are computed by the benefit plan that need to report to CalPERS must now be stored in a pay component for the UPCAPERSMXL program to pick up.
At line 16 changed 3 lines
||Report Parameters||
|Entity|Mandatory, LOV available\\This field limits the process to the entity specified.
|Pay Calendar|Mandatory, LOV available\\This field limits the process to the pay calendar specified.
!!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'.
At line 20 changed 4 lines
Pay Period
Directory Name
CPE File Name
SP2 File Name
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 25 removed 4 lines
|Test Report|If set to “No”, the POSTED UPCAPERS field will be updated with a “Y” so the pay header being processed does not get picked up again in a subsequent run. The generated XML file will be marked as a valid file.
If set to “Yes” the generated XML file will be marked as a ‘Test Run’ and the POSTED UPCAPERS field will not be updated.
|Exception Level|Optional, [Exception Level|X_TRACE_LEVEL] lexicon available\\This field defines the exception level (report messages) required. A ‘trace’ report of exception messages may be produced to assist in the testing phase. If necessary, choose from 0 – 9 (highest) level of trace. Please note that this is a voluminous report and will cause very slow performance.
|User Comments |Optional, Text \\This field holds the user-supplied comment which will appear in the header of all pages of the report. This is useful during testing phases to identify similar reports from each other.
At line 30 removed 25 lines
|Include All Pays (Testing)|Optional,[Yes or No|X_YES_NO] lexicon available\\If <YES>, the report will include all pays.
|For Pay Ending Date|Mandatory, Date, LOV available\\This field allows you to indicate the last date for the pay you are processing.
|Include Elected Officials|Optional,[Yes or No|X_YES_NO] lexicon available\\If <YES>, the report will include elected officials. If on the employee's Benefit Enrollment form, the Elected Official user field is <Yes>, that employee may be included in this report.
|Re-compute ER at Summary|Optional,[Yes or No|X_YES_NO] lexicon available\\If this parameter is <Yes> then the ER contribution will be recalculated in the summary based on the earnings and rate from the benefit coverage.
|Sort By Name|Optional,[Yes or No|X_YES_NO] lexicon available\\If this field is <Yes>, the employee records will be printed in name order. If the field is <No> the records will be sorted by person code.
|Create File|Optional,[Yes or No|X_YES_NO] lexicon available\\If this field is <Yes>, an output file is created. If this field is <No>,the report is run without creating an interface file (normally for testing purposes).
|Interface Code|Optional, LOV available\\Only those reports of the format “CAPERS Diskette” will display. Choose from the report formats created. The format “HL$CAPERS” has been provided as a sample, but should be copied, and the copy edited, by the client before running this report. The report definition selected will determine the format of the output file (if any), as well as the columnar content of the report.
|Interface Directory|Optional, Text\\Must be a directory on the server for which the current user (as signed onto the client’s network) has write capability. For example, the entry ‘C:\TEMP’ accesses the ‘TEMP’ directory on the server, not the local directory for the computer terminal being used.
|File Name|Optional, Text\\Enter the name of the file that will be created in the interface directory specified.
|Trial|Optional, [Yes or No|X_YES_NO] lexicon available//You may choose to run the report in a trial mode to see results <Yes> or in update mode <No>.
||Report Filters||
|Payroll|Optional, Mandatory, LOV available, <ALL>\\This field limits the report to the payrolls specified.
|Test Person |Optional, Multiple Selection, LOV available, <ALL>\\This field limits the report to the test persons specified.
!!Benefit Plan Changes - Setup
The Benefit Plan is still required, any values that are computed by the benefit plan that need to report to CalPERS must now be stored in a pay component for the UPCAPERSMXL program to pick up.
At line 56 changed one line
To facilitate reporting through UPCAPERSXML, certain elements have been defined. The following elements may be defined to include the pay components that reflect the different categories of information. If one of these categories is not used, then the element does not need to be set up.
To facilitate reporting through UPCAPERSXML, certain elements have been defined. The following elements may be defined to include the pay components that reflect the different categories of information. Unless otherwise identified below, these elements must all be set up, even if they are empty.
At line 70 changed one line
|PERSRPT LOAN|After tax loan payment
|PERSRPT LOAN|After tax loan payment - This element is optional
|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 added 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 80 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.
|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.
|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.
At line 95 changed one line
Retired Annuitants may be identified either through their Employment Status (on [IEAS]) or via enrollment in a CALPERS plan.
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.
At line 79 added 11 lines
!Semi-Monthly payrolls
Note that for semi-monthly payrolls, the user has to run UPCAPERSXML for the __SECOND__ period in the month. Semi-monthly payrolls are reported on a monthly basis and therefore only one out of the two pay periods are used for reporting (the second pay period in the month).
!!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 103 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 116 changed 9 lines
;Entity Code:One entity is allowed only per execution. Employer CalPERS ID is unique per entity.
;Pay Calendar:Only one pay calendar (frequency) is allowed per execution.
;Pay Period: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.
;Directory Name:This is the directory on the data base server that you want to have the file created in. This must be a directory (or directory object) that is write-enabled for the data base process.
;CPE File Name:This is the name of the actual file you want created, for Payroll & Retirement submission. Note that CalPERS expects files that will be submitted to be in a specific naming format.
;SP2 File Name:The name of the actual file you want created, for SIP2 submission. If this file name is provided __and__ there are SIP2 entries to be made, they will be written to this file, instead of the CPE file. Note that this file name is optional.
;Test Report:If set to “No”, the POSTED UPCAPERS field will be updated with a “Y” so the pay header being processed does not get picked up again in a subsequent run. The generated XML file will be marked as a valid file.
If set to “Yes” the generated XML file will be marked as a ‘Test Run’ and the POSTED UPCAPERS field will not be updated.
;Filters:These filters can be used to further narrow down the list of pay headers that you wish to process. Typically 'Entity', 'Payroll' and 'Pay Run Number' are used to filter to a specific pay run, or 'Person' may be used to run tests against a subset of employees.
!Report Parameters & Filters
||Report Parameters||
|Entity|Mandatory, LOV available\\One entity is allowed only per execution. Employer CalPERS ID is unique per entity.
|Pay Calendar|Mandatory, LOV available\\This field limits the process to the pay calendar specified. Only one pay calendar (frequency) is allowed per execution.
|(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.
|Directory Name|Mandatory, Text\\This is the directory on the data base server that you want to have the file created in. This must be a directory (or directory object) that is write-enabled for the data base process.
|CPE File Name|Mandatory, Text\\This is the name of the actual file you want created, for Payroll & Retirement submission. Note that CalPERS expects files that will be submitted to be in a specific naming format.
|SP2 File Name|Optional, Text\\The name of the actual file you want created, for SIP2 submission. If this file name is provided __and__ there are SIP2 entries to be made, they will be written to this file, instead of the CPE file. Note that this file name is optional.
|Test Report|Mandatory, LOV available\\If set to “No”, the POSTED UPCAPERS field will be updated with a “Y” so the pay header being processed does not get picked up again in a subsequent run. The generated XML file will be marked as a valid file.\\ \\If set to “Yes” the generated XML file will be marked as a ‘Test Run’ and the POSTED UPCAPERS field will not be updated.
|Exception Level|Optional, [Exception Level|X_TRACE_LEVEL] lexicon available\\This field defines the exception level (report messages) required. A ‘trace’ report of exception messages may be produced to assist in the testing phase. If necessary, choose from 0 – 9 (highest) level of trace. Please note that this is a voluminous report and will cause very slow performance.
|User Comments |Optional, Text \\This field holds the user-supplied comment which will appear in the header of all pages of the report. This is useful during testing phases to identify similar reports from each other.
At line 120 added 15 lines
||Report Filters||
These filters can be used to further narrow down the list of pay headers that you wish to process. Typically 'Entity', 'Payroll' and 'Pay Run Number' are used to filter to a specific pay run, or 'Person' may be used to run tests against a subset of employees.
|Person List Code|Optional, Multiple selections, LOV available\\This field limits the report to the person lists specified.
|Person|Optional, Multiple selections, LOV available\\This field limits the report to the persons specified.
|Unit|Optional, Multiple selections, LOV available\\This field limits the report to the units specified.
|Group|Optional, Multiple selections, LOV available\\This field limits the report to the groups specified.
|Payroll|Optional, Multiple selections, LOV available\\This field limits the report to the payrolls specified.
|Payrun Number|Optional, Multiple selections, LOV available\\This field limits the report to the payrun numbers specified.
|Department|Optional, Multiple selections, LOV available\\This field limits the report to the departments specified.
|Org Level Type|Optional, Multiple selections, LOV available\\This field limits the report to the org level types specified.
|Org Level|Optional, Multiple selections, LOV available\\This field limits the report to the org levels specified.
|Authorization|Optional, Multiple selections, LOV available\\This field limits the report to the authorizations specified.
|Location|Optional, Multiple selections, LOV available\\This field limits the report to the locations specified.
|Status|Optional, Multiple selections, LOV available\\This field limits the report to the status specified.
This page (revision-26) was last changed on 31-Aug-2022 10:30 by Karen ParrottTop