Results for “pay_element_links_x”

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

Overview

PAY_ELEMENT_LINKS_X is a date-effective (or "X") view owned by the APPS schema in Oracle E-Business Suite, belonging to the Payroll (PAY) product family. Its documented description is simply "Date-effective view," and it exposes the current, active row for each element link record as of the system date. Element links define the criteria by which a payroll element is associated with a specific set of employees, assignments, or payrolls; they are the mechanism that determines eligibility for recurring and non-recurring element entries.

The view is not a stored table but a runtime filter over the underlying date-tracked (or "_F") table. Because date-effective logic is applied at query time, PAY_ELEMENT_LINKS_X returns only those rows where TRUNC(SYSDATE) falls between EFFECTIVE_START_DATE and EFFECTIVE_END_DATE. This makes it the standard reporting surface for integration and inquiry, since it hides the historical and future-dated versions that clutter the base table. In Oracle EBS 12.1.1 and 12.2.2 the object is documented as VALID, and the ETRM metadata confirms it references a single base object.

Underlying Base Objects

The ETRM metadata lists exactly one referenced object: PAY_ELEMENT_LINKS_F, accessed through a synonym. PAY_ELEMENT_LINKS_F is the multi-row, date-tracked table that stores all versions of an element link, keyed on ELEMENT_LINK_ID plus the effective date range. The view's defining query selects the full set of business and audit columns from that base table and applies the effective-date predicate.

Note that the metadata does not document the "_F" and "_X" companion pair convention explicitly, but the naming is consistent with Oracle's standard datetracking pattern: the "_F" table holds the full, unbounded history of versions; the "_X" view presents the single version in force at the current date. There is no separate "_A" or "_B" join documented here, so the view is a straight projection and filter rather than a multi-table consolidation.

Key Columns

• ELEMENT_LINK_ID – Primary identifier for the link record; joins back to the base table's version history.
• EFFECTIVE_START_DATE / EFFECTIVE_END_DATE – Bracket the effective period; the view's WHERE clause relies on these.
• ELEMENT_TYPE_ID – The payroll element being linked.
• BUSINESS_GROUP_ID – Legislative data group / business group context.
• EMPLOYMENT_CATEGORY – The column returned by the user's search; distinguishes categories such as Employee, Applicant, or Contingent Worker, and drives eligibility for the link.
• PAYROLL_ID, JOB_ID, POSITION_ID, GRADE_ID, LOCATION_ID, ORGANIZATION_ID, PEOPLE_GROUP_ID – Eligibility criteria dimensions.
• LINK_TO_ALL_PAYROLLS_FLAG, STANDARD_LINK_FLAG, MULTIPLY_VALUE_FLAG, TRANSFER_TO_GL_FLAG – Behavioral flags controlling application and costing.
• QUALIFYING_AGE, QUALIFYING_LENGTH_OF_SERVICE, QUALIFYING_UNITS – Age and service eligibility thresholds.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–20 – Descriptive flexfield storage.
• LAST_UPDATE_DATE, CREATED_BY, CREATION_DATE and related audit columns – Standard WHO audit information.

Common Use Cases and Queries

The view is typically queried to report which elements are currently linked, and under what eligibility rules, without needing to reason about effective dating. A common pattern joins it to PAY_ELEMENT_TYPES_F to resolve element names, and filters on EMPLOYMENT_CATEGORY:

• Current links by employment category – SELECT el.ELEMENT_LINK_ID, el.EMPLOYMENT_CATEGORY, el.EFFECTIVE_START_DATE, el.EFFECTIVE_END_DATE FROM APPS.PAY_ELEMENT_LINKS_X el WHERE el.EMPLOYMENT_CATEGORY IS NOT NULL;
• Links for a specific element – filter on ELEMENT_TYPE_ID and BUSINESS_GROUP_ID for a targeted eligibility report.
• Costing and GL transfer audit – filter on TRANSFER_TO_GL_FLAG and COSTABLE_TYPE to verify which links post to the general ledger.
• Qualifying rules review – examine QUALIFYING_AGE and QUALIFYING_LENGTH_OF_SERVICE to validate automatic entry eligibility.
• Integration extracts – because the view already applies the effective-date predicate, it is a safe source for downstream interfaces that must not ingest future or expired link versions.

When historical or future-dated versions are required, query PAY_ELEMENT_LINKS_F directly instead, as PAY_ELEMENT_LINKS_X will never return them.