Search Results hr_h2pi_data_feed_hist_pk

Overview

HR_H2PI_DATA_FEED_HIST is a Human Resources (PER) module table in the Oracle E-Business Suite that stores historical information about data feeds pushed from Oracle HR to the Oracle Payroll Interface (commonly abbreviated H2PI). The H2PI mechanism is the integration layer that transfers HR assignment, element, and payroll-related data from the HR schema to the Payroll product so that payroll processing has current, accurate employee information. This table preserves a dated audit trail of those feed executions, capturing when each feed ran, which business group it targeted, and which concurrent program produced it.

From a Data Vault modeling perspective, the mined foreign-key structure classifies this object heuristically as a standalone table, meaning it is not a hub or link participating in a documented parent/child relationship. In practice the surrogate-keyed rows behave as a satellite-style historical record: each row represents an immutable snapshot event (a completed or attempted data feed) keyed by a sequence number and bracketed by a start and end date.

Key Information Stored

The table contains 16 documented columns. The most significant are:

• SEQUENCE_NUMBER — the surrogate primary key (HR_H2PI_DATA_FEED_HIST_PK) that uniquely identifies each historical feed record.
• START_DATE / END_DATE — the effective window of the feed; together they delimit the period a given feed history entry covers.
• BUSINESS_GROUP_ID — the HR business group (operating unit) for which the feed was executed; the primary business-key candidate for filtering feeds by organization.
• BUSINESS_GROUP_NAME — the descriptive name of that business group, denormalized for reporting convenience.
• CLIENT_ID — the multi-tenant / client identifier used in hosted or shared-services deployments.
• REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID, PROGRAM_UPDATE_DATE — concurrency metadata linking the history row to the Oracle concurrent program and request that generated the feed.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard Oracle WHO-column audit trail identifying who created and last modified each row and when.
• OBJECT_VERSION_NUMBER — the optimistic locking counter used by the Oracle Applications framework to detect concurrent updates.

The surrogate key is SEQUENCE_NUMBER; BUSINESS_GROUP_ID combined with START_DATE and END_DATE is the natural business-key candidate for de-duplicating feed runs.

Common Use Cases and Queries

Typical uses include auditing payroll-interface runs, diagnosing missing or duplicate HR-to-Payroll feeds, and confirming the last successful feed per business group before a payroll cycle. A representative query lists the most recent feed window for a given business group:

• SELECT business_group_id, business_group_name, start_date, end_date, request_id, program_update_date FROM hr.hr_h2pi_data_feed_hist WHERE business_group_id = :p_bg_id ORDER BY start_date DESC;
• Join to concurrent-program history via REQUEST_ID to retrieve the run status and completion time.
• Detect date gaps: compare consecutive END_DATE/START_DATE values to spot periods where no HR feed reached Payroll.
• Reconcile feed counts against FND_CONCURRENT_REQUESTS for the H2PI program to validate scheduler behavior.

Because the table is standalone with no documented foreign keys, all joins are logical (driven by REQUEST_ID, PROGRAM_ID, and BUSINESS_GROUP_ID) rather than enforced.

Related Objects

The table has no declared foreign keys, so its relationships are operational rather than physical. The most significant objects to consult alongside it are:

• FND_CONCURRENT_REQUESTS — join on REQUEST_ID to obtain execution status and timing.
• FND_CONCURRENT_PROGRAMS — join on PROGRAM_ID and PROGRAM_APPLICATION_ID for the feed program definition.
• HR_OPERATING_UNITS / HR_ALL_ORGANIZATION_UNITS — resolve BUSINESS_GROUP_ID to an organization.
• PAY_PAYROLL_ACTIONS and PAY_ASSIGNMENT_ACTIONS — downstream payroll side of the H2PI transfer.
• HR_H2PI_* interface/feed tables in the PER schema that hold the transmitted data itself.