Search Results qa_char_indexes_u1

Overview

QA.QA_CHAR_INDEXES is a transaction-data table in the Oracle E-Business Suite Quality (QA) schema that stores metadata about user-defined indexes created on collection elements. A collection element, represented by the QA_CHARS entity, defines a measurable or descriptive characteristic that is captured during quality data collection. When users require faster retrieval or specialized query behavior on data associated with a collection element, they may define indexed elements; QA_CHAR_INDEXES records the definition, naming, textual expression, and enabled state of each such user-defined index.

The table resides in the APPS_TS_TX_DATA tablespace with a PCT Free of 10, a typical setting for transactional data that undergoes insert and update activity. Its primary key, QA_CHAR_INDEXES_PK, is defined on CHAR_ID, establishing a one-row-per-collection-element relationship. A unique index, QA_CHAR_INDEXES_U1, is defined on the column pair (CHAR_ID, ENABLED_FLAG). From a Data Vault modeling perspective, this object exhibits satellite-leaning characteristics: it carries descriptive, version-relevant attributes (index name, function text, parameters, enabled flag) that qualify the parent collection element rather than acting as an independent hub or as a pure link between two business entities. Treating it as a satellite hanging off the collection element hub is a reasonable heuristic when reverse-engineering the model.

Key Information Stored

The table contains 15 documented columns. The most significant are summarized below.

• CHAR_ID (NUMBER) — The collection element ID for which a user-defined index exists. This column is the primary key and also participates in the foreign key relationship to QA_CHARS.
• ENABLED_FLAG (NUMBER) — Indicates whether the index definition is active. A value of 1 means enabled; 2 means disabled. This flag is the second column of the unique index QA_CHAR_INDEXES_U1.
• INDEX_NAME (VARCHAR2(30)) — The name of the index as specified by the user.
• DEFAULT_RESULT_COLUMN (VARCHAR2(30)) — The default result column used as the final catch-all parameter in the decode function supporting function-based index behavior.
• TEXT (CLOB, 4000) — The function text used in the function-based index expression.
• ADDITIONAL_PARAMETERS (VARCHAR2(2000)) — Optional user-supplied parameters applied as hints to the create index command.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard Who columns providing audit and ownership context.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — Standard Who columns identifying the concurrent request and program that last touched the row.

The surrogate identity in the physical design is the primary key on CHAR_ID. The business-key candidate surfaced by the unique index is the composite (CHAR_ID, ENABLED_FLAG), which prevents duplicate enabled or disabled states per collection element. The LOB column TEXT is supported by a system-managed LOB index, SYS_IL0000412102C00014$$.

Common Use Cases and Queries

Typical usage centers on administration of function-based indexing for collection elements and on diagnostics of indexing configuration.

• Retrieve all enabled indexes for a collection element: SELECT INDEX_NAME, TEXT FROM QA.QA_CHAR_INDEXES WHERE CHAR_ID = :char_id AND ENABLED_FLAG = 1;
• Audit recently modified index definitions using the Standard Who columns, filtering on LAST_UPDATE_DATE or the concurrent program identifiers.
• Report users who created or disabled index definitions by joining CREATED_BY or LAST_UPDATED_BY to FND_USER.
• Investigate performance issues by reviewing ADDITIONAL_PARAMETERS, since these parameters carry hints applied to the create index command.
• Validate the decode fallback logic by inspecting DEFAULT_RESULT_COLUMN alongside the TEXT expression.

The canonical query pattern remains the documented selection of all 15 columns from QA.QA_CHAR_INDEXES, typically constrained by CHAR_ID and ENABLED_FLAG.

Related Objects

The documented dependency trail identifies QA_CHARS as the referenced parent through the foreign key QA_CHAR_INDEXES.CHAR_ID → QA_CHARS, making it the most direct join target for collection element attributes. Because the table contains Standard Who columns, it also relates to FND_USER, FND_APPLICATION, and FND_CONCURRENT_PROGRAM for ownership and request context. Reporting views and QA collection element setup forms that expose collection element indexing behavior depend upon this table as the source of user-defined index definitions, and the LOB index SYS_IL0000412102C00014$$ is an internal structural dependency supporting the TEXT column.