Results for “plan_type_description”

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

Overview

The view APPS.MTL_GENEALOGY_QA_DATA is a reporting and integration object within the Oracle E-Business Suite Inventory (INV) module. It is defined in the APPS schema and carries VALID status in both release 12.1.1 and 12.2.2. Its purpose is to expose a consolidated, joined representation of quality assurance plan definitions and the quality results recorded against those plans, correlated with genealogy information such as lot, serial, and component identifiers.

In practice, the view supports downstream genealogy analysis by flattening the relationship between a QA plan (the specification or test definition) and its associated QA results (the executed measurements and outcomes). This makes it suitable for reporting, extract generation, and integration into external quality or traceability systems where a single denormalized result set is preferred over multi-step joins. Because it draws on the results validation view, it reflects only validated QA result records rather than raw or in-progress entries, which is important when the data is consumed for compliance or audit reporting.

Underlying Base Objects

According to the documented view text, MTL_GENEALOGY_QA_DATA is defined over two principal objects joined on PLAN_ID:

• QA_PLANS_VAL_V — the validated QA plans view, supplying plan-level attributes such as PLAN_ID, ORGANIZATION_ID, NAME, DESCRIPTION, and PLAN_TYPE_DESCRIPTION.
• QA_RESULTS_VAL_V — the validated QA results view, supplying result-level and genealogy attributes including ITEM_ID, COMP_ITEM_ID, LOT_NUMBER, COMP_LOT_NUMBER, SERIAL_NUMBER, COMP_SERIAL_NUMBER, WIP_ENTITY_ID, and PLAN_ID.
• FND_GLOBAL — the standard Oracle EBS package referenced by the underlying validation views to resolve session context such as user and organization.

The join predicate is QPV.PLAN_ID = QR.PLAN_ID, and the outermost operation is a SELECT DISTINCT, which suppresses duplicate rows produced when multiple results share the same plan-level attribute combination. The dependency on FND_GLOBAL means the underlying validation views are sensitive to the active session's organization and responsibility context, so results returned can vary with the runtime environment.

Key Columns

• PLAN_ID — identifier of the QA plan; the join key linking plans to results.
• ORGANIZATION_ID — the inventory organization context for the plan.
• NAME — the name of the QA plan.
• DESCRIPTION — descriptive text for the QA plan.
• PLAN_TYPE_DESCRIPTION — textual description of the plan type.
• ITEM_ID — the item to which the QA result applies.
• COMP_ITEM_ID — the component item associated with the result, supporting assembly/component relationships.
• LOT_NUMBER — lot of the primary item.
• COMP_LOT_NUMBER — lot of the component item.
• SERIAL_NUMBER — serial of the primary item.
• COMP_SERIAL_NUMBER — serial of the component item.
• WIP_ENTITY_ID — the work in process entity associated with the result, linking the record to a manufacturing job.

Common Use Cases and Queries

Typical scenarios include tracing quality results back to the plans that generated them, building genealogy reports that span item, lot, and serial identifiers, and extracting validated QA data into external traceability or compliance repositories. A representative query retrieves all validated QA results for a given plan:

• SELECT PLAN_ID, ORGANIZATION_ID, NAME, ITEM_ID, COMP_ITEM_ID, LOT_NUMBER, COMP_LOT_NUMBER, SERIAL_NUMBER, COMP_SERIAL_NUMBER, WIP_ENTITY_ID FROM APPS.MTL_GENEALOGY_QA_DATA WHERE PLAN_ID = :p_plan_id;
• SELECT * FROM APPS.MTL_GENEALOGY_QA_DATA WHERE ORGANIZATION_ID = :p_org_id AND WIP_ENTITY_ID = :p_wip_entity_id;
• SELECT DISTINCT PLAN_ID, NAME, PLAN_TYPE_DESCRIPTION FROM APPS.MTL_GENEALOGY_QA_DATA WHERE ORGANIZATION_ID = :p_org_id ORDER BY NAME;

Queries should always filter by organization and, where applicable, by plan or WIP entity to keep result sets bounded, given the DISTINCT-based deduplication and the potentially large cardinality of joined plan/result data.