Search Results pay_formulas_f

Overview

PAY_ELEMENT_TYPES_F is the DateTracked table owned by the HR schema that stores the definitions of all elements in Oracle HRMS. Elements are the atomic building blocks used to construct every earning, deduction, benefit, and non-payment informational item that can be attached to an employee assignment. Each row represents one element definition valid for a defined date range, which is why the table is DateTracked and why its primary key incorporates effective dates. Localization teams define primary classifications that determine how each element is processed by payroll for a given legislation, such as Pre-Tax Deduction or Tax Deduction.

The table also hosts non-payment element types, for example records describing assets or equipment issued to employees. Because of this breadth, PAY_ELEMENT_TYPES_F is a foundational configuration object referenced by payroll processing, benefits, and legislative localization logic throughout Oracle EBS 12.1.1 and 12.2.2. The Developer Descriptive Flexfield columns (the ATTRIBUTE columns) are reserved for localization and verticalization teams and must not be populated by end users.

From a modeling perspective, the metadata supports a heuristic Data Vault classification of this object as a satellite. It carries descriptive, time-variant attributes (element name, classification, formula references, processing flags) that describe a business key rather than acting as a pure hub or a relationship link.

Key Information Stored

The surrogate primary key is ELEMENT_TYPE_ID, combined with EFFECTIVE_START_DATE and EFFECTIVE_END_DATE to form the DateTracked unique index PAY_ELEMENT_TYPES_F_PK. Two business-key candidates are documented through unique indexes: ELEMENT_NAME, BUSINESS_GROUP_ID, LEGISLATION_CODE, and the effective dates (PAY_ELEMENT_TYPES_F_UK2), which ensures an element name is unique within a business group and legislation for a given date range. The most significant columns include:

• ELEMENT_TYPE_ID — system-generated surrogate primary key uniquely identifying each element definition.
• BUSINESS_GROUP_ID — foreign key to HR_ORGANIZATION_UNITS, scoping the element to a business group.
• LEGISLATION_CODE — foreign key to FND_TERRITORIES, identifying the legislative context.
• ELEMENT_NAME / REPORTING_NAME / DESCRIPTION — the element's display and statutory reporting identifiers.
• CLASSIFICATION_ID — FK to PAY_ELEMENT_CLASSIFICATIONS, controlling payroll treatment.
• BENEFIT_CLASSIFICATION_ID — FK to BEN_BENEFIT_CLASSIFICATIONS for benefit-related elements.
• FORMULA_ID / ITERATIVE_FORMULA_ID / PRORATION_FORMULA_ID — references to payroll formulas that compute element values.
• PROCESSING_TYPE / PROCESSING_PRIORITY / PROCESS_IN_RUN_FLAG — govern how and when the element is processed.
• MULTIPLE_ENTRIES_ALLOWED_FLAG / ADJUSTMENT_ONLY_FLAG / CLOSED_FOR_ENTRY_FLAG — entry control flags.
• PRORATION_GROUP_ID / RECALC_EVENT_GROUP_ID / TIME_DEFINITION_ID — FKs to event groups and time definitions.
• EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — DateTrack validity boundaries.
• ZD_EDITION_NAME — supports the edition-based redefinition model introduced in 12.2.

Common Use Cases and Queries

Payroll administrators and developers query this table to inventory element definitions, verify formula attachments, and audit which elements are active for a legislation on a given date. A typical lookup joins the classification table to report elements by category:

• Enumerate active elements for a business group: SELECT element_name, legislation_code FROM pay_element_types_f WHERE business_group_id = :p_bg AND TRUNC(SYSDATE) BETWEEN effective_start_date AND effective_end_date;
• Trace formula usage: join FORMULA_ID to FF_FORMULAS_F to identify all elements driven by a specific formula, which is directly relevant to users searching for pay_formulas_f.
• DateTrack history reporting: querying without an effective-date filter exposes all historical versions, useful for change auditing.
• Benefits reporting: joining BENEFIT_CLASSIFICATION_ID to benefits setup to list benefit-linked elements.

Because of the 98 columns and the presence of descriptive flexfields, query projections should always name columns explicitly rather than using SELECT *.

Related Objects

The following objects are the most significant dependencies, joined on documented FK columns:

• PAY_ELEMENT_CLASSIFICATIONS — joined via CLASSIFICATION_ID, defines primary payroll classification.
• BEN_BENEFIT_CLASSIFICATIONS — joined via BENEFIT_CLASSIFICATION_ID.
• PAY_EVENT_GROUPS — joined via PRORATION_GROUP_ID (and RECALC_EVENT_GROUP_ID).
• PAY_TIME_DEFINITIONS — joined via TIME_DEFINITION_ID.
• FF_FORMULAS_F — joined via FORMULA_ID, ITERATIVE_FORMULA_ID, and PRORATION_FORMULA_ID.
• HR_ORGANIZATION_UNITS — joined via BUSINESS_GROUP_ID.
• FND_TERRITORIES — joined via LEGISLATION_CODE.
• PAY_ELEMENT_LINKS_F and PAY_ELEMENT_ENTRIES — downstream objects that reference element definitions at runtime.