Message ID |
Description |
Suggested Resolution |
000005 |
The deduction code displayed below was not found in the deduction table. |
Table Setup:
- Check the associate's Benefit Program, make sure that the spelling of the Deduction Code matches the row in the Deduction Table.
- Either change the Benefit Program or the Deduction Table entry to match the other.
- Rerun the process following the 'Prep Error' procedure.
|
000011 |
The pay group displayed below was found but is currently inactive. |
Table Setup:
- Determine the associate's company and paygroup on Job Data.
- Then, lookup the company/ paygroup combination in the Paygroup Table.
- Either change the associate's paygroup or activate the paygroup on Paygroup Table.
- Rerun the BenAdmin process following the 'Prep Error' procedure.
|
000014 |
The pay group displayed below was not found in the pay group table. |
Table Setup:
- Determine the associate's company and paygroup on Job Data.
- Then, determine whether the paygroup should be added to the Paygroup Table.
- If not, correct the associate's paygroup on Job Data.
- Rerun the BenAdmin process following the 'Prep Error' procedure.
|
000015 |
The pay calendar entry displayed below was not found in the pay calendar table. |
Table Setup:
- Coordinate with payroll to run the pay calendar setup program for the indicated paygroup.
- Rerun the BenAdmin process following the 'Prep Error' procedure.
|
000023 |
The company displayed below was not found in the company table. |
Table Setup:
- Determine the associate's company on Job Data.
- Then, determine whether the company should be added to the Company Table.
- If not, correct the associate's company on Job Data.
- Rerun the BenAdmin process following the 'Prep Error' procedure.
|
000024 |
The company displayed below was found but is currently inactive. |
Table Setup:
- Determine the associate's company on Job Data.
- Then, determine whether the company should be active on the Company Table.
- If not, correct the associate's company on Job Data.
- Rerun the BenAdmin process following the 'Prep Error' procedure.
|
000027 |
The benefit plan displayed below was not found in the appropriate benefit table. |
Table Setup:
- Check the Benefit Plan Table to ensure benefit plan has been set up.
- If it exists, then check the associate’s Benefit Program Table to ensure that the benefit plan exists as an option.
- Correct where appropriate
- Rerun the BenAdmin process following the 'Prep Error' procedure.
|
000030 |
An age-graded rate was not found for the employee's category. |
- Review the Age Graded Rate Table set-up for the benefit specified / table ID specified. Review the associate’s age / sex to ensure it applies to the table data.
- Many times, this error is caused by no sex or birthdate being specified in Personal Data.
- Correct where appropriate
- erun the BenAdmin process following the 'Prep Error' procedure.
|
000039 |
The Coverage Group for the Life/ADD plan was not found. |
- Review the Life and AD/D Plan Table for the benefit plan specified to ensure the proper Coverage Group Code is present.
- Correct where appropriate
- Rerun the BenAdmin process following the 'Prep Error' procedure.
|
000056 |
The form displayed below was not found in the Form Table. |
- Review the Form Table for the form ID specified.
- Correct where appropriate
- Rerun the BenAdmin process following the 'Prep Error' procedure.
|
000070 |
There is no birth date provided for this employee. The employee participates in the life insurance plan identified below. That plan uses an age-graded rate table to determine costs and requires a birth date. |
- Review the associate’s Personal Data page to ensure that a birth date is specified on the page.
- Correct where appropriate
-
Rerun the BenAdmin process following the 'Prep Error' procedure.
|
000087 |
The Benefit Program defined for this employee was not found. |
- Review the Ben Prog Partic record for the associate
- then the Benefit / Deduction Program Table for the specified program.
- Correct where appropriate
- Rerun the BenAdmin process following the 'Prep Error' procedure.
|
000088 |
The Benefit Program defined for this employee was inactive for the current check date. |
- Review the Benefit / Deduction Program Table status for the program specified.
- Correct if appropriate
-
Rerun the BenAdmin process following the 'Prep Error' procedure.
|
000089 |
The Benefit Plan / Deduction Code is not found for the Benefit Program defined for this employee. |
- Review the Benefit / Deduction Program Table status for the program specified.
- Correct if appropriate
- Rerun the BenAdmin process following the 'Prep Error' procedure.
|
000090 |
The Calculation Rules table was not found for the Benefit defined. |
- Review the Benefit / Deduction Program Table for the specified calc rules ID.
- Correct if appropriate
- Rerun the BenAdmin process following the 'Prep Error' procedure.
|
000099 |
The Service Rate Table named below was not found in the database. |
- Review the Service Rate Table for the specified service rate ID.
- Correct where appropriate
- Rerun the BenAdmin process following the 'Prep Error' procedure.
|
000100 |
The service value for this employee was not found in the ranges defined for this Service Rate Table or the Service Step Table. The first value is the Plan Type, next is the table name, and finally, the table type. |
- Review the message detail.
- The first value is the Plan Type, next is the table name, and finally, the table type.
- Determine the benefit and table ID assigned to the plan.
- Then review the Service Rate Table or Service Step Table with which the Plan Type is associated.
- Correct where appropriate
- Rerun the BenAdmin process following the 'Prep Error' procedure.
|
000128 |
During Program Assignment, it was determined that this employee is eligible for more than one program. The Eligibility Rules Tables need to be modified to make Program eligibility unique. One error message will be generated for each eligible program. (MSGData1: Benefit-Program) |
- Associates can only be eligible for one benefit program per empl record.
- Review the Eligibility Rules Table, comparing the data there with the data on the associate’s record.
- Correct data where eligibility duplicates exist.
- Rerun the BenAdmin process following the 'Assgn Error' procedure.
|
000129 |
During Program Assignment, it was determined that this employee is not eligible for any Benefit Program. The system attempted to terminate current participation, but no currentPS_Ben_Prog_Partic record was found (default Hire record is missing). |
- The bottom row of the associate’s Ben Prog Partic record should be effective dated to match that of the effective date of the bottom row of their Job record (Hire record).
- Review the associate’s Ben Prog Partic record.
- If no data exists which matches the Hire date, insert a row with the effective date matching the effective date of the Hire record.
- Rerun the BenAdmin process following the 'Assgn Error' procedure.
|
000132 |
The indicated salary-rate was not found on the Salary_Rate_Tbl. (MSGData1: Plan-Type; MSGData2: Benefit-Plan;MSGData3: Table-Id) |
- Review the Salary Rate Table to ensure proper set up of rate information.
- Correct where appropriate
- Rerun the BenAdmin process following the 'Prep Error' procedure.
|
000133 |
The indicated flat-rate was not found on the Flat_Rate_Tbl. (MSGData1: Plan-Type; MSGData2: Benefit-Plan;MSGData3: Table-Id) |
- Review the Flat Rate Table to ensure proper set up of rate information.
- Correct where appropriate
- Rerun the BenAdmin process following the 'Prep Error' procedure.
|
000149 |
Duplicate Enrollment Replaced. Informational Only: The system encountered a new enrollment action for which a Benefit Enrollment record already exists with the same Effective Date. The system deleted the current Benefit Enrollment record (and all associated dependent/beneficiary and investment records where applicable) and replaced it with the new enrollment.(MSGData1: Plan-Type; MSGData2:EffDt) |
- This message indicates that two events have processed for the individual that have overwritten one another meaning the deduction begin date was the same for both events.
- This may be a coordination issue depending on which event was processed last.
- Check your events to make sure they processed in correct order.
|
000150 |
The Event Rule for this Plan Type requires that an election be made (theElection-Required indicator onBas_Event_Rules is Yes) but no Option-Cd has been specified on Bas_Partic_Plan. (MSGData1: PlanType) |
- This message indicates that the Elect Required flag has been turned on for this particular event and that no election was made for this event. Peruse the Benefit / Deduction Program Table to find the Event Rules ID associated with the plan type indicated. Now review the Event Rules Table using the proper Event Rules ID. Correct where appropriate and rerun the BenAdmin process following the 'Election Error' procedure.
|
000151 |
The Option-Cd elected on Bas_Partic_Plan does not exist as an eligible 'O' or 'W' entry on Bas_Partic_Optn. (MSGData1: Plan-Type; MSGData2: Option-Cd) |
- Review the Benefit / Deduction Program Table for the specified plan type and option. If data is correct, re-enter the Emplid in the Election Entry pages and correct the option code in error. If data on the Benefit / Deduction Program Table is in error, correct where appropriate and rerun the BenAdmin process following the 'Election Error' procedure.
|
000152 |
The Option-Cd elected on Bas_Partic_Plan requires proof of insurability (the Proof-Required-Indicator on Bas_Partic_Optn is Yes) but the Proof-Received-Indicator is still No. (MSGData1: Plan-Type; MSGData2: Option-Cd) Bas_Partic_Plan requires proof of insurability (the Proof-Required-Indicator on Bas_Partic_Optn is Yes) but the Proof-Received-Indicator is still No. |
- Peruse the Benefit / Deduction Program Table to find the Event Rules
- ID associated with the Plan Type indicated. Now review the Event Rules Table using the proper Event Rules ID.
- If the rule is incorrect, correct where appropriate.
- If the rule is correct and proof has not been received, the associate is not eligible for the benefit until such time as proof is received.
- Rerun the BenAdmin process following the 'Election Error' procedure.
|
000153 |
A Life_ADD_Tbl record was not found for the indicated 2x Plan Type being processed on Bas_Partic_Plan. (MSGData1: Plan-Type; MSGData2: Benefit-Plan; MSGData3: Event-Dt) |
- Review the Life and AD/D Table to ensure proper set up of the benefit plan indicated.
- Correct where appropriate
- Rerun the BenAdmin process following the 'Election Error' procedure.
|
000154 |
Event / Record Mismatch. The PS_Job record which triggered a previous event can no longer be found (the record may have been deleted). Because of this, the Event cannot be processed any further. (MSGData1: Event Date) |
- Review the associate’s Job record matching the Empl Rcd #, Effective Date and / or Effective Date Sequence # indicated.
- If proper data exists, contact your technical support person for assistance.
- If data does not exist, the associate can no longer be processed in this Event Maintenance cycle for the event, due to the deletion of Job data.
- Examine more closely the event that had been processed to see if any action needs to be done.
- If the event was already finalized it may now need to be voided.
|
000155 |
No Schedule could be found to process a new event. A Schedule-Id must exist that matches the employee’s Company and BAS-Group-ID. (MSGData1: Company; MSGData2: BAS-Group-Id) |
- Review the Schedule Table to ensure proper set up of the schedule indicated.
- If none exists, add a Schedule to the table including the proper BAS Group ID for processing Event Maintenance.
- Restart COBOL process with “None” Reprocess radio button turned on.
|
000156 |
The Option-Cd elected on Bas_Partic_Plan requires that a flat coverage amount be supplied (the Life-Bas_Partic_Plan requires that a flat coverage amount be supplied (the Life-ADD-Covrg code is '1') but the FlatAmount on Bas_Partic_Plan is zero. ADD-Covrg code is '1') but the FlatAmount on Bas_Partic_Plan is zero. (This message will only occur when the Life-ADD-Covrg type on Life_ADD_Tbl is '3' -Specify on Employee Record). (MSGData1: Plan-Type; MSGData2:Option-Cd) |
- This message will only occur when the Life-ADD-Covrg type on Life_ADD_Tbl is '3' -Specify on associate Record.
- Review the Life and AD/D Table to ensure that the data established is correct for the benefit plan in question.
- If data is correct, re-enter the EmplID in the Election Entry pages and supply the flat amount of insurance.
- If data on the Life and AD/D Table is in error, correct where appropriate.
- Rerun the BenAdmin process following the 'Election Error' procedure.
|
000157 |
The Option-Cd elected on Bas_Partic_Plan requires that a salary coverage factor be supplied (the LifeADD-Covrg code is '2') but the FactorXsalary on Bas_Partic_Plan is zero. (This message will only occur when the Life-ADD-Covrg type on Life_ADD_Tbl is '3' -Specify on Employee Record).(This message will only occur when the Life-ADD-Covrg type on Life_ADD_Tbl is '3' -Specify on Employee Record). (MSGData1: Plan-Type; MSGData2: Option-Cd) |
- This message will only occur when the Life-ADD-Covrg type on Life_ADD_Tbl is '3' -Specify on associate Record.
- Review the Life and AD/D Table to ensure that the data established is correct for the benefit plan in question.
- If data is correct, re-enter the EmplID in the Election Entry pages and supply the salary coverage factor for the proper insurance coverage calculation.
- If data on the Life and AD/D Table is in error, correct where appropriate.
- Rerun the BenAdmin process following the 'Prep Error' procedure.
|
000158 |
The Option-Cd elected on Bas_Partic_Plan requires that a Benefits Base (either the Annual or BenefitsBase salary) be indicated for use in the calculation of Factor-Times-Salary life coverage amounts (the Life-ADD-Covrg code is '2') but the Benefits-Base flag on Bas_Partic_Plan is blank. (This message will only occur when the Life-ADD-Covrg code on Life_ADD_Tbl is '3' - Specify on Employee Record) (MSGData1: Plan-Type; MSGData2: Option-Cd) |
- This message will only occur when the Life-ADD-Covrg code on Life_ADD_Tbl is '3' - Specify on associate Record.
- Review the Life and AD/D Table to ensure that the data established is correct for the benefit plan in question.
- If data on the Life and AD/D Table is in error, correct where appropriate.
- If data is correct, review the associate’s Job Data to ensure that an Annual Rate or Benefits Base Rate is specified.
- If one is not present, contact the Payroll Supervisor for corrective action.
- If a salary is present, contact your technical support person for assistance.
- When data is corrected, rerun the BenAdmin process following the 'Election Error' procedure.
|
000159 |
The Option-Cd elected on Bas_Partic_Plan requires that a coverage calculation method be specified, but the Life-ADD-Covrg code on Bas_Partic_Plan is neither '1'(Flat Amount) nor '2'(Factor Xsalary). (This message will only occur when the LifeADD-Covrg code on Life_ADD_Tbl is '3' - Specify on Employee Record) (MSGData1: Plan-Type; MSGData2 Option-Cd) |
- Review the Life and AD/D Table to ensure that the data established is correct for the benefit plan in question.
- If data on the Life and AD/D Table is in error, correct where appropriate.
- If ‘3’ - Specified in associate Record is turned on review the associate’s Job Data - Use - Job Data) to ensure that an Annual Rate or Benefits Base Rate is specified.
- If one is not present, contact the Payroll Supervisor for corrective action.
- If ‘4’ - Special Calculation Routine or ‘5’ - Sum of Dependent Coverage is turned on, contact your technical support person for assistance.
- When corrections are complete, rerun the BenAdmin process following the 'Election Error' procedure.
|
000160 |
The Option-Cd elected on Bas_Partic_Plan is not defined as "Specify on Employee Record" (the LifeADD-Covrg code on Life_ADD_Tbl is not '3'), but one of the fields Flat-Amount or Factor-Xsalary on Bas_Partic_Plan is not equal to zero. These two fields can only be used when the Life Plan is "Specify on Employee Record". (MSGData1: Plan-Type; MSGData2: Option-Cd) |
- Review the Life and AD/D Table to ensure that the data established is correct for the benefit plan in question.
- If data on the Life and AD/D Table is in error, correct where appropriate.
- If data is correct, re-enter the EmplID in the Election Entry pages and delete the Flat Amount or Factor –x Salary for the proper insurance coverage calculation.
- When corrections are complete, rerun the BenAdmin process following the 'Election Error' procedure.
|
000161 |
A Savings_Plan_Tbl record was not found for the indicated 4x Plan Type being processed on Bas_Partic_Plan. (MSGData1: Plan-Type; MSGData2: Benefit-Plan; MSGData3: Event-Dt) |
- Review the Savings Plan Table to ensure proper set up of the benefit plan indicated.
- Correct where appropriate
- Rerun the BenAdmin process following the 'Election Error' procedure.
|
000162 |
For the Option-Cd indicated on Bas_Partic_Plan, the employee has elected before-tax contributions on a "Percent of Gross" basis (the SavingsCovrg field equals '2') but the Flat-DedAmt field on Bas_Partic_Plan is not equal to zero. (MSGData1: Plan-Type; MSGData2: Option-Cd) |
- Review the Savings Plan Table to ensure proper set up of the benefit plan indicated.
- If data is correct, re-enter the EmplID in the Election Entry pages and delete the Flat Deduction Amount data and enter the correct before-tax Percent of Gross.
- Correct where appropriate
- Rerun the BenAdmin process following the 'Election Error' procedure.
|
000163 |
The employee's before-tax Savings Plan contribution rate (the Pct-Gross field on Bas_Partic_Plan) is greater than the maximum allowed percentage contribution on the Savings_Pln_Tbl (Empl-Pct-Btax field). (MSGData1: Plan-Type; MSGData2: Option-Cd) |
- Review the Savings Plan Table and correct the associate Before Tax Investment Limited To amount.
- Correct where appropriate
- Rerun the BenAdmin process following the 'Election Error' procedure.
|
000164 |
For the Option-Cd indicated on Bas_Partic_Plan, the employee has elected before-tax contributions on a "Flat-Amount" basis (the Savings-Covrg field equals '1') but the Pct-Gross field on Bas_Partic_Plan is not equal to zero. (Empl-Pct-Btax field). (MSGData1: Plan-Option-Cd) |
- Review the Savings Plan Table to ensure proper set up of the benefit plan indicated.
- If data is correct, re-enter the EmplID in the Election Entry pages and delete the Percent of Gross data and enter the correct Flat Deduction Amount.
- Correct where appropriate
- Rerun the BenAdmin process following the 'Election Error' procedure.
|
000165 |
For the Option-Cd indicated on Bas_Partic_Plan, the employee has elected after-tax contributions on a "Percent of Gross" basis (the SavingsCovrg-Atax field equals '2') but the FlatDed-Amt-Atax field on Bas_Partic_Plan is not equal to zero. (MSGData1: Plan-Type; MSGData2: Option-Cd) |
- Review the Savings Plan Table to ensure proper set up of the benefit plan indicated.
- If data is correct, re-enter the EmplID in the Election Entry pages and delete the Flat Deduction Amount data and enter the correct after-tax Percent of Gross.
- Correct where appropriate
- Rerun the BenAdmin process following the 'Election Error' procedure.
|
000166 |
The employee's after-tax Savings Plan contribution rate (the Pct-Gross-Atax field on Bas_Partic_Plan) is greater than the maximum allowed percentage contribution on the Savings_Pln_Tbl(Empl-Pct-Atax field). (MSGData1: Plan-Type; MSGData2: Option-Cd) |
- Review the Savings Plan Table and correct the associate After Tax Investment Limited To amount.
- Correct where appropriate
- Rerun the BenAdmin process following the 'Election Error' procedure.
|
000167 |
For the Option-Cd indicated on Bas_Partic_Plan, the employee has elected after-tax contributions on a "FlatAmount" basis (the Savings-Covrg-Atax field equals '1') but the Pct-Gross-Atax field on Bas_Partic_Plan is not equal to zero. (MSGData1: Plan-Type;MSGData2: Option-Cd) |
- Review the Savings Plan Table to ensure proper set up of the benefit plan indicated.
- If data is correct, re-enter the EmplID in the Election Entry pages and delete the Percent of Gross data and enter the correct Flat Deduction Amount.
- Correct where appropriate
- Rerun the BenAdmin process following the 'Election Error' procedure.
|
000168 |
The employee has elected a Savings Plan option, but no contribution rate has been specified (the combined sum of Pct-Gross, Pct-Gross-Atax, Flat-DedAmt and Flat-Ded-Amt-Atax fields on Bas_Partic_Plan equals zero).(MSGData1: Plan-Type; MSGData2:Option-Cd) |
- Re-enter the EmplID in the Election Entry pages and enter the correct data required for the associate enrollment for the Savings Plan.
- Correct where appropriate
- Rerun the BenAdmin process following the 'Election Error' procedure.
|
000169 |
The employee has elected a Savings Plan option, but the total contribution rate (sum of Pct-Gross and Pct-Gross-Atax fields on Bas_Partic_Plan) is greater than the maximum allowed combined percentage contribution on the Savings_Pln_Tbl (Empl-Limit-Pct field).(MSGData1: Plan-Type; MSGData2:Option-Cd) |
- Review the Savings Plan Table (Define Business Rules - Administer Base Benefits - Setup) to find the associate Investment Limited To Percentage.
- Re-enter the EmplID in the Election Entry pages and enter the proper percentages to be less than or equal to the total investment limit.
- Correct where appropriate
- Rerun the BenAdmin process following the 'Election Error' procedure.
|
000171 |
The total of percentage allocation of all Savings Plan investment options is invalid (the Investment-Pct fields for each Investment-Opt elected on Bas_Partic_Invt are greater than zero but are not equal to 100%. (MSGData1: Plan-Type; MSGData2: Option-Cd) |
- Re-enter the EmplID in the Election Entry pages and enter the proper percentages for investment purposes, ensuring that all percentages are equal to 100%.
- Correct where appropriate
- Rerun the BenAdmin process following the 'Election Error' procedure.
|
000172 |
The indicated Investment-Opt elected on Bas_Partic_Invt was not found as an active, eligible option in the Savings_Inv_Tbl. (MSGData1: Plan-Type; MSGData2: Option-Cd;MSGData3: Investment-Opt) |
- Review the Savings Plan Table for the Investment Options set up.
- If incorrect, add or delete the proper investment options.
- Re-enter the EmplID in the Election Entry pages and enter the proper investment option(s).
- Correct where appropriate
- Rerun the BenAdmin process following the 'Election Error' procedure.
|
000173 |
The employee elected an FSA Plan option, but the Empl-Contributn-Amt or Annual-Pledge fields on Bas_Partic_Plan are less than or equal to zero. (MSGData1: Plan-Type; MSGData2: Option-Cd) |
- Re-enter the EmplID in the Election Entry pages and enter the proper associate Contribution Amount of Annual Pledge amount for the FSA plan.
- Correct where appropriate and rerun the BenAdmin process following the 'Election Error' procedure.
|
000174 |
The employee elected an FSA Plan option, but the Annual_Pledge amount specified on Bas_Partic_Plan is less than the minimum allowed on Ben_Defn_Plan (Min-Annual-Contrib). (MSGData1: Plan-Type; MSGData2: Option-Cd) |
- Review the Benefit / Deduction Program Table for the amount specified as the FSA Minimum Annual Pledge.
- Re-enter the EmplID in the Election Entry pages and enter the proper Annual Pledge amount for the associate.
- Correct where appropriate
- Rerun the BenAdmin process following the 'Election Error' procedure.
|
000175 |
The employee elected an FSA Plan option, but the Annual_Pledge amount specified on Bas_Partic_Plan is more than the maximum allowed on Ben_Defn_Plan (Max-Annual-Contrib). (MSGData1: Plan-Type; MSGData2: Option-Cd) |
- Review the Benefit / Deduction Program Table for the amount specified as the FSA Maximum Annual Pledge.
- Re-enter the EmplID in the Election Entry pages and enter the proper Annual Pledge amount for the associate.
- Correct where appropriate
- Rerun the BenAdmin process following the 'Election Error' procedure.
|
000184 |
The employee has covered a dependent or assigned a beneficiary on the Bas_Partic_Dpnd table whose Dependent-Benef Id could not be found in the base Dependent_Benef table. (MSGData1: Plan-Type; MSGData2: Option-Cd; MSGData3: Dependent- Benef) |
- Review the Dependent / Beneficiary to review the established dependents and/or beneficiaries the associate has listed. Correct data, where appropriate.
- Re-enter the EmplID in the Election Entry pages and enter the correct dependent / beneficiary ID on the proper page. Correct where appropriate
- Rerun the BenAdmin process following the 'Election Error' procedure.
|
000185 |
The employee has specified on Bas_Partic_Dpnd the Id of a beneficiary (type 'B') to be covered under a Plan Type that only allows dependents (types 'D' or 'O'). Only "dependents" may be covered under Plan Types 1X, 24 and 25. (MSGData1: Plan-Type; MSGData2: Option-Cd; MSGData3: Dependent- Benef) |
- Re-enter the EmplID in the Election Entry pages and enter the correct beneficiary ID on the proper page for the Plan Type specified.
- Correct where appropriate
- Rerun the BenAdmin process following the 'Election Error' procedure.
|
000186 |
The employee has specified on Bas_Partic_Dpnd the Id of a dependent (type 'D') to be an assignee under a Plan Type that only allows beneficiaries (types 'B' or 'O'). Only "beneficiaries" may be covered under Plan Types 20, 21, 22, 4X and 8X. (MSGData1: Plan-Type; MSGData2: Option-Cd; MSGData3: Dependent-Benef) |
- Re-enter the EmplID in the Election Entry pages and enter the correct dependent ID on the proper page for the Plan Type specified.
- Correct where appropriate.
- Rerun the BenAdmin process following the 'Election Error' procedure.
|
000187 |
The employee has elected a Dependent Coverage Plan Type (eg., 24 or 25). While specifying the dependents to be covered on Bas_Partic_Dpnd, beneficiary percentages were entered. This is not valid for these Plan Types. (MSGData1: Plan-Type; MSGData2: Option-Cd) |
- Re-enter the EmplID in the Election Entry pages moving to the proper page for the Plan Type specified.
- Delete the beneficiary percentages entered.
- Correct where appropriate.
- Rerun the BenAdmin process following the 'Election Error' procedure.
|
000188 |
The employee has assigned benefits under a Plan using percentage allocations, but the percentages do not total 100% for both primary and contingent beneficiaries. (MSGData1: Plan-Type; MSGData2: Option-Cd) |
- Re-enter the EmplID in the Election Entry pages moving to the proper page for the Plan Type specified.
- Change the beneficiary percentages to total 100%.
- Correct where appropriate.
- Rerun the BenAdmin process following the 'Election Error' procedure.
|
000192 |
The employee has assigned benefits under a Plan using flat-amount allocations but has failed to designate an "excess" beneficiary. An excess beneficiary must be specified to handle the possibility that the coverage amount exceeds the specified flat allocations. (MSGData1: Plan-Type; MSGData2: Option-Cd) |
- Re-enter the EmplID in the Election Entry pages moving to the proper page for the Plan Type specified.
- Enter an excess beneficiary or change one of the beneficiaries already designated as the excess beneficiary, leaving flat amount blank.
- Correct where appropriate
- Rerun the BenAdmin process following the 'Election Error' procedure.
|
000193 |
The sum of the Health Care FSA and Dependent Care FSA Annual-Pledge fields on Bas_Partic_Plan is greater than allowable combined maximum as defined on Ben_Defn_Pgm (the FSAMax-Annl-Pldg field). (MSGData1: Plan-Type; MSGData2: Option-Cd) |
- Re-enter the EmplID in the Election Entry pages moving to the proper page for the Health Care spending account benefit. Review the pledge amount entered.
- Now scroll to the Dependent Care spending account benefit and review the pledge amount entered there.
- Add the two amounts together and adjust the totals according to the FSA Maximum Pledge Amount specified on the Benefit / Deduction Program Table.
- Correct where appropriate
- Rerun the BenAdmin process following the 'Election Error' procedure.
|
000195 |
Based on the Event date being processed, the Pay-Begin-Date for the next pay period cannot be determined from PS_Pay_Calendar. Establish the missing periods in the pay calendar. (MSGData1: Company; MSGData2: Pay- Group; MSGData3: Event-Dt) |
- Contact the Payroll Supervisor to have him/her establish the missing periods in the pay calendar table.
- Correct where appropriate
- Rerun the BenAdmin process following the 'Election Error' procedure.
|
000196 |
Current Pay Period Not Found. Based on the Event date being processed, the Pay-Begin-Date for the current pay period cannot be determined from PS_Pay_Calendar. Establish the missing periods in the pay calendar. (MSGData1: Company; MSGData2: Pay- Group; MSGData3: Event-Dt) |
- Contact the Payroll Supervisor to have him/her establish the missing periods in the pay calendar table.
- Correct where appropriate
- Rerun the BenAdmin process following the 'Election Error' procedure.
|
000197 |
Based on the Event date being processed, the Pay-Begin-Date for the next full pay period cannot be determined from PS_Pay_Calendar. Establish the missing periods in the pay calendar. (MSGData1: Company; MSGData2: Pay-Group; MSGData3: Event-Dt) |
- Contact the Payroll Supervisor to have him/her establish the missing periods in the pay calendar table.
- Correct where appropriate.
- Rerun the BenAdmin process following the 'Election Error' procedure.
|
000198 |
Event Rules ID Not Found. While processing an event for this employee which involves a transfer between Benefit Programs, the system could not find an applicable Event Rule on PS_Ben_Defn_Plan to use to terminate the employee’s current elections. (MSGData1: Plan-Type; MSGData2: Benefit-Program; MSGData3: Event-Dt) |
- When an individual moves between benefit programs the Ben Admin process will use the newly assigned benefit program’s event rules to determine how to process an event.
- However, for Plan Types that are not in the new benefit program, the process goes back to the previous program to determine how to process the Plan Type.
- If the Plan Type is not in the previous program either, then the process does not know how to handle the Plan Type.
- Most of the time the COBOL process wills abend.
- In very few instances you will get this message.
- In either case, to resolve, you will need to manually fix the data and prepare options again on the event.
|
000199 |
A Bas_Partic_Cost record required for computing the indicated option's price or credit amount cannot be found. (MSGData1: Plan-Type; MSGData2: Option-Id) |
- Review the Benefit / Deduction Program Table- Cost page for the Plan Type and option ID indicated.
- Enter the appropriate rate information.
- Most of the time this will abend the COBOL batch process.
- In the event that you do get this message the event should be in a “Prep Error” status and you should be able to just rerun the process once the program entry is corrected.
|
000200 |
The employee has elected a Plan Type that requires covered dependents, but no dependents (Dependent-Benef types 'D' or 'O') have been specified on Bas_Partic_Dpnd. Dependents must be specified under Plan Types 1X, 24 and 25. (MSGData1: Plan-Type; MSGData2: Option-Cd) |
- Re-enter the EmplID in the Election Entry pages moving to the proper page for the Plan Type specified.
- Enter the covered dependents for the Health Plans the associate is enrolled in or change the coverage code to ‘1’ associate Only.
- Correct where appropriate.
- Rerun the BenAdmin process following the 'Election Error' procedure.
|
000201 |
The employee has elected a Plan Type that requires assignment of beneficiaries, but no beneficiaries (Dependent-Benef types 'B' or 'O') have been specified on Bas_Partic_Dpnd. Beneficiaries must be specified under Plan Types 20, 21, 22, 4X and 8X. (MSGData1: Plan-Type; MSGData2: Option-Cd) |
- Re-enter the EmplID in the Election Entry pages moving to the proper page for the Plan Type specified.
- Enter the correct dependent information or make sure the coverage code is correct for the plans the associate is enrolled in.
- Correct where appropriate
- Rerun the BenAdmin process following the 'Election Error' procedure.
|
000202 |
The employee has elected a Savings Plan that requires the selection of investment options, but no investment entries exist on Bas_Partic_Invt. (MSGData1: Plan-Type; MSGData2: Option-Cd) |
- Re-enter the EmplID in the Election Entry pages moving to the proper page for the Plan Type specified.
- Enter the investment option for the benefit plan specified.
- Correct where appropriate.
- Rerun the BenAdmin process following the 'Election Error' procedure.
|
000220 |
Dependent enrolled in a health plan is deceased as of the event date. |
- Re-enter the EmplID in the Election Entry pages moving to the proper page for the Plan Type specified.
- Enter the correct dependent information or make sure the coverage code is correct for the plans the associate is enrolled in.
- Correct where appropriate
- Rerun the BenAdmin process following the 'Election Error' procedure.
|
000221 |
A dependent who is an ex-spouse with a marital status date less than or equal to the event date may not be enrolled in a health plan. |
- Re-enter the EmplID in the Election Entry pages moving to the proper page for the Plan Type specified.
- Enter the correct dependent information or make sure the coverage code is correct for the plans the associate is enrolled in.
- Correct where appropriate
- Rerun the BenAdmin process following the 'Election Error' procedure.
|
000222 |
Non-student is overage. A dependent that is not a student is over the age limit specified at the benefit program level as of the event date. |
- Re-enter the EmplID in the Election Entry pages moving to the proper page for the Plan Type specified.
- Enter the correct dependent information or make sure the coverage code is correct for the plans the associate is enrolled in.
- Correct where appropriate
- Rerun the BenAdmin process following the 'Election Error' procedure.
|
000223 |
A dependent that is a student as of the event date is over the age limit specified at the benefit program level. |
- Re-enter the EmplID in the Election Entry pages moving to the proper page for the Plan Type specified.
- Enter the correct dependent information or make sure the coverage code is correct for the plans the associate is enrolled in.
- Correct where appropriate
- Rerun the BenAdmin process following the 'Election Error' procedure.
|
000224 |
The benefit program does not allow coverage for married dependents. |
- Re-enter the EmplID in the Election Entry pages moving to the proper page for the Plan Type specified.
- Enter the correct dependent information or make sure the coverage code is correct for the plans the associate is enrolled in.
- Correct where appropriate
- Rerun the BenAdmin process following the 'Election Error' procedure.
|
000225 |
The number of dependents is less than the minimum defined for the elected coverage code. |
- Re-enter the EmplID in the Election Entry pages moving to the proper page for the Plan Type specified.
- Enter the correct dependent information or make sure the coverage code is correct for the plans the associate is enrolled in.
- Correct where appropriate
- Rerun the BenAdmin process following the 'Election Error' procedure.
|
000226 |
The number of dependents enrolled exceeds the maximum allowed for the coverage code. |
- Re-enter the EmplID in the Election Entry pages moving to the proper page for the Plan Type specified.
- Enter the correct dependent information or make sure the coverage code is correct for the plans the associate is enrolled in.
- Correct where appropriate
- Rerun the BenAdmin process following the 'Election Error' procedure.
|
000227 |
A dependent that is a spouse has been elected for coverage. The coverage code prohibits spouses from being enrolled. |
- Re-enter the EmplID in the Election Entry pages moving to the proper page for the Plan Type specified.
- Enter the correct dependent information or make sure the coverage code is correct for the plans the associate is enrolled in.
- Correct where appropriate
- Rerun the BenAdmin process following the 'Election Error' procedure.
|
000228 |
A dependent with the relationship of spouse must be enrolled for the coverage elected. |
- Re-enter the EmplID in the Election Entry pages moving to the proper page for the Plan Type specified.
- Enter the correct dependent information or make sure the coverage code is correct for the plans the associate is enrolled in.
- Correct where appropriate
- Rerun the BenAdmin process following the 'Election Error' procedure.
|
000232 |
The FSA Annual Pledge elected cannot be less than the total amount of claims that have been approved for payment to date. Increase the Annual Pledge until it equals or exceeds the Approved amount, as shown on the FSA Year-to-Date. Activity page. (MSGData1: Plan-Type; MSGData2: Option-Cd) |
- This message is saying that when the enrollment for FSA was done, the associate was enrolled in the plan, but the Annual Pledge amount was less than the total YTD approved for payment amount for the MER/DCA plan in the calendar year.
- Correct where appropriate
- Rerun the BenAdmin process following the 'Election Error' procedure.
|
000233 |
The FSA Annual Pledge elected cannot be less than the total amount of FSA contributions that have been deducted to date. Increase the Annual Pledge until it equals or exceeds the Contributions amount, as shown on the FSA Year-to- Date Activity page. (MSGData1: Plan-Type; MSGData2: Option-Cd) |
- This message is saying that when the enrollment for FSA was done, the associate was enrolled in the plan, but the Annual Pledge amount was less than the total YTD deductions taken for the MER/DCA plan in the calendar year.
- Correct where appropriate
- Rerun the BenAdmin process following the 'Election Error' procedure.
|
000234 |
No Open On-Cycle Pay Periods |
|
000235 |
The current FSA deduction calculation was determined to be negative, indicating that the Annual Pledge and the year-to-date Deduction Balance for this Plan Type are out of agreement. For consistency, a zero deduction amount has been returned since negative deductions are not supported. Please adjust as required either to the employee's benefit election or to his deduction balances. (MSGData1: PlanType and Benefit-Plan; MSGData2: Deduction-Code and Class; MSGData3: Calculated negative deduction) |
- This message is saying that when the enrollment for FSA was done, the associate was enrolled in the plan, but the Annual Pledge amount was less than the total YTD deductions taken for the MER/DCA plan in the calendar year.
- Correct where appropriate
- Rerun the BenAdmin process following the 'Election Error' procedure.
|
000236 |
The employee elected an FSA Plan option, but the Annual-Pledge field on Bas_Partic_Plan is less than or equal to zero. This is a required entry and must be a positive dollar amount. (MSGData1: Plan-Type; MSGData2: Option-Cd) |
- This message is saying that when the enrollment for FSA was done, the associate was enrolled in the plan, but forgot to put in an YTD pledge amount.
- Correct where appropriate
- Rerun the BenAdmin process following the 'Election Error' procedure.
|
000288 |
No covered dependents were found for this Plan. This is a Dependent Life plantype, which requires that each dependent covered by the policy be individually entered. Because no dependents were found, the Coverage Amount, and therefore the resulting Deduction, may have been calculated as $0. This may also impact imputed income calculations. (MSGData1: Plan-Type) |
- This message is saying that when the enrollment for dependent life was done, no dependents were ever tied to the plan, so there may be a problem with imputed income on dependent life.
- Correct where appropriate
- Rerun the BenAdmin process following the 'Election Error' procedure.
|
000292 |
The employee has an unfinalized event on a job row that is not the highest sequence number for that day. This can be caused by someone adding a new row for the day after event maintenance has already started processing the earlier row. Please review the employee's events and take appropriate action. (MSGData1: Job-EffDate;MSGData2: Job-EffSeq) |
- This message is telling you that a new event has been initiated with an event date prior to a finalized future event.
- There may be some coordination issues to deal with so examination of the future event needs to take place and possibly reprocessing of the event.
|
000293 |
The system has found a new sequence number on this date. The system has already processed an event for this date. Please review this employee’s events. The system will not take any automatic action against the earlier event. (MSGData1: Job-EffDate; MSGData2:Job-EffSeq) |
- This message is telling you that a new event has been initiated with an event date equal to a currently processing event.
- There may be some coordination issues to deal with so examination of the current event needs to take place and possibly reprocessing of the event.
|
000294 |
This event has become disconnected (the associated JOB record has been deleted or redated). This event has a status of Finalized-Enrolled. This means that the system may have made changes to the employee's benefit elections. Review the employee's benefits to see if the employee's benefits should be changed or redated. (MSGData1: Event-Date) |
- This message is telling you about an event in a Finalized-Enrolled status has been disconnected.
- The event was completed and an enrollment situation was performed meaning that before the job record was deleted, the event should have been voided.
- Be sure that there are no active elections for this disconnected event in Base Benefits.
|
000295 |
Future Election Deleted. Informational only: The system encountered a new enrollment action for a plan type for which a future dated benefit enrollment record already exists. The existing enrollment record was inserted by an event which precedes the current event. The system deleted the future benefit enrollment record (and all associated dependent/beneficiary, investment and billing records where applicable). |
- Happens when you add dependents to vision and the vision has already been assigned.
- System is overwriting the enrollment without dependents with the enrollment that includes dependents.
|
000325 |
Multi Job Not Found. A job record does not exist as of the event date specified on the BAS_ACTIVITY record. |
- A job record/row was deleted or There’s a mismatch in the Benefit Rcd Nbr/Empl Rcd in the Bas Activity table vs the Per Org Asgn table.
- The system deletes the schedule ID from the bas activity, so it no longer appears on the Review Bas Activity page.
|
000326 |
Duplicate Manual Event. A BAS_PARTIC record exists for the same manual event on the BAS_ACTIVITY record. The BAS_ACTIVITY was not processed and was not deleted. (MSGData1: Empl Rcd No, MSGData2: Event Dt, MSGData3: Event Class) |
- Employees appeared on the BAS03 report.
- Unable to resolve/reprocess, no schedule ID.
- Delete the offending rows from the BAS_MESSAGE table via SQL. An event already exists with the same emplid, benefit rcd nbr, event date and bas action.
- The system deletes the schedule ID from the bas activity, so it no longer appears on the Review Bas Activity page.
|
000327 |
No Job Data for Event. The HR data required to process eligibility for the participant does not exist. |
- The event has been disconnected because an effective dated job or address row that was originally used to determine eligibility for the event no longer exists.
- REQUIRED ACTION only if the process status of the event is Finalized-Enrolled (FE or Enrolled) is to change the process indicator on the event to VOID and run the batch cobol process to back out any rows that the event posted to base benefits.
- The process status changes to “Re-enter.” Disconnected events cannot be processed other than to void finalized-enrolled events.
|
000328 |
Partic Eligibility has changed. The eligibility data has changed between benefit program assignment and option processing phases. Review the participant's HR data to determine if reprocessing is required. |
- This is a student and does not have any qualifying appointments. Close the open event. Change flag(s) to processed.
|
000330 |
Current Coverage Ineligible. The employee is not eligible for the coverage in the base benefits tables. This may be either an error in the data load to the base benefits tables or an error in the eligibility rules. |
|
000351 |
While processing eligibility for this event, none of the employee's jobs were evaluated, even though an eligibility rule contained job-level eligibility criteria. Check this employee's benefit system and "include for eligibility" flags to determine why no jobs were evaluated. This message will appear for each eligibility rule evaluated, containing joblevel eligibility criteria. |
|
000608 |
Minimum Number Covered Error. There are not enough dependents of this type of dependent and this coverage code. |
- This happens when you enter party code 3 but only one dependent won't let you save until you fix it.
- There are an insufficient number of dependents enrolled for the coverage code.
- The event needs to have election entry corrected to reflect the correct coverage code for the # of covered dependents.
|
000609 |
Maximum Number Covered Error |
- Too many dependents were enrolled for the coverage code.
- The event needs to have election entry corrected to reflect the correct coverage code for the # of covered dependents.
|
000613 |
Future Dated Enrollment Exists. Informational only: The system encountered a new enrollment action for which a benefit enrollment record already exists with the future effective date. Correct accordingly. |
- Enrollment dates need to be verified and corrected as needed.
|
0 Comments
Add your comment