Results for “qa_in_lists_v”

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

Overview

QA_IN_LISTS_V is a reporting view in the Oracle E-Business Suite Quality (QA) module, owned by the APPS schema and shipped in a VALID state in both 12.1.1 and 12.2.2. The view exposes the collection values that populate the "in list" operator used by Quality character definitions (QA_CHARS). In Oracle Quality, a specification or collection element can be validated against a predefined list of acceptable values rather than a free-form entry. The inlist mechanism is the vehicle that stores and evaluates those discrete value sets, and QA_IN_LISTS_V is the read-only interface through which report writers, forms, and integration routines retrieve them.

The view performs a join between the list-element storage table (QA_IN_LISTS) and the character definition table (QA_CHARS), enriching each stored list element with the descriptive attributes of its parent character: the character name, its datatype, decimal precision, whether any values currently exist, and critically the SQL_STRING_FLAG. Because the view is built on the APPS synonyms QA_IN_LISTS and QA_CHARS, it respects the standard EBS security model and multiorg behavior configured on those base tables. It is consequently a stable, upgrade-tolerant access point for list data, avoiding direct dependence on the underlying table columns.

Underlying Base Objects

The ETRM metadata records two referenced base objects, both accessed through APPS synonyms: QA_CHARS and QA_IN_LISTS. QA_CHARS defines the individual quality characteristics (collection elements) and carries the datatype and validation rules applied to each. QA_IN_LISTS stores one row per value belonging to a list, keyed by LIST_ID and LIST_ELEM_ID, and links back to the owning character through CHAR_ID. The view joins these on QIL.CHAR_ID = QC.CHAR_ID, so every list element inherits its character-level metadata. The SQL_STRING_FLAG is derived with a DECODE on QC.SQL_VALIDATION_STRING, translating a non-null SQL validation string into 'Y' and a null into 'N'.

Key Columns

• ROW_ID — the ROWID of the QA_IN_LISTS row, useful for identifying the physical list-element record.
• LIST_ELEM_ID — primary identifier of the individual value within the list.
• LIST_ID — identifies the parent inlist to which the value belongs, grouping related values together.
• VALUE / VALUE_ID — the actual list entry and its associated value identifier used for validation matching.
• CHAR_ID / CHAR_NAME — the owning quality character and its human-readable name.
• DATATYPE / DECIMAL_PRECISION — the data type and, for numeric characters, the number of decimal places applied to the list value.
• VALUES_EXIST_FLAG — indicates whether valid list values currently exist for the character.
• SQL_STRING_FLAG — 'Y' where a SQL validation string is defined for the character, 'N' otherwise; this is the column of interest in the user's search.
• Audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN provide standard EBS who/when tracking.

Common Use Cases and Queries

Typical uses include reporting on the allowed values for each quality character, validating configuration during implementations, and identifying characters that rely on SQL-based validation versus static lists.

List values for a character:

SELECT char_name, value, value_id
FROM   qa_in_lists_v
WHERE  char_name = :character
ORDER  BY value;

Identifying SQL-validated characters:

SELECT DISTINCT char_name, sql_string_flag
FROM   qa_in_lists_v
WHERE  sql_string_flag = 'Y';

Auditing list configuration for a block or datatype:

SELECT parent_block_name, char_name, datatype, value
FROM   qa_in_lists_v
WHERE  values_exist_flag = 'Y';