Search Results qa_plan_char_actions




Overview
Explore in AI Chat

Overview

The QA_PLAN_CHAR_ACTIONS table is a core data object within the Quality (QA) module of Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2. It functions as the central repository for defining and storing actions that are assigned to specific collection plan elements. In the context of Quality's collection plans, which are templates for data gathering during inspections and tests, this table enables the automation of business processes. It links a defined action—such as creating a Corrective Action Request (CAR), sending a notification, or updating a status—to a characteristic or element within a plan, typically based on a trigger condition. This mechanism is fundamental for implementing automated quality workflows directly from data collection points.

Key Information Stored

The table's primary purpose is to maintain the association between a collection plan element and an executable action. Its structure is defined by key foreign key relationships. The primary identifier for each unique action assignment is the PLAN_CHAR_ACTION_ID column, which is the table's primary key. Critical relational columns include ACTION_ID, which references the QA_ACTIONS table to identify the specific action to be performed (e.g., "Create CAR"). The PLAN_CHAR_ACTION_TRIGGER_ID links to the QA_PLAN_CHAR_ACTION_TRIGGERS table, defining the condition (e.g., "Result is Out of Specification") that fires the action. Furthermore, the CAR_TYPE_ID column references QA_CAR_TYPES, specifying the type of Corrective Action Request to generate if the associated action is of that nature.

Common Use Cases and Queries

A primary use case is auditing or reporting on the automated workflows configured within collection plans. For instance, a quality analyst may need to list all actions tied to a specific collection plan characteristic to verify process rules. A common query pattern involves joining to related tables to get descriptive information.

Sample Query: To retrieve all action assignments with their trigger conditions and action details, a developer might use: 

SELECT pca.PLAN_CHAR_ACTION_ID,
       a.ACTION_NAME,
       t.TRIGGER_NAME,
       ct.CAR_TYPE_NAME
FROM QA.QA_PLAN_CHAR_ACTIONS pca,
     QA.QA_ACTIONS a,
     QA.QA_PLAN_CHAR_ACTION_TRIGGERS t,
     QA.QA_CAR_TYPES ct
WHERE pca.ACTION_ID = a.ACTION_ID
  AND pca.PLAN_CHAR_ACTION_TRIGGER_ID = t.PLAN_CHAR_ACTION_TRIGGER_ID
  AND pca.CAR_TYPE_ID = ct.CAR_TYPE_ID(+);
This is also critical for troubleshooting why an expected automated action, such as a CAR creation, did not fire during a transaction, by verifying the configuration stored in this table.

Related Objects

The QA_PLAN_CHAR_ACTIONS table sits at the center of a key relationship network within the Quality schema, as documented in the ETRM metadata.

  • Referenced Foreign Keys (This table references):
    • QA_PLAN_CHAR_ACTION_TRIGGERS via PLAN_CHAR_ACTION_TRIGGER_ID: Links to the condition that triggers the action.
    • QA_CAR_TYPES via CAR_TYPE_ID: Specifies the type of Corrective Action Request.
    • QA_ACTIONS via ACTION_ID: Defines the executable action code.
  • Referencing Foreign Key (Another table references this one):
    • QA_PLAN_CHAR_ACTION_OUTPUTS via PLAN_CHAR_ACTION_ID: This table stores specific output parameters or results generated when the action is executed, creating a one-to-many relationship where a single plan action can produce multiple outputs.