Results for “hr_h2pi_payrolls_v”

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

Overview

The HR_H2PI_PAYROLLS_V view is a reporting and integration object owned by the APPS schema in Oracle E-Business Suite, residing in the PER (Human Resources) product family. Its name reflects its purpose: it exposes payroll definitions that participate in the Oracle HR to Oracle Payroll Interface (H2PI), the mechanism by which payroll-relevant records originate in Oracle HRMS and are transferred to an external or downstream payroll processing system. In EBS 12.1.1 and 12.2.2 the object remains a VALID, read-only view, meaning it carries no storage of its own and is populated at query time.

The view serves two principal audiences. First, it supports H2PI configuration and diagnostic reporting, allowing implementers and support analysts to identify which payrolls have been enabled for the interface. Second, because it is a stable, APPS-owned view, customer extensions, concurrent programs, and interfaces can reference it without depending directly on the payroll base table, insulating them from changes in the underlying definition.

Underlying Base Objects

The view is defined over a single base object: the synonym PAY_ALL_PAYROLLS_F, which in turn resolves to the payroll definition table in the Payroll application. The defining query selects nine columns from that table and applies one filter predicate, restricting the result set to rows where ATTRIBUTE2 equals 'Y'. This descriptor flexfield column functions as the H2PI enablement flag, so the view returns only payrolls that have been explicitly designated for the HR to Payroll Interface rather than the complete set of payroll definitions. The documented ETRM metadata for 12.2.2 confirms the owner as APPS and the referenced base object as PAY_ALL_PAYROLLS_F (SYNONYM). Because the underlying table is a date-tracked (_F) entity, the view surfaces effective date columns but does not itself restrict to a single effective version beyond the ATTRIBUTE2 predicate.

Key Columns

• PAYROLL_ID — Primary identifier for the payroll definition. Join key to payroll-related tables such as assignment, element, and run result entities.
• PAYROLL_NAME — User-facing name of the payroll, typically reflecting pay frequency and grouping, for example a monthly or semi-monthly payroll.
• BUSINESS_GROUP_ID — Identifies the business group (legislative context) to which the payroll belongs. Used to scope queries by enterprise or country configuration.
• NUMBER_OF_YEARS — The number of years associated with the payroll definition on the underlying record. Searched frequently by users reconciling payroll configuration.
• FIRST_PERIOD_END_DATE — The end date of the first payroll period, establishing the payroll calendar's starting point.
• PERIOD_TYPE — The periodicity of the payroll, such as weekly, biweekly, semi-monthly, or monthly.
• EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — Date-tracked validity range for the payroll definition row.
• LAST_UPDATE_DATE — Audit column used to identify recently modified payroll definitions. Note the view's documented column list shows LAST_UPD_DATE, while the view text selects LAST_UPDATE_DATE.

Common Use Cases and Queries

A frequent requirement is to enumerate H2PI-enabled payrolls for a business group and inspect their calendars, for example to validate NUMBER_OF_YEARS or PERIOD_TYPE before a data load.

• Listing enabled payrolls: SELECT payroll_id, payroll_name, period_type, number_of_years, first_period_end_date FROM apps.hr_h2pi_payrolls_v WHERE business_group_id = :p_bg_id ORDER BY payroll_name;
• Filtering by periodicity: add WHERE period_type = 'M' to isolate monthly payrolls for reconciliation.
• Change auditing: SELECT payroll_name, last_update_date FROM apps.hr_h2pi_payrolls_v WHERE last_update_date >= SYSDATE - 30; to detect recent configuration changes.
• Joining to assignments or element entries on PAYROLL_ID to correlate payroll definitions with employee-level H2PI data.

Because the view is read-only and driven by the ATTRIBUTE2 flag, H2PI enablement is controlled on the underlying payroll definition rather than through the view. Queries should always qualify the APPS schema and restrict by business group in multi-organization environments.