Search Results hr_h2pi_element_entries




Overview
Explore in AI Chat

Overview

The HR.HR_H2PI_ELEMENT_ENTRIES table is a staging table for the Oracle HR to Oracle Payroll Interface (H2PI). Its documented purpose is to store data related to element entries while a data upload is in progress. During H2PI processing, element entry information extracted from Oracle Human Resources is written into this table before it is transmitted to the target Oracle Payroll instance. The table therefore acts as a transient holding area rather than a permanent system-of-record structure; rows persist only for the duration of an upload batch and are typically purged or overwritten once the transfer completes successfully.

The object is owned by the HR schema and resides within the PER — Human Resources product module. The documented physical schema for ETRM 12.2.2 lists 71 columns. The primary key is defined by the constraint HR_H2PI_ELEMENT_ENTRIES_PK over ELEMENT_ENTRY_ID, EFFECTIVE_START_DATE, EFFECTIVE_END_DATE, BUSINESS_GROUP_ID, and CLIENT_ID. Regarding Data Vault classification, the metadata's heuristic mining returns a classification of standalone, which suggests modeling the object as an independent structure without resolved parent hubs or links; note that this is a heuristic result rather than a normative architectural directive.

Key Information Stored

The most significant columns in this staging table are:

  • ELEMENT_ENTRY_ID — Identifier for the element entry being staged; the leading component of the composite primary key.
  • EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — Date-effective boundaries for the element entry record; both participate in the primary key.
  • BUSINESS_GROUP_ID — Business group context for the staged row; part of the composite primary key.
  • CLIENT_ID — Multi-tenancy discriminator; also part of the composite primary key.
  • PERSON_ID — The person to whom the element entry relates.
  • ASSIGNMENT_ID — The assignment associated with the element entry.
  • ELEMENT_LINK_ID — Reference to the element link that governs eligibility and input values for the entry.
  • ENTRY_TYPE / CREATOR_TYPE — Classify the nature and origin of the entry.
  • DATE_EARNED — The date the entry is considered earned.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE20 — Descriptive flexfield context and segment values associated with the entry.
  • CONCATENATED_SEGMENTS, ID_FLEX_NUM, SEGMENT1–SEGMENT30 — Key flexfield representation and segments carried with the staged entry.
  • STATUS — Processing status of the staging row.
  • PERSONAL_PAYMENT_METHOD_ID — Payment method reference for the person.

The surrogate identifier is ELEMENT_ENTRY_ID, while the full unique business key is the five-column composite enforced by HR_H2PI_ELEMENT_ENTRIES_PK. The documented schema does not list additional unique indexes beyond this primary key.

Common Use Cases and Queries

Typical use cases center on monitoring and diagnosing H2PI upload runs. Common patterns include counting staged rows per business group, checking for rows left behind after a failed interface run, and validating that effective dates and assignment identifiers are populated before the payroll transfer proceeds. A representative query follows:

  • SELECT BUSINESS_GROUP_ID, COUNT(*) FROM HR.HR_H2PI_ELEMENT_ENTRIES GROUP BY BUSINESS_GROUP_ID;
  • SELECT ELEMENT_ENTRY_ID, PERSON_ID, ASSIGNMENT_ID, EFFECTIVE_START_DATE, EFFECTIVE_END_DATE, STATUS FROM HR.HR_H2PI_ELEMENT_ENTRIES WHERE STATUS = 'ERROR';
  • Join patterns against HR_PER_ASG_ASSIGNMENTS_F on ASSIGNMENT_ID to reconcile staged entries with current assignments.

Because the table is a staging artifact, reporting should be treated as operational rather than historical. Persisting staged data for audit purposes requires copying rows to a custom table before the interface purges them.

Related Objects

The metadata classifies the object as standalone with no mined foreign-key dependencies, so related objects are identified by shared column semantics rather than enforced constraints.

  • HR.HR_H2PI_ELEMENT_ENTRIES — The staging table itself, referenced through its primary key constraint HR_H2PI_ELEMENT_ENTRIES_PK.
  • PAY_ELEMENT_TYPES_F / PAY_ELEMENT_LINKS_F — Define the element and element link referenced by ELEMENT_LINK_ID.
  • HR.PER_ALL_PEOPLE_F — Source of PERSON_ID values.
  • HR.PER_ALL_ASSIGNMENTS_F — Source of ASSIGNMENT_ID values.
  • HR.PAY_ELEMENT_ENTRIES_F — The production element entry entity that the staged data ultimately represents in payroll.
  • HR.HR_H2PI_* interface tables — Companion staging objects used by the H2PI upload process.

These relationships should be confirmed against the specific environment, as the documented metadata does not define enforced referential constraints for this object.