Results for “qa_spec_chars_val_v”

26 results




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

Overview

The QA_SPEC_CHARS_VAL_V view in the APPS schema is a denormalized reporting object within the Oracle E-Business Suite Quality (QA) module. Its documented purpose in ETRM is to expose "specification and collection elements," combining specification headers, specification-characteristic assignments, characteristic master definitions, and lookup translations into a single queryable structure. The view is registered as VALID in both 12.1.1 and 12.2.2, and is principally used by quality data collection, results entry, and specification inquiry functionality where a flat list of enabled specification elements is required. By resolving status and yes/no flags to their translated meanings through MFG_LOOKUPS, the view delivers presentation-ready data without requiring the calling form or report to perform additional lookup joins.

Underlying Base Objects

The view is defined over four documented objects: QA_SPECS, QA_SPEC_CHARS, QA_CHARS, and MFG_LOOKUPS. The core join links QA_SPEC_CHARS (aliased QSC) to QA_CHARS (QC) on CHAR_ID, and to QA_SPECS (QS) on the condition QSC.SPEC_ID = QS.COMMON_SPEC_ID. This mapping against COMMON_SPEC_ID rather than SPEC_ID reflects the QA specification hierarchy, in which specifications are versioned and share a common identifier across revisions. MFG_LOOKUPS is referenced twice as a non-mandatory (outer-joined) lookup source: once as ML2 to translate the enabled flag through the SYS_YES_NO lookup type, and once as ML3 to translate specification status through the QA_ERES_SPEC_STATUS lookup type.

Key Columns

The view projects identification columns (SPEC_ID, CHAR_ID, SPEC_NAME, CHAR_NAME), effective dating (EFFECTIVE_FROM, EFFECTIVE_TO), and the full set of specification limits: TARGET_VALUE, UPPER_SPEC_LIMIT, LOWER_SPEC_LIMIT, UPPER_REASONABLE_LIMIT, LOWER_REASONABLE_LIMIT, UPPER_USER_DEFINED_LIMIT, and LOWER_USER_DEFINED_LIMIT. Data typing metadata is supplied via DATATYPE and DECIMAL_PRECISION from QA_CHARS. Notably, the unit of measure is coalesced as NVL(QSC.UOM_CODE, QC.UOM_CODE), so the specification-characteristic override takes precedence over the characteristic default; the original characteristic-level value is also retained separately as QSC_UOM_CODE. The SPEC_CHAR_ENABLED flag and its decoded SPEC_CHAR_ENABLED_MEANING, together with SPEC_STATUS and its lookup meaning, provide the status semantics needed for filtering and display. The fifteen ATTRIBUTE columns and ATTRIBUTE_CATEGORY are carried through from QA_SPEC_CHARS for descriptive flexibility.

Common Use Cases and Queries

The view is filtered to enabled rows only, since the definition includes NVL(QSC.ENABLED_FLAG,-1)=1; calls that require disabled elements must query the base table instead. A typical inquiry retrieving the active specification elements for a given specification is:

  • SELECT spec_name, char_name, target_value, upper_spec_limit, lower_spec_limit, uom_code FROM qa_spec_chars_val_v WHERE spec_id = :spec_id ORDER BY char_name;
  • SELECT spec_id, spec_name, char_name, datatype, decimal_precision FROM qa_spec_chars_val_v WHERE spec_char_enabled_meaning = 'Yes';
  • SELECT spec_id, spec_name, spec_status, effective_from, effective_to FROM qa_spec_chars_val_v WHERE SYSDATE BETWEEN NVL(effective_from, SYSDATE) AND NVL(effective_to, SYSDATE);

Because the view already resolves lookup meanings, it is well suited to inbound integration extracts and QA results-entry validations that must determine the valid numeric boundaries for a characteristic before accepting a measured value. Reports and concurrent programs joining specification data to collection plans should prefer this view over the base tables to avoid replicating the COMMON_SPEC_ID join and lookup decoding logic.