Search Results pay_org_pay_method_usages_f




Overview
Explore in AI Chat

Overview

PAY_ORG_PAY_METHOD_USAGES_F is a dated (effective-dated) table in the HR schema of Oracle E-Business Suite, belonging to the Payroll (PAY) product family. It stores the payment methods that are available to assignments on a specific payroll. In practical terms, it defines, for a given payroll, which organizational payment methods an employee assignment may select or be paid through, which is a prerequisite for generating valid payment instructions during a payroll run.

The table is implemented as a datable (non-"_ALL") entity, which means it is not partitioned by a business group or legislation column in the documented column set; the standard EBS datable pattern (EFFECTIVE_START_DATE / EFFECTIVE_END_DATE plus WHO audit columns) governs row validity. Based on the mined foreign-key and structure heuristics, the ETRM relationship data classifies this object as standalone, suggesting it behaves as a reference/lookup table rather than a transactional link or a pure dependent satellite. From a Data Vault modeling perspective, this would most naturally be modeled as a satellite attached to a hub (the payment method usage), because it carries descriptive attributes (the effective dates, payroll, and payment method references) that change over time; the surrogate identifier ORG_PAY_METHOD_USAGE_ID anchors the entity while the effective dating captures history.

Key Information Stored

The documented physical schema in ETRM 12.2.2 contains 10 columns. The most significant are:

  • ORG_PAY_METHOD_USAGE_ID — the surrogate primary key component that uniquely identifies a payment-method usage record (combined with effective dates).
  • EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — the date range during which the payment method is valid for the payroll; these form the temporal boundary of the business key.
  • PAYROLL_ID — references the payroll to which the available payment methods apply.
  • ORG_PAYMENT_METHOD_ID — references the organizational payment method being made available.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE — the standard WHO audit columns that record who created and last changed the row and when.

The primary key PAY_ORG_PAY_METHOD_USAGES_PK is defined on (ORG_PAY_METHOD_USAGE_ID, EFFECTIVE_START_DATE, EFFECTIVE_END_DATE). The unique index documented as the business-key candidate is the same PK index, meaning the surrogate ORG_PAY_METHOD_USAGE_ID together with the effective-dating columns serves as both the technical and the candidate business key. The Payroll and Org Payment Method identifiers act as the principal foreign-key join points, even though the heuristic classifier flagged the table as standalone.

Common Use Cases and Queries

This object is primarily consumed when validating whether an employee's assignment may use a particular payment method for a given payroll, and when presenting the list of permitted payment methods in self-service or payroll administration flows. Typical usage includes:

  • Enumerating the active payment methods for a payroll as of a run date.
  • Checking that a proposed payment method is authorized for the payroll before creating a payment.
  • Reconciling payroll payment configuration across effective-dated changes.

A representative query against the current effective set:

SELECT p.PAYROLL_ID, m.ORG_PAYMENT_METHOD_ID
FROM   HR.PAY_ORG_PAY_METHOD_USAGES_F m,
       HR.PAY_PAYROLLS_F p
WHERE  m.PAYROLL_ID = p.PAYROLL_ID
AND    SYSDATE
       BETWEEN m.EFFECTIVE_START_DATE
       AND     NVL(m.EFFECTIVE_END_DATE, SYSDATE);

For historical reporting, omit the SYSDATE predicate and filter on the effective range that matches the payroll period in question. Because the table is datable, reports should always include the effective-date predicates to avoid returning multiple historical versions of the same usage record.

Related Objects

The table connects principally to payroll and payment method configuration. Significant related objects include:

  • PAY_PAYROLLS_F (join on PAYROLL_ID) — defines the payroll to which the payment methods are attached.
  • PAY_ORG_PAYMENT_METHODS_F (join on ORG_PAYMENT_METHOD_ID) — the organizational payment method definitions.
  • PAY_ORG_PAY_METHOD_USAGES_PK — the primary key constraint enforcing uniqueness across the effective dates.
  • PAY_ASSIGNMENT_PAY_METHODS / PAY_PERSONAL_PAYMENT_METHODS — assignment and personal payment method records that consume the availability rules defined here.
  • PAY_PAYROLL_ACTIONS — payroll run actions where the permitted payment methods are applied during processing.

Together these objects allow the payroll module to determine, for any effective date, exactly which payment methods are valid for each payroll and, by extension, for the assignments processed through it.