Results for “short_code”

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

Overview

QA_CHAR_VALUE_LOOKUPS is a Quality (QA) module table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores the set of permissible values for collection elements. In the QA model, collection elements (also called specification characteristics) are defined in QA_CHARS, and each element may be constrained to a discrete list of valid values. QA_CHAR_VALUE_LOOKUPS holds those discrete value lists, enabling quality specifications to validate that recorded results fall within an approved enumeration rather than an arbitrary free-form entry.

The table resides in the QA schema and is classified as VALID. Its primary key, QA_CHAR_VALUE_LOOKUPS_PK, is composed of CHAR_ID and SHORT_CODE, confirming that a lookup value is uniquely identified by the collection element it belongs to plus the short code assigned to that value. A documented unique index, QA_CHAR_VALUE_LOOKUPS_U1, spans CHAR_ID, SHORT_CODE, and ZD_EDITION_NAME, indicating that the value list is additionally partitioned by a data-vault edition attribute. Based on the foreign-key topology, the heuristic Data Vault classification is satellite-leaning: the table hangs directly off QA_CHARS and describes that parent entity rather than acting as an independent hub or a many-to-many link.

Key Information Stored

The documented schema contains 26 columns. The most important are:

• CHAR_ID — Foreign key to QA_CHARS and the first component of the composite primary key. It ties the lookup value to its parent collection element.
• SHORT_CODE — The distinct value or abbreviation presented as a permissible choice; second component of the primary key.
• SHORT_CODE_ID — A supplementary identifier associated with the short code entry.
• DESCRIPTION — Descriptive text for the lookup value, typically the long or displayed name of the code.
• ZD_EDITION_NAME — Edition designator included in the unique index QA_CHAR_VALUE_LOOKUPS_U1; supports multi-edition or data-vault partitioning of the value list.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — The standard Oracle EBS flexfield-style descriptive columns, available for customer-specific extensions and context-sensitive attributes.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard WHO audit columns capturing insert and update provenance.

The surrogate primary key (CHAR_ID, SHORT_CODE) establishes row identity, while the unique index (CHAR_ID, SHORT_CODE, ZD_EDITION_NAME) functions as the broader business-key candidate when editions are in use.

Common Use Cases and Queries

The primary use case is retrieving the valid value list for a specification element so that result entry or specification validation can be restricted to approved codes. A representative query joins the lookup table to its parent:

• SELECT v.SHORT_CODE, v.DESCRIPTION FROM QA.QA_CHAR_VALUE_LOOKUPS v WHERE v.CHAR_ID = :char_id ORDER BY v.SHORT_CODE; — returns the permissible values for one collection element.
• SELECT c.CHAR_NAME, v.SHORT_CODE, v.DESCRIPTION FROM QA.QA_CHARS c, QA.QA_CHAR_VALUE_LOOKUPS v WHERE c.CHAR_ID = v.CHAR_ID ORDER BY c.CHAR_NAME, v.SHORT_CODE; — produces a complete catalog of elements and their allowed values for configuration review.
• Reporting queries filter on ZD_EDITION_NAME when multiple editions coexist, and on CREATION_DATE or LAST_UPDATE_DATE for change auditing.
• Validation logic verifies that a recorded quality result matches an existing SHORT_CODE for the relevant CHAR_ID before acceptance.

Related Objects

The following objects are the most significant in relation to this table:

• QA_CHARS — Parent table referenced by QA_CHAR_VALUE_LOOKUPS.CHAR_ID; the defining source of collection elements.
• QA_CHAR_VALUE_LOOKUPS_PK — The primary key constraint (CHAR_ID, SHORT_CODE) enforcing row uniqueness.
• QA_CHAR_VALUE_LOOKUPS_U1 — Unique index on CHAR_ID, SHORT_CODE, ZD_EDITION_NAME supporting the business key.
• QA_CHAR_VALUE_LOOKUPS_N1 — Typical non-unique index on the CHAR_ID foreign key used for parent-child joins.
• QA_RESULTS — Stores recorded collection results that are validated against the permissible values held in this table.

Together these objects form the specification-to-result chain in the Oracle Quality module, with QA_CHAR_VALUE_LOOKUPS serving as the controlled vocabulary layer.