Search Results short_code_id

Overview

The QA_CHAR_VALUE_LOOKUPS_V view is a Quality (QA) module database object owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented description states that it "shows values assigned to collection element." In practice, the view exposes the list of valid values (lookups) that can be recorded against a specific collection element, which in EBS Quality terminology corresponds to a QA character (a specification or collection characteristic). Each character can have one or more predefined short code values that a user selects when entering quality results.

Because it is a view rather than a table, QA_CHAR_VALUE_LOOKUPS_V provides a read-only, denormalized presentation of quality lookup data. This makes it well suited for reporting, ad hoc queries, and outbound integration extracts. Report developers can join it to quality result tables without needing to resolve multiple foreign keys, since the view already merges the character name onto each value row. The presence of audit columns such as CREATION_DATE, CREATED_BY, and LAST_UPDATE_DATE also supports audit and data-governance reporting.

Underlying Base Objects

The view is defined over two documented base objects, referenced in the ETRM metadata as synonyms:

• QA_CHARS — the QA character master table holding collection element definitions.
• QA_CHAR_VALUE_LOOKUPS — the table storing the individual short code values assigned to each character.

The view text joins these on the CHAR_ID column: WHERE QCVL.CHAR_ID = QC.CHAR_ID. This is an inner join, so only value rows with a matching character are returned. The alias QC supplies the character NAME, while QCVL supplies the value-level attributes such as SHORT_CODE, DESCRIPTION, and SHORT_CODE_ID. The view also selects ROWID from QA_CHAR_VALUE_LOOKUPS, which effectively identifies the underlying base row and can be used for row-level operations against the base table.

Key Columns

• ROW_ID — ROWID of the underlying QA_CHAR_VALUE_LOOKUPS row; unique row identifier.
• SHORT_CODE_ID — the primary key of the lookup value record. This is the column referenced by the user search term and is the identifier to use when joining to other quality tables that store a selected value.
• CHAR_ID — foreign key linking the value to its parent character in QA_CHARS.
• SHORT_CODE — the code or abbreviated value presented to users for selection.
• NAME — the character name from QA_CHARS, denormalized onto each row.
• DESCRIPTION — descriptive text for the individual lookup value.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard EBS audit columns reflecting who created or last modified the value.

Common Use Cases and Queries

Typical uses include validating that collection results reference legitimate short codes, building value lists for quality data entry screens, and extracting lookup definitions for integration or master data management. A common query retrieves all values for a character:

SELECT short_code_id, short_code, description, name
FROM apps.qa_char_value_lookups_v
WHERE char_id = :p_char_id
ORDER BY short_code;

To resolve the meaning of a stored result value, join on SHORT_CODE_ID:

SELECT v.name, v.short_code, v.description
FROM apps.qa_char_value_lookups_v v
WHERE v.short_code_id = :p_short_code_id;

A broader audit query lists lookup values by last update:

SELECT char_id, short_code_id, short_code, name,
      last_update_date, last_updated_by
FROM apps.qa_char_value_lookups_v
ORDER BY last_update_date DESC;

Because the view already joins QA_CHARS and QA_CHAR_VALUE_LOOKUPS, these queries avoid manual joins and reduce reporting complexity. Consumers should note the inner-join behavior: value rows lacking a valid parent character will not appear.