Results for “txn_category_attribute_id”

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

Overview

PQH_SPECIAL_ATTRIBUTES is an HR-schema table within the Public Sector HR (PQH) product family of Oracle E-Business Suite, valid in both 12.1.1 and 12.2.2. The table identifies attributes that perform special functions within the PQH transaction framework, acting as a configuration and metadata registry that maps transaction-category attributes to specific processing behaviors and descriptive flexfield (DDF) column bindings. Rather than storing transactional payload data itself, it governs how other PQH objects interpret and expose their attributes at runtime.

The ETRM metadata classifies this object heuristically as a link in Data Vault modeling terms. This classification is derived from the foreign-key structure: the table sits at the intersection of PQH_TXN_CATEGORY_ATTRIBUTES and PQH_COPY_ENTITY_CONTEXTS, carrying its own descriptive columns alongside those relationships. A link classification is a modeling suggestion only, reflecting the table's role in resolving many-to-many style associations between transaction-category attribute definitions and copy/context definitions.

Key Information Stored

The primary key is a surrogate identifier, SPECIAL_ATTRIBUTE_ID, enforced by the index PQH_SPECIAL_ATTRIBUTES_PK. The documented unique index is composite — PQH_SPECIAL_ATTRIBUTES_PK (SPECIAL_ATTRIBUTE_ID, ZD_EDITION_NAME) — indicating that in the 12.2.2 schema the edition name participates in uniqueness, consistent with the Edition-Based Redefinition (EBR) architecture introduced in EBS 12.2.

The most significant columns are:

• SPECIAL_ATTRIBUTE_ID — surrogate primary key for the special-attribute definition.
• TXN_CATEGORY_ATTRIBUTE_ID — foreign key to PQH_TXN_CATEGORY_ATTRIBUTES, tying the special function to a specific transaction-category attribute.
• CONTEXT — foreign key to PQH_COPY_ENTITY_CONTEXTS, providing the contextual scope in which the special attribute applies.
• ATTRIBUTE_TYPE_CD and KEY_ATTRIBUTE_TYPE — code columns that classify the attribute's behavior and its role as a key attribute.
• DDF_COLUMN_NAME and DDF_VALUE_COLUMN_NAME — physical column bindings for the descriptive flexfield storage associated with the attribute.
• FLEX_CODE — the flexfield reference used to resolve the attribute's flexfield definition.
• ENABLE_FLAG — controls whether the special-attribute definition is active.
• OBJECT_VERSION_NUMBER — optimistic locking column used by the framework during concurrent DML.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard Who-column audit trail.
• ZD_EDITION_NAME — EBR edition discriminator, part of the composite unique key.

Common Use Cases and Queries

The table is queried primarily during PQH configuration and diagnostics work. A typical lookup resolves the special attributes for a given transaction-category attribute:

• SELECT SPECIAL_ATTRIBUTE_ID, ATTRIBUTE_TYPE_CD, KEY_ATTRIBUTE_TYPE, FLEX_CODE FROM HR.PQH_SPECIAL_ATTRIBUTES WHERE TXN_CATEGORY_ATTRIBUTE_ID = :attr_id AND ENABLE_FLAG = 'Y';
• Joining to PQH_TXN_CATEGORY_ATTRIBUTES to report which transaction categories use flexfield-bound special attributes.
• Filtering on ZD_EDITION_NAME when validating configuration in parallel 12.2 editions.
• Auditing active versus inactive bindings with an ENABLE_FLAG predicate for release or migration checks.

Reporting use cases include configuration inventory reports, flexfield binding impact analysis before patch application, and reconciliation between editions after an online patching cycle.

Related Objects

• PQH_TXN_CATEGORY_ATTRIBUTES — parent table joined via PQH_SPECIAL_ATTRIBUTES.TXN_CATEGORY_ATTRIBUTE_ID; supplies the attribute definition context.
• PQH_COPY_ENTITY_CONTEXTS — joined via PQH_SPECIAL_ATTRIBUTES.CONTEXT; provides the entity-copy context scope.
• PQH_SPECIAL_ATTRIBUTES_PK — the primary/unique index on SPECIAL_ATTRIBUTE_ID and ZD_EDITION_NAME.
• HR schema flexfield objects — the DDF_COLUMN_NAME, DDF_VALUE_COLUMN_NAME, and FLEX_CODE columns reference the application's descriptive flexfield infrastructure.
• Public Sector HR transaction-processing APIs — consume this table to determine which attributes require special handling during transaction execution.

Because the table is narrow (16 documented columns) and configuration-oriented, its row count is typically small, and it is best treated as reference metadata rather than transactional data.