Results for “pay_org_payment_methods”

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

Overview

PAY_ORG_PAYMENT_METHODS is a date-effective (effective-dated) view owned by the APPS schema in Oracle E-Business Suite, belonging to the PAY (Payroll) product family. It presents organization-level payment method definitions as they are valid at the current session's effective date, and it is the read-only reporting and integration interface through which external processes, concurrent programs, and custom reports retrieve payment method records for a given business group.

Because payment method configuration is date-tracked, the underlying transaction table retains multiple versions of each payment method row. This view resolves those versions to the single row that is effective for the current user session, which is established by the FND_SESSIONS effective date. As a result, the view returns exactly one row per payment method identifier per session, presenting the configuration as it applies "today" within the session context. This behavior makes it appropriate for operational reporting and integrations that must consume the currently effective configuration rather than historical or future-dated versions.

The view is valid and documented in ETRM for both Oracle EBS 12.1.1 and 12.2.2, with the same structure and semantics across the two releases.

Underlying Base Objects

The view is defined over three referenced objects, all accessed through synonyms in the APPS schema:

• PAY_ORG_PAYMENT_METHODS_F — the date-effective base table storing the organization payment method definitions, including the effective start and end dates, business group, external account, currency, payment type, and the descriptive flexfield and PMETH information columns.
• PAY_ORG_PAYMENT_METHODS_F_TL — the translation (TL) table supplying the language-specific payment method name. The view joins this table on ORG_PAYMENT_METHOD_ID and filters on LANGUAGE = USERENV('LANG').
• FND_SESSIONS — the session table used to resolve the effective date for the current session. The view correlates the session row through SESSION_ID = USERENV('SESSIONID') and compares that row's EFFECTIVE_DATE against the record's EFFECTIVE_START_DATE and EFFECTIVE_END_DATE.

The join is an equi-join between the transaction table and its translation table on the primary key ORG_PAYMENT_METHOD_ID, combined with a language filter and two correlated scalar subqueries against FND_SESSIONS that enforce the date-effective predicate.

Key Columns

• ORG_PAYMENT_METHOD_ID — primary identifier for the organization payment method.
• EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — the date range during which this version of the record is valid.
• BUSINESS_GROUP_ID — the business group (organization) that owns the payment method.
• EXTERNAL_ACCOUNT_ID — reference to the associated external bank account.
• CURRENCY_CODE — currency in which the payment method operates.
• PAYMENT_TYPE_ID — reference to the payment type definition.
• DEFINED_BALANCE_ID — reference to a defined balance, where the payment method is balance-driven.
• ORG_PAYMENT_METHOD_NAME — the translated, language-specific name of the payment method.
• COMMENT_ID — reference to any associated comment or note.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE20 — descriptive flexfield context and segment columns.
• PMETH_INFORMATION1–PMETH_INFORMATION20 — the payment method "information" flexfield columns supporting additional configuration data.
• SYSTEM_ORG_PAY_METHOD_NAME — the untranslated base payment method name from the transaction table.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE — standard audit columns.

Common Use Cases and Queries

Typical uses include validating payment method configuration for a business group, joining payment methods to external accounts and currencies in integration extracts, and reporting on currently effective configuration for payroll processing. The following query lists effective payment methods for the session:

• SELECT org_payment_method_id, org_payment_method_name, currency_code, payment_type_id, business_group_id FROM apps.pay_org_payment_methods WHERE business_group_id = :p_business_group_id;
• SELECT opm.org_payment_method_name, opm.currency_code, pext.account_number FROM apps.pay_org_payment_methods opm, apps.pay_external_accounts pext WHERE opm.external_account_id = pext.external_account_id AND opm.business_group_id = :p_business_group_id;

Because the view derives the effective date from FND_SESSIONS, callers must ensure a valid session context; queries issued outside a properly initialized session may return no rows or unexpected results. Where historical or date-parameterized results are required, querying the underlying PAY_ORG_PAYMENT_METHODS_F table directly with explicit date predicates is the recommended alternative.