Results for “qa_specs_chars”

6 results




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

Overview

QA.QA_SPECS is the master specification definition table within the Oracle EBS Quality Management (QA) module. It stores the header-level attributes that define a quality specification, together with the entities to which that specification is bound. A specification may be associated with an item, an item-supplier combination, or an item-customer combination, and it may be further constrained by a collection element and value pair commonly referred to as a specification subtype. The specification header carries effective dating so that different rules can apply across time windows, and it participates in a parent-to-child relationship with QA.QA_SPECS_CHARS, which holds the individual specification characteristics and their target values.

From a Data Vault modeling perspective, the mined foreign-key structure classifies QA_SPECS as hub-leaning. The stable business concept — the specification keyed by SPEC_ID — anchors the model, while assignment attributes such as organization, item, vendor, customer, and category behave more like descriptive context than independent hubs. This classification is a heuristic suggestion derived from the FK topology rather than an Oracle-declared design.

Key Information Stored

The table is physically owned by the QA schema and resides in the APPS_TS_TX_DATA tablespace with a PCTFREE of 10. The documented schema in ETRM 12.2.2 exposes 38 columns, of which the most operationally significant are:

The composite unique index QA_SPECS_U3 spans ORGANIZATION_ID, ITEM_ID, ITEM_REVISION, VENDOR_ID, CUSTOMER_ID, CATEGORY_SET_ID, CATEGORY_ID, CHAR_ID, SPEC_ELEMENT_VALUE, and SPEC_ID, and is the business-key candidate that enforces uniqueness of an assignment combination. QA_SPECS_U1 enforces uniqueness on SPEC_ID, and QA_SPECS_N1 provides a non-unique access path on COMMON_SPEC_ID. All indexes reside in APPS_TS_TX_IDX.

Common Use Cases and Queries

Typical usage centers on resolving which specification applies to a given item, supplier, or customer at a point in time, and on joining the header to its characteristic lines. An effective-dated lookup might resemble:

  • SELECT SPEC_ID, SPEC_NAME, ASSIGNMENT_TYPE, EFFECTIVE_FROM, EFFECTIVE_TO FROM QA.QA_SPECS WHERE ORGANIZATION_ID = :org AND ITEM_ID = :item AND TRUNC(SYSDATE) BETWEEN TRUNC(EFFECTIVE_FROM) AND NVL(TRUNC(EFFECTIVE_TO), TRUNC(SYSDATE));
  • Joining to characteristic definitions: SELECT s.SPEC_NAME, c.CHAR_ID, c.* FROM QA.QA_SPECS s, QA.QA_SPECS_CHARS c WHERE s.SPEC_ID = c.SPEC_ID AND s.SPEC_STATUS = 1;
  • Reporting specifications by supplier for incoming inspection planning, filtering on VENDOR_ID and ASSIGNMENT_TYPE.
  • Identifying orphaned or duplicate assignments through the QA_SPECS_U3 column set.
  • Auditing DFF values stored in ATTRIBUTE_CATEGORY and ATTRIBUTE1–15.

Related Objects

The following objects are the most significant dependents and references for QA_SPECS:

  • QA.QA_SPECS_CHARS — child table keyed by SPEC_ID; holds characteristic-level details.
  • QA.QA_RESULTS — references SPEC_ID and stores inspection results gathered against a specification.
  • QA.QA_SPEC_CHARS — references SPEC_ID; defines characteristic rules used in specification evaluation.
  • QA_SPECS_U1, QA_SPECS_U2, QA_SPECS_U3 — unique indexes enforcing the primary key and business-key candidates.
  • QA_SPECS_N1 — non-unique index on COMMON_SPEC_ID.
  • Item, vendor, customer, and category master tables referenced through the ASSIGNMENT_TYPE-driven columns (ITEM_ID, VENDOR_ID, CUSTOMER_ID, CATEGORY_SET_ID, CATEGORY_ID).