OAB
OAB
OAB
Document Control
Change Record
Date May-10-00 Oct-23-00 Nov-30-00 Dec-12-00 Dec-18-00 Apr-10-01 Author Oracle Consulting Tanie Guy Keith Ekiss Tanie Guy Tanie Guy Tanie Guy Version 1 2.0 2.1 2.2 2.3 2.4 Change Reference No Previous Document Update Existing info and Major Additions Edited Document Fixed Employer Deduction Answer Fixed Change record; Added Performance Section Added New FAQs Since Last Updated
Reviewers
Name Phil Chapman Keith Ekiss Position OAB Product Manager OAB Information Designer
Distribution
Copy No. 1 2 3 4 Name Location
Document Control
ii
Contents
Document Control..................................................................................................................................................ii Introduction............................................................................................................................................................5 Expected Background for the Reader of this Document..........................................................................5 General.....................................................................................................................................................................6 Compensation Object Design ..............................................................................................................................8 Life Events (Triggers)............................................................................................................................................9 Eligibility................................................................................................................................................................11 Electability.............................................................................................................................................................13 Derived Factors ....................................................................................................................................................14 Rates/Coverage....................................................................................................................................................15 Actual Premiums ..................................................................................................................................................16 Communications...................................................................................................................................................17 COBRA / HIPAA (US Customers)....................................................................................................................18 Flex Credit Plans...................................................................................................................................................19 Flexible Spending Accounts ..............................................................................................................................20 `Waive Plans.........................................................................................................................................................21 What-If Modeling................................................................................................................................................22 Elements ................................................................................................................................................................23 Payroll....................................................................................................................................................................27 Batch Processes ...................................................................................................................................................28 Reports ..................................................................................................................................................................29 System Extract ......................................................................................................................................................30 Benefits Self Service............................................................................................................................................31
File Ref: R11i Benefits Frequently Asked Questions.doc Document Control iii
Upgrade / Migration Path...................................................................................................................................32 Benefits and FastFormula ...................................................................................................................................34 Performance Considerations ..............................................................................................................................35
Document Control
iv
Introduction
Expected Background for the Reader of this Document
This document is written for a reader who currently understands Oracle and Oracle HRMS Applications R11i. Refer to Managing Total Compensation Using HRMS Release 11i (March 2000), available from Oracle Documentation for further information.
Introduction
5 of 36
General
What benefit functionality is available in Oracle HR Release 11i? There are three levels of benefits available, Oracle Basic Benefits, Oracle Standard Benefits and Oracle Advanced Benefits. Oracle Basic Benefits (OBB) is part of the core HRMS product and is included in Release 10.7, Release 11.x and Release 11i. Oracle Basic Benefits allows for element based benefit processing. In this basic model, the element and element link have limited eligibility restrictions and functionality. The election opportunities or enrollments made under this model are not available for display under any enrollment forms in Standard or Advanced Benefits. Oracle Standard Benefits (OSB), Release 11i is considerably more powerful than the earlier Oracle Basic Benefits. Within this product, clients have the added capability of eligibility determination using profiles with a variety of criteria, and using enrollment forms to enter election information. Oracle Advanced Benefits (OAB), Release 11i contains all the functionality of Oracle Standard Benefits plus: Life Event Management: Online and Batch Flex Credit Calculations and Administration Communications triggers Reimbursement Requests Batch Processing features for Enrollment Management What-if Enrollment Eligibility Modeling Benefits Service Center Management R11i Oracle Advanced Benefits is tailored to 3 groups: 1. 2. 3. Employers who administer their benefit programs in-house Companies who administer benefits for other companies Insurance carriers of benefit offerings
Where do I find the latest information regarding Oracle Consulting Tools for R11i Benefits? Information can be found on the Oracle intranet at the iXchange Portal. http://ixchange.us.oracle.com Follow this path from the iXchange home page: HRMS Professional Community : Reusable Components : HRMS Applications : Release 11i Benefits Do I have to purchase a separate license for Oracle Advanced Benefits if I purchase an HRMS Release 11i license? Yes, you must purchase a separate license for Oracle Advanced Benefits in addition to your license for Oracle HRMS. Licensing of Oracle Payroll is not a requirement, as the core product contains all the information necessary to establish your benefit plans. What languages are available with Oracle Advanced Benefits and Oracle Standard Benefits? Presently, Oracle Advanced Benefits is available in English and Canadian French.
File Ref: R11i Benefits Frequently Asked Questions.doc General 6 of 36
Oracle Standard Benefits is translated into all languages supported by the core HRMS product. Is datetracking available in Standard Benefits and Advanced Benefits? Yes, over ninety percent of the forms are date tracked in both applications. What types of plans can be set up in Standard Benefits and Advanced Benefits? Plans such as Medical, Dental, Life Insurance, Vacation Buy/Sell, Savings Plans, etc. Please refer to Managing Total Compensation Using HRMS Release 11i (March 2000) for more examples. This can document can be downloaded from the iXchange Portal. Does Oracle Advanced Benefits provide a user interface for telephone service representatives for online counseling of employees and other benefits participants? Yes, Oracle Advanced Benefits has a user interface optimized for environments which support counseling to employees and other benefits participants. The Benefits Service Center form provides access to a participants relevant benefit information. Do I have to purchase a separate license for Self Service Human Resources (SSHR)? Yes, you must purchase an additional license for Self Service Human Resources for use with either Standard or Advanced Benefits.
General
7 of 36
8 of 36
person has or has not used during the preceding 12 months. This feature is being considered as an enhancement to the product.
10 of 36
Eligibility
What are Eligibility Profiles? Eligibility profiles determine whether a person satisfies the rules which govern whether that person could ever enroll in a program, plan, or a coverage option within a plan. For example, in order to be eligible for the Acme HMO, a person might have to work more than 30 hours a week and be located in Nevada. Both Standard and Advanced Benefits give you the flexibility to define eligibility at many levels within your benefits program. How do you resolve the following scenario: a Dependent Life plan needs an eligibility profile (the participant must be an employee) and a FastFormula rule (the participant must have elected EE Life). Can you use supply both criteria in one profile? You can create an eligibility profile with multiple criteria and one of those criteria can be a FastFormula Rule. Youll find this eligibility criteria on the tabbed region labeled Other on the Participation Eligibility Profiles window. The person would have to satisfy all criteria in order to satisfy the criteria of the profile, including the rule. However, the above scenerio refers to a Post Enrollment Edit. The system does not know a persons election until the enrollment is recorded. Eligibility profiles are examined during eligibility determination before electable choices are determined. In order to allow a participant to enroll in Dependent Life, the participant needs to be found eligible given that the person is an Employee'. You must attach a Rule to the Program Enrollment Requirements>General>Plan>Post Election Edit Rule that returns a 'Y' or an 'N' for the Dependent Life. This Rule will only allow the person to enroll in Dependent Life if they elect Employee life. The rule type needed is "Post Election Edit". According to the Managing Total Compensation users guide, when you define eligibility profiles, you can define multiple criteria such as location and organization. The participant then must meet at least one value for each criteria defined. Can you define multiple criteria and have the participant meet the value of only one of the criteria, that is having an 'OR' condition as opposed to an 'AND' condition? Could this be done without defining a FastFormula rule? When you attach an eligibility profile to a compensation object (for example, program, plan, plan-inprogram), you can specify whether the profile is required. The person processing must satisfy ALL required profiles and AT LEAST ONE optional profile. If you attach only one profile, the profile is mandatory regardless if the profile is indicated as required. The system will read this profile as optional and at least one optional profile must be satisfied. If you attach more than one profile and no profile is required, only one profile needs to be satisfied to make the person eligible. If you attach more than one profile and all are marked as required, all profiles must be satisfied to make the person eligible. If you attach more than one profile and some profiles are marked as required and some are not marked as required, all of the required profiles must be satisfied and only one of the nonrequired profiles must be satisfied to make the person eligible. You do not have to write a FastFormula rule to accomplish most and/or conditions for eligibility.
File Ref: R11i Benefits Frequently Asked Questions.doc Eligibility 11 of 36
How do you access the benefits tab on the People form which has the benefits group field that is used to attach a Benefits Group to an employee? This is a secured view (function) that should be available on all of the seeded menus for each localization. The following seeded US navigators have this function: US SHRMS Navigator, US HRMS Navigator, US HR Navigator, US HR + OAB (also called US SHR Navigator). These are the menu structures customers in the US should be using as models for customized menus. This also applies for the UK, Canada, France, Global, and all other menu structures. The above menus are attached to seeded responsibilities such as US Super HRMS Manager, US HRMS Manager, US HR Manager, and US Benefits Manager. Therefore, when logging on as one of the seeded responsibilities, you should have access to the appropriate menu structure. Note: It is possible to change the menu structure for these seeded responsibilities or to create new responsibilities with the incorrect menus. Should either event occur, you can update the menu structure to include the Benefits tabbed region. As a system administrator, query the BEN_MANAGER menu in the Menus window and add the HR View Benefits function to the menu. The menu should not have a display name.
Eligibility
12 of 36
Electability
What is Electability? Electability determines whether a person can enroll in a plan for which they satisfy the eligibility criteria. In order for a benefits choice to be electable, a person must be eligible for it. However, there are many cases when a person cannot elect a benefit for which they are eligible. Typically, plan sponsors (and the IRS in the US) place restrictions on when a person can enroll in a benefit plan for which they are eligible. For example, Fred is eligible for all coverage options (Employee Only, Employee Plus Spouse, Family) in the Acme HMO and the Good Health Medical Plan and is currently enrolled in Acme HMO Employee Only. If he gets married, Fred receives Acme Employee Plus Spouse as an electable choice but the coverage options for the Good Health plan will not be electable choices. Medical plans are electable. If Fred moves to a location where Acme HMO plan is not offered, he loses eligibility for that plan and the Good Health Medical Employee Only choice becomes electable. During open enrollment, a person can typically enroll in all of the electable plans and options for which they are eligible. Exceptions to this exist: for example, once a person has enrolled in a given dental plan, often they cannot enroll in a different dental plan (even if they are eligible) until they have satisfied the minimum enrollment period (often two years) in the original dental plan.
Electability
13 of 36
Derived Factors
On the Derived Factors window, there is a field labeled "Alternate Value." This field contains a list of values including "Persons Eligibility Value" and Persons Rate Value". What are these values, where are they defined, and what would trigger their use? The Alternate Value is the value to use when the system tries unsuccesfully to find a given value. This is more likely to happen in cases of compensation than length of service. The person's eligibility value is the value used to determine whether the person is eligible. This value is recorded on the BEN_ELIG_PER_F or BEN_ELIG_PER_OPT_F table. This value can be viewed on the Participation Override window along with the participants rate value. Note: This functionality is planned for future implementation. What is the Override Service Date and where is it defined? The Override Service Date can be entered and viewed on the Participation Override window. It allows the user to enter a date to be used in place of the other service dates: original hire date, hire date, adjusted service date. The user can specify that the length of service factor look at any of these dates. There is a hierarchy in place that checks if the date specified is not available/null. If the service date is not available or null, the system check for the next available service date in the hierarchy. The hierarchy is: Override Service Date Adjusted Service Date Hire Date Original Hire Date
Derived Factors
14 of 36
Rates/Coverage
Which default enrollment code do I use to provide no default elections for a new enrollee, but to retain the existing election for a current participant, while assigning the latest rates? Use the default enrollment code of 'New Nothing, Current Same, Enrollment and Rates'. The issue you may be having is around the 'latest rates'. The default process enrolls the person into whatever rate they previously had ONLY if the rate is defined with 'Enter Value at Enrollment. For example, last year a participant elected to contribute $1200 per year to a Health Care spending account. Using the default enrollment code of 'New Nothing, Current Same, Enrollment and Rates' maintains the default enrollment in this plan at the rate of $1200. If you use the code 'New Nothing, Current Same, Enrollments but Default Rates' the system applies the default value defined on the Standard Rates window for the activity base rate when it is 'Enter Value at Enrollment'. Customers may set up the Health Care spending account with minimum and maxium values, for example Min $120 to Max $1200, with a default rate, such as $120. If a specific election is not made, the participant receives the default min of $120. For open enrollment, the coverage/rates start the first day of next year and end the last day of the following year. What coverage/rate end date should I use? One day before event? For open enrollment, you could use a coverage/rate start date of 'Event' and an End date of 'One day before Event date'. During open enrollment, we specify the life event occurred on date for the open event, for example 01-JAN-2001. This is the date you want the system to determine age, length of service, salary, etc, and the date you want rates and coverage to begin. How does Benefits handle arrearages? Example: New Hire on 08/01/01. Check Date is Semi-Monthly 8/15/01 but New Hire wasn't entered until 08/16/01 which is one payroll later. Benefits doesn't change the way arrearages are handled. This is a payroll function. This feature works as it has in previous releases of Oracle HRMS and is determined based on how elements are defined for your implementation. You should create elements using the Deductions form (template). This form does all of the FastFormula work behind the scenes. Then, if you need to alter anything for arrearages, you would alter the formula as you did prior to r11i. How do I set up the Employer portion of a benefits deduction? Create another standard rate and check the "Assign on Enrollment" field on the Standard Rates window. The person will be assigned this rate (i.e, the system will create a Participant Rate Value). Do not check the "Display on Enrollment" field. This prevents the value from displaying in the enrollment form. If you pass the value to the assignment element entries, you must create an element entry for the employer liability that will be processed by Oracle Payroll. To accomplish this, check the Process in Run field for this rate. What is the appropriate use of the Parent/Child rate field? The use of this field is to identify the Parent rate, and additional rates for the same comp object, child rate(s). One of the Calculation Methods available for rates is Multiple of Parent. This allows the user to set up a Parent rate that is perhaps the Total Amount Due, one Child rate that is the Employee portion, e.g. 60% of Parent, and another that is the Employer portion, e.g. 40% of Parent.
File Ref: R11i Benefits Frequently Asked Questions.doc Rates/Coverage 15 of 36
Actual Premiums
To take advantage of the Premium Calculation process, do I need to set up a separate rate for the employer cost on each option? The premium is the amount paid by the plan sponsor (employer) to the carrier (Aetna, Kaiser etc). Premiums are usually calculated on a per participant basis for an option in plan. Sometimes premiums are based on the total number of participants covered in a plan or an option in plan. So, you will want to consider the premium to be the total cost to the 'Company'. How the company determines what it will pay versus what the employee pays is accomplished through defining Standard Rates. Define the premiums on the Actual Premiums window as the total cost of a benefit to the 'Company', usually for an option in plan. Then define a standard rate for the Employee portion and one for the Employer portion. The two rates should total the premium amount for the option in plan. This is how you derive the 'Employer' portion of the premium. You can also attach elements that will cost the Employer portion accordingly if you use Oracle Payroll. Please refer to the Managing Total Compensation Using Oracle HRMS users guide or your online help system for more information.
Actual Premiums
16 of 36
Communications
How is the term communications used with the applications? Generally, communications are the primary means by which you inform employees and other participants of enrollment periods, administrative procedures, and electable choices. Within the applications, communications refer to the triggers created for a participant under certain conditions that are written to the Person Communication table. For example, a communications trigger indicates that a New Hire Statement should be generated when certain eligibility requirements are met. What types of communications triggers are available in Standard Benefits? Standard Benefits supports manually triggered communications. Because this product does not have any automatic processes, the communication triggers cannot be created automatically. What types of communications triggers are available in Advanced Benefits? Within Advanced Benefits, some examples of the communication triggers that are available to trigger automatically are: Pre-Enrollment Literature - Enrollment Window Opened, Final Confirmation Literature - Close Enrollment, Election Modification Literature - Determined First Time Ineligible and De-Enrolled. Does Oracle Standard Benefits or Oracle Advanced Benefits automatically send out communications? No, neither system automatically sends out communications. Within Advanced Benefits, after running a batch process, a communication row is written to the Person Communication table. Using the System Extract feature, data from this table may be extracted to a text file and then merged into the body of your communication. Do both Oracle Standard Benefits and Oracle Advanced Benefits have the ability to handle targeted mass mailings? Only Advanced Benefits has the Determine Communications Batch Process. However by using the System Extract process, Standard Benefits administrators may create extract files that will function similarly if the proper eligibility is defined.
Communications
17 of 36
18 of 36
19 of 36
20 of 36
Waive Plans
What is a Waive Plan? The 'Waive Plan' flag indicates which plan will represent your 'No Coverage' plan. Since the plan names are user defined, the system has no way of knowing which plan represents no coverage. You will need to explicitly enroll them into the 'No Coverage' plan (waive plan) if you want to track this information. You would want to track this information if you need to report on the number of participants who explicitly elected NOT to accept provided coverage. Note: This concept also applies to Options.
Waive Plans
21 of 36
What-If Modeling
The What-if Modeling feature in Oracle Advanced Benefits covers employee modeling. Does it also include employer modeling? The What-If feature covers only employee life event eligibility modeling. Future plans include the addition of employer what-if modeling, which would allow the employer to model costs associated with different program and plan designs. Is What-if Modeling included in Oracle Standard Benefits? No. What-if Modeling is only included in Oracle Advanced Benefits. Does What-if modeling change information at the database level? No. What-if modeling does not change database information. This feature examines information for a person at a specific point in time (snapshot) and allows the participant to model the effect of changes to their benefits. When you exit the form, the data is not saved.
What-If Modeling
22 of 36
Elements
How do you fill out the Element Description form when creating elements for Standard or Advanced Benefits? Primary Classification: This only tells Payroll how to tax the element once it comes over to Payroll. Thus, if the primary classification is pretax then make it pretax, if it is after-tax then make it after-tax, etc. This does not change the calculated rate within the benefits module. Benefit Classification: Leave this field blank. This was used only for basic benefits with Release 10.7 and 11. Recurring vs Non-recurring: Usually, for benefits, the element will be recurring. Make sure that the Allows Multiple Entries flag is checked to ON. Make sure that you have chosen the correct ending point, either actual or final close (normally actual termination). For imputed income, do not use the payroll seeded element because it may double calculate imputed income. Further Information: This is a required field for Oracle payroll field. It is mainly used for Tax purposes. Select the option that is most relevant (i.e. using Pre-tax 123). This field provides instruction to payroll regarding how to calculate the element. Note: Once you define your elements and attach them to your rates, if you go back and change anything to your elements you must unattached them from your rates and then reattach them. If you do not do this, you will cause problems with your rates. Note: When linking the elements, in order for costing to work correctly, you need to be consistent with whatever criteria you link with. For example, consistently linking your benefits elements to all payrolls would allow eligibility calculations to work properly. When should I use existing elements vs new elements? Without a clear understanding of existing element setup, it is impossible to know the ramifications of using existing elements. Therefore, Oracle development (Payroll and Benefits) strongly encourages creating new elements when using Standard or Advanced Benefits to capture rates (costs) associated with benefit elections. Oracle Benefits will be authoring a detailed white paper on the subject of using elements. For now, here is a brief explanation of the concepts and the pros and cons of using existing elements vs. creating new elements. Basic Benefits The old way of administering benefits, prior to r11i, has not been removed from the product. Elements and Input Values use benefit tables and FastFormula to derive an amount (Employee or Employer contributions/distributions). Element linking restricts which elements can be assigned to an individuals assignment. Once assigned to an individuals assignment, these amounts can then be processed accordingly by Oracle Payroll or a third party payroll. Standard or Advanced Benefits
File Ref: R11i Benefits Frequently Asked Questions.doc Elements 23 of 36
Users create a compensation hierarchy of Plans (HCA) or options in plans (Coyote Dental - EE only). The eligibility criteria are attached to the individual compensation objects within the hierarchy to determine participant eligibility. The coverage amounts, flex credits, premiums, imputed income, and Rates (EE/ER contrib/distribs) are also created for each compensation object. Activity Base Rates (ABRs) are created on the Standard Rate form (imputed income has its own form) for each compensation object for which we calculate costs such as EE/ER contribs/distribs. For Payroll to process, 1 Element and 1 Input Value is attached to the ABR on the Standard Rate form. We can have multiple ABRs for each comp object. Example, 1 ABR for EE contribs and 1 ABR for ER liabilities. When a person enrolls in a compensation object, the associated element(s) and input value(s), on the ABR, are assigned to the employees assignment or benefits assignment element entry. The input value will contain the amount calculated by BEN and will simply need to be added/subtracted/costed by payroll. Pros and cons for Using Existing Elements: Pros 1. 2. Cons 1. 2. 3. 4. 5. Cannot create new input values for elements that have already been linked Must disable existing benefit tables Must alter ALL existing FastFormula which uses the input value in the element Additional T&E altering old benefit tables and formulas Exposure to errors in changing benefit tables and formulas Already linked for costing No transfer of balances needed
Pros and cons for Creating New Elements: Pros 1. 2. 3. 4. Less setup needed with new elements as BEN is doing all of the calculations Can create new input values to capture calculations from BEN Open link can be used if there is NO costing No manipulation needed for benefit tables or FastFormula, the Amount input value will appear correctly on SOE New Input Values are NOT being used by existing benefit tables and FastFormula Can add a new input value to existing FastFormula if needed
5. 6. Cons 1. 2.
Costing - new elements would have to be linked accordingly (however, may have fewer elements) Balances may need to be transferred if converting mid year
Elements 24 of 36
3.
There may be additional pros and cons under each category depending on the specific conditions of your implementation. How do I setup elements for Benefits and the ADP Connection? There are 4 different types of elements you might set up when implementing the ADP interface. You wouldn't normally set up both basic and standard/advanced benefits. Basic benefits When creating basic benefit elements, create elements with a a primary element classification of "Voluntary Deductions" and a benefit classification of Medical, Dental or Vision. Set the ADP Deduction flag to Yes. Three input values will automatically be created (for coverage, EE contribution and ER contribution). When you use basic benefits, deductions relating to non-Medical/Dental/Vision benefits (for example, savings plans) should be implemented as regular ADP deductions if they are to be interfaced to ADP. Basic benefit info is interfaced using the hr_adp_benefit_v view. Standard and Advanced Benefits Standard and Advanced benefits functionality is new in 11i. The ADP interface will interface employer and employee payroll contributions for benefit plans defined using the new standard and advanced benefits functionality, providing the following conditions are adhered to: 1) Benefit contribution amounts are calculated by standard/advanced benefits and the results of the calculations are interfaced to ADP via element entries. So you must associate elements with your activity rates if you want the contribution amounts to be interfaced to ADP. Check the "Assign on Enrollment" checkbox when you create your activity rates so that the appropriate element entries are created on enrollment. The elements that you associate with activity rates do not have to be created as ADP deduction elements. You simply need to create an element with one input value. This input value will hold the rate. Create a different element for each activity rate. If you have already created your activity rate elements as ADP deduction elements, this is not a problem. Use the amount input value to hold the rate, and set the ADP Deduction flag to No. Also set the Units input value to not required. Your activity rate elements will have 3 input values instead of 1, but that will not break the interface. 2) Activity rates should have activity rate types of either "Employer Payroll Contribution" or "Employee Payroll Contribution". If you want to pass both Employee and Employee Contribution amounts to ADP you should create two activity rates. You should use a different element definition for each rate. If you use variable rate profiles, these should also have activity rate types of "Employer Payroll Contribution" or "Employee Payroll Contribution" if they map to activity rates that are used in plans whose contribution amounts are to be interfaced to ADP. If you want to interface flat dollar contribution limits, you can do so by setting up period-to-date limits against your activity rates. Please ensure you create only one period-to-date limit for each activity rate.
Elements 25 of 36
3)
4)
5)
Element definitions that are created as part of your activity rate setup should have the ADP Deduction flag set to No. If this flag is set to Yes it can adversely impact the operation of the standard/advanced benefits functionality.
Standard/advanced benefits information is interfaced using the hr_adp_oab_benefit_v view. GTL There is a GTL specific view called hr_adp_gtl_v that returns GTL info. To interface GTL info to ADP, set up an element called ADP GTL as described in the ADP interface implementation guide. Regular ADP Deductions If you want to interface any other deductions that are not returned by the previous three views, set up regular ADP deductions as described below. These regular deductions are interfaced via the hr_adp_deduction_v view. 1) 2) Set ADP Deduction flag to Yes. Each Element should have the 3 Input Values - Amount (type Money), Units ( type Look-up HR_ADP_DEDUCTION_UNITS and Limit (type Money).
How does the system utilize Deduction Schedules? The deduction schedules are currently only used for reference or exporting a name to a foreign payroll. They don't do any calculations. The process that creates element entries does look at the Frequency Rules defined for related Element Types.
Elements
26 of 36
Payroll
Do both Oracle Standard Benefits and Oracle Advanced Benefits integrate with Oracle Payroll? Yes, both products integrate with Oracle Payroll. Why must you define a default monthly payroll? A monthly payroll must be determined to be the default monthly payroll for non-active employees who elect continuing benefits such as COBRA in the US. A monthly payroll must be set up only if no other monthly payroll exists in the designated Business Group. This allows the administration and costing of assignments for non-active employees who elect continuing benefits. Please refer to Managing Total Compensation Using HRMS Release 11i for a further discussion of benefits assignments. This users guide can be downloaded from the iXchange Portal. How are element entries created for participants? Elements are automatically created in Standard and Advanced Benefits after saving the record within the enrollment forms as well as through the certain batch processes in Oracle Advanced Benefits. Must Oracle Payroll be installed if the client purchases an Oracle Advanced Benefits license? No. Does Oracle Advanced Benefits utilize any of the Oracle HR and / or Oracle Payroll tables? Yes, in addition to the newly created benefits tables, Oracle Advanced Benefits utilizes some of the Oracle Human Resource and Oracle Payroll tables (shared/core applications tables).
Payroll
27 of 36
Batch Processes
What Benefits Batch Processes are included in Oracle Standard Benefits? Three batch processes exist in Oracle Standard Benefits, they are: Extract Process - creates an extract for an extract definition you have defined. Extract Write Process - saves the output from the Extract Process to a file. Premium Calculation Process - selects appropriate participants and creates premium results. What Benefits Batch Processes are included in Oracle Advanced Benefits? Oracle Advanced Benefits contains the three batch processes that are included with Oracle Standard Benefits. In addition, Oracle Advanced Benefits includes the following seven batch processes: Participation Batch Process - determines eligibility and enrollment information for the persons and benefits plans you select. Back Out Life Events Process - this process is run when a life event has been started in error for a group of persons. Default Enrollment Process - automatically enrolls a person into a plan based on predefined criteria. Close Unresolved Action Items Process - used to close any required or optional Action Items that have not been completed by the participant. Close Enrollments - closes a persons enrollment after elections have been made and resolves any incomplete election information. Temporal Communications. Maintain Designee Eligibility. How frequently should the Oracle Advanced Benefits Participation Batch Process run? This varies based on the size of the organization. Typically, plan sponsors with large employee populations will run the process daily, whereas small employers may run the process once a pay period, prior to each payroll processing. Depending on client requirement for Life Event detection and timeliness of life event evaluation, the Participation Process may be run as often as required. I get an ORA-20001:BEN_91663_BENMNGLE_LOGGING: error when trying to run participant management batch process? This is because the Audit Log Flag is turned ON and the Audit log tables are running out of space. Proper procedure should be to keep the Audit Log flag turned OFF. Refer to the report created by the Participation process for errors and for the number of people processed in the run. Note: If you receive this error, you need to run the Participation Audit Activity Purge batch process. This will clean out your Audit log tables.
Batch Processes
28 of 36
Reports
Are standard benefits reports included in Oracle Advanced Benefits? There are no standard reports delivered in Oracle Advanced Benefits at this time. Reports may be developed using Oracle Reports, or, ad hoc reports may be developed using Oracle Discoverer. The OAB System Extract process may be run to extract data in a file that could be imported into another external report writer product. Note: Oracle Consulting has developed some custom reports for Oracle Advanced Benefits. Contact your Oracle Consulting representative for more information. Why do I see Benefits Reports in the Table of Contents of the Managing Total Compensation User Guide? This section refers to the capabilities within the product to identify reporting groups for selection within the System Extract process. What are the Summary reports? These are the activity summary reports generated by the batch processes. They display information such as number of people processed successfully, number of people processed with an error detected, total processed, etc. How do I add a Regulator Body to the system? Use the Organizations window to set up an external organization with a classification of Regulatory Body. You can then select the Regulatory Body when defining a regulation.
Reports
29 of 36
System Extract
Is the System Extract functionality available with Oracle Standard Benefits? Yes. The System Extract functionality is a part of the core HR product in Release 11i, and as part of Oracle Standard Benefits and Oracle Advanced Benefits. The System Extract functionality can be accessed from the navigator window. Is the System Extract an Application Object Library (AOL) function or does it utilize Application Data Export (ADE)? The System Extract function is a part of the core HRMS product. It is not related to the Application Object Library or Application Data Export functionality. Is the System Extract date tracked? The System Extract is not date tracked. However, when you submit a job through the Concurrent Manager you are able to enter an effective date for the extract. Does the System Extract function provide the ability to meet ANSI (American National Standards Institute) standards for benefit enrollment and maintenance (834)? Yes. The System Extract feature allows plan administrators the ability to create field definitions, file layouts and criteria to meet the U.S standard benefits interface format ANSI 834. Is the System Extract functionality available with Oracle Basic Benefits? Yes. The following list of fields do not need any benefits data (OSB or OAB data) to be extracted. Element Name Element Reporting Name Element Description Element Processing Type Element Input Currency Element Skip Rule Element Input Value Name Element Input Value Units Element Entry Value Element Entry Costing Element Entry Effective End Date Element Entry Identifier Element Primary Classification Element Output Currency Element Input Value Sequence Element Entry Reason Element Entry Effective Start Date The following list of fields require Enrollment Data to be extracted: Enrollment Entry Value - Employee Pre Tax Contribution Enrollment Entry Value - Employee After Tax Contribution Enrollment Entry Value - Employee Total Contribution Enrollment Entry Value - Employer Total Contribution Enrollment Entry Value - Employee Total Distributions Enrollment Entry Value - Employer Total Distributions Enrollment Entry Value - Total Other Rates
File Ref: R11i Benefits Frequently Asked Questions.doc System Extract 30 of 36
31 of 36
32 of 36
Which version of Datapump does Benefits use? Same as HR11i. Note: A detailed document on converting historical benefits elections to the new benefits tables (including table and column information) has been authored by development and is available on MetaLink. See the document titled: Implementation Approach, Oracle Applications HRMS: Implementing Oracle Benefits in Release 11i. Data Pump calls the APIs and knows in which order to call the APIs and which columns need data. Can you convert text notes to OAB? You cannot convert text files to OAB. When converting data, do the APIs or Data Pump do any eligibility checking? No. Using the APIs or Data Pump (which uses the APIs) only enforces the business rules built into the APIs, (i.e. cannot be enrolled in multiple medical plan types). They do not evaluate records based on the eligibility criteria profiles that you link to Programs and Plans.
33 of 36
34 of 36
Performance Considerations
Which tables are the high volume and need to be watched by the local DBAs? The tables that will have the most data are the tables where participant information is stored. The largest of these are the eligibility tables: BEN_ELIG_PER_F BEN_ELIG_PER_OPT_F The Participation process loads about 100 - 300 rows per participant into these two tables. These tables will balloon in size if you have track in-eligibility on your plan design set. The next in size are the electable choice and enrollment results tables: BEN_ELIG_PER_ELCTBL_CHC (The Participation process loads about 60 - 100 rows per participant life event into this table.) BEN_PRTT_ENRT_RSLT_F Other high volume tables would include: BEN_ENRT_BNFT BEN_ENRT_RT (The Participation process loads between 20 - 50 rows per participant life event into this table). BEN_PRTT_RT_VAL BEN_ELCTBL_CHC_POPL BEN_PER_IN_LER BEN_PTNL_LER_FOR_PER BEN_REPORTING (This is a problem if you are running a participation process with audit log on). BEN_PERSON_ACTIONS (Gets very large if you run batch processes for the population with a chunk size of 1). BEN_BATCH_RANGES (Gets very large if you run batch processes for the population with a chunk size of 1). and look at the other children of: BEN_ELIG_PER_ELCTBL_CHC BEN_PRTT_ENRT_RSLT_F
Performance Considerations
35 of 36
Batch processes are running extremely slow and forms list of values are taking a long time to load. What do I need to check? The main areas of performance problems are not analyzing the BEN tables and compensation object design. Starting with 11i we have moved from a rules based optimizer to a cost based optimizer (CBO). The CBO uses table statistics to determine the least expensive access path to retrieve the requested data. To analyze the BEN tables you will need to submit from the concurrent manager the following: FND_STATS.GATHER_SCHEMA_STATISTICS ( schemaname VARCHAR2, estimate_percent NUMBER DEFAULT 10, degree NUMBER DEFAULT NULL, internal_flag NUMBER DEFAULT NULL, request_id NUMBER DEFAULT NULL ); For the schemaname use BEN and for estimate_percent a number from 0-99. For compensation object design keep in mind the following: Program/Plan Hierarchy: Try and minimize the number of plans not in program. By putting a plan in a program you can minimize the hits to the database by including business requirements at the program level which will cascade to the lower levels. Eligibility/Electability: Set the track ineligible flag off below the program level. This prevents multiple writes for ineligible compensation objects within the same program. Eligibility has a top down hierarchy so by defining the broadest criteria at the top and refining the criteria as you drill down you can find the highest population ineligible at the highest level in the hierarchy to reduce processing for participants. Electability has a bottoms up determination. Define the most general at highest level and restrict at the lowest levels. Rates: Define rates at the highest possible common level to minimize calculation and write processing. Avoid option in plan in program (lowest level) as this has the highest processing times. Rules: Create these at the lowest level possible. A person level rule, i.e. a derived factor, will be fired off for every person processed verses a rate or coverage rule that would only be fired once for the associated compensation level.
Performance Considerations
36 of 36