[{TableOfContents }]

!!!MINNESOTA PERA REPORT
----

!!SET UP REQUIREMENTS
!!1. Setup new User Fields - IMUF
One new user field is needed to set up in the BEND table(P2K_ENROLLMENT_DETAILS) to translate and populate the PERA demographic record type (Type 42) for new employees where applicable.

The PERA_EXLCUDE_CODE user field should be set up to populate the exclusion code field (Positions 101-103)

!!2. Setup new User Defined Lexicons - IMLN
Three new User Defined Lexicons must be set up to specify the:

* PERA employment status
* PERA position class
* PERA position code


!!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.

Any Change Codes that are not entered in this table are assumed to be not reportable to PERA.

!! PERA Position Class
Lexicon Name: PERA_POSITION_CLASS
This lexicon is used to cross reference the Group Code with the PERA Position Class Code.  Enter the Group Code under the SAVED VALUE column and enter the corresponding Position Class Code under the DISPLAYED VALUE column.

!! PERA Position Code
Lexicon Name:  PERA_POSITION_CODE
This lexicon is used to cross reference the reportable JOB CODES with the PERA Position Code.  Only the Job Codes that have equivalent PERA positions are required to be entered in this table.  Any Job Codes not listed in this table will automatically be translated to the OTHER PERA Position Code.  Enter the Job Code under the SAVED VALUE column and enter the PERA Position Code under the DISPLAYED VALUE column.

!! 3. Setup new Plan Type - IBPT
Plan Type Name: MNPERA (No exceptions)
Define the MN Public Employee Retirement Administration System benefit plan type.

!! 4. Setup new Plan - IBPN
Plan Name:  MNPERA
Define the MN_PERA Plans.  Users can define the Plan Code and the Plan Name, but the various PERA assigned Plan IDs must be entered as a COVERAGE within this Plan.  The PERA Plan ID must be entered as the first 2 characters in the Policy Number of the COVERAGE table.

!!5. Setup PERA Benefit Components - IBPN
Components section for the MN PERA Benefit Plans. Regular Date Components also applied where necessary.

!!6. Setup PERA Contribution Rates - IBPN
The RATES section of the MN PERA Plan (only the EE, ER and User 1 rates are used, and are expressed as a percentage.  The User 1 Rate is used to define the Additional ER contribution RATE.

!!PROCESSING
* Once the set up of the MN PERA Benefit Plan Types and Plans is complete, the Pay Elements for each Benefit Component must be established.  The Plan setup will be used as the definition for processing.
* All Employee/Employer Amounts calculated through this Plan will be reported on the File and the Report.
* Normally, only PERA Record Types of 30, 31 AND 38 will be created.
* When a new employee starts the PERA deduction, or there is a change of employment status, or address change, then Record Type 42 will be created under a separate demographic file.
* A change of employment status, including new employment, is defined as the record having a Change Reason Code that is defined in the User Lexicon PERA_EMPLOY_STATUS.
* A switch in PERA plans must occur at the end of a Pay period.  Example: The old Plan will be terminated at the end of a pay period and the new Plan will be effective at the beginning of the immediately following pay period.



!!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. 
 
----

![Notes|Edit:Internal.RBMNPERA] 	
[{InsertPage page='Internal.RBMNPERA' default='Click to create a new notes page'}]