This is the list of the more common csv files that can be downloaded from the File Depot application in SSO. Contact your ASR to request access to File Depot.
|File Name||File Description|
|ANENRL19_BP7077_NOCOBLTR.CSV||This job runs after Insurance Initialization. Identifies Individuals who did not get a Letter in HRConnect.
For additional Documentation see:
|ANENRL19_BP7077_NOCOBLTR.CSV||File lists errors in COBRA notify flag indicating insurance coverage in last 60 days but did not get a personal benefits summary letter.|
|BHUPDATES.CSV||This file lists all updates to benefit history. A hardcopy report is no longer generated. This file provides the detail to a summary email that is sent to the processor on a daily basis.
Benefit History can be viewed on the 750 Series Screens.
|BILL0015_BP7005N_PRTYCD.CSV||This CSV file is a reflection of updates that occurred on Screen 106/115 and in Benefit History.|
|BPP_LOG.CSV||This file lists updates entered in the BPP Log File. There is a matching summary email that is sent to the processors. The file is primarily used to log updates that are outside of benefits. This file replaces hardcopy reports that were formerly produced when an automated process generated an update. The UINs in this report can be used to identify the automated process that was run and to verify an entry was updated. The before and after picture can be viewed for a UIN by pressing the ‘PF9-Key’ from any screen.
Additional information regarding logging can be found in the hyperlink below:
|BUDGT500_BP1606_ACTIONS.CSV||Lists recent employment actions that may affect benefits. Records should be inspected to determine if an employee is still eligible or newly eligible for benefits, needs an adjustment to the SGIP rate or needs a change in deduction code or insurance coverage based on the reported budget action. The file contains budget action changes including new hires, re-hires, transfers, terminations, retirements, changes in position, annual term months, start/return leave, and percent effort.|
|FISYE101_BP9224_01_INIT.TXT||This text file shows an employee’s iBenefits Annual Enrollment document compared to the employee’s current benefit selections, including dependents.
During Insurance Initialization, usually on September 1st of each year, the employee’s benefits will be updated with the values from the AE document.
Beginning FY 2014, this report will be discontinued. The comparison information will be moved to the Screen 106 AE Extended Screen.
|FISYE101_BP9224_01_INIT.TXT||This text file shows an employee’s iBenefits Annual Enrollment document compared to the employee’s current benefit selections, including dependents. During insurance initialization, usually on September 1st of each year, the employee’s benefits will be updated with the values from the AE document.
Beginning FY 2014, this report will be discontinued. The comparison information will be moved to the Screen 106 AE Extended Screen.
|FISYE101_BP9224_ERROR.TXT||This file reports warnings of possible errors and actual errors found on all of the AE documents in iBenefits. The documents are run through a series of validations necessary before they can be initialized in the B/P/P System for the new Fiscal Year. Unresolved warnings and errors will show up on the Master Error list after Insurance Initialization.|
|FISYE101_BP9224_ERROR.TXT||This file reports possible and actual errors found on all of the AE documents in iBenefits. The documents are run through a series of validations before initialization in the B/P/P System for the new fiscal year. Unresolved warnings and errors will show up on the Master Error list after insurance initialization.
This file will be discontinued FY 2014
|FISYE102_BP9202_ERROR.CSV||This file lists employees with more than one PIN in the Active Budget for the upcoming fiscal year. These PINS will need to be reconciled in the budget before Insurance Initialization begins so that the employee's insurance can be automatically initialized. Most of the errors in this file will need to be reconciled with help from the Workstation’s Budget or Payroll office.
Employees with multiple PINS that aren't reconciled before Insurance Initialization will require manual processing after the Insurance Initialization process has completed. Employees with multiple PINS that are deemed eligible for the Full SGIP rate will need their SGIP Rate flag on Screen 106 manually updated.
|FISYE102_BP9202_ERROR.CSV||This file lists employees with more than one PIN in the active budget for the upcoming fiscal year. These PINS will need to be reconciled in the budget before Insurance Initialization begins so that the employee's insurance can be automatically initialized. Most of the errors in this file will need to be reconciled with help from the Workstation’s Budget or Payroll office.
Employees with multiple PINS that aren't reconciled before insurance initialization will require manual processing after the process has completed. Employees with multiple PINS that are deemed eligible for the full SGIP rate will need their SGIP Rate flag on Screen 106 manually updated.
|FISYE103_BP9203_01_INIT.TXT||This file shows the employee’s updated insurance selections after combing the iBenefits Annual Enrollment Document with the employee's current insurance selections. It also accounts for the employee's information from the new fiscal year's Active Budget.|
|FISYE103_BP9203_01_INIT.TXT||This file shows employee updated insurance selections after combining the iBenefits annual enrollment document with the current employee insurance selections. It also references employee information from the new fiscal year active budget.
|FISYE103_BP9203_02_ERROR.CSV||Errors related to the employee's budget and insurance records that may have occurred during the Fiscal Year Insurance Initialization process.|
|FISYE103_BP9203_02_ERROR.CSV||Reports errors related to the employee budget and insurance records that have occurred during the insurance initialization process which loads the employee's benefit selections for the new fiscal year after the budget for the new fiscal year has been loaded into the B/P/P System.
|FISYE103_BP9203_03_ERROR.CSV||Errors related to the employee's budget and insurance records that may have occurred during the Fiscal Year Insurance Initialization process.|
|FISYE103_BP9203_03_ERROR.CSV||Report of errors related to the employee's budget and insurance records occurring during the insurance initialization process which loads the employee's benefit selections for the new fiscal year after the new fiscal year budget has been loaded into the B/P/P system.
|IBENEFIT_LOCKS.CSV||This file contains records that have been locked by iBenefits on the 106/115 Screen. The processor can expect these UINs to post to Screen 106/115 according to new employee rules.|
|INSUR021_BP7077_NOCOBLTR.CSV||Reports errors in the COBRA Notify flag. Will find anyone who has their COBRA Notify flag set to 'N' and does not already have a letter generated in HRConnect.|
|LEVMON04_BP0206_02_PEND.CSV||This file lists inactive employees with pending or future leave transactions. Inactive employees for this list must not have been paid in the last 2 months for vacation and the last 13 months for sick.|
|LEVMON04_LB0206_01_LAPSE.CSV||This program generates leave vacation and sick lapse report and transactions for inactive employees. Must not have been paid in the last 2 months for vacation and the last 13 months for sick.|
|MASTER_ERROR_FILE.CSV||This is the Daily Master Error List. The Daily Master Error List reports real time errors. A full sweep of the database is done at month end, this generates a base set of UIN's that will be run through the edits at month end. The Benefit History files are then read capturing any updates that have happened since month end, this includes iBenefit Postings and Budget Updates happening from Canopy. The UIN's generated from this list are also run through the benefit edits allowing the Master Error List to report real time errors. Once an error is corrected the error will not be reported the next day.|
|MONINS02_BP8020_PERFORM.CSV||File to report those either Hired or Promoted. Produces Letters for some workstations. This report varies by workstation - some do not get this report. This file is generally tied to Performance Evaluations.|
|MONINS03_BP8003_LEAVE.CSV||Produces a report of all employees with Insurance Deduct Codes of 'L' or 'M'.
|MONINS04_BP7005N_PRTYCD.CSV||BP7005N is run both at Billing and at Month End. This CSV file is a reflection of updates that occurred on Screen 106/115 and in Benefit History. There are many instances where there is a need for a new employee to be entered with a future SGIP Date. A person will not receive SGIP until his SGIP Date matches their Premium Due Date as shown on Screen 106. A person can be entered with a future SGIP Date on Screen 106 or set up as a New Employee in iBenefits. It is important to update the priority code prior to the next months Bills or Payroll is run, since the priority codes determine how SGIP is applied. A priority code of ‘N’ states that no SGIP will be applied, all the money will be taken out of the employee deduct amount. An active priority code will have the SGIP applied to the employer amount. In order for priority codes to get updated, the premium due date must be greater than or equal to the SGIP eligibility Date. The Basic Life priority code will get updated to ‘1’; Medical updated to a ‘2’; Dental updated to a ‘4’; Vision update to a ‘5’; ADD updated to a ‘3’; The LTD deduct code is not updated with this process. A message is placed on the report stating ‘ à LTD PRTY ‘N’ MAY NEED MANUAL UPDATE’. The LTD priority is not automatically set to ‘6’, since an employee will get a different benefit depending on whether he chooses to use SGIP.|
|MONINS04_BP7107_DIS_RET.CSV||This file is produced every Month End. It reports Disability Retirees with coverage ending in 3 months or less from the month end date. A Disability Retiree is defined as anyone with an employee status code of 'I'. The Insurance Stop Date is used to determine if the three month criteria has been met.
|MONINS04_BP8030_01_DEPGT24.CSV||Obsolete as of 11/2015. Since maximum age for coverage is now 26 for all coverage types, all are combined in one file (MONINS04..._02)|
|MONINS04_BP8030_02_DEPGT25.CSV||Each of these individuals have a letter in HRConnect titled ‘Notice of Dependent Reaching Maximum Coverage Age’, available for downloading in HRConnect Admin by processors. This letter gives advance notice to the employee that the dependent's coverage will be turned off once they reach the age of 26. Once the dependent stop date is reached, an automated process turns off the coverage.
Below is a sample of the benefit update ID and comment written to benefit history when the stop date is reached.
BEBM8096 MONINS04/BP8096N Dependents turning 26 - Med
|MONINS04_BP8033_SPOUSES_65.CSV||Complete documentation regarding this output file can be found
in the MONINS04_BP8033_EMP_RET_65.CSV Documentation.
|MONINS06_BP7030N_SPODBLCOV.CSV||This monthly file lists employees that are married to other employees where benefit coverage may be duplicated for Medical, Dental, Vision, or Optional Life/Dependent Life.|
|MONINS06_BP7032N_DEPDBLCOV.CSV||Dependents with Double Insurance Coverage. This monthly report notifies the processor of employees who have the same dependents who may have duplicate Medical, Dental, Vision, or Dependent Life Coverage.|
|MONINS06_BP7033N_NSPDBLCOV.CSV||Non-Spouse with Double Insurance Coverage. This monthly report is a mirror of the Spouse Double Coverage Report, but only reports Non-Spouse Dependents or Sons or Daughters who are now employees that have Double Insurance Coverage.|
|MONINS06_BP7106N_RET65PLUS.CSV||This file is generated by reading the Retiree Employment and Benefit History File and identifies Retirees who are approaching working 6 months and are 65 plus. This is the same file that can be viewed on Screen 730.|
|MONINS06_BP8580N_TOB.CSV||This file lists the details of Tobacco Users and Premiums for a Workstation. It lists both users and non-users and their employee status. It also provides totals for premiums by user and gender.|
|MONINS06_BP8580N_TOB.CSV||This file lists the details of tobacco users and premiums for a workstation. It lists both users and non-users and their employee status. It also provides totals for premiums by user and gender.
|MONINS07_BP8008_01_TRSORPELIG.CSV||Employees that are budgeted at 100 percent and have an Annual Term Months of 4 or greater. All Employees must complete the ORP Acknowledgement form.|
|MONINS07_BP8008_02_ORPELIG.CSV||Employees that are budgeted at 100 percent and have an Annual Term Months of 4 or greater. All Employees must complete the ORP Acknowledgment form.|
|MONINS07_BP8018||Three files are produced. File list Terminations, Retirements, Promotions, and Transfers that occurred in a specified month. Faculty (i.e. EEO job of 2) are excluded from this reporting.
|MONINS09_BP8011_CAUTIONRPT.CSV||This file lists employees with Medical, Dental, and Vision coverage that have not been paid as of the beginning of the month and have not had any deductions taken.|
|MONPAY08_BP8611_01_TRS5PLUS.CSV||This file contains records of wage employees that may be eligible for TRS participation. It includes wage employees working at least 50% effort for 4.5 or more months.
|MONPAY08_BP8611_02_TRSDETAIL.CSV||This file contains detail records of budget and wage employees potentially eligible for TRS participation.
|MONPAY08_BP8611_03_TRSSUMMARY.CSV||This file contains a summary of budget and wage employees potentially eligible for TRS.
|MONPAY08_BP8611_EFFORT.CSV||Pay History Tapes are read and a person’s Monthly Hours are Totaled. If a person’s Monthly Hours are greater than the Monthly Hours for the relative month listed in this file then the person is considered to have this month considered when determining TRS Eligibility.
|MONPAY08_BP8612_01_WAGE4PLUS.CSV||This report is the primary report that should be examined to quickly identify those who may be Benefit Eligible. Employees with only 4 Months worked have been placed on the report to give an alert that the employee will become benefit eligible within the next month.
|MONPAY08_BP8612_02_BUDGETDTL.CSV||This file contains hours worked and gross pay detail records of budgeted employees potentially eligible for benefits.
|MONPAY08_BP8612_02_WAGEDTL.CSV||This file contains detail records of gross pay and hours worked for wage employees potentially eligible for benefits.
|MONPAY08_BP8612_03_BUDGETSUM.CSV||This file contains summary records of budgeted employees that may possibly be eligible for benefits.
|MONPAY08_BP8612_03_WAGESUM.CSV||This file contains summary records of wage employees that may possibly be eligible for benefits.
|MONPAY08_BP8612_EFFORT.CSV||In order to be Benefit Eligible, a person must work 50 percent effort for at least 4.5 consecutive months. The BP8612 Reports deal specifically with Hours Worked. This report will define the number of Hours necessary in order for a person to have worked 50 percent. The number of Hours worked will vary by Month. Once a person has passed the number of Hours worked specified for the month on this report, the person is considered to have worked 1 month towards benefit eligibility. Working 4 and 1/2 Consecutive Months is required to be considered Benefit Eligible. In order to compute the number of Hours Worked for the month, the Work Days table on Screen 414 is used to determine the number of Working Days. The Hours Worked for the month is calculated by multiplying number of Working Days for the month by 8. The number of Hours for the Month is then multiplied by 50 percent. Once an employee has worked at least 50 percent Hours, the employee will have a month incremented toward Benefit Eligibility. Pay Periods will be Split and the number of working days will get applied to the respective month.
Working 4 and 1/2 Consecutive Months is required to be considered Benefit Eligible. In order for the program to identify consecutive months the program will be run under two different time periods at the beginning of the Calendar Year and the beginning of the Fiscal Year. At the beginning of the Fiscal Year, the Work Days table will be updated to reflect the new Fiscal Year and Pay History is reviewed for the months of January thru August of the previous Fiscal Year. At the beginning of the Calendar Year, the program will run against the months of September through December. Special attention should be paid to the report during the months of September and January.
Budgeted Employees who are paid monthly will have their number of Hours Worked Computed. The Calculation for Monthly Budgeted Employees is:
Monthly Hours Per Month (Usually 173.33) * Monthly Gross Pay. The result is then divided by the FTE Monthly Salary.
|MONPAY08_BP8612N_TTRAQ.CSV||Used to help determine Benefit Eligibility, this file reports Actual Hours based on TimeTraq Data. This report is optional since not all workstations use TimeTraq.
Differences between this report and the Pay History BP8612 are:
* The Pay History BP8612 is based on Screen 414 Working Days Table which assumes an 8 hour day, weekends are not considered to be working days. This reports the actual hours from TimeTraq and may include more than 8 hours per day hours worked on weekends.
|MONPAY08_BP8612N_TTRAQ.CSV||This file reports actual hours based on TimeTraq data to help determine benefit eligibility. This report is optional since not all workstations use TimeTraq.
Differences between this report and the Pay History BP8612 report are:
The BP8612 report is based on the screen 414 Working Days Table and assumes an 8-hour day and a 5-day week.
The BP8612N report shows actual hours from TimeTraq and may include more than 8 hours per day as well as weekend hours.
|PAYRL31_BP5047_ADDRPRV.CSV||Report of Certified Peace Offers who got their Address Privacy Flag Set.|
|STOPPED_ERRORS.CSV||This is a report of UINs that have been reviewed and should no longer appear on the daily Master Error List.
Screen 342 allows the processor to review the error so that the Master Error File will only contain new errors or errors that have not been reviewed. On Screen 342, the UIN, error number and stop date are entered once the record has been reviewed on the Master Error List. The error will be checked again when the stop date has passed and may reappear on the Master Error List.