1. Implementing Payroll for Bahrain
  2. Overview of Values Defined by Criteria

Overview of Values Defined by Criteria

Each value defined by criteria requires you to specify one or more evaluation conditions that determine a particular value or rate.

In cases where you specify many conditions, each condition is defined as a separate level and placed in priority order to produce a tree structure.

You control the criteria that you enter and the resulting tree structure. In each branch of the tree, you can have multiple evaluation conditions. If the conditions that you've set don't meet your requirements, the payroll process uses the value established for the default criteria that you set up. Each criterion and value, as well as the parent criteria definition, is stored as a calculation value definition. You can define a rate definition to retrieve a rate based on values defined by criteria.

You can also search for criteria and value records, on a value defined by criteria, to quickly select a record you want to view or update. For more information, see Search for Values Defined by Criteria.

Criteria and Evaluation Conditions

Within the tree structure, you create the criteria rules. For example, you can define criteria rules based on the location of an employee. You can select or enter the specific location for each criterion, such as London, from a value set or on the criteria page.

You can also define a default criterion if an employee doesn't meet any other condition. Defining a default also includes a situation in which the application hasn't captured criteria information on the employee record, such as location. If you know the criteria definitions you set up cover all the conditions for all employees, then you don't need a default criterion.

Each criterion is stored as a calculation value definition. You must enter a name for the calculation value definition that's unique within a legislative data group. With a unique name, you can identify the record while you create the values defined by criteria hierarchy through HCM Data Loader.

You must also select a value definition group for each criterion. The group enables you to manage the value definitions within your legislative data group; it doesn't impact the behavior of the criterion. Use the Retrieval Date to determine whether the criterion uses the date earned or effective date to retrieve information. The default value is the effective date.

Once you have created a criterion, you can enter these condition details:

  • Sequence: Define the priority of each criterion using the sequence. The application uses the sequence order to produce a tree structure, which affects processing and the value that's returned. For example, the first criteria definition has a condition of age greater than 0 years, and the next criteria definition in the sequence has the condition of age greater than 55 years. In this scenario, all employees would meet the first condition and there would be no results for the second condition. To fix this situation, you would reverse the order of the criteria definitions where the condition greater than 55 years is first in the sequence.

  • Database Item Name: Select a database item to identify the type of criteria. For example, if your criterion is the location of an employee you could select PER_ASG_LOCATION_NAME.

    Note:

    If you're defining values by criteria for Salary Rates, select one of the database items that are supported by HR flows such as new hire and promotion.

  • Display Name: You have the option to enter a name for the criteria. This name doesn't need to be unique and is displayed in the value by criteria hierarchy record. If you don't enter a display name, the database item description or name gets displayed.

  • Operand: You use operands when you're creating criteria. You can specify whether the value defined by the database item should be equal to, greater than, less than, greater than or equal to, or less than or equal to the literal value. To capture multiple values for the same criteria, use the In operand. For example, if you want to give employees that work in City 1 and City 2 the same bonus, you can create a single evaluation condition for both cities using the In operand.

  • Value Sets: Specify a value set to provide a dynamic list of values from which you can select an entry. This option is available for input values that provide text only.

  • Literal Value: If you specify a value set, you can select an entry from a list of values you have chosen. If you leave the Value Set field blank, you can enter any information that's appropriate for the value definition that you're creating.

Values

Create one or more value records for each criterion. Here you enter the calculation types and rates. For example, you can enter the bonus values for each location.

Each value record gets stored as a calculation value definition. You must enter a name for the calculation value definition that's unique within a legislative data group. With a unique name, you can identify the record while you create the values defined by criteria hierarchy through HCM Data Loader.

You must enter a value identifier when you define multiple value records for a criterion. This identifier enables you to define which value record should be calculated. For example, your company calculates car allowance and housing allowance rates for an employee based on their job. The job criteria details and the allowance values are captured in a Values Defined by Criteria. You can indicate which of the values captured on the Values Defined by Criteria should be calculated when processing an element in the payroll run.

If you don't enter a value identifier, the name of the calculation value definition gets displayed for the value on the hierarchy. You must select a value definition group for each value record. The group enables you to manage the value definitions within your legislative data group; it doesn't impact the behavior of the value. Use the Retrieval Date to determine whether the date earned or effective date retrieves the information of the value. The default is the effective date.

