Search Results qa_plan_collection_triggers_pk

Overview

The QA_PLAN_COLLECTION_TRIGGERS table is a core data object within the Oracle E-Business Suite (EBS) Quality (QA) module, specifically for versions 12.1.1 and 12.2.2. It serves as the master repository for defining the specific conditions, or triggers, that initiate a data collection event within a Quality Collection Plan. A Collection Plan is a predefined template for gathering inspection or test data. This table is integral to the transactional workflow of the Quality module, as it links the business logic of when to collect quality data (the trigger) to the actual collection transaction and the specific characteristic to be measured. Its primary role is to enable automated, rule-based quality data capture within manufacturing, procurement, and other business processes.

Key Information Stored

The table stores the relationships and identifiers that define a collection trigger. Based on the provided metadata, the critical columns include the primary key, TXN_TRIGGER_ID, which uniquely identifies each trigger record. The foreign key PLAN_TRANSACTION_ID links the trigger to its parent collection plan transaction record in the QA_PLAN_TRANSACTIONS table, defining the overall context (e.g., inspection for a specific purchase order receipt). The COLLECTION_TRIGGER_ID column is a foreign key to the QA_CHARS table, which stores the master definition of the quality characteristic (e.g., "Diameter," "Hardness") that is to be collected when this trigger fires. This structure allows a single collection plan transaction to have multiple triggers for different characteristics.

Common Use Cases and Queries

This table is central to configuring and troubleshooting automated quality inspections. A common use case is analyzing all active triggers within a specific collection plan to understand its inspection scope. For reporting, one might join this table to QA_PLAN_TRANSACTIONS and QA_CHARS to generate a list of characteristics triggered for a given plan. Database administrators or support personnel may query it to diagnose missing collection prompts in transactional forms. A typical analytical query pattern would be:

• Identifying all triggers for a plan: SELECT txn_trigger_id, collection_trigger_id FROM qa_plan_collection_triggers WHERE plan_transaction_id = <ID>;
• Joining to get characteristic names: SELECT pct.txn_trigger_id, qc.name FROM qa_plan_collection_triggers pct, qa_chars qc WHERE pct.collection_trigger_id = qc.char_id AND pct.plan_transaction_id = <ID>;

Related Objects

As indicated by the foreign keys, QA_PLAN_COLLECTION_TRIGGERS has direct and essential dependencies on two primary tables. The QA_PLAN_TRANSACTIONS table is the parent, containing the header-level information for the collection plan transaction, such as the associated document (e.g., PO, WO) and plan details. The QA_CHARS table is the master list of all definable quality characteristics within the system; the COLLECTION_TRIGGER_ID points to the specific characteristic to be measured. This table is also referenced by the primary key constraint QA_PLAN_COLLECTION_TRIGGERS_PK. Understanding these relationships is crucial for any data extraction, integration, or extension involving Quality's collection plan functionality.