Results for “assign_type”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

QA_PLAN_CHAR_ACTIONS is a transactional table in the Oracle Quality (QA) module of Oracle E-Business Suite, present in both release 12.1.1 and 12.2.2. It stores the actions that are assigned to individual collection elements (characteristics) within a collection plan. In the Oracle Quality execution model, a collection plan defines what data is gathered during an inspection, test, or data collection event, and each element of that plan may carry one or more predefined responses — corrective actions, alerts, notifications, or workflow invocations — that fire when the collected value meets a configured condition. QA_PLAN_CHAR_ACTION_TRIGGERS defines the condition, while QA_PLAN_CHAR_ACTIONS defines what should happen when that condition evaluates true. The table is therefore central to automating quality responses, from opening a corrective action request to sending an alert or routing a message.

From a Data Vault modeling perspective, metadata heuristics classify this object as satellite-leaning. It is best treated as a descriptive satellite attached to a hub or link representing the plan/characteristic/action trigger combination, carrying the attributes that describe the assigned action and its status rather than defining an independent business entity.

Key Information Stored

The table’s documented physical schema contains 19 columns. The surrogate primary key is PLAN_CHAR_ACTION_ID, enforced by the QA_PLAN_CHAR_ACTIONS_PK constraint and generated per row. A unique index, QA_PC_ACTIONS_U1, covers PLAN_CHAR_ACTION_ID together with ZD_EDITION_NAME, making the pair a business-key candidate under the editioning model used in 12.2.x.

• PLAN_CHAR_ACTION_ID – surrogate primary key identifying each assigned action record.
• PLAN_CHAR_ACTION_TRIGGER_ID – foreign key to QA_PLAN_CHAR_ACTION_TRIGGERS, linking the action to the condition that fires it.
• ACTION_ID – foreign key to QA_ACTIONS, identifying the action definition to be executed.
• CAR_TYPE_ID – foreign key to QA_CAR_TYPES, specifying the corrective action request type when the action raises a CAR.
• CAR_NAME_PREFIX – prefix used to name the generated corrective action request.
• CAR_OWNER – the owner assigned to the resulting corrective action request.
• MESSAGE – text delivered with the action, typically an operator-facing message.
• STATUS_CODE – code indicating the disposition or state of the action assignment.
• ALR_ACTION_SET_ID / ALR_ACTION_ID – references to the Oracle Alert action set and alert action used when the response is delivered through the Alert engine.
• ASSIGNED_CHAR_ID / ASSIGN_TYPE – identify the characteristic to which the action is assigned and the assignment type.
• STATUS_ID – status identifier associated with the action record.
• ZD_EDITION_NAME – editioning column supporting Online Patching in 12.2.x.
• Audit columns – CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

Quality analysts and implementers query this table to audit which automated responses are attached to a collection plan element, to troubleshoot actions that did not fire, or to report on corrective action routing. A typical join traces a plan element to its trigger and action definition:

SELECT pca.plan_char_action_id,
       pca.action_id,
       pca.car_type_id,
       pca.car_owner,
       pca.message,
       pca.status_code
FROM   qa.qa_plan_char_actions pca
WHERE  pca.plan_char_action_trigger_id = :trigger_id;

A second pattern joins to QA_ACTIONS to describe the action name, or to QA_CAR_TYPES to determine the corrective action request type raised. Reporting extracts commonly include actions grouped by collection plan, actions referencing Oracle Alert action sets, and inventories of CAR-producing actions for quality management review.

Related Objects

• QA_PLAN_CHAR_ACTION_TRIGGERS – joined on PLAN_CHAR_ACTION_TRIGGER_ID; supplies the condition that invokes the action.
• QA_ACTIONS – joined on ACTION_ID; holds the action definition and its type.
• QA_CAR_TYPES – joined on CAR_TYPE_ID; defines corrective action request types.
• QA_PLAN_CHAR_ACTION_OUTPUTS – references this table via PLAN_CHAR_ACTION_ID; stores the outputs produced by the action.
• QA collection plan setup forms and the Quality API set – read and maintain rows here as plan elements are configured.

Together these objects form the action layer of the Oracle Quality collection plan framework, linking conditions to executable responses and their downstream outputs.