Results for “hr_h2pi_org_payment_methods_v”

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

Overview

The HR_H2PI_ORG_PAYMENT_METHODS_V view is a reporting and integration object owned by the APPS schema in Oracle E-Business Suite, catalogued under the PER (Human Resources) product family. It exists to expose organization-level payment method definitions that are relevant to the Oracle HR to Oracle Payroll Interface (H2PI) flow. In releases 12.1.1 and 12.2.2, the view carries a VALID status and is preserved as documented metadata in ETRM.

Functionally, the view consolidates payment method configuration — currency, effective dating, external account references, and payment type classification — into a single denormalized shape suitable for interfaces, extracts, and ad hoc reporting. Where the search term "payment_type_name" is relevant, the view supplies this value by joining to the payment type definition, which allows consumers to resolve a numeric PAYMENT_TYPE_ID into a human-readable label without an additional lookup. This makes the view a convenient access point for H2PI-related extracts that must describe how an organization pays its employees or third parties.

Underlying Base Objects

The view text is defined over two synonyms that resolve to base tables:

• PAY_ORG_PAYMENT_METHODS_F — the effective-dated (date-tracked) table holding organization payment method records. It is aliased OPM and contributes the identity, business group, name, effective dates, currency, external account, and the PAYMENT_TYPE_ID used for the join.
• PAY_PAYMENT_TYPES — the payment type lookup, aliased PYT. It supplies PAYMENT_TYPE_NAME and TERRITORY_CODE.

The join condition is OPM.PAYMENT_TYPE_ID = PYT.PAYMENT_TYPE_ID, and a further filter restricts results to rows where OPM.ATTRIBUTE2 = 'Y'. This attribute filter is the Oracle HR to Payroll Interface marker: only payment methods flagged in ATTRIBUTE2 are surfaced for H2PI purposes, so the view is deliberately narrower than the underlying table.

Key Columns

• ORG_PAYMENT_METHOD_ID — primary identifier of the organization payment method.
• BUSINESS_GROUP_ID — the business group to which the payment method belongs, enabling multi-organization filtering.
• ORG_PAYMENT_METHOD_NAME — the descriptive name of the payment method.
• EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — the date-tracked validity window inherited from the _F table.
• CURRENCY_CODE — currency in which the payment method operates.
• EXTERNAL_ACCOUNT_ID — reference to the associated external account.
• PAYMENT_TYPE_NAME — the readable payment type label derived from PAY_PAYMENT_TYPES; the column matched by the "payment_type_name" search.
• TERRITORY_CODE — territory associated with the payment type.
• LAST_UPDATE_DATE — audit column supporting incremental extracts.

The documentation lists the audit column as LAST_UPD_DATE in the column inventory, though the view text selects LAST_UPDATE_DATE.

Common Use Cases and Queries

Typical scenarios include validating payment method setup prior to a payroll interface run, building extracts that require the payment type name, and auditing which organizations have H2PI-enabled methods. A representative query is:

SELECT org_payment_method_id,
       org_payment_method_name,
       payment_type_name,
       currency_code,
       territory_code,
       effective_start_date,
       effective_end_date
FROM   apps.hr_h2pi_org_payment_methods_v
WHERE  business_group_id = :p_business_group_id
AND    TRUNC(SYSDATE) BETWEEN effective_start_date
                          AND NVL(effective_end_date, TRUNC(SYSDATE));

For incremental synchronization, filtering on last_update_date greater than a stored high-water mark limits the result set to changed rows. Because the view already applies the ATTRIBUTE2 = 'Y' restriction, no additional H2PI qualification is required by callers.