Results for “hr_h2pi_patch_status”

50+ results




Overview
Explore in AI Chat

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

Overview

The HR_H2PI_PATCH_STATUS table is a Human Resources (PER) application table within the Oracle E-Business Suite, owned by the HR schema. Its name indicates a role in tracking the application status of H2PI-related patches against a specific business group. H2PI ("HR to Payroll Interface" style processing and its associated data collections) involves staged handoffs between HR and Payroll; this table appears to record which patches have been applied and their outcome, providing an auditable reference point for patch-level state within the HR module.

From a data modeling perspective, the heuristic Data Vault classification mined from the foreign key structure is standalone. No FK relationships are documented, suggesting the table is intended as a self-contained reference/status ledger rather than a transactional hub or link. Analysts modeling this object should treat it as a satellite-like reference set (state history for a business key) rather than as a hub with downstream links, and should not assume implicit joins unless verified against the underlying schema.

Key Information Stored

The table carries a documented total of six columns. The most important ones are:

  • PATCH_NUMBER — the patch identifier; part of the composite primary key and the principal business-key candidate for identifying a specific patch record.
  • PATCH_NAME — a descriptive label for the patch, useful for reporting without a lookup to external patch repositories.
  • STATUS — the current disposition of the patch (for example applied, pending, or failed), which represents the primary state attribute of the record.
  • APPLIED_DATE — the date the patch was applied, supporting timeline and audit reporting.
  • BUSINESS_GROUP_ID — the operating unit/business group context; part of the composite primary key, ensuring patch status is scoped per business group.
  • CLIENT_ID — the multi-tenant client discriminator; also part of the composite primary key.

The surrogate/primary key is the composite index HR_H2PI_PATCH_STATUS_PK, defined over (CLIENT_ID, BUSINESS_GROUP_ID, PATCH_NUMBER). There is no separate single-column surrogate key; identity is established by the combination of client, business group, and patch number. Queries that match the user search term "hr_h2pi_patch_status_pk" refer to this index, and any direct lookup by patch should include all three key columns to leverage the index efficiently.

Common Use Cases and Queries

Typical usage revolves around patch auditing and interface readiness checks:

  • Verifying whether a specific patch has been applied for a given business group before running H2PI-dependent processes.
  • Reporting on patch application timelines using APPLIED_DATE.
  • Identifying patches still in a non-applied STATUS for remediation.

Representative SQL patterns:

  • Key-based lookup: SELECT patch_name, status, applied_date FROM hr.hr_h2pi_patch_status WHERE client_id = :p_client AND business_group_id = :p_bg AND patch_number = :p_patch;
  • Status summary by business group: SELECT business_group_id, status, COUNT(*) FROM hr.hr_h2pi_patch_status GROUP BY business_group_id, status;
  • Recent applications: SELECT patch_number, patch_name, applied_date FROM hr.hr_h2pi_patch_status WHERE applied_date >= :p_from ORDER BY applied_date DESC;

Because the table is standalone and small, it is well suited to lightweight BI extracts and DBA check scripts rather than heavy transactional joins.

Related Objects

Documented FK relationships are absent, so related objects are inferred from the HR module and the H2PI process family:

In the absence of documented FKs, join columns should be validated against the live schema before being relied upon in reports.