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:
- MFG_LOOKUPS (VIEW) — joined twice in the view text, aliased as ML2 and ML3, for the SYS_YES_NO and QA_ERES_SPEC_STATUS lookup types.
- QA_SPECS (SYNONYM) — the specification header, providing SPEC_NAME, EFFECTIVE_FROM, EFFECTIVE_TO, and SPEC_STATUS.
- QA_CHARS (SYNONYM) — the characteristic master, providing NAME, DATATYPE, DECIMAL_PRECISION, and the default UOM_CODE.
- QA_SPEC_CHARS (SYNONYM) — the specification-characteristic intersection holding targets, spec limits, reasonable limits, user-defined limits, and descriptive flexfield attributes.
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
- ROW_ID — the ROWID of the QA_SPEC_CHARS row.
- SPEC_ID / CHAR_ID — specification and characteristic identifiers.
- SPEC_NAME / CHAR_NAME — descriptive names for the specification and characteristic.
- SPEC_STATUS — the specification status value, decoded via lookup type QA_ERES_SPEC_STATUS.
- TARGET_VALUE, UPPER_SPEC_LIMIT, LOWER_SPEC_LIMIT — the nominal target and specification limits.
- UPPER_REASONABLE_LIMIT, LOWER_REASONABLE_LIMIT — reasonable (process) limits.
- UPPER_USER_DEFINED_LIMIT, LOWER_USER_DEFINED_LIMIT — user-defined limits.
- UOM_CODE — NVL of the specification-characteristic UOM and the characteristic default UOM; QSC_UOM_CODE exposes the raw intersection value.
- DATATYPE, DECIMAL_PRECISION — characteristic data type and precision.
- EFFECTIVE_FROM / EFFECTIVE_TO — specification validity window.
- SPEC_CHAR_ENABLED, SPEC_CHAR_ENABLED_MEANING — enabled flag and its SYS_YES_NO meaning.
- ATTRIBUTE_CATEGORY, ATTRIBUTE1–ATTRIBUTE15 — descriptive flexfield context and segments from QA_SPEC_CHARS.
- LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — audit 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.
-
View: QA_SPEC_CHARS_V 12.1.1
Shows specification and collection elements
APPS.QA_SPEC_CHARS_V·↳ MFG_LOOKUPS·↳ QA_CHARS·↳ QA_SPECS·Explore QA module →
-
View: QA_SPEC_CHARS_V 12.2.2
Shows specification and collection elements
APPS.QA_SPEC_CHARS_V·↳ MFG_LOOKUPS·↳ QA_CHARS·↳ QA_SPECS·Explore QA module →
-
VIEW: APPS.QA_SPEC_CHARS_V 12.2.2
-
VIEW: APPS.QA_SPEC_CHARS_V 12.1.1
-
SYNONYM: APPS.QA_SPEC_CHARS 12.2.2
-
SYNONYM: APPS.QA_SPECS 12.2.2
-
SYNONYM: APPS.QA_SPECS 12.1.1
-
12.1.1 DBA Data 12.1.1
-
12.2.2 FND Design Data 12.2.2
-
12.1.1 FND Design Data 12.1.1
-
SYNONYM: APPS.QA_SPEC_CHARS 12.1.1
-
12.2.2 DBA Data 12.2.2
-
SYNONYM: APPS.QA_CHARS 12.2.2
-
SYNONYM: APPS.QA_CHARS 12.1.1
-
PACKAGE BODY: APPS.QLTTRAWB 12.1.1
-
PACKAGE: APPS.QLTTRAWB 12.1.1
-
PACKAGE BODY: APPS.QLTTRAWB 12.2.2
-
PACKAGE: APPS.QLTTRAWB 12.2.2
-
View: QA_CRITERIA_HEADERS_V 12.2.2
Shows chart and Quality Dynamic Reportwriter settings
APPS.QA_CRITERIA_HEADERS_V·↳ FND_LOOKUP_VALUES·↳ MTL_UNITS_OF_MEASURE_TL·↳ QA_CHARS·Explore QA module →
-
View: QA_CRITERIA_HEADERS_V 12.1.1
Shows chart and Quality Dynamic Reportwriter settings
APPS.QA_CRITERIA_HEADERS_V·↳ FND_LOOKUP_VALUES·↳ MTL_UNITS_OF_MEASURE_TL·↳ QA_CHARS·Explore QA module →
-
VIEW: APPS.MFG_LOOKUPS 12.2.2
-
VIEW: APPS.MFG_LOOKUPS 12.1.1
-
APPS.QLTTRAWB SQL Statements 12.1.1
-
APPS.QLTTRAWB SQL Statements 12.2.2
-
eTRM - QA Tables and Views 12.1.1
Define information on applicability of a collection plan for a Quality Collection transaction
-
eTRM - QA Tables and Views 12.2.2
Define information on applicability of a collection plan for a Quality Collection transaction
-
PACKAGE BODY: APPS.QLTTRAWB 12.1.1
-
PACKAGE BODY: APPS.QLTTRAWB 12.2.2
-
12.2.2 DBA Data 12.2.2
-
12.1.1 DBA Data 12.1.1
-
eTRM - INV Tables and Views 12.1.1
-
eTRM - INV Tables and Views 12.2.2
-
eTRM - QA Tables and Views 12.1.1
Define information on applicability of a collection plan for a Quality Collection transaction
-
eTRM - QA Tables and Views 12.2.2
Define information on applicability of a collection plan for a Quality Collection transaction
-
eTRM - INV Tables and Views 12.1.1
-
eTRM - INV Tables and Views 12.2.2