Search Results qa_in_lists




Overview
Explore in AI Chat

Overview

QA_IN_LISTS is a table in the QA (Quality) product schema of Oracle E-Business Suite, valid in both 12.1.1 and 12.2.2. As documented in the ETRM metadata, it stores "in lists" definitions — the individual element rows that make up collection lists used throughout Oracle Quality. These lists provide the selectable value sets and block-level groupings that drive entry behavior in collection plans, specifications, and quality data collection screens.

The table's heuristic Data Vault classification is standalone, mined from its foreign-key structure. In Data Vault modeling terms this suggests the table is best treated as a satellite-like detail store rather than a hub or link: it holds descriptive attribute rows (the list element value, its parent block, associated value and character identifiers) with no strong outbound FK dependencies captured in the metadata. Its 11-column footprint is narrow and attribute-centric, consistent with a definition/detail table rather than a transactional or relationship entity. Note this classification is a modeling suggestion derived heuristically, not an authoritative Data Vault mapping.

Key Information Stored

The table is defined with a primary key of QA_IN_LISTS_PK, which is enforced on the column LIST_ELEM_ID. This surrogate key uniquely identifies each list element row and is the column referenced by dependent objects.

Two unique indexes document the business-key candidates. QA_IN_LISTS_U1 is defined on LIST_ELEM_ID alone. QA_IN_LISTS_U2 is a composite unique index on LIST_ID, PARENT_BLOCK_NAME, and VALUE, meaning that within a given list and parent block, each element value must be unique. Together these express the natural identity of a list element.

  • LIST_ELEM_ID — surrogate primary key identifying the individual list element.
  • LIST_ID — identifies the parent list to which the element belongs; the primary grouping/join attribute.
  • PARENT_BLOCK_NAME — names the block or grouping context the element is scoped to within the list.
  • VALUE — the stored element value presented or selected in that list context.
  • VALUE_ID — identifier referencing the underlying value (for example, a lookup or coded value) associated with the element.
  • CHAR_ID — character identifier associated with the element, commonly tied to a value/characteristic definition used in Quality setups.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — standard Oracle EBS WHO columns recording audit and accountability information.

Common Use Cases and Queries

Principal use cases involve resolving the valid elements available for a given list, and validating that a collected value is defined for its list and block. Because QA_IN_LISTS is a definition table, it is queried far more often than it is written, and it is typically joined through LIST_ID to the parent list header.

  • Retrieve all elements for a list: SELECT list_elem_id, parent_block_name, value, value_id FROM qa.qa_in_lists WHERE list_id = :p_list_id;
  • Resolve a specific element by its business key: SELECT list_elem_id FROM qa.qa_in_lists WHERE list_id = :p_list_id AND parent_block_name = :p_block AND value = :p_value; — this exploits QA_IN_LISTS_U2.
  • Report list contents with their blocks for setup review, ordered by parent_block_name and value.
  • Validate data-collection input by checking that a submitted value exists as an element for the list and block in use.

Related Objects

The metadata classifies this table as standalone, so no outbound FK relationships are captured; nevertheless, LIST_ID functions as the logical join to the list definition header, and VALUE_ID and CHAR_ID reference value and characteristic definitions. Significant related objects include:

  • The QA list header table (the parent of LIST_ID), which names and describes each list.
  • QA value/characteristic definition tables referenced by VALUE_ID and CHAR_ID.
  • Collection plan and specification setup tables that consume list elements through LIST_ID.
  • Quality data collection and results tables where selected element values are captured.
  • Oracle Quality public APIs and concurrent programs that maintain list definitions.

When referencing these related objects, LIST_ELEM_ID and LIST_ID are the columns most commonly used for joins. Readers should confirm exact table and column names against their instance, as the supplied metadata documents the QA_IN_LISTS schema in detail but leaves related-object names implicit.