QA Collection Plan Transactions – Oracle EBS SQL Report

Oracle E-Business Suite SQL report from the Enginatics Library powered by Blitz Report™.

Overview

Every collection transaction an Oracle Quality collection plan is attached to, with the trigger conditions that decide whether collection actually fires, the Mandatory Collection, Background Collection and Enabled flags, and each trigger’s field, database field, datatype, operator and low and high values. Attachments that collect unconditionally are listed too, with a blank Collection Trigger.

Attaching a collection plan to a transaction is what makes Oracle Quality collect anything at all: until a plan is attached to a transaction such as Receiving Transactions or Completion Transactions it is only a definition, and nothing is ever collected against it. Trigger conditions narrow that further, so the attachment on its own does not tell you when collection happens - a plan attached to Completion Transactions with a trigger of Item equals a single assembly collects for that assembly and no other. Mandatory Collection means the transaction cannot be saved without quality results, and Background Collection means results are collected without prompting the operator.

A plan can be attached to the same transaction more than once, each attachment carrying its own trigger conditions. Transaction Attachments counts how many attachments the plan has for that transaction, so one attachment with several triggers can be told apart from several separate attachments. Trigger Field is the form prompt the trigger tests and Trigger Database Field is the column behind it, both taken from the transaction’s own trigger list in qa_txn_collection_triggers, so a condition can be traced from the prompt an implementer sees to the column a data load has to supply.

Leave the parameters blank for the full picture, or narrow with Organization, Collection Plan, Plan Type, Transaction and Collection Trigger. Mandatory Collection Only and Enabled Transactions Only restrict to attachments carrying those flags. 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.

Report Parameters

Organization, Collection Plan, Plan Type, Transaction, Collection Trigger, Mandatory Collection Only, Enabled Transactions Only

Oracle EBS Tables Used

qa_plan_transactions, qa_txn_collection_triggers, qa_plans, mtl_parameters, qa_plan_collection_triggers, qa_chars, org_access_view

Report Categories

Enginatics

QA Collection Plans, QA Collection Plan Actions, QA Collection Plan Upload, QA Quality Results, QA Collection Plan Elements, QA Collection Plan Relationships, QA Collection Plan Element Values, FND Attached Documents

Running This SQL Without Blitz Report

Some Oracle EBS SQL reports in this library require functions from the utility package xxen_util. Install it before running the SQL directly against your Oracle EBS database.

Download & Import Options

Resource Link
Excel Example Output QA Collection Plan Transactions 14-Aug-2026 112113.xlsx
Blitz Report™ XML Import QA_Collection_Plan_Transactions.xml
Full SQL on Enginatics www.enginatics.com/reports/qa-collection-plan-transactions/

© 2026 Enginatics