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

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
36 26-Nov-2021 10:22 107 KB JMyers to previous
35 26-Nov-2021 10:22 107 KB JMyers to previous | to last
34 26-Nov-2021 10:22 110 KB JMyers to previous | to last
33 26-Nov-2021 10:22 110 KB JMyers to previous | to last
32 26-Nov-2021 10:22 109 KB JMyers to previous | to last
31 26-Nov-2021 10:22 109 KB JMyers to previous | to last
30 26-Nov-2021 10:22 109 KB JMyers to previous | to last
29 26-Nov-2021 10:22 108 KB JMyers to previous | to last
28 26-Nov-2021 10:22 108 KB JMyers to previous | to last
27 26-Nov-2021 10:22 108 KB JMyers to previous | to last
26 26-Nov-2021 10:22 108 KB JMyers to previous | to last
25 26-Nov-2021 10:22 108 KB JMyers to previous | to last
24 26-Nov-2021 10:22 108 KB JMyers to previous | to last
23 26-Nov-2021 10:22 108 KB JMyers to previous | to last
22 26-Nov-2021 10:22 108 KB JMyers to previous | to last
21 26-Nov-2021 10:22 108 KB JMyers to previous | to last

Page References

Incoming links Outgoing links
CAPERS
CAPERS

Version management

Difference between version and

At line 1,194 changed 18 lines
!‘Process California PERS’ Highlights
‘Process California PERS’ Usages and Examples
Report Parameter Form Payroll Mandatory, LOV available, <ALL>
Limits the process to the payroll specified.
Person Code (for Test) Mandatory, Multiple Selection, LOV available, <ALL>
The person code(s) of specific employee(s) to be processed for testing purposes.
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>
!Report Parameters & Filters
At line 1,213 changed 21 lines
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.
Interface Format
If not already defined in the Interface Formats Definition form (IDIF), load the standard interface file format using the starter_idif_hl$capers.sql script.
||Report Parameters||
|Payroll|Mandatory, LOV available, <ALL>\\Limits the process to the payroll specified.
|Person Code (for Test)|Mandatory, Multiple Selection, LOV available, <ALL>\\The person code(s) of specific employee(s) to be processed for testing purposes.
|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.
!Interface Format
If not already defined in the Interface Formats Definition form (IDIF), load the standard interface file format using the starter_idif_hl$capers.sql script.\\ \\
At line 1,236 changed 9 lines
RECOR D FIELD START POSITION ENDING POSITION NAME VARIABLE NUMBER NOTES
1 1 1 1 Record ID Constant = 0
1 2 2 5 Employer Code Enter in Constant Value
1 3 6 8 Unit Code Enter in Constant Value or leave blank
1 4 9 17 Filler Zero-filled
1 5 18 19 Service Period Month MM of the Pay End Date
1 6 20 23 Service Period Year YY of the Pay End Date
||RECORD||FIELD||START POSITION||ENDING POSITION|NAME||VARIABLE NUMBER||NOTES
|1 | 1 | 1 | 1 | Record ID| |Constant = 0
|1 | 2 | 2 | 5 | Employer Code| | Enter in Constant Value
|1 3 6 8 Unit Code Enter in Constant Value or leave blank
|1 4 9 17 Filler Zero-filled
|1 5 18 19 Service Period Month MM of the Pay End Date
|1 6 20 23 Service Period Year YY of the Pay End Date
At line 1,254 removed 4 lines
RECOR D FIELD START POSITION ENDING POSITION NAME VARIABLE NUMBER NOTES
This page (revision-36) was last changed on 26-Nov-2021 10:22 by JMyersTop