Results for “char_id”

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

Overview

QA_CHAR_ACTION_OUTPUTS is a QA (Quality) module table in the Oracle E-Business Suite schema owned by QA. Its documented description is "Stores mapping between tokens and collection elements." In practice, the table defines the output contract for a character-based quality action: it maps symbolic tokens declared on a QA character action to the specific collection elements (characteristics) that supply values for those tokens at runtime. This makes it a configuration or metadata table rather than a transactional results table; it governs how specification and collection logic parameterises action text, calculations, or generated output.

The ETRM relationship metadata classifies this object heuristically as a link entity in Data Vault terms. That classification reflects its structure: the primary key is composite and is composed of two foreign key columns, making the row an association between a character action and a character rather than an independently identified business entity. It is recommended as a modeling suggestion only, since the heuristic is derived from the foreign-key structure and not from a formally declared Data Vault design.

Key Information Stored

The documented physical schema contains eight columns. The most significant are:

• CHAR_ACTION_ID — Identifier of the parent character action. Part of the composite primary key and a foreign key to QA_CHAR_ACTIONS.
• TOKEN_NAME — The symbolic token being defined or resolved for the action. Part of the composite primary key.
• CHAR_ID — Identifier of the QA character (specification characteristic) bound to the token; foreign key to QA_CHARS.
• LAST_UPDATE_DATE — Audit column recording the most recent modification timestamp.
• LAST_UPDATED_BY — Audit column recording the user who performed the last update.
• CREATION_DATE — Audit column recording row creation timestamp.
• CREATED_BY — Audit column recording the creating user.
• LAST_UPDATE_LOGIN — Audit column recording the login session associated with the last update.

The surrogate primary key is QA_CHAR_ACTION_OUTPUTS_PK, defined as (CHAR_ACTION_ID, TOKEN_NAME). A second unique index, QA_CHAR_ACTION_OUTPUTS_U1, is defined on the identical column pair and is therefore not an independent business-key candidate; both constraints enforce that a single token may be defined only once per character action. The business-key role is effectively carried by the combination of the action and the token name, with CHAR_ID acting as the descriptive attribute identifying the mapped collection element. The audit columns follow standard Oracle EBS WHO-column conventions and are populated automatically by the application and concurrent programs.

Common Use Cases and Queries

Typical usage centres on configuration validation, dependency analysis, and migration or upgrade verification. Quality engineers and implementers query this table to confirm which collection elements drive a given action, and to detect tokens that are defined on an action but reference characteristics that have been disabled or end-dated.

Resolving the collection elements for a specific action:

• SELECT o.char_action_id, o.token_name, o.char_id, c.character_name FROM qa_char_action_outputs o, qa_chars c WHERE o.char_id = c.char_id AND o.char_action_id = :action_id;

Detecting tokens mapped to inactive or invalid characteristics:

• SELECT o.char_action_id, o.token_name, c.char_id, c.character_name, c.disable_date FROM qa_char_action_outputs o, qa_chars c WHERE o.char_id = c.char_id AND (c.disable_date IS NOT NULL OR c.disable_date < SYSDATE);

Auditing recent configuration changes for a release or migration window:

• SELECT char_action_id, token_name, char_id, last_update_date, last_updated_by FROM qa_char_action_outputs WHERE last_update_date >= :from_date ORDER BY last_update_date DESC;

Because the table is configuration data, reporting typically joins it to QA_CHAR_ACTIONS and QA_CHARS to produce documentation of quality action definitions, or extracts it as part of a setup data migration between environments.

Related Objects

• QA_CHAR_ACTIONS — Parent entity; joined on QA_CHAR_ACTION_OUTPUTS.CHAR_ACTION_ID = QA_CHAR_ACTIONS.CHAR_ACTION_ID. Owns the action whose tokens are mapped.
• QA_CHARS — Referenced entity; joined on QA_CHAR_ACTION_OUTPUTS.CHAR_ID = QA_CHARS.CHAR_ID. Supplies the character or collection element bound to each token.
• QA_CHAR_ACTION_OUTPUTS_PK — Primary key constraint on (CHAR_ACTION_ID, TOKEN_NAME).
• QA_CHAR_ACTION_OUTPUTS_U1 — Unique index reinforcing the same column pair.
• QA_SPEC_CHAR_ACTIONS / QA_SPEC_CHARS — Related QA specification characteristic and action definitions commonly queried alongside this table when tracing specification-level quality setup.
• QA_RESULTS and QA_RESULT_VALUES — Downstream transactional tables where collected values for the mapped characters are recorded, and against which token output can be validated.

The linkage through QA_CHAR_ACTIONS and QA_CHARS establishes this table as the configuration bridge between action definitions and character definitions within the Oracle Quality module, and any deletion or change to those parent rows has a direct impact on the integrity of the mappings held here.