Search Results child_organization_name




Overview
Explore in AI Chat

Overview

APPS.QA_SPEC_ORGS_V is a reporting and integration view in Oracle E-Business Suite that exposes the relationship between quality specifications (QA_SPECS) and the inventory organizations in which the specified items are defined. It resolves a common reporting requirement: given a quality specification and its associated item, return the child organization context — the organization identifier, organization code, and organization name — for that item/specification combination.

The view is particularly relevant to users searching for child_organization_name, which is exposed as the CHILD_ORGANIZATION_NAME column. This column provides the translated, user-facing name of the organization from HR_ALL_ORGANIZATION_UNITS_TL, filtered to the session language via USERENV('LANG'). The view is owned by APPS and is available across 12.1.1 and 12.2.2, though the ETRM documentation is formally recorded at 12.2.2. It is typically used in quality, inventory, and item-master reporting where specification-to-organization attribution must be presented in a denormalized, query-friendly form.

Underlying Base Objects

The view is defined over four documented synonym base objects:

The join logic is significant: the view links QA_SPECS.SPEC_ID to QA_SPECS.COMMON_SPEC_ID, meaning it surfaces common (shared) specifications rather than spec-version rows. QA_SPECS.ITEM_ID joins to MTL_SYSTEM_ITEMS_B.INVENTORY_ITEM_ID, and MTL_SYSTEM_ITEMS_B.ORGANIZATION_ID joins to both MTL_PARAMETERS.ORGANIZATION_ID and HR_ALL_ORGANIZATION_UNITS_TL.ORGANIZATION_ID. The organization context is therefore driven by the item's organization, labeled as the "child" organization relative to the specification's own ORGANIZATION_ID.

Key Columns

  • SPEC_ID — identifier of the quality specification.
  • SPEC_NAME — name of the specification.
  • ITEM_ID — inventory item associated with the specification.
  • ORGANIZATION_ID — organization identifier from QA_SPECS (the specification's own organization context).
  • CHILD_ORGANIZATION_ID — organization identifier sourced from MTL_SYSTEM_ITEMS_B, i.e., the organization where the item is defined.
  • CHILD_ORGANIZATION_CODE — the organization code from MTL_PARAMETERS.
  • CHILD_ORGANIZATION_NAME — the translated organization name from HR_ALL_ORGANIZATION_UNITS_TL, restricted to USERENV('LANG').

Note that the CHILD_ORGANIZATION_NAME is language-sensitive; if no translation exists for the session language, the organization name may not be returned, and rows could be filtered out by the language join condition.

Common Use Cases and Queries

Typical uses include quality specification reports that must display the owning child organization by name, integration extracts that map specs to organization codes, and reconciliation queries validating common-spec distribution across organizations.

Example — list specifications with their child organization details:

SELECT spec_id, spec_name, item_id, child_organization_id, child_organization_code, child_organization_name FROM apps.qa_spec_orgs_v;

Example — filter by specification name:

SELECT spec_name, child_organization_code, child_organization_name FROM apps.qa_spec_orgs_v WHERE spec_name LIKE 'CQ%';

Example — join back to items for additional attribute reporting:

SELECT v.spec_name, v.item_id, v.child_organization_name FROM apps.qa_spec_orgs_v v WHERE v.child_organization_id = :org_id;

Because the view restricts organization names by language and depends on item/organization joins, users should validate that the target item is enabled in the child organization and that a translation exists for the session language before relying on CHILD_ORGANIZATION_NAME in extracts.