Search Results qa_plan_transactions




Overview
Explore in AI Chat

Overview

The QA_PLAN_TRANSACTIONS table is a core data object within the Oracle E-Business Suite (EBS) Quality (QA) module. It serves as a critical junction table that establishes and manages the relationship between Quality Collection Plans and the specific business transactions that trigger the execution of those plans. In essence, it defines which transactions—such as a purchase order receipt, a work order completion, or an inventory transfer—are linked to a given collection plan, thereby determining when and where quality data must be collected. This table is fundamental to the automated execution of quality processes, enabling the system to initiate the appropriate collection of inspection results or test data based on predefined business events.

Key Information Stored

The primary data stored in this table centers on the linkage identifiers and descriptive details of the transaction trigger. The key column is PLAN_TRANSACTION_ID, which serves as the unique primary key for each record. The PLAN_ID column is a foreign key that references the QA_PLANS table, identifying the specific collection plan to be executed. While the provided metadata does not list all columns, typical transactional data in this context would include fields to identify the transaction type (e.g., RECEIVING, WIP) and potentially the specific source document or event that serves as the trigger. This mapping allows the system to query for all relevant collection plans when a qualifying transaction occurs.

Common Use Cases and Queries

The primary use case is the dynamic triggering of quality collection activities. When a user performs a transaction in an integrated module like Purchasing or Manufacturing, the system queries QA_PLAN_TRANSACTIONS to find any collection plans associated with that transaction type and context. Common reporting and diagnostic queries involve analyzing plan coverage. For instance, to list all transaction triggers for a specific collection plan, a query would join QA_PLAN_TRANSACTIONS to QA_PLANS. Conversely, to audit which plans are triggered by a particular transaction type, one would filter on the relevant transaction type column. Sample SQL to find all plans linked to transaction triggers would be:

  • SELECT p.PLAN_NAME, pt.* FROM QA_PLANS p, QA_PLAN_TRANSACTIONS pt WHERE p.PLAN_ID = pt.PLAN_ID;

Related Objects

QA_PLAN_TRANSACTIONS sits at the center of a key relationship hierarchy within the Quality schema, as documented by its foreign keys. It has a direct parent-child relationship with the QA_PLANS table, which stores the master definition of the collection plan itself. It also has a parent-child relationship with the QA_PLAN_COLLECTION_TRIGGERS table, which likely holds more granular details about the trigger conditions. The specific, documented relationships are:

  • Parent Table (Foreign Key): QA_PLANS
    • Join Column: QA_PLAN_TRANSACTIONS.PLAN_ID references QA_PLANS (presumably on PLAN_ID)
  • Child Table (Referenced by Foreign Key): QA_PLAN_COLLECTION_TRIGGERS
    • Join Column: QA_PLAN_COLLECTION_TRIGGERS.PLAN_TRANSACTION_ID references QA_PLAN_TRANSACTIONS.PLAN_TRANSACTION_ID