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 17 changed 10 lines
|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.
Pay Period
Directory Name
CPE File Name
SP2 File Name
|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.
|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.
|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.
|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.
At line 30 removed 15 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>.
At line 46 changed one line
|Payroll|Optional, Mandatory, LOV available, <ALL>\\This field limits the report to the payrolls specified.
|Payroll|Optional, LOV available, <ALL>\\This field limits the report to the payrolls specified.
At line 30 added 12 lines
Person List Code
Person
Unit
Group
Payroll
Payroll Number
Department
Org Level Type
Org Level
Authorization
Location
Status
At line 51 removed one line
This page (revision-26) was last changed on 31-Aug-2022 10:30 by Karen ParrottTop