MINNESOTA PERA REPORT#
Set Up Requirements#
- Setup new User Fields - IMUF
The PERA_EXLCUDE_CODE user field should be set up to populate the exclusion code field (Positions 101-103)
- Setup new User Defined Lexicons - IMLN
PERA employment status PERA position code PERA position class
PERA Employment Status#
Lexicon Name: PERA_EMPLOY_STATUS Cross reference the EASD Change Reason with the PERA Employment status. Enter the PERA reportable Change Reason codes only in the SAVED VALUE column and enter the corresponding PERA status in the DISPLAYED VALUE column. A PERA_SWITCH/SW row must exist in order to report those employees who switch PERA plans.Report Parameters & Filters#
Report Parameters | |
---|---|
Plan Type | Mandatory, LOV available |
Plan Code | Optional, LOV available |
Department Code | Optional, LOV available |
Pay Category | Optional, LOV available |
Include Reversal | Optional, LOV available, <YES/NO> |
Reversal Pay Category | Optional, LOV available |
Pay Calendar | Mandatory, LOV available Limits the process to the pay calendar specified. |
Pay Issue Date | Mandatory, Date, LOV available This field displays the pay issue date. |
PERA Employer ID | Mandatory,text |
Create File | Optional, LOV available, <YES/NO> The report may be run without creating an interface file (normally for testing purposes). |
Directory Name | 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. |
Detail File Name | Mandatory, text Enter the name of the file that will be created in the interface directory specified. |
Enroll File Name | Mandatory, text Enter the name of the file that will be created in the interface directory specified. |
Include Exception | Optional, LOV available, <YES/NO> |
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. |