Search Results pay_assignment_link_usages_f




Overview
Explore in AI Chat

Overview

PAY_ASSIGNMENT_LINK_USAGES_F is a date-tracked (suffix _F denoting "flex"/effective-dated) intersection table in the Oracle E-Business Suite Payroll (PAY) module, owned by the HR schema. As the ETRM metadata states, it represents the "intersection between PAY_ELEMENT_LINKS_F and PER_ALL_ASSIGNMENTS_F" — in other words, it records which element link definitions have actually been applied to which employee assignments. An element link determines whether a particular element (earnings, deduction, accrual, etc.) is available to a payroll and to whom it applies; this table resolves that definition into concrete, per-assignment usage.

Under a heuristic Data Vault classification derived from its foreign-key/relationship structure, this object is modeled as a standalone entity — it is not identified as a hub, link, or satellite. Operationally it behaves as a dependent intersection/child table: its rows exist only in the context of the parent element link and the parent assignment.

Key Information Stored

The table is documented with only five columns, so the full set is material. They fall into two roles:

Two unique indexes therefore exist. The primary key is surrogate-based, while the alternate unique index PAY_ASSIGNMENT_LINK_USAGES_U50 (ASSIGNMENT_ID, ELEMENT_LINK_ID, EFFECTIVE_START_DATE, EFFECTIVE_END_DATE) is the true business key: for a given assignment and element link, no overlapping effective-dated duplicates are permitted. Date-effectivity is enforced through the start/end date pair rather than a dedicated "current" flag.

Common Use Cases and Queries

Typical scenarios include determining which elements have been attached to an assignment, auditing the result of element-link eligibility processing, and reporting on element usage across a population for a given date.

  • Elements used by one assignment: SELECT element_link_id FROM pay_assignment_link_usages_f WHERE assignment_id = :p_assignment_id AND TRUNC(SYSDATE) BETWEEN effective_start_date AND effective_end_date;
  • Assignments touched by one element link: filter by element_link_id with the same effective-date predicate to produce a usage count or payroll-impact list.
  • Trend/audit reporting: because the table is date-tracked, comparing EFFECTIVE_START_DATE/EFFECTIVE_END_DATE windows supports point-in-time reconstructions of link application and de-application.
  • Reconciliation: join to PAY_ELEMENT_LINKS_F and PER_ALL_ASSIGNMENTS_F on the respective IDs to translate internal IDs into element, link, and person/assignment descriptors for BI Publisher or ad hoc reports.

All queries should honor the effective dates, since historical versions of a usage row remain in the table.

Related Objects