Results for “quality_specification”

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

Overview

APPS.QABV_QUALITY_SPECIFICATIONS is a read-only Oracle E-Business Suite view that presents quality specification definitions maintained within the Oracle Quality module. The view flattens the central specification header table (QA_SPECS) and enriches each row with the descriptive meaning of its assignment type, resolved through the QA_SPEC_TYPE lookup held in MFG_LOOKUPS. In the EBS 12.1.1 and 12.2.2 data models the object is documented under the APPS schema and is exposed as a preformatted, read-only view (the source text concludes with "WITH READ ONLY"), meaning it supports query and reporting activity but not DML.

The view serves as a stable, denormalized reporting interface over specification metadata. Rather than requiring report authors and integration developers to join QA_SPECS to the lookup table and decode lookup codes themselves, the view supplies human-readable assignment type meanings and consistent column aliases. This makes it suitable for quality dashboards, specification audits, and inbound/outbound interface extracts that must identify which specifications apply to a given item, item revision, vendor, customer, category, or organization.

Underlying Base Objects

The view is defined over two documented base objects:

• QA_SPECS (SYNONYM) — the primary source, aliased as QUALITY_SPECIFICATION. This holds the specification header records, including identity, effective dating, assignment context, and element/subtype references.
• MFG_LOOKUPS (VIEW) — the lookup source, aliased as MF, filtered to LOOKUP_TYPE = 'QA_SPEC_TYPE' and joined on LOOKUP_CODE = QA_SPECS.ASSIGNMENT_TYPE.

The join is an inner-style equality predicate on the lookup code, so a specification row is returned only when a matching QA_SPEC_TYPE lookup exists. Because the view is read-only, it cannot be used as a DML target; modifications must be performed against QA_SPECS and its related specification tables through the supported Oracle Quality APIs or forms.

Key Columns

• SPECIFICATION_ID — alias of QA_SPECS.SPEC_ID, the primary specification identifier.
• SPECIFICATION_NAME — alias of SPEC_NAME, the user-defined specification name.
• START_EFFECTIVE_DATE / END_EFFECTIVE_DATE — the effective-from and effective-to dates controlling specification validity.
• ASSIGNMENT_TYPE — the decoded lookup meaning indicating how the specification is assigned (for example, to an item or organization).
• SUBTYPE_ELEMENT_ID / SUBTYPE_ELEMENT_VALUE — alias of CHAR_ID and SPEC_ELEMENT_VALUE, identifying the specification subtype element and its value.
• ORGANIZATION_ID, CATEGORY_ID, CATEGORY_SET_ID — organizational and category assignment context.
• ITEM_ID, ITEM_REVISION — item-level assignment, including revision where applicable.
• VENDOR_ID, CUSTOMER_ID — supplier and customer assignment context.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY — standard audit columns.

Common Use Cases and Queries

Typical uses include listing active specifications for an item, auditing vendor- or customer-scoped specifications, and feeding specification data into external quality or MES systems. A representative query retrieves specifications effective on the current date:

• SELECT specification_id, specification_name, assignment_type, item_id, item_revision FROM apps.qabv_quality_specifications WHERE TRUNC(SYSDATE) BETWEEN start_effective_date AND NVL(end_effective_date, TRUNC(SYSDATE));
• SELECT specification_id, specification_name FROM apps.qabv_quality_specifications WHERE vendor_id = :p_vendor_id ORDER BY specification_name;
• SELECT organization_id, COUNT(*) FROM apps.qabv_quality_specifications GROUP BY organization_id;

Because the view is read-only and decodes the assignment type through MFG_LOOKUPS, it is best used for extraction and reporting rather than for transactional processing. Consumers should apply effective-date filtering, since historical and future-dated specifications coexist in QA_SPECS.