Overview of EO benefit and transaction definition

Shortcut/mask: HREOSU

Employee Online reads an HR table to understand benefits at a given site. This table controls how benefits will be displayed to the employee and what, if anything, an employee can change for a particular benefit. We modify this table using HREOSU window.

EO Benefit Setup tab

  • EO Group: There are four possible benefit groups: INS (insurance), REIM (reimbursements), RETI (retirement), OTH (other). Groupings are arbitrary. It is not necessary to use them all. Entries in other groups will be determined by how a site's benefits are organized.
  • Plan Type: A site-defined value used to create subgroups within an EO Group. A plan type should be defined for each type of benefit which EO will allow a user to see. For example, a site that has three different dental plans would define three different entries with EO Group set to INS and Plan Type set to DENTAL PLAN.
  • Exclusive in Plan Type: A ‘Y’ indicates that an employee may only have one of the possibilities defined in the Plan Type.
  • Target Record: The name of the target cluster that Employee Online will use for the benefit. The only supported targets are "BENEINFO" and "CDHASSGN".
  • Entity: The Entity ID to which the record is associated. If employees from different entities are going to log in, then separate entries must be made for each entity.
  • Benefit Code: The Benefit code from the Benefit plan associated with the benefit.
  • Benefit Type: The Benefit type from the Benefit plan associated with the benefit.
  • Allowed Categories: A comma-separated list of categories allowed in the Benefit plan for the benefit.
  • Display Order: The sort order EO will use when displaying the benefit. Typically, this field will be numbered so that related Plan Types are shown together and in a certain order.
  • Allow Close: A value of 'N' or 'NO' indicates the employee is not allowed to close the benefit.
  • New Hire Period: If a benefit can only be added within a certain number of days from the hire date then enter the number of days. Leave blank if the employee can add the benefit at any time. A negative value in the field indicates that the employee is not allowed to add the benefit through Employee Online.
  • Mid-Year Changes: A 'NO' means that no change is allowed. A '125' means that change requests must meet section 125 criteria. 'OK' or blank means that the EO user is allowed to make changes at any time.
  • Vendor Url: Field should be populated if EO users are allowed to navigate to a site relevant to the benefit. The vendor's url should be in the format of: www.xxx.yy.
  • Include Employee Types: Enter a comma-separated list of employee types to be included. If inclusion is not based on employee type then leave blank. Populate only if certain employee types are eligible for the benefit. Wildcards are allowed in the list. A '?' acts as a single character wildcard while '*' can be used to match zero or more characters.
  • Exclude Employee Types: A comma-separated list of employee types who are to be excluded from the benefit. Leave blank if exclusion is not based on employee type. Wildcards are allowed in the list. A '?' acts as a single character wildcard while '*' can be used to match zero or more characters.
  • Read Only: A 'Y' indicates the benefit cannot be modified by Employee Online. A user will be able to view information regarding the benefit but will not be allowed to request any changes.
  • Form Required: A 'Y' indicates a form is required for changes to the benefit.
  • Form Name: The file name for the form associated with the benefit. Currently these files live in the ClientSpecific directory in the Employee Online website and must be in PDF format. The suffix should be included in the file name (i.e. GroupTermLife.pdf).
  • Dependent Info: A ‘Y’ indicates dependent information should be recorded by name.
  • Special Code Box # - Denotes the special code box that should record the number of dependents covered.
  • Record Dependent # - A ‘Y’ indicates the benefit needs to record the number of dependents covered.
  • Coverage Info: A ‘Y’ indicates the benefit has a coverage amount associated with it.
  • Special Code Box # - Denotes the special code box that should record the coverage amount.
  • Units: Denotes the units of the coverage amount placed in the special code box.
  • Increment Amount-Thousands: Denotes the increment between coverage steps. It should only be used if the increment is consistent between all steps.

Open Enrollment Information

  • Period 1 Begin: The MM/DD part of the begin date for the first open enrollment period for the benefit. If open enrollment does not apply then leave blank.
  • Period 1 End: The MM/DD part of the end date for the first open enrollment period for the benefit. If open enrollment does not apply then leave blank.
  • Start MM/DD for Coverage: The MM/DD part of the date on which the first open enrollment request are to become effective.
  • Period 2 Begin: The MM/DD part of the begin/end dates for the second open enrollment period for the benefit. If open enrollment does not apply then leave blank.
  • Period 2 End: The MM/DD part of the begin/end dates for the second open enrollment period for the benefit. If open enrollment does not apply then leave blank.
  • Start MM/DD for Coverage: The MM/DD part of the date on which the second open enrollment requests are to become effective.

EO Transaction Definition tab

  • Transaction Class: Transaction Class.
  • Primary target: Primary Target Record Type.
  • Subsystem: Subsystem.
  • Secondary Target: Secondary Target Record Type.
  • Allowed Modes: Flag values for Add, Update, Close and Switch.
  • Procedure to Call: Procedure to call for Add, Update, Close and Switch.
  • Transaction Flag Titles: Transaction Flag Title 1, Title 2, Title 3 and Title 4 for Add Update, Close, and Switch.
  • Sub Key Title: Subsystem Key Title.
  • Sub Key Cluster: Sub Key Cluster.
  • Sub Key Attribute: Sub Key Attribute.
  • Echo Cluster: Echo Cluster.
  • Echo Attribute: Echo Attribute.
  • Notes: Notes.