Results for “default_value”

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

Overview

QAFV_COLLECTION_PLAN_ELEMENTS is a read-only view owned by the APPS schema within the Oracle E-Business Suite Quality (QA) module. It presents the association between collection plans and the collection elements (characteristics) that those plans are configured to gather. In ETRM terms the object is classified as a retrofitted view, meaning it was reconstructed to preserve the interface expected by existing code or reports during upgrade or reimplementation activity. The view does not store data itself; it projects and denormalizes records held in the collection plan and characteristic tables, joining them to lookup values to resolve internal codes into user-facing meanings.

Its principal role is to support reporting, extracts, and integration interfaces that require a flat, human-readable representation of plan-element configuration. By exposing resolved plan names, element names, prompts, default values, and translated flag meanings, it removes the need for downstream consumers to perform their own joins across QA_PLAN_CHARS, QA_PLANS, QA_CHARS, and MFG_LOOKUPS. The presence of standard WHO columns allows auditing and delta extraction by date.

Underlying Base Objects

The documented referenced base objects are QA_PLAN_CHARS, QA_PLANS, QA_CHARS, and MFG_LOOKUPS. In the shipped environment QA_PLAN_CHARS, QA_PLANS, and QA_CHARS are exposed as synonyms within APPS, while MFG_LOOKUPS is itself a view. The view aliases these objects as COLLECTION_PLAN_ELEMENT, COLLECTION_PLAN, COLLECTION_ELEMENT, MF1, and MF2 respectively.

• QA_PLAN_CHARS supplies the core association rows: PLAN_ID, CHAR_ID, DEFAULT_VALUE, PROMPT, ENABLED_FLAG, MANDATORY_FLAG, and the audit columns.
• QA_PLANS supplies the collection plan header, contributing NAME as COLLECTION_PLAN_NAME.
• QA_CHARS supplies the collection element definition, contributing NAME as COLLECTION_ELEMENT_NAME.
• MFG_LOOKUPS is joined twice, once against ENABLED_FLAG and once against MANDATORY_FLAG, both restricted to LOOKUP_TYPE = 'SYS_YES_NO', to translate the stored codes into their MEANING values.

The joins are all equi-joins on the natural keys (PLAN_ID and CHAR_ID) and on the SYS_YES_NO lookup codes. The view is declared WITH READ ONLY, confirming it is strictly a query interface and cannot be used for DML.

Key Columns

• COLLECTION_PLAN_ID / COLLECTION_PLAN_NAME — identifier and descriptive name of the parent collection plan.
• COLLECTION_ELEMENT_ID / COLLECTION_ELEMENT_NAME — identifier and name of the characteristic (collection element) attached to the plan. COLLECTION_ELEMENT_NAME is the column most frequently used when searching for a specific element across plans.
• DEFAULT_VALUE — the default value applied to the element when results are entered for the plan.
• RESULTS_COLUMN_PROMPT — the prompt displayed to the user for the results column, sourced from QA_PLAN_CHARS.PROMPT.
• ENABLED_FLAG / MANDATORY_FLAG — resolved meanings of the SYS_YES_NO lookups governing whether the element is active and whether data entry is required.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY — standard audit columns enabling change tracking.

Common Use Cases and Queries

Typical uses include identifying which plans reference a given element, auditing mandatory versus optional data entry, and feeding external quality systems with plan-element configuration. A representative query locating a specific collection element is:

SELECT collection_plan_name, collection_element_name, results_column_prompt, enabled_flag, mandatory_flag FROM apps.qafv_collection_plan_elements WHERE collection_element_name = :collection_element_name ORDER BY collection_plan_name;

To list all mandatory elements for a plan:

SELECT collection_element_name, default_value FROM apps.qafv_collection_plan_elements WHERE collection_plan_id = :plan_id AND mandatory_flag = 'Yes';

Incremental extracts should filter on LAST_UPDATE_DATE. Because the view resolves both plan and element names and translates flags, it is well suited to ad hoc reporting and interface staging without additional lookup resolution.