QA Collection Plan Actions – 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 every action rule defined against an Oracle Quality collection plan - the trigger condition that fires the rule, the action it runs, the element it assigns, the alert it raises and the collection elements bound into its message - as a union of the rules attached to the collection plan itself and the rules defined on the collection element master, discriminated by an Action Level column. Trigger conditions that carry no action are listed too.

Oracle Quality evaluates these rules while quality results are entered. A rule is a trigger condition on one collection element - the element is entered, equals a value, falls outside its specification limits - paired with one or more actions. The rules are stored in two independent places. A collection plan carries its own rules in qa_plan_char_action_triggers and qa_plan_char_actions, and a collection element carries master rules in qa_char_action_triggers and qa_char_actions. The two are not linked: an element master rule is never copied into a plan, it simply applies to every plan that uses the element. The Action Level column says which is which. Plan means the rule is defined on this collection plan. Element means the rule is defined on the collection element master and therefore applies to every plan carrying that element, this one included.

Online Action separates the actions the results entry engine evaluates inline, as values are entered, from the actions it defers to background processing. The inline ones - display a message to the operator, reject the input, assign a value to a collection element - are the class of action that can change or refuse the data a results load submits. The deferred ones - alerts, workflow, holds - do not alter the collected values inline.

Assign Type and Assigned Element are populated only where the action assigns a value to another collection element; the formula or SQL statement itself is in Action Message. Output Variable and Output Element are a matched pair listing the tokens bound into that message and the collection element each token reads, so a formula referencing several elements can be resolved from the row. A trigger bound may be a literal or a statistical limit, and both are rendered. Status Code is the status string the action assigns to the quality result; Oracle Quality stores it as free text with no lookup behind it, so it is shown exactly as it was configured and is not translated.

Leave the parameters blank for the full picture, or narrow with Organization, Collection Plan, Plan Type, Collection Element and Action. Online Actions Only restricts to the actions evaluated inline during results entry, Enabled Elements Only to elements still enabled on the plan, and Action Level isolates plan level or element level rules. Element level rules are shown against the collection plans that use the element, so a rule on an element that no collection plan uses is not listed. 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, Action, Online Actions Only, Enabled Elements Only, Action Level

Oracle EBS Tables Used

qa_plan_char_action_outputs, qa_chars, qa_plans, mtl_parameters, qa_plan_char_action_triggers, qa_plan_chars, qa_plan_char_actions, qa_actions, alr_action_sets, alr_actions, org_access_view, qa_char_action_outputs, qa_char_action_triggers, qa_char_actions

Report Categories

Enginatics

QA Collection Plan Upload, QA Collection Plans, QA Plan Relationship Upload, QA Collection Plan Transactions, QA Quality Results, QA Collection Plan Element Values

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 Actions 14-Aug-2026 111941.xlsx
Blitz Report™ XML Import QA_Collection_Plan_Actions.xml
SQL Source QA Collection Plan Actions.sql
Full Report on Enginatics www.enginatics.com/reports/qa-collection-plan-actions/

Case Study & Technical Analysis: QA Collection Plan Actions

Executive Summary

This report lists every action rule defined for an Oracle Quality collection plan. A rule is a trigger condition on one collection element, such as the element being entered, equalling a value, or falling outside its specification limits, paired with one or more actions. The report shows the rules attached to the collection plan itself and the rules defined on the collection element master, distinguished by an Action Level column. Quality engineers, quality managers and EBS functional consultants use it to review how results entry behaves for a plan, to find the inline actions that can reject or change data during a results load, and to confirm which alerts, workflows and holds will fire after results are collected.

Business Challenge

The Solution

Technical Architecture (High Level)

Primary Tables

Logical Relationships

  1. The plan-level branch joins QA_PLANS to the plan trigger rows, to the element, to the plan element record, and to the action and alert.
  2. The element-level branch joins the plan element record to the element’s trigger rows, and to the element-level actions, which are shown against every plan that uses the element.
  3. Each action’s output tokens are listed with LISTAGG and the elements they read are resolved from QA_CHARS.
  4. The assigned element is joined as a second instance of QA_CHARS, used only when the action assigns a value.
  5. The two branches are combined with UNION ALL and filtered by the organization access list, with the seeded template plans included.

Parameters & Filtering

Performance & Optimization

FAQ

Q: Why does an element-level rule appear against several plans? A: Element master rules apply to every collection plan that uses the element, so each plan that carries the element shows the rule.

Q: Which actions can change data during results entry? A: Filter with Online Actions Only set to Yes. These are the inline actions, such as displaying a message, rejecting the input or assigning a value to another element.

© Enginatics GmbH