Results for “pay_assignment_link_usages_x”
18 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
The view PAY_ASSIGNMENT_LINK_USAGES_X is a date-effective (or "X" suffix) view owned by the APPS schema within the PAY — Payroll product of Oracle E-Business Suite. It is documented as VALID in both the 12.1.1 and 12.2.2 releases and serves as a reporting and integration layer over the underlying date-effective date-tracked table. In Oracle EBS conventions, a view whose name ends in _X is a "translated" date-effective view that returns only the currently active row for each logical record, filtering records based on the effective date range relative to the current system date (SYSDATE). This allows reports, concurrent programs, and external integrations to query assignment-to-element-link relationships without having to manually construct effective date range predicates.
The object is relevant to payroll administrators, HRMS technical consultants, and developers who need to determine, for a given assignment, which element links (the eligibility rules connecting assignments to payroll elements) are in effect. The view exposes the association between an assignment and an element link, a relationship that governs how elements such as earnings, deductions, and contributions are attached to a specific assignment in a payroll run.
Underlying Base Objects
The view is defined over a single documented base object: PAY_ASSIGNMENT_LINK_USAGES_F, which is referenced in the ETRM metadata as a SYNONYM in the APPS schema. The _F suffix denotes the full, un-translated date-effective table that stores all historical and future-dated rows for each assignment link usage record. Each row is bounded by an effective start date and an effective end date.
The view definition applies the following predicate against that base object:
TRUNC(SYSDATE) BETWEEN EFFECTIVE_START_DATE AND EFFECTIVE_END_DATE
This filter restricts the result set to the single date-effective row that is valid on the current date for each ASSIGNMENT_LINK_USAGE_ID. Because the view selects directly from the base table without joins, aggregation, or additional staging objects, it is a thin, performance-friendly translation layer. Consumers benefit from the effective-date logic being encapsulated, but they inherit the storage characteristics and indexing of the underlying table.
Key Columns
ASSIGNMENT_LINK_USAGE_ID— The primary identifier of the assignment link usage record. This is the unique key that links back to the base table and identifies the specific assignment-to-link relationship.EFFECTIVE_START_DATE— The date from which the record becomes effective. Used in the date-effective filter to determine currency.EFFECTIVE_END_DATE— The date until which the record remains effective. Combined with the start date, it defines the valid period.ELEMENT_LINK_ID— The identifier of the element link that is applied to the assignment. This is the column most frequently referenced in user searches ("element_link_id") and is central to resolving element eligibility. It joins to the element link definition, which in turn points to the element being assigned.ASSIGNMENT_ID— The identifier of the assignment (employee or applicant assignment) to which the element link usage applies.
Together, ELEMENT_LINK_ID and ASSIGNMENT_ID allow the view to answer the core question: "Which element links are currently active for this assignment?"
Common Use Cases and Queries
A primary use case is determining which element links are actively associated with a given assignment as of today. The following query retrieves current link usages for a specific assignment:
SELECT assignment_link_usage_id, element_link_id, assignment_id, effective_start_date, effective_end_date FROM apps.pay_assignment_link_usages_x WHERE assignment_id = :p_assignment_id;
Another scenario involves auditing element link assignment histories for reporting or data validation. Because the view is date-filtered, historical analysis requires querying the base table directly:
SELECT * FROM apps.pay_assignment_link_usages_f WHERE assignment_id = :p_assignment_id ORDER BY effective_start_date DESC;
A third common pattern is joining the view to element link and element definitions to produce human-readable reports of active elements per assignment:
SELECT x.assignment_id, x.element_link_id, el.element_link_name FROM apps.pay_assignment_link_usages_x x, apps.pay_element_links_f el WHERE x.element_link_id = el.element_link_id;
Because the view returns only current effective rows, it is well-suited for operational dashboards and integration extracts that must reflect the live state. For as-of-date or retrospective reporting, developers should query PAY_ASSIGNMENT_LINK_USAGES_F directly, as the _X view does not accept a date parameter and is anchored to TRUNC(SYSDATE).
-
Date-effective view.
APPS.PAY_ASSIGNMENT_LINK_USAGES_X·↳ PAY_ASSIGNMENT_LINK_USAGES_F·Explore PAY module →
-
Date-effective view.
APPS.PAY_ASSIGNMENT_LINK_USAGES_X·↳ PAY_ASSIGNMENT_LINK_USAGES_F·Explore PAY module →
-
12.1.1 DBA Data 12.1.1
-
12.2.2 FND Design Data 12.2.2
-
12.2.2 DBA Data 12.2.2
-
12.1.1 FND Design Data 12.1.1
-
12.1.1 DBA Data 12.1.1
-
12.2.2 DBA Data 12.2.2
-
12.1.1 DBA Data 12.1.1
-
eTRM - PAY Tables and Views 12.1.1
Temporary table used to hold invalid location addresses.
-
eTRM - PAY Tables and Views 12.2.2
Temporary table used to hold invalid location addresses.
-
eTRM - PAY Tables and Views 12.1.1
Temporary table used to hold invalid location addresses.
-
eTRM - PAY Tables and Views 12.2.2
Temporary table used to hold invalid location addresses.