Results for “pay_element_links_d”
30 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
PAY_ELEMENT_LINKS_D is an APPS-owned view in the Oracle E-Business Suite Payroll (PAY) module, retaining a VALID status across both 12.1.1 and 12.2.2 releases. The name suffix "_D" follows the Oracle EBS convention for the DateTrack history (or "date-tracked") presentation of a base entity, in this case the element link records held in PAY_ELEMENT_LINKS_F. The view's stated purpose in the ETRM metadata is simply "Used by DateTrack History" — it exposes a flattened, human-readable projection of element link definitions together with their effective date ranges, allowing users and concurrent programs to examine how a link was configured at any point in time.
Element links determine which element entries an assignment is eligible for, and carry critical payroll accounting attributes such as the costable type and the flag controlling whether the element's costing results are transferred to the General Ledger. Because the view decodes these internal codes into descriptive meanings, it is heavily used in reporting, reconciliation, and data-extraction routines rather than in transactional processing.
Underlying Base Objects
The documented base objects for this view are FND_USER (synonym), HR_API (package), HR_LOOKUPS (view), PAY_ELEMENT_LINKS_F (synonym), PAY_ELEMENT_SETS (synonym), and PAY_ELEMENT_TYPES_F (synonym). The view text joins PAY_ELEMENT_LINKS_F (aliased ELEMENT) as the driving table to PAY_ELEMENT_TYPES_F (ELETYPE) on ELEMENT_TYPE_ID, constrained so that the link's effective start date falls within the element type's own effective range. PAY_ELEMENT_SETS (ELESET) is outer-joined on ELEMENT_SET_ID, permitting links that are not restricted to a set.
Five outer joins to HR_LOOKUPS decode internal lookup codes into meanings: QUALIFYING_UNITS, two YES_NO lookups for MULTIPLY_VALUE_FLAG and STANDARD_LINK_FLAG, the TRANSFER_TO_GL_FLAG lookup (also YES_NO), and COSTABLE_TYPE. An outer join to FND_USER resolves LAST_UPDATED_BY to a user name. The date-effectiveness mechanics themselves are supplied by the HR_API package, which underlies the DateTrack framework supporting the "_F" (current/dated) and "_D" (display/history) object pairing.
Key Columns
- ELEMENT_LINK_ID — Primary identifier of the element link record.
- EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — The DateTrack validity window for the link.
- TRANSFER_TO_GL — Decoded YES/NO meaning indicating whether costing for elements associated with the link is transferred to the General Ledger. This is the column targeted by searches for "transfer_to_gl".
- COSTABLE_TYPE — Decoded meaning of the costable classification for the link.
- DISTRIBUTION_SET — The element set name (ELEMENT_SET_NAME) used for eligibility, if any.
- MULTIPLY_VALUE / STANDARD — Decoded YES/NO meanings for the multiply-value and standard-link flags.
- AGE / LENGTH_OF_SERVICE — Qualifying age and qualifying length of service thresholds.
- UNITS — Decoded qualifying units meaning.
- LAST_UPDATE_DATE, LAST_UPDATED_BY — Audit columns, with the user identifier resolved to FND_USER.USER_NAME.
Common Use Cases and Queries
Typical scenarios include auditing which links post to the GL, reconciling element link configuration against costing setup, and extracting dated link definitions for migration or SOX reporting. The view is preferred over PAY_ELEMENT_LINKS_F when descriptive meanings are required without additional lookup joins.
SELECT element_link_id,
effective_start_date,
effective_end_date,
transfer_to_gl,
costable_type,
distribution_set
FROM apps.pay_element_links_d
WHERE transfer_to_gl = 'Y'
AND SYSDATE BETWEEN effective_start_date AND effective_end_date;
A second common pattern retrieves the full change history for a single link:
SELECT element_link_id,
effective_start_date,
effective_end_date,
standard,
last_update_date,
last_updated_by
FROM apps.pay_element_links_d
WHERE element_link_id = :p_link_id
ORDER BY effective_start_date;
Because the view decodes flags via HR_LOOKUPS, results reflect standard Oracle meanings and should be validated against any customer-specific lookup extensions before being relied upon for automated processing.
-
View: PAY_ELEMENT_LINKS_D 12.2.2
Used by DateTrack History
APPS.PAY_ELEMENT_LINKS_D·↳ FND_USER·↳ HR_API·↳ HR_LOOKUPS·Explore PAY module →
-
View: PAY_ELEMENT_LINKS_D 12.1.1
Used by DateTrack History
APPS.PAY_ELEMENT_LINKS_D·↳ FND_GLOBAL·↳ FND_USER·↳ HR_API·Explore PAY module →
-
12.2.2 FND Design Data 12.2.2
-
12.1.1 DBA Data 12.1.1
-
12.1.1 FND Design Data 12.1.1
-
12.2.2 DBA Data 12.2.2
-
12.1.1 DBA Data 12.1.1
-
VIEW: APPS.HR_LOOKUPS 12.1.1
-
VIEW: APPS.HR_LOOKUPS 12.2.2
-
SYNONYM: APPS.FND_USER 12.2.2
-
SYNONYM: APPS.FND_USER 12.1.1
-
12.2.2 DBA Data 12.2.2
-
eTRM - PAY Tables and Views 12.1.1
Temporary table used to hold invalid location addresses.
-
12.1.1 DBA Data 12.1.1
-
eTRM - PAY Tables and Views 12.2.2
Temporary table used to hold invalid location addresses.
-
eTRM - PER Tables and Views 12.2.2
Table to store NQF Training info for a person
-
eTRM - PER Tables and Views 12.1.1
Table to store NQF Training info for a person
-
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 - PER Tables and Views 12.2.2
Table to store NQF Training info for a person
-
eTRM - PER Tables and Views 12.1.1
Table to store NQF Training info for a person