Search Results pay_org_pay_method_usages




Overview
Explore in AI Chat

Overview

The PAY_ORG_PAY_METHOD_USAGES view is a date-effective (also known as effective-dated or "date-tracked") reporting object owned by the APPS schema in Oracle E-Business Suite, belonging to the PAY (Payroll) product family. In both release 12.1.1 and 12.2.2, it presents the transactional definitions that associate an organization's payment methods with payrolls, exposing only the row that is valid for the current database session date.

Because Oracle Payroll stores organization payment method usages as effective-dated records, the underlying data may hold many historical, current, and future versions of the same logical association. The view resolves this complexity by filtering on the session effective date, so a query against PAY_ORG_PAY_METHOD_USAGES returns the single valid version of each record as of the current session date. This makes it the standard access point for reporting, concurrent programs, and integrations that need the "as-of-now" picture of how payment methods are assigned to payrolls without writing their own date-range logic. It is documented as VALID in the ETRM repository for release 12.2.2.

Underlying Base Objects

The view is defined in the ETRM metadata as selecting from two referenced objects:

  • PAY_ORG_PAY_METHOD_USAGES_F — the underlying _F (date-effective) base table that stores all versions of the organization payment method usage records, including historical and future-dated rows.
  • FND_SESSIONS — the Applications session table, referenced via a synonym, from which the view derives the effective date used for date-range filtering.

The view text confirms this relationship: it selects the core columns from PAY_ORG_PAY_METHOD_USAGES_F and applies the WHERE clause EFFECTIVE_START_DATE <= (SELECT SS.EFFECTIVE_DATE FROM FND_SESSIONS SS WHERE SS.SESSION_ID = USERENV('SESSIONID')) AND EFFECTIVE_END_DATE >= (SELECT SE.EFFECTIVE_DATE FROM FND_SESSIONS SE WHERE SE.SESSION_ID = USERENV('SESSIONID')). The session effective date is therefore the pivot point: whichever date is registered for the current FND session controls which effective-dated row is returned. The view exposes the _F table's columns directly and does not itself aggregate or join to further tables.

Key Columns

  • ORG_PAY_METHOD_USAGE_ID — primary identifier for the organization payment method usage record. This is the key used for joins and for referencing a specific assignment.
  • EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — the date-effective bounds of the row. Together they define the validity window; a row is returned only when the session effective date falls within this range.
  • PAYROLL_ID — foreign key to the payroll to which the organization payment method is applied. This links the usage to a specific payroll definition.
  • ORG_PAYMENT_METHOD_ID — foreign key to the organization payment method being associated with the payroll.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE — standard Oracle EBS WHO and audit columns recording creation and last-modification metadata for the row.

The pairing of PAYROLL_ID and ORG_PAYMENT_METHOD_ID is the substantive content: it defines which payment method is available for which payroll within the organization. Because the view is date-effective, the returned combination always reflects the configuration valid at the current session date.

Common Use Cases and Queries

Typical uses include identifying the payment methods currently associated with a given payroll, validating configuration during implementations, and driving downstream payment processing or reporting logic that depends on the active organization payment method setup.

To list all currently effective usages with their payroll and payment method identifiers:

  • SELECT org_pay_method_usage_id, payroll_id, org_payment_method_id, effective_start_date, effective_end_date FROM apps.pay_org_pay_method_usages;

To find the payment methods for a specific payroll:

  • SELECT org_payment_method_id FROM apps.pay_org_pay_method_usages WHERE payroll_id = :payroll_id;

Because the view already filters to the session effective date, no additional date predicate is required for as-of-now reporting. Queries are commonly joined to payroll and payment method definition tables using PAYROLL_ID and ORG_PAYMENT_METHOD_ID to resolve descriptive names. In all cases, the result set represents only the effective-dated rows valid at the session date, which is the view's defining behavior.