Results for “pay_batch_element_links”

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

Overview

The PAY_BATCH_ELEMENT_LINKS table, owned by the HR schema and part of the PAY (Payroll) product module in Oracle EBS 12.1.1 and 12.2.2, is a batch staging table that captures the definition of element links prior to their upload or validation into the core element link structures. Element links determine which employees are eligible to receive a given element and under what conditions. Because payroll processing frequently requires the bulk creation, adjustment, or transfer of element eligibility criteria across large populations, PAY_BATCH_ELEMENT_LINKS provides an intermediate holding area where these definitions are assembled, staged, and subsequently processed by concurrent programs. The table is documented as VALID in the ETRM data model and contains 53 columns.

From a heuristic Data Vault modeling perspective, this table is classified as standalone, meaning it exhibits no dependent-child foreign key structure that would naturally map it to a satellite or subordinate link. It is best treated as a transactional or staging source that feeds the core PAY_ELEMENT_LINKS construct rather than as a durable analytical hub.

Key Information Stored

The primary key of the table is a surrogate identifier, BATCH_ELEMENT_LINK_ID, enforced by the PAY_BATCH_ELEMENT_LINKS_PK unique index. This is the only documented business-key candidate unique index, and it distinguishes each staged link row.

The most operationally significant columns include:

• ELEMENT_LINK_ID — the identifier of the corresponding core element link record; the typical join key back to PAY_ELEMENT_LINKS.
• ELEMENT_TYPE_ID and ELEMENT_SET_ID — identify the element and element set whose eligibility is being staged.
• EFFECTIVE_DATE — the date from which this staged link is intended to apply.
• PAYROLL_ID — restricts eligibility to a specific payroll.
• PEOPLE_GROUP_ID — the population group to which the link applies.
• JOB_ID, POSITION_ID, GRADE_ID, LOCATION_ID, ORGANIZATION_ID — organizational eligibility criteria.
• PAY_BASIS_ID — the pay basis qualifying the link.
• COST_ALLOCATION_KEYFLEX_ID and BALANCING_KEYFLEX_ID — cost allocation and balancing flexfield references.
• LINK_TO_ALL_PAYROLLS_FLAG, MULTIPLY_VALUE_FLAG, STANDARD_LINK_FLAG, TRANSFER_TO_GL_FLAG — control flags governing link behavior.
• BUSINESS_GROUP_ID — enterprise/legislative grouping.

Twenty descriptive ATTRIBUTE columns and audit columns (LAST_UPDATE_DATE, CREATED_BY, OBJECT_VERSION_NUMBER, etc.) round out the structure.

Common Use Cases and Queries

Typical usage centers on bulk element link load and verification. A common pattern joins staged rows to their source attributes to confirm eligibility before upload:

• Identifying staged links for a given element set: SELECT batch_element_link_id, element_type_id, effective_date FROM pay_batch_element_links WHERE element_set_id = :p_element_set_id;
• Validating that staged links resolve to valid people groups and pay bases before processing.
• Reporting on the volume of pending element link changes by business group.
• Auditing which links carry the transfer-to-GL or multiply-value flags.
• Reconciling staged rows against PAY_ELEMENT_LINKS using ELEMENT_LINK_ID to confirm successful upload.

Because the table is a batch construct, queries should generally be scoped by business group and effective date to avoid full scans of historical staging data.

Related Objects

The documented foreign keys establish the principal relationships of this table:

• PAY_PEOPLE_GROUPS — joined via PEOPLE_GROUP_ID; defines the population group eligibility.
• PAY_COST_ALLOCATION_KEYFLEX — joined via COST_ALLOCATION_KEYFLEX_ID; supplies cost allocation flexfield combinations.
• PAY_ELEMENT_SETS — joined via ELEMENT_SET_ID; the element set grouping the staged link belongs to.
• PER_PAY_BASES — joined via PAY_BASIS_ID; the pay basis applied to the link.
• PAY_ELEMENT_LINKS — the core target table referenced through ELEMENT_LINK_ID and ELEMENT_TYPE_ID.
• PAY_ELEMENT_TYPES and PER_ALL_PEOPLE_GROUPS — supporting the element and population definitions used during staging and upload.

These relationships reflect the table's role as an intermediary between element eligibility configuration and the final payroll element link repository.