Search Results pay_org_payment_methods_x




Overview

The PAY_ORG_PAYMENT_METHODS_X view is a date-effective (X) view in the Oracle E-Business Suite Payroll (PAY) module, owned by the APPS schema. It exposes organization payment methods — the payment delivery mechanisms (for example, direct deposit, check, or wire) defined for a specific organization or business group — that are valid as of the current system date. As a date-effective view, it abstracts the underlying date-tracked (_F) table plus its translation (_TL) table, automatically filtering rows so that only the version effective on the current date is returned and joining in the language-appropriate name.

Because the view handles effectivity and language resolution on behalf of the caller, it is the preferred entry point for reporting, integrations, and custom concurrent programs that need a flat, current-state view of organization payment methods. Rather than writing the date-range predicate and translation join manually, developers and report builders query this view directly.

Underlying Base Objects

The view is defined over two documented base objects:

The two are joined on ORG_PAYMENT_METHOD_ID, with the translation row restricted by OPMTL.LANGUAGE = USERENV('LANG') so that the name is returned in the session's current language. The effectivity filter is applied as TRUNC(SYSDATE) BETWEEN EFFECTIVE_START_DATE AND EFFECTIVE_END_DATE, which restricts the result to the single currently effective version of each payment method.

Key Columns

Common Use Cases and Queries

Typical scenarios include listing valid payment methods for a business group, feeding data into extract files, or validating configuration before running a payroll or third-party payment process.

To list all currently effective payment methods for a business group:

  • SELECT ORG_PAYMENT_METHOD_ID, ORG_PAYMENT_METHOD_NAME, CURRENCY_CODE, PAYMENT_TYPE_ID
  • FROM APPS.PAY_ORG_PAYMENT_METHODS_X
  • WHERE BUSINESS_GROUP_ID = :p_business_group_id
  • ORDER BY ORG_PAYMENT_METHOD_NAME;

To resolve a method's key flexfield information for a specific currency:

  • SELECT ORG_PAYMENT_METHOD_NAME, PMETH_INFORMATION_CATEGORY, PMETH_INFORMATION1
  • FROM APPS.PAY_ORG_PAYMENT_METHODS_X
  • WHERE CURRENCY_CODE = :p_currency;

Because the view already enforces the current-date effectivity predicate, callers do not need to supply date ranges; historical or future-dated analysis must instead query the base F and TL tables directly. Note that results are limited to records valid as of TRUNC(SYSDATE), so any application requiring point-in-time history should not rely on this view.