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:
- PAY_ORG_PAYMENT_METHODS_F — the date-effective (F) table holding the dated records, including the effectivity dates, descriptive flexfield attributes, the key flexfield information columns (PMETH_INFORMATION1 through PMETH_INFORMATION20), and the system name.
- PAY_ORG_PAYMENT_METHODS_F_TL — the translation (TL) table providing the language-specific
ORG_PAYMENT_METHOD_NAME.
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
- ORG_PAYMENT_METHOD_ID — unique identifier of the organization payment method; the join key between the F and TL tables.
- EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — the date range for which the record is active.
- BUSINESS_GROUP_ID — the business group that owns the payment method.
- ORG_PAYMENT_METHOD_NAME — the language-appropriate name from the translation table.
- SYSTEM_ORG_PAY_METHOD_NAME — the seeded system name (aliased from the F table's
ORG_PAYMENT_METHOD_NAME) used for predefined methods. - CURRENCY_CODE — the currency associated with the payment method.
- PAYMENT_TYPE_ID, EXTERNAL_ACCOUNT_ID, DEFINED_BALANCE_ID, COMMENT_ID — references to the payment type, external account, defined balance, and comment associated with the method.
- ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE20 — descriptive flexfield context and segment values.
- PMETH_INFORMATION_CATEGORY and PMETH_INFORMATION1–PMETH_INFORMATION20 — key flexfield context and segment values.
- CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit 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_IDFROM APPS.PAY_ORG_PAYMENT_METHODS_XWHERE BUSINESS_GROUP_ID = :p_business_group_idORDER 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_INFORMATION1FROM APPS.PAY_ORG_PAYMENT_METHODS_XWHERE 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.
-
View: PAY_ORG_PAYMENT_METHODS_X
12.1.1
owner:APPS, object_type:VIEW, fnd_design_data:PAY.PAY_ORG_PAYMENT_METHODS_X, object_name:PAY_ORG_PAYMENT_METHODS_X, status:VALID, product: PAY - Payroll , description: Date-effective view. , implementation_dba_data: APPS.PAY_ORG_PAYMENT_METHODS_X ,
-
View: PAY_ORG_PAYMENT_METHODS_X
12.2.2
owner:APPS, object_type:VIEW, fnd_design_data:PAY.PAY_ORG_PAYMENT_METHODS_X, object_name:PAY_ORG_PAYMENT_METHODS_X, status:VALID, product: PAY - Payroll , description: Date-effective view. , implementation_dba_data: APPS.PAY_ORG_PAYMENT_METHODS_X ,
-
VIEW: APPS.HRFV_PAYROLLS
12.1.1
-
SYNONYM: PUBLIC.PAY_ORG_PAYMENT_METHODS_X
12.1.1
owner:PUBLIC, object_type:SYNONYM, object_name:PAY_ORG_PAYMENT_METHODS_X, status:VALID,
-
VIEW: APPS.HRFV_PAYROLLS
12.2.2
-
View: HRFV_PAYROLLS
12.2.2
owner:APPS, object_type:VIEW, fnd_design_data:PER.HRFV_PAYROLLS, object_name:HRFV_PAYROLLS, status:VALID, product: PER - Human Resources , description: Business view template from which the flexfield view is generated. , implementation_dba_data: APPS.HRFV_PAYROLLS ,
-
View: HRFV_PAYROLLS
12.1.1
owner:APPS, object_type:VIEW, fnd_design_data:PER.HRFV_PAYROLLS, object_name:HRFV_PAYROLLS, status:VALID, product: PER - Human Resources , description: Business view template from which the flexfield view is generated. , implementation_dba_data: APPS.HRFV_PAYROLLS ,
-
SYNONYM: APPS.PAY_ORG_PAYMENT_METHODS_F_TL
12.1.1
owner:APPS, object_type:SYNONYM, object_name:PAY_ORG_PAYMENT_METHODS_F_TL, status:VALID,
-
VIEW: APPS.HRFV_PAYROLLS
12.1.1
owner:APPS, object_type:VIEW, fnd_design_data:PER.HRFV_PAYROLLS, object_name:HRFV_PAYROLLS, status:VALID,
-
VIEW: APPS.HRFV_PAYROLLS
12.2.2
owner:APPS, object_type:VIEW, fnd_design_data:PER.HRFV_PAYROLLS, object_name:HRFV_PAYROLLS, status:VALID,
-
VIEW: APPS.PAY_ORG_PAYMENT_METHODS_X
12.1.1
owner:APPS, object_type:VIEW, fnd_design_data:PAY.PAY_ORG_PAYMENT_METHODS_X, object_name:PAY_ORG_PAYMENT_METHODS_X, status:VALID,
-
SYNONYM: APPS.PAY_ORG_PAYMENT_METHODS_F_TL
12.2.2
owner:APPS, object_type:SYNONYM, object_name:PAY_ORG_PAYMENT_METHODS_F_TL, status:VALID,
-
VIEW: APPS.PAY_ORG_PAYMENT_METHODS_X
12.2.2
owner:APPS, object_type:VIEW, fnd_design_data:PAY.PAY_ORG_PAYMENT_METHODS_X, object_name:PAY_ORG_PAYMENT_METHODS_X, status:VALID,
-
SYNONYM: APPS.PAY_ORG_PAYMENT_METHODS_F
12.1.1
owner:APPS, object_type:SYNONYM, object_name:PAY_ORG_PAYMENT_METHODS_F, status:VALID,
-
SYNONYM: APPS.PAY_ORG_PAYMENT_METHODS_F
12.2.2
owner:APPS, object_type:SYNONYM, object_name:PAY_ORG_PAYMENT_METHODS_F, status:VALID,
-
12.2.2 DBA Data
12.2.2
-
12.1.1 DBA Data
12.1.1
-
12.2.2 FND Design Data
12.2.2
-
12.1.1 FND Design Data
12.1.1
-
12.1.1 DBA Data
12.1.1
-
12.2.2 DBA Data
12.2.2
-
eTRM - PAY Tables and Views
12.1.1
description: Temporary table used to hold invalid location addresses. ,
-
12.1.1 DBA Data
12.1.1
-
eTRM - PAY Tables and Views
12.2.2
description: Temporary table used to hold invalid location addresses. ,
-
eTRM - PER Tables and Views
12.2.2
description: Table to store NQF Training info for a person ,
-
eTRM - PER Tables and Views
12.1.1
description: Table to store NQF Training info for a person ,
-
eTRM - PAY Tables and Views
12.1.1
description: Temporary table used to hold invalid location addresses. ,
-
eTRM - PAY Tables and Views
12.2.2
description: Temporary table used to hold invalid location addresses. ,
-
eTRM - PER Tables and Views
12.2.2
description: Table to store NQF Training info for a person ,
-
eTRM - PER Tables and Views
12.1.1
description: Table to store NQF Training info for a person ,