Results for “pay_element_links_f”

50+ results




AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

PAY_ELEMENT_LINKS_F is the datable (date-effective) eligibility rule table in the Oracle EBS Payroll (PAY) module, owned by the HR schema. Its documented purpose is to store eligibility rules for an element type: each row defines the criteria under which a specific payroll element (for example, a salary element, an earnings type, or a deduction) may be linked to an assignment, applicant, or other payroll entity. In EBS 12.1.1 and 12.2.2 this table is created and maintained by the element link definition forms, and it is a central configuration object for payroll processing because an element cannot be processed for a person unless an eligibility link matches that person.

Under the heuristic Data Vault classification mined from its foreign key structure, PAY_ELEMENT_LINKS_F is best modelled as a link table. It associates one or more dimension entities (element type, organization, location, grade, job, position, people group, payroll, element set, and pay basis) with the element link itself, while the date-effective attributes, flags, and qualifying-rule columns behave as satellite-style descriptive data. The physical table in 12.2.2 contains 53 columns.

Key Information Stored

The surrogate primary key is ELEMENT_LINK_ID, and the documented unique index PAY_ELEMENT_LINKS_F_PK combines ELEMENT_LINK_ID with EFFECTIVE_START_DATE and EFFECTIVE_END_DATE. This composite business key is what makes the row date-effective: a given element link can exist in multiple versions over time, and only one version may be active on any given date. ELEMENT_TYPE_ID identifies the element whose eligibility is being defined.

Eligibility is expressed through a set of optional criteria columns, each referencing a reference entity: PAYROLL_ID, ORGANIZATION_ID, LOCATION_ID, GRADE_ID, JOB_ID, POSITION_ID, PEOPLE_GROUP_ID, PAY_BASIS_ID, and ELEMENT_SET_ID. Where these are populated, they constrain who the link applies to. BUSINESS_GROUP_ID anchors the row to a specific business group, which is essential in multi-organization installations. COST_ALLOCATION_KEYFLEX_ID and BALANCING_KEYFLEX_ID point to costing and balancing key flexfield definitions.

Behavioural control columns include LINK_TO_ALL_PAYROLLS_FLAG, MULTIPLY_VALUE_FLAG, STANDARD_LINK_FLAG, TRANSFER_TO_GL_FLAG, and COSTABLE_TYPE, which govern how the link is applied and how resulting costs flow. The qualifying columns QUALIFYING_AGE, QUALIFYING_LENGTH_OF_SERVICE, and QUALIFYING_UNITS support length-of-service and age-based entitlement rules. EMPLOYMENT_CATEGORY further filters the eligible population. Standard EBS audit columns (LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATED_BY, CREATION_DATE, OBJECT_VERSION_NUMBER) and the ATTRIBUTE_CATEGORY plus ATTRIBUTE1 through ATTRIBUTE20 descriptive flexfield columns complete the row.

Common Use Cases and Queries

Typical scenarios include identifying which elements are eligible for a given organization, grade, or people group; auditing links that are currently effective; and extracting element eligibility for payroll reconciliation or data migration. Because the table is date-effective, queries must respect the effective date range.

  • Active links for an element type as of a date: SELECT element_link_id, element_type_id, effective_start_date, effective_end_date FROM pay_element_links_f WHERE element_type_id = :p_element_type_id AND TRUNC(:p_date) BETWEEN effective_start_date AND effective_end_date;
  • Elements linked to a specific organization: filter on ORGANIZATION_ID and the current effective window, then join to the element name via the element type.
  • Costing and GL transfer audit: SELECT element_link_id, cost_allocation_keyflex_id, balancing_keyflex_id, transfer_to_gl_flag FROM pay_element_links_f WHERE business_group_id = :p_bg_id;
  • Eligibility by grade or job for a compensation review: filter on GRADE_ID or JOB_ID within the effective period to determine who qualifies for a given element.

Reporting extracts frequently need the element link combined with its element type and the payroll or organization name, and are best driven from the effective dates to avoid returning historical versions.

Related Objects

The foreign keys documented in the ETRM metadata identify the principal related tables. PAY_ELEMENT_LINKS_F.ELEMENT_TYPE_ID references the element type definition (PAY_ELEMENT_TYPES_F) and is the primary link to the element. HR_ALL_ORGANIZATION_UNITS is referenced twice, by BUSINESS_GROUP_ID and ORGANIZATION_ID. PAY_ELEMENT_SETS is joined via ELEMENT_SET_ID, and PAY_PEOPLE_GROUPS via PEOPLE_GROUP_ID. HR_LOCATIONS_ALL is joined via LOCATION_ID, PER_GRADES via GRADE_ID, PER_JOBS via JOB_ID, and PER_ALL_POSITIONS via POSITION_ID. PER_PAY_BASES is joined via PAY_BASIS_ID. PAY_COST_ALLOCATION_KEYFLEX is referenced twice, by COST_ALLOCATION_KEYFLEX_ID and BALANCING_KEYFLEX_ID, and supplies the costing and balancing flexfield structures used to distribute the element's cost.

Together these relationships make PAY_ELEMENT_LINKS_F the eligibility bridge between element definitions and the organizational and people structures of Oracle HRMS, and any reporting or integration involving element eligibility must join through these documented foreign key columns.