Results for “qa_spec_chars”

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

Overview

QA_SPEC_CHARS is a Quality (QA) module table in Oracle E-Business Suite 12.1.1 and 12.2.2 that defines the association between a quality specification and the individual specification elements (characteristics) that make up that specification. Each row represents one specification element — the assignment of a quality characteristic (a measurable attribute such as pH, viscosity, color, or assay) to a specific specification, together with the target value and the tolerance limits that govern acceptance or rejection of a lot or sample. In practice QA_SPEC_CHARS is the child table of QA_SPECS, which holds the specification header, and the parent-side reference to QA_CHARS, which holds the reusable characteristic definitions. Its role is therefore central to the specification model: it is the table from which the quality data collection and results validation logic derive the expected value and limits for each characteristic being tested against a given specification.

From a Data Vault modeling perspective, the metadata's heuristic classification for QA_SPEC_CHARS is link. This is consistent with its composite primary key (SPEC_ID, CHAR_ID), which naturally expresses a many-to-many association between specifications and characteristics. A warehouse design following Data Vault conventions would typically model SPEC_ID and CHAR_ID as the two hub references joined by this link, with the descriptive attributes carried either on the link satellite or on a dependent satellite keyed to the same composite business key.

Key Information Stored

The table is documented with 32 columns. The most significant are the two foreign key columns that form the composite primary key and business-key candidate:

• SPEC_ID — foreign key to QA_SPECS; identifies the parent specification to which this element belongs.
• CHAR_ID — foreign key to QA_CHARS; identifies the characteristic being specified.
• TARGET_VALUE — the nominal or ideal value the characteristic should attain for the specification.
• UPPER_SPEC_LIMIT / LOWER_SPEC_LIMIT — the specification limits beyond which the material is out of specification.
• UPPER_REASONABLE_LIMIT / LOWER_REASONABLE_LIMIT — the reasonable-range bounds, typically wider than the spec limits, used for alerting or trending.
• UPPER_USER_DEFINED_LIMIT / LOWER_USER_DEFINED_LIMIT — configurable limits available to the customer for supplemental control.
• ENABLED_FLAG — indicates whether the specification element is active and eligible for collection.
• UOM_CODE — the unit of measure applicable to the target value and limits.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — standard EBS Who columns providing audit trail.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the standard EBS descriptive flexfield (DFF) columns.

The primary key constraint is QA_SPEC_CHARS_PK on (SPEC_ID, CHAR_ID). A unique index, QA_SPEC_CHARS_U1, is documented on the same (SPEC_ID, CHAR_ID) columns, confirming that no duplicate association of a characteristic within a single specification is permitted. Because the primary key is composite and fully business-meaningful, there is no separate surrogate key column; SPEC_ID and CHAR_ID together serve as both the primary key and the business-key candidate.

Common Use Cases and Queries

The most common query pattern is a join from QA_SPECS to QA_SPEC_CHARS to QA_CHARS to produce a readable specification report showing each characteristic, its target value, limits, and unit of measure. For example:

• Specification detail report — SELECT s.spec_name, c.char_name, sc.target_value, sc.lower_spec_limit, sc.upper_spec_limit, sc.uom_code FROM qa_spec_chars sc, qa_specs s, qa_chars c WHERE sc.spec_id = s.spec_id AND sc.char_id = c.char_id AND sc.enabled_flag = 'Y'.
• Out-of-specification analysis — compare recorded results against LOWER_SPEC_LIMIT and UPPER_SPEC_LIMIT to flag failing characteristics.
• Characteristic usage audit — WHERE char_id = :char_id against QA_SPEC_CHARS reveals every specification in which a given characteristic is used, supporting impact analysis before changing a characteristic definition.
• Limited-specification migration — queries returning TARGET_VALUE and the four limit columns are used to migrate specification elements between environments or organizations.

Because the DFF columns are present, reporting tools and descriptive flexfield-based inquiries can filter on ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 where customer-specific attributes have been configured.

Related Objects

• QA_SPECS — parent specification header; joined via QA_SPEC_CHARS.SPEC_ID = QA_SPECS.SPEC_ID.
• QA_CHARS — characteristic definition; joined via QA_SPEC_CHARS.CHAR_ID = QA_CHARS.CHAR_ID.
• QA_SPEC_CHARS_PK / QA_SPEC_CHARS_U1 — the primary key constraint and unique index on (SPEC_ID, CHAR_ID).
• Quality results and collection tables (for example QA_RESULTS and related specification-element associations) that reference specification elements to validate recorded values against the limits defined here.
• Standard EBS APIs and concurrent programs within the QA module that create, update, or copy specifications, which write to QA_SPEC_CHARS as part of specification maintenance and specification-set assignment.

Together, QA_SPEC_CHARS functions as the operational junction between the specification definition and the characteristic master, and it is the source of the limits against which quality data is evaluated throughout the Quality module in both 12.1.1 and 12.2.2.