Search Results pay_element_class_usages_uk1

Overview

PAY_ELEMENT_CLASS_USAGES_F is a payroll configuration table owned by the HR schema within the PAY (Payroll) product family of Oracle E-Business Suite 12.1.1 and 12.2.2. The table stores the element classification usages associated with a defined payroll run type. In Oracle Payroll, every payroll run operates against a specific run type (for example, a regular payroll run, a reversal, a quick pay, or a prepayment process), and only elements belonging to the classifications permitted for that run type are processed during the run. PAY_ELEMENT_CLASS_USAGES_F records precisely which element classifications are included in each defined run type.

The "_F" suffix identifies this as a date-tracked (datetracked) table, meaning every row carries EFFECTIVE_START_DATE and EFFECTIVE_END_DATE columns and is subject to Oracle Applications date-tracked (DateTrack) logic. Rows are versioned rather than physically overwritten, allowing historical and future-dated configuration changes to coexist. The ETRM metadata classifies this object heuristically as a Data Vault standalone structure — that is, it is not modeled as a hub, link, or satellite in the mined relationship graph, and no foreign-key dependencies to other tables were identified in the source Data Vault mining. In practice it functions as a configuration or reference table whose rows describe the inclusion of an element classification within a run type.

Key Information Stored

The table contains 15 documented columns. The most significant are:

• ELEMENT_CLASS_USAGE_ID — The surrogate primary key that uniquely identifies each element classification usage record. It leads the primary key PAY_ELEMENT_CLASS_USAGES_F_PK.
• EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — The DateTrack effective dating columns that define the period during which a given row version is valid. These participate in both the primary key and the unique index.
• RUN_TYPE_ID — Identifies the payroll run type to which the element classification usage applies. This is the anchor that ties the record to a specific processing run type.
• CLASSIFICATION_ID — Identifies the element classification (for example, earnings, deductions, or information elements) that is permitted within the run type.
• INCLUSION_FLAG — Indicates whether the referenced classification is included in or excluded from the run type, controlling whether elements of that classification are processed.
• BUSINESS_GROUP_ID — The business group that owns the configuration, providing the multi-tenant partitioning used throughout HR and Payroll tables.
• LEGISLATION_CODE — The legislation under which the classification usage is valid, ensuring payroll rules are localized correctly.
• CREATED_BY, CREATION_DATE, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, OBJECT_VERSION_NUMBER — Standard Oracle EBS WHO columns and optimistic locking column, used for audit and concurrency control.
• ZD_EDITION_NAME — The edition name column that supports the online patching (Edition-Based Redefinition) architecture introduced in EBS 12.2.

The documented unique index PAY_ELEMENT_CLASS_USAGES_F_PK covers ELEMENT_CLASS_USAGE_ID, EFFECTIVE_START_DATE, EFFECTIVE_END_DATE, and ZD_EDITION_NAME. The business-key unique index PAY_ELEMENT_CLASS_USAGES_UK1 covers CLASSIFICATION_ID, RUN_TYPE_ID, EFFECTIVE_START_DATE, EFFECTIVE_END_DATE, and BUSINESS_GROUP_ID, which together guarantee that a given classification can appear only once per run type, per business group, per effective date range.

Common Use Cases and Queries

The primary use case is determining which element classifications a given run type will process. A typical query joins classification and run type identifiers to resolve the permitted classifications for a payroll run:

• Querying current valid usages: SELECT ELEMENT_CLASS_USAGE_ID, RUN_TYPE_ID, CLASSIFICATION_ID, INCLUSION_FLAG FROM HR.PAY_ELEMENT_CLASS_USAGES_F WHERE TRUNC(SYSDATE) BETWEEN EFFECTIVE_START_DATE AND EFFECTIVE_END_DATE;
• Resolving the configuration for one run type: filter on RUN_TYPE_ID and BUSINESS_GROUP_ID, applying the effective date range.
• Auditing historical changes: since rows are datetracked, querying without a date filter returns all versions, allowing comparison of prior and current inclusion rules.
• Reporting on legislation-specific configurations by grouping on LEGISLATION_CODE.

Analysts should remember the ZD_EDITION_NAME column in 12.2.2 environments, since edition-aware queries and code must account for the active edition. In 12.1.1 this column is absent, so SQL written for one release may require adjustment for the other.

Related Objects

The documented metadata identifies no explicit foreign-key relationships, so the following related objects reflect functional dependencies within the Payroll module:

• PAY_RUN_TYPES_F — Provides the run type referenced by RUN_TYPE_ID.
• PAY_ELEMENT_CLASSIFICATIONS — Provides the classification referenced by CLASSIFICATION_ID.
• PAY_ELEMENT_CLASS_USAGES — The non-datetracked or public view commonly used by clients to read current date-tracked rows.
• PAY_RUN_TYPES — The non-datetracked counterpart of the run type definition.
• HR_ALL_ORGANIZATION_UNITS — Resolves BUSINESS_GROUP_ID to an organization.
• FND_LANGUAGES / FND_TERRITORIES — Often joined to interpret LEGISLATION_CODE.
• PAY_ELEMENT_CLASS_USAGES_F_PK / PAY_ELEMENT_CLASS_USAGES_UK1 — The primary and unique indexes enforced on the table itself.

No validation API specific to this table is documented; changes are typically applied through Oracle Payroll configuration forms or the underlying datetracked DML patterns used in Payroll setup.