Search Results qa_char_indexes_pk

Overview

QA_CHAR_INDEXES is a Quality (QA) module table in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented description is "Collection Element User-Defined Indexes," and it keeps track of information about user-defined indexes created on collection elements. In practice, the table stores the definitions of result-oriented indexes that users attach to a collection element (a specification character or "char"), allowing results captured during collection plans to be indexed, filtered, or surfaced through a designated result column rather than being treated as free-form text.

The table resides in the QA schema and carries a primary key constraint QA_CHAR_INDEXES_PK on CHAR_ID. A foreign key defines QA_CHAR_INDEXES.CHAR_ID as a reference to QA_CHARS, tying each index definition to its parent collection element. A unique index, QA_CHAR_INDEXES_U1, is defined on (CHAR_ID, ENABLED_FLAG), which functions as the business-key candidate for this object. Mined from the foreign-key structure, the heuristic Data Vault classification is satellite-leaning: QA_CHAR_INDEXES behaves as a dependent satellite of the QA_CHARS hub, carrying descriptive and configuration attributes keyed by the parent element identifier.

Key Information Stored

The documented physical schema consists of 15 columns. The surrogate primary key is CHAR_ID, which also serves as the foreign key to QA_CHARS; it identifies the parent collection element for which the index is defined.

• CHAR_ID — primary key and foreign key identifying the owning collection element.
• INDEX_NAME — the user-supplied name of the index created on the collection element.
• ENABLED_FLAG — controls whether the index definition is active; combined with CHAR_ID it forms the unique business key QA_CHAR_INDEXES_U1.
• DEFAULT_RESULT_COLUMN — the result column to which index results are directed by default.
• TEXT — the index text or definition expression associated with the element.
• ADDITIONAL_PARAMETERS — supplementary parameters that further qualify the index definition.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — concurrent program context identifying the request and program that created or last modified the record.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — standard EBS audit "Who" columns tracking creation and modification history.

Common Use Cases and Queries

Typical uses center on determining which indexes exist for a collection element, whether they are enabled, and how they feed result columns. A common query retrieves enabled indexes for a given element:

• SELECT char_id, index_name, default_result_column, enabled_flag FROM qa.qa_char_indexes WHERE char_id = :char_id AND enabled_flag = 'Y';
• Reporting on all user-defined indexes with audit context: SELECT index_name, text, additional_parameters, last_update_date, last_updated_by FROM qa.qa_char_indexes WHERE enabled_flag = 'Y';
• Isolating records loaded by a specific concurrent request: SELECT * FROM qa.qa_char_indexes WHERE request_id = :request_id;

These patterns support specification setup verification, index maintenance, and audit of changes made through the Quality collection element and collection plan configuration screens.

Related Objects

• QA_CHARS — parent collection element table; joined on QA_CHAR_INDEXES.CHAR_ID = QA_CHARS.CHAR_ID via the documented foreign key. This is the primary relationship.
• QA_CHAR_INDEXES_PK — primary key constraint over CHAR_ID.
• QA_CHAR_INDEXES_U1 — unique index over (CHAR_ID, ENABLED_FLAG), enforcing the business key.
• FND_CONCURRENT_REQUESTS — referenced by REQUEST_ID for concurrent program context.
• FND_APPLICATION / FND_PROGRAM (concurrent program definitions) — referenced by PROGRAM_APPLICATION_ID and PROGRAM_ID.
• FND_USER — referenced by CREATED_BY and LAST_UPDATED_BY for audit attribution.
• QA_RESULTS / QA_RESULT_VALUES — collection result tables whose indexed access is influenced by the result column defined here.