This page (revision-10) was last changed on 26-Nov-2021 10:22 by ihowie

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

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
10 26-Nov-2021 10:22 3 KB ihowie to previous
9 26-Nov-2021 10:22 3 KB jmyers to previous | to last
8 26-Nov-2021 10:22 3 KB JMyers to previous | to last
7 26-Nov-2021 10:22 3 KB JMyers to previous | to last
6 26-Nov-2021 10:22 2 KB JMyers to previous | to last
5 26-Nov-2021 10:22 2 KB JMyers to previous | to last
4 26-Nov-2021 10:22 2 KB JMyers to previous | to last
3 26-Nov-2021 10:22 2 KB JMyers to previous | to last
2 26-Nov-2021 10:22 2 KB JMyers to previous | to last
1 26-Nov-2021 10:22 46 bytes UnknownAuthor to last

Page References

Incoming links Outgoing links

Version management

Difference between version and

At line 1 removed 2 lines
UPCAPERS - function deprecated with the progression and continued development of the CAPERS functionality. Review [UPCAPERSXML]
At line 5 changed one line
!!!REPORT CALIFORNIA PERS
!!!CREATE ICMA INTERFACE FILE
At line 10 changed 14 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.
|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.
|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.
|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>.
|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.
|Entity|Mandatory, LOV available\\Limits the process to the entity specified.
|Pay Calendar|Mandatory, LOV available\\Limits the process to the pay calendar specified.
|Include All Pays (Testing)|Toggle
|For Pay Ending Date|Mandatory, Date, LOV available\\Usually the last pay date processed.
|Include Elected Officials|Mandatory, LOV available <No>\\If the User Field of 'ELECETED OFFICIAL' has a 'Y' on the Employee's Benefit Enrollment form then they may be included or excluded from the report/interface.
|Re-compute ER at Summary|Mandatory, LOV available <No>\\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|Mandatory, LOV available\\Employees will be printed in this person code order unless this parameter is <Yes>
|Create File|Mandatory, LOV available\\The report may be run without creating an interface file (normally for testing purposes).
|Interface Code|Mandatory, 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|Mandatory, 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|Mandatory, text\\Enter the name of the file that will be created in the interface directory specified.
|Exception Level|Mandatory, LOV available\\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.
|Trial|Mandatory, LOV available\\The report may be run in trial mode (Yes) or update mode (No)
|User Comment|Optional, text\\Users may enter a comment here that will appear on the selection criteria (header page) of the report. This is useful during testing phases to identify similar reports from each other.
At line 26 changed 2 lines
|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.
|Payroll|Mandatory, LOV available, <ALL>\\This field limits the report to the payroll specified.
|Test Person |Multiple Selection, LOV available, <ALL>\\This field limits the report to the test persons specified.
At line 30 changed 2 lines
![Notes|Edit:Internal.UPCAPERS]
[{InsertPage page='Internal.UPCAPERS' default='Click to create a new notes page'}]
[{If var='loginstatus' contains 'authenticated'
![Discussion|Edit:Internal.UPICMA]
[{InsertPage page='Internal.UPICMA' default='Click to create a new discussion page'}]
}]