Search Results pay_element_class_usages_x




Overview
Explore in AI Chat

Overview

The PAY_ELEMENT_CLASS_USAGES_X view is a public, APPS-owned database object within the Oracle E-Business Suite Payroll (PAY) module. It exposes the currently effective rows of the Element Class Usages entity, which governs the association between an element classification and a payroll run type. In Oracle Payroll, an element classification (such as Earnings, Deductions, or Employer Liabilities) must be linked to one or more run types before the associated elements can be processed in a payroll run. The _X suffix identifies this object as the "date-tracked" or "effective" view, meaning it returns only those class usage records whose effective date range includes the current system date.

Because it filters to the current effective row set, the view is well suited to runtime processing logic, concurrent programs, and reporting that must reflect the state of element class usages "as of today." It shields consumers from the multi-versioned nature of the underlying date-tracked table by presenting a single, unambiguous row per active usage, which simplifies both SQL joins and application-level integration.

Underlying Base Objects

The view is defined over a single documented base object, PAY_ELEMENT_CLASS_USAGES_F, referenced in the ETRM metadata as a synonym owned by APPS. The _F suffix denotes the "full" or "frozen" date-tracked table that stores every version of each element class usage record, keyed by surrogate identifier and bounded by an effective start and end date.

The defining query selects the full column list from the base table and applies a single predicate:

This predicate is the essential behaviour of the view: it collapses the date-tracked history in PAY_ELEMENT_CLASS_USAGES_F down to only the row that is active on the current date. Rows whose effective range has expired, or that have not yet become effective, are excluded. Consumers therefore see the same surrogate ELEMENT_CLASS_USAGE_ID values that exist in the base table, but only for the current effective version of each usage.

Key Columns

The view projects the complete column set of the base table. The most significant columns are:

  • ELEMENT_CLASS_USAGE_ID — the system-generated surrogate primary key uniquely identifying each element class usage record. This is the column most commonly referenced when users search for the identifier.
  • RUN_TYPE_ID — foreign key to the payroll run type to which the classification usage applies.
  • CLASSIFICATION_ID — foreign key to the element classification being associated with the run type.
  • EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — the date-tracked validity window; the view returns only rows where the current date falls within this range.
  • BUSINESS_GROUP_ID — the business group (legislative/organizational) context for the usage.
  • LEGISLATION_CODE — the legislation under which the usage is defined.
  • Standard audit columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE, and OBJECT_VERSION_NUMBER — supporting change tracking and optimistic locking.

Common Use Cases and Queries

The view is typically used to determine which classifications are valid for a given run type, or to retrieve the surrogate identifier of an active usage. A representative query resolving a usage by its identifier is shown below:

  • SELECT element_class_usage_id, run_type_id, classification_id, legislation_code FROM pay_element_class_usages_x WHERE element_class_usage_id = :p_id;
  • SELECT classification_id, run_type_id FROM pay_element_class_usages_x WHERE run_type_id = :p_run_type AND business_group_id = :p_bg;

In integration and conversion routines, the view is often joined to run type and classification reference objects to validate that a usage is currently effective before creating pay elements. Because the view applies a SYSDATE-based filter, applications requiring historical or future-dated usages must query the underlying PAY_ELEMENT_CLASS_USAGES_F table directly.