Search Results child_spec_name_old

Overview

The QA_SPEC_ORG_ASSIGNMENTS_V view is a Quality (QA) module database object owned by the APPS schema and defined as a VALID view in Oracle EBS 12.1.1 and 12.2.2. Its documented purpose is to support the specification organization assignment window within the Oracle Quality application. The view presents the relationship between a parent specification (defined at the master or common level) and its potential child organization specifications, exposing both the parent specification context and any specification that has been assigned to a specific inventory organization.

Functionally, QA_SPEC_ORG_ASSIGNMENTS_V is a reporting and forms-support view. It flattens the hierarchical relationship between common specifications in QA_SPECS and their organization-specific counterparts, joining organization information from inventory and HR tables. This makes it directly usable in custom reports, concurrent programs, and integration extracts where the assignment status of a specification to a child organization must be determined. Because the description field explicitly identifies it as the view behind the spec org assignment window, it plays a role in both the presentation layer (Oracle Forms) and in downstream reporting.

Underlying Base Objects

The ETRM 12.2.2 metadata documents the following referenced base objects, all exposed through APPS synonyms or views:

• QA_SPEC_ORGS_V (VIEW) — aliased as QS1, this is the primary driver object and supplies the parent specification and organization context, including SPEC_ID, SPEC_NAME, ORGANIZATION_ID, ITEM_ID, and the CHILD_ORGANIZATION_ID/CODE/NAME columns.
• QA_SPECS (SYNONYM, aliased QS2) — the specifications table, joined on QS1.SPEC_ID = QS2.COMMON_SPEC_ID to identify any child specification assigned to the child organization.
• MTL_PARAMETERS (SYNONYM, aliased MP) — supplies the organization code for the parent organization (QS1.ORGANIZATION_ID = MP.ORGANIZATION_ID, outer-joined).
• HR_ALL_ORGANIZATION_UNITS_TL (SYNONYM, aliased HRORG) — supplies the translated organization name, joined on ORGANIZATION_ID with LANGUAGE(+) = USERENV('LANG').

All non-driving joins use Oracle outer-join syntax (+), meaning the view returns parent specification rows even when no child specification, organization code, or organization name exists.

Key Columns

• ROW_ID — the ROWID of the QA_SPECS child record; NULL when no child specification is assigned.
• SPEC_ID, SPEC_NAME — the parent (common) specification identifier and name.
• CHILD_SPEC_ID — the organization-specific specification ID, if one exists.
• CHILD_SPEC_NAME — the assigned child specification name; when unassigned, a derived value combining SUBSTR(SPEC_NAME,1,26) with the CHILD_ORGANIZATION_CODE.
• CHILD_SPEC_NAME_OLD — the raw QA_SPECS.SPEC_NAME of the child record, retained for backward compatibility.
• ORGANIZATION_ID, ORGANIZATION_CODE, ORGANIZATION_NAME — the parent organization context derived from MTL_PARAMETERS and HR_ALL_ORGANIZATION_UNITS_TL.
• ASSIGN_FLAG — DECODE(QS2.SPEC_ID, NULL, 2, 1); a value of 1 indicates an assigned child spec, 2 indicates unassigned.
• ITEM_ID — the item associated with the specification assignment, where applicable.
• CHILD_ORGANIZATION_ID / CODE / NAME — the target (child) organization to which the specification may be assigned.

Common Use Cases and Queries

The most frequent query pattern surfaces specifications that have not yet been assigned to a child organization, using ASSIGN_FLAG = 2. This supports gap analysis and bulk assignment reporting. A second common pattern displays the effective child specification name alongside the assigned organization for audit purposes.

Sample query listing assignments:

• SELECT spec_name, child_organization_code, child_spec_name, assign_flag FROM qa_spec_org_assignments_v WHERE assign_flag = 1 ORDER BY spec_name;
• SELECT spec_id, spec_name, child_organization_code FROM qa_spec_org_assignments_v WHERE assign_flag = 2;

Because CHILD_SPEC_NAME is NVL-derived, reports should prefer this column over CHILD_SPEC_NAME_OLD when presenting user-facing output, while CHILD_SPEC_NAME_OLD is useful when the literal underlying QA_SPECS row must be inspected. Filtering by ORGANIZATION_ID or CHILD_ORGANIZATION_ID allows multi-org-scoped reporting consistent with EBS multi-organization security.