Results for “hr_h2pi_element_entries_v”

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

Overview

The HR_H2PI_ELEMENT_ENTRIES_V view, owned by the APPS schema and validated in Oracle E-Business Suite 12.1.1 and 12.2.2, is the Oracle Human Resources to Oracle Payroll Interface (H2PI) element-entries extraction view. It exposes the element entry rows that are eligible for transfer across the HR-to-Payroll boundary, allowing payroll to receive earnings, deductions, and other element-based inputs that were created or maintained in the HR product (PER). The view underpins H2PI processing where element entries recorded against an assignment must be validated and pushed to the payroll application, including their associated costing information.

Because HR and Payroll frequently reside in the same EBS instance but may also be deployed separately, this view acts as a standardized, join-enriched projection of PAY_ELEMENT_ENTRIES_F rather than a raw table. It combines the assignment context supplied by HR_H2PI_ASSIGNMENTS_V with the cost allocation flexfield information from PAY_COST_ALLOCATION_KEYFLEX, so downstream H2PI concurrent programs and extracts can process element entries without performing the joins themselves.

Underlying Base Objects

The ETRM metadata documents three referenced base objects, all accessed through APPS synonyms:

• PAY_ELEMENT_ENTRIES_F (SYNONYM) — the primary driver table, aliased EE. It supplies the element entry identity, dates, entry type, creator type, and the 20 descriptive flexfield attribute columns.
• HR_H2PI_ASSIGNMENTS_V (VIEW) — aliased ASG. It provides the assignment-to-person and business group context, and is joined on ASSIGNMENT_ID with an effective-date range check.
• PAY_COST_ALLOCATION_KEYFLEX (SYNONYM) — aliased CAK. It supplies the concatenated cost allocation keyflex segments and the 30 individual segment columns, outer-joined on COST_ALLOCATION_KEYFLEX_ID.

Two join conditions shape the result set. The assignment join requires EE.EFFECTIVE_START_DATE BETWEEN ASG.EFFECTIVE_START_DATE AND ASG.EFFECTIVE_END_DATE, so only entries effective within the assignment's validity window are returned. The costing join uses an outer join (CAK.COST_ALLOCATION_KEYFLEX_ID(+)), meaning element entries without cost allocation are still returned, with the CAK columns null.

Key Columns

• ELEMENT_ENTRY_ID — primary identifier of the element entry; the key used by H2PI to reconcile records between HR and Payroll.
• ASSIGNMENT_ID, PERSON_ID, BUSINESS_GROUP_ID — the assignment, person, and business group context, sourced via the assignments view.
• CREATOR_TYPE — the focus of the user's search. It records the origin of the entry and is filtered by the view to values 'A', 'B', 'F', 'H', and 'UT'. This restriction ensures only entries created through supported channels (for example by the payroll batch, balance, or formula processes, or by user/H2PI transfer) are exposed.
• ENTRY_TYPE, DATE_EARNED — further characterize the element entry, particularly relevant for earnings and time-related inputs.
• EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — the dated range of the entry, used both for the assignment join and for payroll-period selection.
• ELEMENT_LINK_ID — identifies the element link governing eligibility of the element for the assignment.
• COST_ALLOCATION_KEYFLEX_ID and the CAK.CONCATENATED_SEGMENTS, SEGMENT1..SEGMENT30 columns — the full costing flexfield breakdown, used where entries must carry cost distribution into payroll.
• ATTRIBUTE1..ATTRIBUTE20 and ATTRIBUTE_CATEGORY — descriptive flexfield values carried on the element entry.

Common Use Cases and Queries

Typical usage includes auditing which element entries will be transferred by H2PI, reconciling HR-created entries against payroll results, and diagnosing why a particular entry was or was not picked up. Filtering by CREATOR_TYPE is a frequent requirement when investigating the origin of entries.

A representative query returns entries and their costing for a given assignment:

SELECT element_entry_id, person_id, assignment_id,
       creator_type, entry_type, effective_start_date,
       effective_end_date, concatenated_segments
FROM   apps.hr_h2pi_element_entries_v
WHERE  assignment_id = :p_assignment_id
AND    creator_type IN ('A','B','F','H','UT')
ORDER  BY effective_start_date;

To isolate entries created directly by the HR/H2PI transfer path:

SELECT element_entry_id, person_id, creator_type, entry_type
FROM   apps.hr_h2pi_element_entries_v
WHERE  creator_type = 'H'
AND    effective_start_date BETWEEN :p_start AND :p_end;

Because the view already enforces the assignment effective-date and creator-type constraints, reports and H2PI extracts built on it avoid duplicating that logic and remain consistent with the delivered interface behavior across both 12.1.1 and 12.2.2.