Results for “subtype_element_id”

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

Overview

QABV_QUALITY_SPECIFICATIONS is a read-only Oracle EBS view owned by the APPS schema and classified under the QA – Quality product family. It is identified in the ETRM metadata as a retrofitted object, indicating that it was introduced or re-pointed as part of an upgrade or modernization effort to preserve backward-compatible access to quality specification data across releases. The view presents a denormalized, reporting-friendly projection of quality specification definitions held in the QA_SPECS table, joined to the MFG_LOOKUPS lookup view to resolve the assignment type code into a user-facing meaning.

Because the view is defined with the READ ONLY clause, it is intended strictly for query, reporting, and integration consumption rather than for DML. It exposes specification identity, naming, effective dating, and the assignment context (organization, category, item, vendor, or customer) in a single flat structure, which makes it suitable for use in concurrent programs, BI Publisher reports, Discoverer worksheets, and outbound integrations that need a stable interface to quality specification master data.

Underlying Base Objects

The view is defined over two documented objects:

• QA_SPECS (referenced as a SYNONYM) — the primary source of quality specification records, aliased in the view text as QUALITY_SPECIFICATION. This object supplies specification identifiers, names, effective dates, assignment attributes, and audit columns.
• MFG_LOOKUPS (VIEW) — joined with the filter LOOKUP_TYPE = 'QA_SPEC_TYPE', matching LOOKUP_CODE to the ASSIGNMENT_TYPE value on the specification record. This join translates the stored assignment type code into its MF.MEANING display value.

The join is effectively a lookup decode: for every row in QA_SPECS, the view returns the corresponding lookup meaning from MFG_LOOKUPS. Because the join is not outer, only specifications whose assignment type resolves to a valid QA_SPEC_TYPE lookup code are returned.

Key Columns

• SPECIFICATION_ID / SPECIFICATION_NAME — the specification's unique identifier and user-defined name, derived from SPEC_ID and SPEC_NAME.
• START_EFFECTIVE_DATE / END_EFFECTIVE_DATE — the validity window of the specification, mapped from EFFECTIVE_FROM and EFFECTIVE_TO.
• ASSIGNMENT_TYPE — the decoded lookup meaning indicating how the specification is assigned (for example organization, item, vendor, or customer level).
• SUBTYPE_ELEMENT_ID / SUBTYPE_ELEMENT_VALUE — the characteristic or element identifier (CHAR_ID) and its associated qualifying value (SPEC_ELEMENT_VALUE).
• ORGANIZATION_ID / CATEGORY_ID / CATEGORY_SET_ID — organizational and category-based scoping attributes.
• ITEM_ID / ITEM_REVISION — item-level assignment context, where applicable.
• VENDOR_ID / CUSTOMER_ID — supplier- and customer-specific assignment context.
• Audit columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, and CREATED_BY, supporting change tracking and extract reconciliation.

Common Use Cases and Queries

Typical scenarios include listing active specifications for a given organization or item, reconciling specification assignments against inventory and purchasing records, and feeding specification master data into downstream quality or manufacturing systems.

• Retrieve all specifications with their assignment meaning:
  SELECT specification_id, specification_name, assignment_type, start_effective_date, end_effective_date FROM apps.qabv_quality_specifications;
• Filter to currently effective item specifications:
  SELECT specification_id, specification_name, item_id, item_revision FROM apps.qabv_quality_specifications WHERE item_id IS NOT NULL AND SYSDATE BETWEEN start_effective_date AND NVL(end_effective_date, SYSDATE);
• Scope by organization and audit recent changes:
  SELECT specification_id, specification_name, organization_id, last_update_date FROM apps.qabv_quality_specifications WHERE organization_id = :org_id ORDER BY last_update_date DESC;

All queries should rely on the view's READ ONLY nature and the documented base objects to ensure compatibility across 12.1.1 and 12.2.2.