RBMNPERA
Back to current versionRestore this version

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#

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.

Pay Component NameSourceDescription
B2010Regular Pensionable Earnings (Pay Type 01)Pay Element/Pay PCTotal employee earnings for the reporting period that are deemed pensionable. It must be stored in a Pay PC that the report program can access.
B2012Regular Employer Contribution AmountPay Element or system calculatedRegular ER Contribution. The system will calculate this amount using the ER rate.
B2014Regular Employee Deduction AmountPay Element or system calculated Regular Deduction Amount for the Pay Period based on the regular pay period salary. The system will calculate this amount using the EE rate.
B2016Additional ER Contribution on Regular EarningsPay ElementAdditional ER Contribution Amount.
B2020Earning Adjustment (Pay Type 02, A)Pay ElementPensionable Salary Adjustment
B2022ER Deduction AdjustmentPay Element or system generatedER Contribution Amount that is based on the Salary Adjustment
B2024EE Contribution AdjustmentPay Element or system generatedDeduction Amount based on the Earning Adjustment
B2026Additional ER Contribution on Adjustment PaysPay ElementAdditional ER Contribution Amount
B2040Grievance Earning (Pay Type 04)Pay Element/Pay PCTotal grievance earnings for the reporting period that are deemed reportable
B2042 Grievance Employer Contribution AmountPay Element or system calculatedGrievance ER contribution amount. The system will calculate this amount using the ER rate
B2044Greivance Employee DeductionPay Element or system calculatedEE Deduction Amount for the Pay Period based on the grievance pay. The system will calculate this amount using the EE rate.
B2046Additional ER amount on grievance paysPay Element or system generatedAdditional ER amount on Grievance Pay
B2050Retroactive Earning (Pay Type 05)Pay ElementPensionalble Retroactive Salary
B2052Retroactive ER ContributionPay Element or system generatedER Contribution amount that is based on the Retroactive Salary
B2054 Retroactive EE DeductionPay Element or system generatedEE Deduction amount based on the Retroactive Earnings
B2060Omitted Earnings (Pay Type 06)Pay ElementOmitted Pays
B2062Omitted ER ContributionPay Element or system generatedER Contribution Amount that is based on the Omitted pays
B2064Omitted EE Deduction (Pay TYpe 06)Pay ElementOmitted EE Deduction Amount
B2066Additional ER Amount on Omitted PayPay Element or system generatedAdditional ER amount on Omitted pay
B2070Lump Sum Comp Pay OutPay ElementTotal Lump Sum Payout
B2072ER Contribution on Lump Sum PayoutPay Element or system generatedER Contribution on Lump Sum Payout
B2074 EE Deduction on Lump Sum PayoutPay Element or system generatedEE Deduction on Lump Sum Payout
B2076Additional ER Amount on Lump Sum PayoutPay Element or system generatedAdditional ER amount on Lump Sum Payout
B0290Member HoursPay ComponentUse for Definition only. It must have an Hours PC associated to it, for reporting pruposes.

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#

REPORTING PROCESS#

MAGNETIC MEDIA REPORTING#

Report Parameters & Filters#

Report Parameters
Plan TypeMandatory, LOV available
Plan CodeOptional, LOV available
Department CodeOptional, LOV available
Pay CategoryOptional, LOV available
Include ReversalOptional, LOV available, <YES/NO>
Reversal Pay CategoryOptional, LOV available
Pay CalendarMandatory, LOV available
Limits the process to the pay calendar specified.
Pay Issue DateMandatory, Date, LOV available
This field displays the pay issue date.
PERA Employer IDMandatory,text
Create FileOptional, LOV available, <YES/NO>
The report may be run without creating an interface file (normally for testing purposes).
Directory NameMandatory, 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 NameMandatory, text
Enter the name of the file that will be created in the interface directory specified.
Enroll File NameMandatory, text
Enter the name of the file that will be created in the interface directory specified.
Include ExceptionOptional, LOV available, <YES/NO>
Exception LevelMandatory, 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 #

Click to create a new notes page