Results for “qa_spec_chars_v”

38 results




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

Overview

The APPS.QA_SPEC_CHARS_V view is a denormalized reporting and integration object within the Oracle E-Business Suite Quality (QA) module. It presents specification characteristics — that is, the individual collection elements that make up a quality specification — alongside the parent specification header and the characteristic definition itself. In EBS 12.1.1 and 12.2.2, this view is commonly used to build quality data extracts, custom inquiry screens, LIMS integrations, and reporting on specification limits and acceptance criteria.

The view carries a recorded status of VALID in the APPS schema. Its defining characteristic is the join across the specification header, the specification-characteristic intersection, and the characteristic master definition, together with decoded lookup values for enabled flags and specification status. Because the underlying intersections reference a common specification identity, the view effectively flattens the specification model into a single row per specification/characteristic combination.

Underlying Base Objects

Per the documented metadata, QA_SPEC_CHARS_V is defined over the following referenced base objects:

Joins: QSC.CHAR_ID = QC.CHAR_ID; QSC.SPEC_ID = QS.COMMON_SPEC_ID; a DECODE on QSC.ENABLED_FLAG maps to ML2 LOOKUP_CODE for 'SYS_YES_NO'; and an outer join (ML3, '+') links QS.SPEC_STATUS to 'QA_ERES_SPEC_STATUS'. Note the outer-join syntax used is the Oracle legacy (+) form supported in both 12.1.1 and 12.2.2.

Key Columns

Common Use Cases and Queries

The view is typically used to report specification limits or to identify specifications by status. Filtering on SPEC_STATUS often involves decoding the status with the same lookup the view references.

Example: list active specification characteristics with limits.

  • SELECT spec_name, char_name, target_value, upper_spec_limit, lower_spec_limit, uom_code FROM qa_spec_chars_v WHERE spec_char_enabled = 1 ORDER BY spec_name, char_name;

Example: retrieve specifications by status meaning.

  • SELECT v.spec_id, v.spec_name, v.spec_status, l.meaning FROM qa_spec_chars_v v, mfg_lookups l WHERE l.lookup_type = 'QA_ERES_SPEC_STATUS' AND l.lookup_code = v.spec_status AND l.meaning = '&spec_status';

Because the view carries no filters of its own beyond the joins, callers should restrict by SPEC_ID, SPEC_NAME, or status to avoid full-table scans in high-volume environments.