QA Collection Plan Element Values – Oracle EBS SQL Report

Oracle E-Business Suite SQL report from the Enginatics Library powered by Blitz Report™. Oracle EBS module: Quality · all Quality reports

Overview

Lists the allowed values behind every list-validated Oracle Quality collection element - the entries an operator can pick when entering quality results, and the collection element master values each plan was seeded from.

Oracle Quality holds these values in two independent places. A collection plan carries its own value list, and the collection element carries a master list. A plan is seeded from the master but is not tied to it afterwards: it can carry codes that were never in the master, override a master value’s description, and leave master values out. The Value Level column says which is which. Plan means the value is offered on this collection plan, and is what quality results entry or a quality results upload must validate against. Element means the value is defined on the collection element master but was not carried into this plan, so it is not offered here.

On a Plan row, Element Master Description shows the master’s own wording for the same short code, In Element Master flags whether the code exists in the master at all, and Description Overridden flags the rows where the plan’s wording differs from the master’s.

Result Column is the qa_results column this element’s value is stored in, so a short code can be traced to the column that will hold it. Collection results are stored generically, so this mapping is what turns a stored value back into a business meaning.

Leave the parameters blank for the full picture, or narrow with Organization, Collection Plan, Plan Type and Collection Element. Enabled Elements Only restricts to elements still enabled on the plan. Value Level isolates one of the two levels, and Short Code finds a particular value across plans.

Run this report in Excel in seconds: download Blitz Report™ free (your first 30 reports are free) or try it in the online demo.

Report Parameters

Organization, Collection Plan, Plan Type, Collection Element, Enabled Elements Only, Value Level, Short Code

Oracle EBS Tables Used

qa_plans, mtl_parameters, qa_plan_chars, qa_chars, qa_plan_char_value_lookups, qa_char_value_lookups, org_access_view

Report Categories

Enginatics

QA Collection Plans, QA Collection Plan Elements, QA Collection Plan Transactions, QA Collection Plan Actions, QA Collection Plan Relationships, QA Collection Plan Upload, QA Quality Results, QA Plan Relationship Upload

Running This SQL Without Blitz Report

The SQL source can be run in any SQL client. Some Oracle EBS SQL reports in this library use functions from the utility package xxen_util – install it first. Blitz Report™ adds parameters, Excel output with pivots, scheduling and security on top.

Download & Import Options

Resource Link
Excel Example Output QA Collection Plan Element Values 14-Aug-2026 112043.xlsx
Blitz Report™ XML Import QA_Collection_Plan_Element_Values.xml
SQL Source QA Collection Plan Element Values.sql
Full Report on Enginatics www.enginatics.com/reports/qa-collection-plan-element-values/

Case Study & Technical Analysis: QA Collection Plan Element Values

Executive Summary

The QA Collection Plan Element Values report lists the allowed values behind every list-validated Oracle Quality collection element. These are the entries an operator can pick when recording quality results, and the master values each collection plan was seeded from. It is written for quality engineers, Oracle Quality administrators and implementation consultants who must confirm which codes a plan will accept before results are entered or loaded. The report separates the two places where Oracle Quality keeps these values, the plan’s own value list and the collection element master, so that differences between them are visible.

Business Challenge

The Solution

Technical Architecture (High Level)

Primary Tables

Logical Relationships

  1. QA_PLANS joins to MTL_PARAMETERS as an outer join on the organisation identifier, so plans without an organisation, such as templates, are still listed.
  2. Plan elements join to QA_PLANS on the plan identifier and to QA_CHARS on the element identifier.
  3. Plan value lists join to the plan elements on the plan and element identifiers, and to the master value list on the element and short code, as an outer join.
  4. The Element branch selects master values that have no matching plan value, using a not exists condition on the plan value list.
  5. The two branches are combined with union all and ordered by organisation, plan name, prompt sequence, element name and short code.

Parameters & Filtering

Performance & Optimization

FAQ

Q: Which values can an operator pick when entering quality results on a collection plan? A: Rows with the Plan value level are the values offered on that plan, and they are what quality results entry must validate against.

Q: What does it mean when a value is listed as Element? A: The value is defined on the collection element master but was not carried into the plan, so it is not offered on that plan.

Q: How do I see which plan values have different wording from the master? A: Read the Description Overridden column, which is set where the plan’s description differs from the element master’s description for the same short code.

© Enginatics GmbH