Results for “spec_id”

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

Overview

QA_SPEC_ORGS_V is an Oracle E-Business Suite database view owned by the APPS schema and defined in the Quality (QA) product module. In EBS 12.1.1 and 12.2.2, its documented role is that of an auxiliary view consumed by QA_SPEC_ORG_ASSIGNMENTS_V. It does not function as an end-user reporting object or a DFF-enabled flexfield view; rather, it supplies the organization enumeration logic that higher-level QA specification views rely upon when resolving the valid organizations associated with a specification.

The view exposes the relationship between a specification and the inventory organizations that reference it. The predicate QS.SPEC_ID = QS.COMMON_SPEC_ID restricts output to specifications that are themselves common (global) specifications, while the join to MTL_SYSTEM_ITEMS_B resolves the child inventory organizations where those specifications are visible. In effect, QA_SPEC_ORGS_V flattens the many-to-many relationship between specifications and organizations into a single denormalized row set. Because it is a standard, VALID APPS view, it is stable across the 12.1.1 and 12.2.2 releases and is safe to reference from custom reports, but it should be treated as an internal helper rather than a supported public interface.

Underlying Base Objects

Per documented ETRM metadata, QA_SPEC_ORGS_V is defined over four base objects, all referenced through synonyms in the APPS schema:

• QA_SPECS — the driving table, supplying SPEC_ID, SPEC_NAME, ITEM_ID, ORGANIZATION_ID, and COMMON_SPEC_ID for the self-referencing common-specification check.
• MTL_SYSTEM_ITEMS_B — joined on INVENTORY_ITEM_ID to enumerate the organizations (ORGANIZATION_ID) in which the specification's item is defined.
• MTL_PARAMETERS — joined on ORGANIZATION_ID to validate that the resulting organization is a genuine inventory organization, and to supply the organization identifier used as CHILD_ORGANIZATION_ID.
• HR_ALL_ORGANIZATION_UNITS_TL — the translated organization-name table, joined on ORGANIZATION_ID and filtered by ORG.LANGUAGE = USERENV('LANG') so that names are returned in the session language.

The view therefore sits one level below QA_SPEC_ORG_ASSIGNMENTS_V, which aggregates and presents the organization assignment information. Because it draws on MTL and HR objects as well as QA, it illustrates the cross-module nature of specification-to-organization resolution.

Key Columns

• SPEC_ID — identifier of the quality specification (from QA_SPECS).
• SPEC_NAME — user-facing name of the specification.
• ITEM_ID — inventory item associated with the specification.
• ORGANIZATION_ID — organization identifier carried from QA_SPECS.
• CHILD_ORGANIZATION_ID — the organization identifier resolved through MTL_SYSTEM_ITEMS_B/MTL_PARAMETERS; identifies the child (inventory) organization to which the specification applies.
• CHILD_ORGANIZATION_CODE — the organization code from MTL_PARAMETERS, used for display and joins.
• CHILD_ORGANIZATION_NAME — the translated organization name from HR_ALL_ORGANIZATION_UNITS_TL in the session language.

Common Use Cases and Queries

Typical usage is diagnostic or reporting-based: confirming which inventory organizations a common specification spans, and reconciling organization names against internal reporting. A representative query follows:

SELECT spec_id,
       spec_name,
       child_organization_id,
       child_organization_code,
       child_organization_name
  FROM apps.qa_spec_orgs_v
 WHERE spec_id = :p_spec_id
 ORDER BY child_organization_code;

Because the view is auxiliary to QA_SPEC_ORG_ASSIGNMENTS_V, direct querying should be limited to analysis and troubleshooting. For production reports, filter on SPEC_ID or ITEM_ID to avoid full scans across QA_SPECS and MTL_SYSTEM_ITEMS_B, and be aware that language-sensitive name retrieval depends on the USERENV('LANG') session setting.