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 521 changed one line
|10|Premium Rate × Special Compensation Amount/ 100|Multiplies the premium rate from the Rates tab by the Special Compensation Amount (B0366) divided by 100.\\ \\The premium rate must be specified as a percentage not a decimal.\\ \\Rule should be used in PERS plan only.|B0366|B0627
|10|Premium Rate × Special Compensation Amount / 100|Multiplies the premium rate from the Rates tab by the Special Compensation Amount (B0366) divided by 100.\\ \\The premium rate must be specified as a percentage not a decimal.\\ \\Rule should be used in PERS plan only.|B0366|B0627
At line 946 changed one line
|02|Same as Employee Amount|The employee amount (B1044) will be used as the tax deferred amount.\\ \\A <PC Code> must be indicated.|B1044|B1275
|02|Same as Employee Amount|The employee amount (B1044) will be used as the tax deferred amount.\\ \\A <PC Code> must be indicated.|B1044|B1275
At line 998 changed one line
|B0620 Premium Calculation Method|10 Eligible Amount X Prem Rate / 100|01| | | |
|B0620 Premium Calculation Method|10 Eligible Amount X Prem Rate / 100|01| | | |
At line 1,000 changed 3 lines
|B0695 Survivor Amount|02 Use Value from Enrollment|01| | |3695 CAPERS Surv|0.93 in the <BC Value> on the Component
|B0800 Contribution Rate|02 Use Value from Coverage Rate Step|ALL| | | |0.0000
|B0810 Contribution Method|11 Contribution Rate X Eligible Earnings|01| | | |
|B0695 Survivor Amount|02 Use Value from Enrollment|01| | |3695 CAPERS Surv|0.93 in the <BC Value> on the Component
|B0800 Contribution Rate|02 Use Value from Coverage Rate Step|ALL| | | |0.0000
|B0810 Contribution Method|11 Contribution Rate X Eligible Earnings|01| | | |
At line 1,070 changed one line
i.e. BC0320 use Rule 01 with an Element of CAPERS EARNS, and a UserCalc that has the following logic: \\
i.e. BC0320 use Rule 01 with an element of CAPERS EARNS, and a UserCalc that has the following logic: \\
At line 1,076 changed one line
On BC0323 use Rule 01 with an Element of CAPERS EARNS, and a UserCalc that has the following logic:\\
On BC0323 use Rule 01 with an element of CAPERS EARNS, and a UserCalc that has the following logic:\\
At line 1,082 changed one line
On BC0325 use Rule 01 with an Element of CAPERS EARNS, and a UserCalc that has the following logic:
On BC0325 use Rule 01 with an element of CAPERS EARNS, and a UserCalc that has the following logic:
At line 1,118 changed one line
!User Fields - IMUF
!User Fields - [IMUF]
At line 1,122 changed 2 lines
;POSTED UPCAPERS
This user field is MANDATORY. CAPERS cannot operate without adding this user field. When the UPCAPERS program is run in update mode (Trial = ‘N’), this user field is used to ‘stamp’ each pay run as ‘Processed by CAPERS’. This prevents pay runs from being processed twice.\\
;POSTED [UPCAPERS]
This user field is MANDATORY. CAPERS cannot operate without adding this user field. When the [UPCAPERS] program is run in update mode (Trial = ‘N’), this user field is used to ‘stamp’ each pay run as ‘Processed by CAPERS’. This prevents pay runs from being processed twice.\\
At line 1,151 changed 2 lines
The ‘CALPERS’ pay code is a required reporting column that determines the basis of the pay rate. UPCAPERS supports ONLY 01-Monthly and 04-Hourly.\\
UPCAPERS assumes that WEEKLY/BIWEEKLY paid employees are to be reported as ‘Hourly’, and that MONTHLY/SEMI-MONTHLY employees are to be reported as ‘Monthly’.\\
The ‘CALPERS’ pay code is a required reporting column that determines the basis of the pay rate. [UPCAPERS] supports ONLY 01-Monthly and 04-Hourly.\\
[UPCAPERS] assumes that WEEKLY/BIWEEKLY paid employees are to be reported as ‘Hourly’, and that MONTHLY/SEMI-MONTHLY employees are to be reported as ‘Monthly’.\\
At line 1,164 changed 3 lines
This update will process all bond plans, and produce a flat file to be remitted.\\
CAPERS reports are due within 30 calendar days after the close of a service period. The report can be produced only after the CAPERS plan/coverages are set up, employees properly enrolled, and payrolls have been closed. At payroll time, the benefit routine will be invoked which populates the CAPERS pay components with values that are derived from pay components/elements as defined in the benefit components. Reporting will be done after the Pay closes; it will extract the numbers from the Benefit Components and produce the CAPERS report using the required format.\\
Function [UPCAPERS] produces the CAPERS report and optionally the associated file for transmission. The function must be executed separately for each payroll due to the different processing frequencies. When run in update mode (Trial = ‘N’), the pay will be marked as ‘processed’, by the program, and will not be processed again in later [UPCAPERS] runs.\\
This update will process all bond plans, and produce a flat file to be remitted.\\ \\
CAPERS reports are due within 30 calendar days after the close of a service period. The report can be produced only after the CAPERS plan/coverages are set up, employees properly enrolled, and payrolls have been closed. At payroll time, the benefit routine will be invoked which populates the CAPERS pay components with values that are derived from pay components/elements as defined in the benefit components. Reporting will be done after the Pay closes; it will extract the numbers from the Benefit Components and produce the CAPERS report using the required format.\\ \\
Function [UPCAPERS] produces the CAPERS report and optionally the associated file for transmission. The function must be executed separately for each payroll due to the different processing frequencies. When run in update mode (Trial = ‘N’), the pay will be marked as ‘processed’, by the program, and will not be processed again in later [UPCAPERS] runs.\\ \\
At line 1,195 removed 20 lines
!Report Parameters & Filters
||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.
At line 1,216 changed 2 lines
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.\\ \\
Modify the standard CAPERS file requirements using the IDIF function. Rename the code from HL$CAPERS to a user-defined code.
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.\\ \\
Modify the standard CAPERS file requirements using the [IDIF] function. Rename the code from HL$CAPERS to a user-defined code.
At line 1,219 changed one line
||RECORD||FIELD||START POSITION||ENDING POSITION|NAME||VARIABLE NUMBER||NOTES
||RECORD||FIELD||START POSITION||ENDING POSITION||NAME||VARIABLE NUMBER||NOTES
This page (revision-36) was last changed on 26-Nov-2021 10:22 by JMyersTop