If you select a Default Calculation Type while creating the values defined by criteria, it gets displayed on each value record. Alternatively, you can enter a calculation type. You have the option to select a different calculation type for each value within the values defined by criteria depending on your business requirements.

The supported calculation types include:

  • Flat Amount Times Multiplier

  • Flat Calculation

  • Flat Rate

  • Grade Rate

  • Incremental Rate

  • Number

  • Rate Definition

  • Standard Formula 1

  • Standard Formula 2

Database Items for Values Defined by Criteria

Each condition refers to a database item to identify where the value is used. It also determines the data type of the value, such as text, number, or date. Define conditions using predefined database items or the dynamically created database items when the application creates data, such as balances and elements.

You can refer to any static or dynamic database items that support these contexts:

  • HR_ASSIGNMENT_ID

  • HR_TERM_ID

  • PAYROLL_ASSIGNMENT_ID

  • PAYROLL_TERM_ID

  • PAYROLL_RELATIONSHIP_ID

  • PERSON_ID

  • CALC_BREAKDOWN_ID

  • PAYROLL_ID

  • EFFECTIVE_DATE

  • DATE_EARNED

  • LEGISLATIVE_DATA_GROUP_ID

Database Items for Salary Rates

Perform rate calculations before information such as job and grade is submitted for the employee. While using salary rates, you can only define values by criteria that use the database items supported by HR flows such as new hire and promotion. If you refer to other types of database items, the process either returns zero or uses the default criteria.

Here's the list of database items to define values by criteria while using salary rates:

Database Item Name

Display Name

PER_ASG_ASSIGNMENT_NUMBER

Assignment Number

PER_ASG_ASSIGNMENT_ID

Assignment ID

PER_ASG_EFFECTIVE_START_DATE

Assignment Start Date

PER_PERSON_ENTERPRISE_HIRE_DATE

Hire Date

PER_ASG_JOB_ID

PER_ASG_JOB_NAME

Job

PER_ASG_JOB_CODE

Job Code

PER_JOB_FAMILY_ID

PER_JOB_FAMILY_NAME

Job Family

PER_ASG_BUSINESS_UNIT_ID

PER_ASG_BUSINESS_UNIT_NAME

Business Unit

PER_ASG_LOCATION_ID

PER_ASG_LOCATION_NAME

Location

PER_ASG_DEPARTMENT_ID

PER_ASG_ORG_DEPARTMENT_NAME

Department

PER_ASG_LEGAL_ENTITY_ID

Legal Entity

PER_ASG_ORG_LEGAL_EMPLOYER_NAME

Legal Employer

PER_ASG_NORMAL_HOURS

Normal Hours

PER_ASG_EMPLOYEE_CATEGORY

PER_ASG_EMPLOYMENT_CATEGORY

Assignment Category

PER_ASG_ORG_LEGAL_EMPLOYER_NAME

Legal Employer

PER_ASG_DF

Assignment Flexfield

PER_GRADES_DF

Grade Flexfield

PER_LOCATIONS_DF

Location Flexfield

PER_ASG_GRADE_CODE

Grade Code

PER_ASG_GRADE_ID

PER_ASG_GRADE_NAME

Grade

PER_ASG_GRADE_LADDER_PGM_ID

Grade Ladder

PER_ASG_GRADE_STEP_ID

PER_GRADE_STEP_NAME

Grade Step

PER_ASG_ESTABLISHMENT_ID

Establishment

PER_ASG_UNION_ID

Worker Union ID

PER_ASG_UNION_NAME

Worker Union Name

PER_ASG_JOB_MANAGER_LEVEL

Job Manager Level

PER_ASG_JOB_MANAGER_LEVEL_NAME

Job Manager Level Name

CMP_ASSIGNMENT_SALARY_BASIS_NAME

Salary Basis

PER_ASG_COLLECTIVE_AGREEMENT_ID

Collective Agreement

PER_ASG_BARGAINING_UNIT_CODE_NAME

Bargaining Unit Name

PER_ASG_BARGAINING_UNIT_CODE

Bargaining Unit Code

PER_ASG_ACTION_CODE

Action Code

PER_ASG_ACTION_REASON_CODE

Action Reason

Related Topics