Search Results patch_name

Overview

The HR_H2PI_PATCH_STATUS_V view is a dictionary-level reporting object owned by the APPS schema within Oracle E-Business Suite. It is classified under the PER — Human Resources product family and exposes patch-status information relevant to the Oracle HR to Oracle Payroll Interface (H2PI). H2PI is the integration mechanism through which employee, assignment, and payroll-related data flow from Oracle HRMS into the Oracle Payroll engine. The view provides a focused, read-only window into the patch records that affect this interface, allowing developers, DBAs, and support analysts to determine which H2PI-relevant patches have been applied and when.

Because the view carries a VALID status in the ETRM 12.2.2 metadata, it is a supported object that can be queried directly in both 12.1.1 and 12.2.2 environments without recompilation concerns. Its principal value lies in auditing and troubleshooting: it isolates a narrow subset of the patch inventory so that the question "has the required H2PI fix been applied?" can be answered quickly and consistently across environments.

Underlying Base Objects

The view is defined over a single documented base object: the synonym PAY_PATCH_STATUS, which is the public synonym layered over the underlying Oracle Payroll patch-registry table. No joins, unions, or additional tables participate in the definition. Instead, the view applies two fixed filters to that base data, as shown in the view text:

• PS.LEGISLATION_CODE = 'US' — restricts output to United States legislative context.
• PS.PATCH_NAME LIKE 'GEOCODE%' — restricts output to patch names beginning with the string "GEOCODE".

Consequently, the view is significantly narrower than its base table. It behaves as a convenience projection that returns only US geocode-related H2PI patch records. Any patch tracked in PAY_PATCH_STATUS that does not satisfy both predicates will not appear here, even if it is otherwise relevant to H2PI processing.

Key Columns

The view exposes four columns, each inherited directly from PAY_PATCH_STATUS:

• PATCH_NUMBER — the identifier assigned to the patch, typically corresponding to the Oracle patch or bug number used for tracking and deployment.
• PATCH_NAME — the descriptive name of the patch. Owing to the view's filter, every value in this column begins with "GEOCODE".
• STATUS — the recorded state of the patch, indicating whether it has been applied, is pending, or failed in the current environment. This is the primary column for determining compliance.
• APPLIED_DATE — the date the patch was recorded as applied. This is the column most frequently targeted by users searching for "applied_date", since it establishes the timeline of H2PI geocode fixes and supports change auditing.

Common Use Cases and Queries

The view is typically queried during patching cycles, post-clone validation, and incident triage. A support analyst confirming whether a geocode-related H2PI fix reached production might run:

• SELECT patch_number, patch_name, status, applied_date FROM apps.hr_h2pi_patch_status_v ORDER BY applied_date DESC;
• SELECT * FROM apps.hr_h2pi_patch_status_v WHERE status = 'APPLIED';
• SELECT patch_name, applied_date FROM apps.hr_h2pi_patch_status_v WHERE applied_date >= TO_DATE('01-JAN-2023','DD-MON-YYYY');

Such queries support environment comparison during cloning, verify remediation of known H2PI geocode defects, and provide evidence for audit or change-control records. Because the view is read-only and filters to US geocode patches, it should be treated as a targeted diagnostic aid; broader patch lineage should be obtained from PAY_PATCH_STATUS directly when non-US or non-geocode patches are in scope.