Results for “pay_org_pay_method_usages_pk”

14 results




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

Overview

HR.PAY_ORG_PAY_METHOD_USAGES_F is a DateTracked transactional table in the Oracle E-Business Suite HR schema. It stores the effective-dated association between a payroll and the organizational payment methods that are permitted for use as personal payment methods by assignments processed on that payroll. In effect, it controls which payment methods an employee may select when defining a personal payment method for a given payroll, and it is the configuration layer that precedes the assignment-level payment method rows held in PAY_PERSONAL_PAYMENT_METHODS_F.

The table is registered in FND Design Data as PAY.PAY_ORG_PAY_METHOD_USAGES_F and resides in the APPS_TS_TX_DATA tablespace with PCT Free 10. It is a VALID object in both Oracle EBS 12.1.1 and 12.2.2. The ETRM metadata classifies this object heuristically as a standalone entity under the Data Vault lens, meaning it is best modeled as a hub-like reference entity rather than a dependent satellite tied to an assignment or person. The presence of its own surrogate identifier and effective-dating columns reinforces this interpretation, as the row's identity is self-contained and does not derive from a parent transaction.

Key Information Stored

The table carries ten documented columns. The most significant are the following:

The primary key PAY_ORG_PAY_METHOD_USAGES_PK is composed of ORG_PAY_METHOD_USAGE_ID, EFFECTIVE_START_DATE, and EFFECTIVE_END_DATE, reflecting Oracle DateTrack convention. The business-key candidate — the combination that logically identifies a usage independent of the surrogate — is best understood as PAYROLL_ID plus ORG_PAYMENT_METHOD_ID within an effective date range; the ETRM metadata lists only the PK as a unique index, and the two remaining indexes are non-unique.

Common Use Cases and Queries

Typical use cases include auditing which payment methods are enabled for a payroll, validating that an employee's chosen payment method is permitted, and reporting on payment method configuration over time.

A basic extraction against current effective rows:

  • SELECT ORG_PAY_METHOD_USAGE_ID, EFFECTIVE_START_DATE, EFFECTIVE_END_DATE, PAYROLL_ID, ORG_PAYMENT_METHOD_ID FROM HR.PAY_ORG_PAY_METHOD_USAGES_F WHERE TRUNC(SYSDATE) BETWEEN EFFECTIVE_START_DATE AND EFFECTIVE_END_DATE;

A join to resolve payroll and payment method names for reporting:

  • SELECT p.PAYROLL_NAME, m.ORG_PAYMENT_METHOD_NAME, u.EFFECTIVE_START_DATE, u.EFFECTIVE_END_DATE FROM HR.PAY_ORG_PAY_METHOD_USAGES_F u JOIN HR.PAY_PAYROLLS p ON p.PAYROLL_ID = u.PAYROLL_ID JOIN HR.PAY_ORG_PAYMENT_METHODS m ON m.ORG_PAYMENT_METHOD_ID = u.ORG_PAYMENT_METHOD_ID WHERE TRUNC(SYSDATE) BETWEEN u.EFFECTIVE_START_DATE AND u.EFFECTIVE_END_DATE;

A historical as-of query using DateTrack semantics:

  • SELECT * FROM HR.PAY_ORG_PAY_METHOD_USAGES_F WHERE PAYROLL_ID = :payroll_id AND :as_of_date BETWEEN EFFECTIVE_START_DATE AND EFFECTIVE_END_DATE;

Because PAY_ORG_PAY_METHOD_USAGES_N1 and _N2 index PAYROLL_ID and ORG_PAYMENT_METHOD_ID respectively, filters on either column benefit from index access, while the PK index supports precise lookups by usage identifier and effective range.

Related Objects

The table participates in a compact set of relationships anchored by its two foreign keys:

  • HR.PAY_PAYROLLS — joined on PAYROLL_ID; the parent payroll definition.
  • HR.PAY_ORG_PAYMENT_METHODS — joined on ORG_PAYMENT_METHOD_ID; the organizational payment method definition.
  • HR.PAY_PERSONAL_PAYMENT_METHODS_F — assignment-level payment method rows that reference the organizational methods enabled here.
  • HR.PAY_ASSIGNMENT_ACTIONS and assignment-related entities — context for how payment methods apply to assignments on the payroll.
  • FND_USER and FND_LOGINS — referenced through the standard Who columns for auditing.

No formal foreign keys from downstream tables into this object are documented in the ETRM extract, so the object is presented as standalone; joins are driven principally by PAYROLL_ID and ORG_PAYMENT_METHOD_ID.