Results for “hr_h2pi_element_types_v”

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

Overview

The HR_H2PI_ELEMENT_TYPES_V view is a seeded Oracle E-Business Suite database object owned by the APPS schema and delivered under the PER (Human Resources) product family. It is a restricted projection of the PAY_ELEMENT_TYPES_F base table and is intended to expose only those element types that participate in the Oracle HR to Oracle Payroll Interface (H2PI). In release 12.1.1 and 12.2.2 this view serves as a read-only integration and reporting surface that allows external or downstream processes to identify payroll element types flagged for H2PI processing without querying the full, multi-column payroll setup table directly.

By filtering the underlying table to rows where ATTRIBUTE2 equals 'Y', the view returns a curated set of element types that have been explicitly enabled for the HR-to-Payroll interface. This restriction simplifies the data set for reporting consumers and shields them from element types used solely for internal payroll processing that are not relevant to the interface.

Underlying Base Objects

The view is defined over a single referenced base object, the synonym PAY_ELEMENT_TYPES_F, which resolves to the underlying Oracle Payroll element types table. The view text performs a straight projection of selected columns from that table:

• FROM clause: PAY_ELEMENT_TYPES_F ET
• Filter predicate: ET.ATTRIBUTE2 = 'Y'
• Select list: LAST_UPDATE_DATE, ELEMENT_TYPE_ID, BUSINESS_GROUP_ID, LEGISLATION_CODE, ELEMENT_NAME, PROCESSING_TYPE, EFFECTIVE_START_DATE, EFFECTIVE_END_DATE

No joins, unions, or aggregations are applied. The view is therefore a lightweight, date-effective filter over the base table, and its validity depends entirely on the structure and content of PAY_ELEMENT_TYPES_F. Because the filter relies on the descriptive flexfield-based ATTRIBUTE2 column, only element types configured with that attribute set to 'Y' are visible to consumers.

Key Columns

The columns exposed by the view carry the following significance:

• ELEMENT_TYPE_ID: Primary identifier for the element type; the key used to join back to the base table or to related payroll objects.
• BUSINESS_GROUP_ID: Identifies the business group that owns the element type, enabling multi-organization filtering.
• LEGISLATION_CODE: The country or legislation under which the element type is defined; important for localization-specific processing.
• ELEMENT_NAME: The descriptive name of the element type presented to users and interfaces.
• PROCESSING_TYPE: Indicates how the element is processed during payroll runs. Because the user query referenced "processing_type," this is typically the primary filter column of interest, distinguishing recurring versus non-recurring processing behavior.
• EFFECTIVE_START_DATE / EFFECTIVE_END_DATE: The date-effective range for which the element type configuration is valid.
• LAST_UPDATE_DATE: Supports incremental extraction and change-tracking in integration scenarios.

Common Use Cases and Queries

Typical scenarios include validating which element types are eligible for H2PI, driving interface extracts, and reporting on element configuration by legislation or business group. A representative query filtering by processing type is shown below:

• SELECT element_type_id, element_name, processing_type, legislation_code FROM apps.hr_h2pi_element_types_v WHERE processing_type = 'R' AND legislation_code = 'US';
• SELECT element_name, effective_start_date, effective_end_date FROM apps.hr_h2pi_element_types_v WHERE business_group_id = :p_bg_id ORDER BY element_name;
• SELECT element_type_id, element_name FROM apps.hr_h2pi_element_types_v WHERE last_update_date >= :p_since_date; for delta extraction.

Because the view is date-effective and filtered on ATTRIBUTE2, queries should account for effective dating and should never assume the view represents the complete set of payroll element types.