Search Results pay_ele_tmplt_class_usages




Overview
Explore in AI Chat

Overview

PAY_ELE_TMPLT_CLASS_USAGES is a Payroll (PAY) module table owned by the HR schema in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented description is "Element Templates and Classifications." The table functions as the mapping store that ties a payroll element template (TEMPLATE_ID) to the classification (CLASSIFICATION_ID) applied to element entries created from that template, and it carries the display and informational attributes that govern how the classified element behaves in entry, costing, and reporting flows.

The documented primary key is the surrogate identifier ELE_TEMPLATE_CLASSIFICATION_ID, defined through PAY_ELE_TMPLT_CLASS_USAGES_PK. Under the supplied heuristic Data Vault classification, this object is modeled as a standalone structure rather than a hub, link, or satellite. That classification suggests the table is treated as a self-contained reference/configuration entity in a analytical or integration model, with its own business key rather than forming a relationship between two other core hubs. In 12.2.2 the object includes the ZD_EDITION_NAME column, consistent with the edition-based redefinition architecture introduced in that release, and the table carries 37 documented columns overall.

Key Information Stored

Two business-key candidates are documented as unique indexes. PAY_ELE_TMPLT_CLASS_USAGES_PK covers the surrogate key ELE_TEMPLATE_CLASSIFICATION_ID together with ZD_EDITION_NAME, while PAY_ELE_TMPLT_CLASS_USAGES_UK2 uniquely identifies the combination of CLASSIFICATION_ID, TEMPLATE_ID, and ZD_EDITION_NAME. The UK2 index is the meaningful business key: it enforces that a given template may be associated with a given classification only once per edition.

The most significant columns include:

  • ELE_TEMPLATE_CLASSIFICATION_ID — the surrogate primary key for the row.
  • TEMPLATE_ID — identifies the element template to which the classification usage applies.
  • CLASSIFICATION_ID — identifies the classification being applied to that template.
  • DISPLAY_PROCESS_MODE — controls how the processing mode is presented when the template is used.
  • DISPLAY_ARREARAGE — controls display behavior relating to arrears processing.
  • ELE_TMPLT_CLASS_INFO_CATEGORY — categorizes the supporting classification information.
  • ELE_TMPLT_CLASS_INFO1 through ELE_TMPLT_CLASS_INFO30 — a thirty-column repeating set of descriptive attributes (the documented columns include INFO1–INFO30) that store classification-specific detail values attached to the template usage.
  • ZD_EDITION_NAME — the edition identifier that participates in the primary and unique keys, used by the 12.2.2 edition-based redefinition model.

Common Use Cases and Queries

The table is typically queried to answer which classifications a template supports, and what information values are stored for each. A join to the template and classification setup tables is the common pattern:

  • Template classification inventory: SELECT TEMPLATE_ID, CLASSIFICATION_ID, DISPLAY_PROCESS_MODE, DISPLAY_ARREARAGE FROM PAY_ELE_TMPLT_CLASS_USAGES WHERE TEMPLATE_ID = :template_id ORDER BY CLASSIFICATION_ID.
  • Duplicate or edition check: query the UK2 business key — CLASSIFICATION_ID with TEMPLATE_ID and ZD_EDITION_NAME — to confirm intended uniqueness after data loads or upgrades.
  • Extract of classification info attributes: projects ELE_TMPLT_CLASS_INFO1 through ELE_TMPLT_CLASS_INFO30 for a given category (ELE_TMPLT_CLASS_INFO_CATEGORY) for conversion or interface feeds.
  • Display-rule reporting: filter rows by DISPLAY_PROCESS_MODE or DISPLAY_ARREARAGE to audit how classifications render in element entry.

Because the table is a configuration reference rather than transactional data, queries are generally small in volume and can safely be joined against template and classification metadata.

Related Objects

The metadata documents the table as standalone in the Data Vault sense, without foreign keys mined to other objects. The strongest documented relationships are the unique business-key join below, supplemented by standard Payroll element setup objects that reference TEMPLATE_ID and CLASSIFICATION_ID:

  • PAY_ELE_TMPLT_CLASS_USAGES_PK — primary key index on ELE_TEMPLATE_CLASSIFICATION_ID and ZD_EDITION_NAME.
  • PAY_ELE_TMPLT_CLASS_USAGES_UK2 — unique index on CLASSIFICATION_ID, TEMPLATE_ID, ZD_EDITION_NAME, the principal join for template-to-classification lookups.
  • Element template objects referencing TEMPLATE_ID, which identify the template context of each usage row.
  • Classification definition objects referencing CLASSIFICATION_ID, which supply the classification detail.
  • Payroll element/classification setup tables that share the ELE_TMPLT_CLASS_INFO attribute pattern for storing classification-specific values.