Results for “hr_h2pi_payment_methods_v”

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

Overview

The APPS.HR_H2PI_PAYMENT_METHODS_V view is a documented, VALID database object owned by the APPS schema and classified under the PER – Human Resources product family in Oracle E-Business Suite 12.1.1 and 12.2.2. Its purpose is to expose data related to the Oracle HR to Oracle Payroll Interface (H2PI) for payment methods, providing a denormalized read model that combines personal payment method records, external bank account details, and assignment context in a single queryable structure.

This view serves as an integration and reporting surface for the HR-to-Payroll data flow. Rather than forcing consumers to join the payment method, external account, and assignment entities independently, HR_H2PI_PAYMENT_METHODS_V consolidates them so that payroll interface processes, extracts, and ad hoc reports can retrieve payment distribution information—amounts, percentages, priorities, and related bank account attributes—in one pass. Because the view resolves assignment-level context through HR_H2PI_ASSIGNMENTS_V, it also enforces the effective-dating relationship between payment methods and assignments, which is essential for date-effective payroll processing.

Underlying Base Objects

The ETRM metadata records three referenced base objects for this view. The primary driving object is PAY_PERSONAL_PAYMENT_METHODS_F (exposed as a SYNONYM), which supplies the payment method record itself, including effective dates, amount, percentage, priority, payee information, and the descriptive attribute columns. Joining to PAY_EXTERNAL_ACCOUNTS (also a SYNONYM) provides the external bank account data associated with the payment method via EXTERNAL_ACCOUNT_ID; this join is an outer join (EXTERNAL_ACCOUNT_ID (+)), so personal payment methods without an associated external account are still returned. The third object, HR_H2PI_ASSIGNMENTS_V (a VIEW), supplies assignment and person context.

The join conditions define the semantic relationships: PPM.EXTERNAL_ACCOUNT_ID = EXA.EXTERNAL_ACCOUNT_ID (+), ASG.ASSIGNMENT_ID = PPM.ASSIGNMENT_ID, and critically PPM.EFFECTIVE_START_DATE BETWEEN ASG.EFFECTIVE_START_DATE AND ASG.EFFECTIVE_END_DATE. This date-bounded join ensures that only payment methods whose effective start date falls within the assignment's effective window are surfaced.

Key Columns

• PERSONAL_PAYMENT_METHOD_ID – Primary identifier of the personal payment method record from PAY_PERSONAL_PAYMENT_METHODS_F.
• ASSIGNMENT_ID / PERSON_ID – Assignment and person identifiers, the latter derived from HR_H2PI_ASSIGNMENTS_V.
• EFFECTIVE_START_DATE / EFFECTIVE_END_DATE – Date-effective bounds for the payment method.
• ORG_PAYMENT_METHOD_ID, AMOUNT, PERCENTAGE, PRIORITY – Define how pay is distributed across payment methods.
• PAYEE_ID / PAYEE_TYPE – Payee identity and classification.
• PRENOTE_DATE – Sourced from PAY_EXTERNAL_ACCOUNTS (EXA.PRENOTE_DATE); indicates when a prenotification was recorded for the external account, relevant to direct deposit validation.
• TERRITORY_CODE – Country/territory of the external account.
• SEGMENT1–SEGMENT30 – Flexible key flexfield segments of the external account.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE20 – Descriptive flexfield context and values from the payment method record.
• LAST_UPDATE_DATE, BUSINESS_GROUP_ID – Audit and multi-organization context.

Common Use Cases and Queries

A frequent use case—reflected by the search term "prenote_date"—is identifying external accounts that have or have not completed prenotification, which affects whether direct deposit can proceed.

SELECT person_id, assignment_id, personal_payment_method_id,
       prENote_date, territory_code, segment1
FROM   apps.hr_h2pi_payment_methods_v
WHERE  prenote_date IS NULL
AND    SYSDATE BETWEEN effective_start_date AND effective_end_date;

Another scenario is reporting payment distribution per assignment for H2PI extracts:

SELECT assignment_id, org_payment_method_id, amount, percentage, priority
FROM   apps.hr_h2pi_payment_methods_v
WHERE  business_group_id = :p_bg_id
AND    SYSDATE BETWEEN effective_start_date AND effective_end_date
ORDER  BY assignment_id, priority;

Because the view touches date-effective and multi-organization data, queries should generally constrain BUSINESS_GROUP_ID and filter on the effective date range to return the currently active payment method rows.