QA Collection Plan Elements – 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

Every collection element assigned to an Oracle Quality collection plan, with the element’s prompt and sequence on the plan, its element type, datatype, display length, decimal precision and unit of measure, the plan level and element level default values, and the Mandatory, Enabled, Displayed, Read Only, Information and Poplist flags. Collection plans that have no elements are listed too.

Oracle Quality stores every collection result generically in qa_results, whose character1 to character100 columns carry no meaning of their own: the element to column mapping is held per plan in qa_plan_chars.result_column_name, and each plan gets its own dynamically generated results view. This report exposes that mapping as the Result Column, shown verbatim next to the element’s native Hardcoded Column so that a divergence between the two is visible at a glance. It also shows the Context Element classification, which separates a quality characteristic the operator enters from predefined reference information captured automatically from the transaction, and all three validation sources an element can use: a validation table with its additional where clause, a SQL validation string, and the number of plan level values the element offers. Use it to document or audit a Quality setup, and as the specification when building an interface or an upload that writes collection results.

Filter with the optional Organization, Collection Plan, Plan Type, Collection Element and Element Type parameters, or set Enabled Elements Only to Yes to hide elements that are disabled on the plan. Leaving Organization blank returns every collection plan the responsibility has inventory organization access to, plus the seeded template plans, which are not owned by an inventory organization and therefore show a blank Organization Code.

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, Element Type, Enabled Elements Only

Oracle EBS Tables Used

mtl_units_of_measure_vl, qa_plan_char_value_lookups, qa_plans, mtl_parameters, qa_plan_chars, qa_chars, org_access_view

Report Categories

Enginatics

QA Collection Plan Element Values, QA Collection Plans, QA Quality Results, QA Collection Plan Transactions, QA Collection Plan Actions, QA Collection Plan Relationships, QA Collection Plan Upload, 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 Elements 14-Aug-2026 071547.xlsx
Blitz Report™ XML Import QA_Collection_Plan_Elements.xml
SQL Source QA Collection Plan Elements.sql
Full Report on Enginatics www.enginatics.com/reports/qa-collection-plan-elements/

Case Study & Technical Analysis: QA Collection Plan Elements

Executive Summary

The QA Collection Plan Elements report lists every collection element assigned to an Oracle Quality collection plan, with its prompt and sequence on the plan, its element type, datatype, display length, decimal precision and unit of measure. It also shows the plan level and element level default values, the Mandatory, Enabled, Displayed, Read Only, Information and Poplist flags, and the validation sources of each element. Quality engineers use it to document or audit a quality setup, and integration developers use it as the specification for an interface or an upload that writes collection results. It runs in Excel through Blitz Report.

Business Challenge

The Solution

Technical Architecture (High Level)

Primary Tables

Logical Relationships

  1. QA_PLANS is outer joined to MTL_PARAMETERS on the organization id, which gives the organization code of each plan.
  2. QA_PLANS is outer joined to QA_PLAN_CHARS on the plan id, so a plan with no elements is still listed.
  3. QA_PLAN_CHARS is outer joined to QA_CHARS on the character id, which supplies the element definition.
  4. The number of plan level values is a count from QA_PLAN_CHAR_VALUE_LOOKUPS on the plan id and character id.
  5. The organization restriction includes plans whose organization id is 0, the seeded template plans, and plans whose organization the responsibility can access.

Parameters & Filtering

Performance & Optimization

FAQ

Q: What does the Result Column show? A: It is the name of the column in the plan’s dynamically generated results view that stores this element, as held in QA_PLAN_CHARS.RESULTCOLUMNNAME.

Q: Why are plans with no elements listed? A: The plans are outer joined to their elements, so a plan without any elements appears with blank element columns.

Q: How do I see which plans use a validation table? A: The Validation Table and Validation Where Clause columns show the table and its additional where clause for each element. Filter the output on those columns to find the plans.

© Enginatics GmbH