Search Results hr_s_element_types_f




Overview
Explore in AI Chat

Overview

HR_S_ELEMENT_TYPES_F is the core definition table for the Oracle Payroll and Oracle Human Resources element architecture. In Oracle E-Business Suite 12.1.1 and 12.2.2, an "element type" represents a reusable definition — such as a salary component, deduction, benefit accrual, or employer contribution — that a payroll run processes to produce entries in the payroll run results. The table is owned by the HR schema under the PER (Human Resources) product module and is documented as a "Retrofitted" object in the ETRM repository, reflecting EBS 12.2 user-interface modernization. The trailing "_F" in the name designates this table as the "date-tracked" or "frozen" version of the element type, meaning that rows are versioned by EFFECTIVE_START_DATE and EFFECTIVE_END_DATE so that historical payroll definitions can be reconstructed. The supplied ETRM metadata classifies this table heuristically as standalone in the Data Vault model. Following that suggestion, this table behaves as a hub-like reference entity that anchors the surrogate identifier ELEMENT_TYPE_ID without being dependent on a parent link structure, though in practice it also carries descriptive satellite attributes such as classification, processing rules, and legislative qualifiers.

Key Information Stored

The documented physical schema in ETRM 12.2.2 lists 96 columns. The surrogate primary key is ELEMENT_TYPE_ID, uniquely identifying each element definition. Effective-dated business versioning is driven by EFFECTIVE_START_DATE and EFFECTIVE_END_DATE. The business-group scope is captured by BUSINESS_GROUP_ID, while LEGISLATION_CODE identifies the legal jurisdiction (for example US or GB) the element is valid for. Element classification and behavior are governed by CLASSIFICATION_ID, PROCESSING_TYPE, PROCESSING_PRIORITY, PROCESS_IN_RUN_FLAG, and the flags ADDITIONAL_ENTRY_ALLOWED_FLAG, ADJUSTMENT_ONLY_FLAG, MULTIPLE_ENTRIES_ALLOWED_FLAG, INDIRECT_ONLY_FLAG, and MULTIPLY_VALUE_FLAG. Formula logic is attached through FORMULA_ID and the iterative-processing pair ITERATIVE_FLAG and ITERATIVE_FORMULA_ID, with ITERATIVE_PRIORITY controlling execution ordering. Monetary and name attributes include INPUT_CURRENCY_CODE, OUTPUT_CURRENCY_CODE, ELEMENT_NAME, and REPORTING_NAME. Qualifying criteria are stored in QUALIFYING_AGE, QUALIFYING_LENGTH_OF_SERVICE, and QUALIFYING_UNITS. The long descriptive and conformed-attribute tail is handled by DESCRIPTION, the 20-column ELEMENT_INFORMATION_CATEGORY/1-20 flexfield, the 20-column ATTRIBUTE1-20 flexfield, and the 20-column ELEMENT_INFORMATION1-20 group. Two foreign keys are documented: BENEFIT_CLASSIFICATION_ID references BEN_BENEFIT_CLASSIFICATIONS, and TIME_DEFINITION_ID references PAY_TIME_DEFINITIONS.

Common Use Cases and Queries

Typical uses include payroll configuration reporting, element eligibility auditing, and change-impact analysis before a legislative patch. A frequently run query resolves the current valid definition of an element within a business group:

  • Current element listing: SELECT element_type_id, element_name, reporting_name, classification_id, processing_type FROM hr.hr_s_element_types_f WHERE business_group_id = :p_bg AND legislation_code = :p_leg AND SYSDATE BETWEEN effective_start_date AND effective_end_date;
  • Classification and formula lookup: join FORMULA_ID to FF_FORMULAS_F to inspect the calculation attached to each element.
  • Date-track history: query without the SYSDATE predicate to trace how a reporting name or processing priority changed across periods.
  • Benefit-linked elements: join BENEFIT_CLASSIFICATION_ID to BEN_BENEFIT_CLASSIFICATIONS to reconcile benefits elements.
  • Time-overlap validation: group by element_type_id and detect overlapping effective-date ranges, a common data-quality check before payroll close.

Related Objects

The most significant related objects, grounded in the documented foreign keys and the standard element architecture, include:

  • BEN_BENEFIT_CLASSIFICATIONS — joined via HR_S_ELEMENT_TYPES_F.BENEFIT_CLASSIFICATION_ID.
  • PAY_TIME_DEFINITIONS — joined via HR_S_ELEMENT_TYPES_F.TIME_DEFINITION_ID.
  • PAY_ELEMENT_TYPES_F / FND lookup values — the CLASSIFICATION_ID and PROCESSING_TYPE decode sources.
  • PAY_ELEMENT_CLASSIFICATIONS — resolves CLASSIFICATION_ID to a classification name.
  • FF_FORMULAS_F — attached through FORMULA_ID and ITERATIVE_FORMULA_ID.
  • PAY_ELEMENT_LINKS_F — links element types to input values and pay run structures.
  • PAY_ELEMENT_ENTRIES / PAY_RUN_RESULTS — the transactional results produced when an element is processed.
  • PAY_ELEMENT_TYPE_USAGES / eligibility tables — governing who may receive the element.
  • FND_LOOKUP_VALUES — supplies legislation and flag decodes used throughout element definitions.