Results for “collection_plan_element”

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

Overview

APPS.QABV_COLLECTION_PLAN_ELEMENTS is a read-only Oracle EBS view that exposes the configuration of Collection Plan Elements — the individual quality characteristics (also called collection elements or QA characters) that are attached to a Collection Plan. In EBS Quality, a Collection Plan groups one or more collection elements together so that a shop-floor or inspection transaction can capture a defined set of quality results in a single pass. This view presents each plan-to-element association as one row, along with the descriptive names of the plan and the element, the default value and prompt that drive the results-entry form, and translated Yes/No meanings for the enabled and mandatory attributes.

Because the view resolves internal lookup codes to user-facing meanings and joins IDs to their descriptive names, it is well suited to reporting and integration scenarios where a flat, readable representation of collection plan setup is required. It is defined with the "with read only" clause, so it can be queried safely in custom reports, concurrent programs, and inbound/outbound interfaces without risk of mutating base setup data.

Underlying Base Objects

The view is defined over four documented base objects in the APPS schema: QA_PLAN_CHARS (referenced via a synonym), QA_PLANS (synonym), QA_CHARS (synonym), and MFG_LOOKUPS (view). QA_PLAN_CHARS is the primary associate table holding one row per plan/element combination; it supplies the PLAN_ID, CHAR_ID, DEFAULT_VALUE, PROMPT, ENABLED_FLAG, MANDATORY_FLAG, and the standard WHO audit columns. QA_PLANS and QA_CHARS are joined on PLAN_ID and CHAR_ID respectively to obtain the human-readable NAME columns, which the view aliases as COLLECTION_PLAN_NAME and COLLECTION_ELEMENT_NAME. MFG_LOOKUPS is joined twice — once for ENABLED_FLAG and once for MANDATORY_FLAG — using LOOKUP_TYPE 'SYS_YES_NO' to translate the stored codes into their MEANING text. All joins are simple equi-joins with no outer joins, so a row appears only where the plan, element, and both lookup codes exist.

Key Columns

• COLLECTION_PLAN_ID / COLLECTION_PLAN_NAME — Surrogate key and name of the parent Collection Plan (QA_PLANS.PLAN_ID / NAME).
• COLLECTION_ELEMENT_ID / COLLECTION_ELEMENT_NAME — Surrogate key and name of the collection element or QA character (QA_CHARS.CHAR_ID / NAME).
• DEFAULT_VALUE — Value pre-populated for the element when results are entered against the plan.
• RESULTS_COLUMN_PROMPT — Label (PROMPT) displayed for the element on the results collection form.
• ENABLED_FLAG — Translated Yes/No meaning indicating whether the element is active on the plan.
• MANDATORY_FLAG — Translated Yes/No meaning indicating whether a result must be captured for the element.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY — Standard WHO audit columns propagated from QA_PLAN_CHARS for change tracking.

Common Use Cases and Queries

Typical uses include validating collection plan setup before go-live, extracting plan structures for quality reporting, and driving external data-collection applications. To list all elements for a specific plan by name, query the view with the plan name as a filter:

SELECT collection_element_name,
       results_column_prompt,
       default_value,
       enabled_flag,
       mandatory_flag
  FROM apps.qabv_collection_plan_elements
 WHERE collection_plan_name = 'INCOMING_INSPECTION';

To audit which plans contain an element that is enabled but not mandatory — often used to understand where inspection users may skip a result — reverse the filter on the element:

SELECT collection_plan_name,
       collection_element_name,
       mandatory_flag
  FROM apps.qabv_collection_plan_elements
 WHERE collection_element_name = 'TEMPERATURE'
   AND enabled_flag = 'Yes'
   AND mandatory_flag = 'No';

Because audit columns are exposed, the view also supports change-tracking extracts, for example returning all associations modified since a given date for downstream synchronization. In all cases, the read-only nature of the view and its use of simple equi-joins keep query behavior predictable, making it a dependable reporting and integration asset in both EBS 12.1.1 and 12.2.2.