Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
Compensation Objects
Eligibility Profile
Activity Rates
Reports
Key Concepts
It is inevitable that the business rules for compensation and benefits will
change over time. We can create new elements and disable existing ones at any
time. We can also make certain changes to existing elements and links, as
outlined below.
Element definitions, link definitions, and element entries are all date tracked.
This lets us track the changes to your compensation and benefit policies
without losing any of our historical employee information. The history of our
definitions remains in place for validation and reporting, and for future
calculations of back pay.
After we have defined and used an element, we can make the following changes:
Alter the sequence in which input values appear in the Element Entries window.
Change the input value validation rules for minimum, maximum, lookup, or
formula.
However, we cannot remove Database Items if they are used in any formulas or
Quick Paint reports.
We cannot remove existing input values or add new ones if we have created any
entries for the element. To add an input value to an element before we create any
entries, ensure that we set the effective date to the element's start date.
Link rules always control the entry of element values at the time of entry.
Changes to link rules affect existing entries in different ways, depending on the
use of standard links and hot defaults. After we have used an element we can
make the following changes to the link rules:
Change the input value defaults and validation.
These changes affect all new entries. Changes to hot defaults affect existing
entries. The system also uses the new validation rules to check any updates you
make to existing entries.
Date-effectively end all of the rules that apply to an element and define a new
set of rules, which are effective from a later date. For example, suppose we
have defined eligibility for a company car based on grade. Following a change
of policy we must now define eligibility based on job.
We will not be allowed to end the link if any nonrecurring entries exist at the
date we want to end the rule. We must delete existing entries before we end
the link.
We can end the link if recurring entries exist. Any existing entries will be
ended automatically when we end the link.
Change the qualifying conditions of age and length of service that employees
must meet to be eligible for the element.
Business Learning Center Satyam Confidential 5
Policy Development
With Date Track we can also make future-dated changes to the information
safe in the knowledge that these changes will not become effective in the
system until the correct date.
In this way we can use our compensation and benefit information to plan
changes ahead of time; analyze the impact of these changes; adjust these
changes and generally smooth out the workload that is often associated with
major changes in compensation and benefits policy.
Plan: A formally defined benefits offering that a participant can elect, such as a
medical plan.
Attributes set at the program level are inherited by each level of the
compensation object hierarchy. However, if these same attributes are set at a
lower level in the hierarchy, the compensation object inherits those attributes
set at the lowest level at or above its level. A compensation object never
inherits attributes set at a lower level in the compensation object hierarchy.
The HR/Payroll Extracts feature enables you to extract employee and payroll
data, such as the details of earnings, deductions, and information elements for
reporting purposes.
You can use the extract reports for internal reporting, such as listing all
employees in receipt of a bonus, or for transfer to third-party providers, such as
pension providers.
For example, you can send details of new hires and terminations to a provider
on a weekly basis.
You can also make copies of the seeded extracts and modify their layout or add
different data elements to suit your reporting requirements. You can view and
correct the extracted information before writing the data to a file.
The extracts support both XML and ASCII formats, you can generate postscript
reports and you can export a file to Excel for reporting.
Your plan design defines, categorizes, and helps you to manage the benefits
that you offer to your employees and other eligible participants. The plan
design is the domain of the benefits practitioner who uses the product to define
the structure and elements of the benefits offering and the rules that administer
these benefits.
At its core, the plan design determines the benefits that eligible participants
may receive. Examples of such benefits include health and welfare plans,
savings plans, and group term life insurance.
You structure your benefits offerings according to a hierarchy so that the rules
and definitions that are set at the top level (the program) cascade to the benefits
at the bottom level (the options in the program).
Central to benefits administration are the compensation objects that you use to
define, categorize, and manage the benefits that you offer to eligible
participants. The four compensation object types that you use to structure your
benefits offerings are programs, plan types, plans, and options.
Defining compensation objects is a key part of your overall plan design that
includes defining eligibility and enrollment requirements, plan year periods,
activity rates, and other elements of benefits management.
Using Oracle HRMS, you can give managers throughout your enterprise the
authority and ability to assign one-time or recurring awards, bonuses, and
allowances to qualified employees and other individuals using Oracle Self-
Service Human Resources.
Components
Compensation Managers use the Oracle HRMS professional user interface to
define components of the award or allowance. They also configure employee
self-service ICD for use by non-manager employees. The manager or the
employee uses Oracle SSHR to assign the award. Compensation Managers set
up the following:
Employees take paid or unpaid time off from work for a variety of purposes,
such as illness or injury, vacation, labor or trade union representation and
professional activities. Maintaining information on employee absences for
reporting and analysis is an important aspect of human resource management.
Medical plans
Dental plans
Vision plans
Prescription drug plans
Short term and long term disability plans
Group term life insurance
Dependent life insurance
Group legal services
Savings plans (such as 401(k) and money purchase)
Vacation Buy/Sell plans
Continuing benefits (such as COBRA and HIPAA)
You define a life event reason as any change to a person that impacts benefits
participation. The system creates a life event when it detects a change in a
person's HR record that you have defined as a life event reason.
Compensation--Use this type to set up one life event reason for each
Compensation Workbench plan
Absence--Use this type to set up three life event reasons (Absence Started,
Absence Ended, and Absence Deleted) to detect creation of, and changes to,
absence records.
Read this section for helpful hints about using the Plan Design Wizard in
conjunction with the professional user interface.
Create HR data first. Use the professional user interface to define your
common HR data, such as organizations, locations, and jobs that you may use
for eligibility determination. You also define distribution-related data, including
elements, input values, and open links. If you use Oracle Payroll, or if you
export payroll or administrative data to third parties, you should create
elements, input values and links. You will attach elements and input values to
the activity rates you define for your plans in the Wizard. You can define HR
data at anytime, then search for the data using the Wizard.
Use Plan Design Copy. You can create one plan and copy the plan as many
times as you need within a business group, or move your entire plan design
setup to a new business group or database instance. You can then use the Wizard
to group the components into your final program.
Create a Final Program. After you complete testing, use the Wizard to create a
final program. Attach the finalized plans and options to the program. Add any
program specific setup, such as eligibility profiles, activity rates, or default
enrollments that are unique to the program