Search Results pay_org_payment_methods_d




Overview
Explore in AI Chat

Overview

The PAY_ORG_PAYMENT_METHODS_D view is an Oracle E-Business Suite database object owned by the APPS schema within the Payroll (PAY) product module. It is a DateTrack history view, a specialized construct used throughout Oracle HRMS and Payroll to expose the full historical record of date-effective (datetracked) entities rather than only the currently active row. The base transactional table, PAY_ORG_PAYMENT_METHODS_F, stores organizational payment methods with EFFECTIVE_START_DATE and EFFECTIVE_END_DATE columns; the view denominated with the "_D" suffix presents these rows in a form suitable for reviewing or auditing the complete timeline of changes, including superseded versions.

In Oracle EBS 12.1.1 and 12.2.2 the view is reported as VALID and is queried by DateTrack History functionality, including the "View History" or "Show History" windows in the Payroll and HRMS forms. Report developers, integration specialists, and support analysts use it to reconstruct the payment method assignments that existed at any point in time for a given organization or business group.

Underlying Base Objects

The view is defined over five documented base objects, all referenced through APPS synonyms:

  • PAY_ORG_PAYMENT_METHODS_F — the primary datetracked table holding organizational payment method definitions, effective dates, and audit columns.
  • PAY_ORG_PAYMENT_METHODS_F_TL — the translated (language) table supplying the organization payment method name in the session language.
  • PAY_PAYMENT_TYPES — the payment type definition table, joined on PAYMENT_TYPE_ID.
  • PAY_PAYMENT_TYPES_TL — the translated table supplying the payment type name in the session language.
  • FND_USER — the application user table, outer-joined to resolve the LAST_UPDATED_BY value to a user name.

The join between the "_F" table and both "_TL" tables is filtered by LANGUAGE = USERENV('LANG'), so the view returns translated names matching the current session language. The outer join to FND_USER ensures rows remain visible even when the updating user cannot be resolved.

Key Columns

  • ORG_PAYMENT_METHOD_ID — primary identifier of the organizational payment method record.
  • EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — the datetrack effective range for each historical version of the record.
  • TYPE — exposes the payment type identifier (derived from PAY_PAYMENT_TYPES.PAYMENT_TYPE_ID).
  • NAME — the organization payment method name in the session language.
  • SYSTEM_ORG_PAY_METHOD_NAME — the untranslated base name from the "_F" table, useful for comparison and troubleshooting translation gaps.
  • PAYMENT_TYPE_NAME — the translated payment type name joined from PAY_PAYMENT_TYPES_TL.
  • LAST_UPDATE_DATE / LAST_UPDATED_BY — audit columns identifying when and by whom the record was last changed; the view text additionally resolves the updater through FUSER.USER_NAME.

Common Use Cases and Queries

Typical scenarios include auditing payment method changes over time, verifying which methods were active on a historical pay date, and supporting data migration or reconciliation between legacy and target environments.

To list all historical versions for a specific organization payment method:

  • SELECT org_payment_method_id, name, payment_type_name, effective_start_date, effective_end_date FROM apps.pay_org_payment_methods_d WHERE org_payment_method_id = :p_id ORDER BY effective_start_date;

To identify methods active as of a given date:

  • SELECT name, payment_type_name, effective_start_date, effective_end_date FROM apps.pay_org_payment_methods_d WHERE TRUNC(:p_date) BETWEEN effective_start_date AND effective_end_date;

To trace recent changes and their authors:

  • SELECT name, effective_start_date, last_update_date, last_updated_by FROM apps.pay_org_payment_methods_d ORDER BY last_update_date DESC;

Because the view performs language filtering against USERENV('LANG'), queries should generally be executed from within an EBS application session or with the correct NLS environment set, so that translated names resolve as expected.