Transaction Requests - HREOTR
Introduction
Most pages in Employee Online (EO) map directly onto corresponding HR pages, with the exception of benefit requests. Requests made in Benefits are recorded in the Transaction Request (hr_trnsreq) table of HREOTR. For processing information, Refer to Processing a Benefit Change Request in HREOTR.
EO Requests
Transaction ID: A request identification number automatically generated by the system.
Transaction Class: Automatically entered by EO. EO BENEINFO REQUEST and EO CDHASSGN REQUEST are the only recognized values.
Mode Type: Automatically entered by EO. Valid values are ADD, UPDATE, CLOSE, or SWITCH. The SWITCH value is used in cases where the request involves a change to a new benefit plan base. The benefit plan is made up of a benefit code, benefit type, and category. The benefit plan base is just the first two of these, the benefit code and the benefit type.
In a scenario where an employee already has a benefit assigned to them with a current fiscal year end date, and they select the same benefit for the next fiscal year, that benefit record comes into HREOTR with a Mode Type of UPDATE. Records are actually being inserted into HR, but because of the connection with the existing record, the Mode Type is handled differently. For example, HRTBBE record and employee record have 7/1/2016 - 6/30/2017 dates. The new fiscal year HRTBBE record has dates of 7/1/2017 - 6/30/2018. During the Open Enrollment timeframe, prior to the end date of the first record, the employee selects the same benefit plan for the next year. Because the original record already has an end date of one day prior to the new record begin date, the system considers this an UPDATE for Mode Type purposes.
Subsys: System generated. The only valid value is HR.
Employee ID: Employee ID for the request. Recorded by Employee Online.
Request Info Tab
Benefit Plan: The benefit plan to be recorded in Benefit Assignments or CDH Assignments pages if the request is approved.
EO Group: From where the EO request originated. Valid groups are INS (insurance), REIM (reimbursements), RETI (retirement), or OTH (other).
EO Plan Type: The plan type.
Request Type: All entries for benefit requests are labeled as OPEN ENROLLMENT.
Requestor Notes: EO entered notes associated with the request. Text appearing prior to a : (colon) records section 125 qualifying events. Text after the : (colon) is further user explanation from the EO page.
Reviewer Notes: Place for the approver to record notes. These notes are not visible to the employee in EO.
Original Request Date: Date of the original request.
Last Action Date: Date of last change to the request.
Request Begin Date: The proposed begin date for the benefit, if the record is approved. The date will vary depending upon whether the benefit is submitted via the Open Enrollment link or the regular Insurance link.
If the benefit is submitted through the regular Insurance link, the begin date will be the effective period when the request is first made. If the benefit is submitted through the Open Enrollment link, it will be the begin date as established on the Benefit Setup page. The date may have to be adjusted depending on when the record is approved.
Request End Date: The proposed end date for the benefit, if the record is approved. If the regular Insurance link is used for the benefit, the end date will be set to the end date of the Benefit Definition record from HRTBBE. If the Open Enrollment link is used, the end date will be derived based on the Benefit Setup page. If the field is not populated, it will default to the end of the current year.
Action: Valid Action codes are EOA, EOU, and EOC. These codes correspond to Add, Update, and Close requests. Code values are defined in the HR Non-Entity Specific Codes (HRTBHR) page under the Code ID of ACTION_CODE.
Approval Type: EO sets the value to WAIT when a request is made. Approvers can prevent any EO modifications to the request by entering a value of LOCK. A HOLD value will prevent EO from withdrawing the request (the employee will not be able to delete it). A value of APPR on saving will fire the transaction codes that move the request into the appropriate Human Resources and Payroll areas. Upon successful completion of the transaction codes, the APPR will automatically be replaced by a value of SEND.
Approval Date: Indicates the date when the record was approved. System generated.
Request Details Tab
Item #: Item number.
Item Name: Item name.
Old Value: Old value.
New Value: New value.
Transaction Description: Transaction description.
New transaction records are automatically created for beneficiary information. Where the Item # begins with P, those are Beneficiary Percentage records. Where the Item # begins with S, those are Primary Beneficiary records.