Results for “qa_pc_actions_u1”

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

Overview

QA.QA_PLAN_CHAR_ACTIONS is an Oracle E-Business Suite collection plan configuration table in the Quality (QA) schema. Each row defines a single action assigned to a collection element (characteristic) within a collection plan. In ETRM terms, an action is the response the quality engine executes when a collection element's result satisfies a defined rule or trigger condition — for example, displaying a message to the operator, assigning an ASL status, invoking an Oracle Alert action set, or writing a value into a destination collection element.

The table is tightly coupled to QA_PLAN_CHAR_ACTION_TRIGGERS, which holds the evaluation condition, and to QA_ACTIONS, which holds the master definition of the action type. Because it stores descriptive attributes that qualify a parent action assignment rather than acting as a standalone master or a pure intersection of two masters, the heuristic Data Vault classification mined from the foreign key structure is satellite-leaning. In a Data Vault model this table would most naturally be modelled as a satellite hanging off the QA_PLAN_CHAR_ACTION_TRIGGERS hub or link, carrying the descriptive action attributes.

Key Information Stored

The table is defined in the APPS_TS_TX_DATA tablespace with PCTFREE 10 and comprises 19 documented columns. The most significant are:

• PLAN_CHAR_ACTION_ID — Surrogate primary key (QA_PLAN_CHAR_ACTIONS_PK) identifying a single action assignment for a collection element in a plan.
• PLAN_CHAR_ACTION_TRIGGER_ID — Foreign key to QA_PLAN_CHAR_ACTION_TRIGGERS; links the action to the rule/trigger that fires it. Indexed by non-unique index QA_PC_ACTIONS_N1.
• ACTION_ID — Foreign key to QA_ACTIONS; identifies the action type (message, ASL status, Alert, assign value, and so on).
• MESSAGE — VARCHAR2(2000) holding the actual text presented to the operator when the action is a message action.
• STATUS_CODE — VARCHAR2(30) holding the specific code applied by the action, such as the ASL status assigned.
• ALR_ACTION_SET_ID and ALR_ACTION_ID — Oracle Alert action set and action identifiers, used when the action delegates to Oracle Alert.
• ASSIGNED_CHAR_ID — Destination collection element for the "assign a value to a collection element" action.
• ASSIGN_TYPE — Indicates the assignment behaviour used with ASSIGNED_CHAR_ID.
• CAR_NAME_PREFIX, CAR_TYPE_ID, CAR_OWNER — Reserved columns intended for future use with the corrective action module.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard Who audit columns.

The documented unique index QA_PC_ACTIONS_U1 spans (PLAN_CHAR_ACTION_ID, ZD_EDITION_NAME), making the pair the business-key candidate. ZD_EDITION_NAME supports edition-based redefinition in 12.2.x.

Common Use Cases and Queries

The primary use case is configuration validation and impact analysis: determining which actions are attached to a collection plan element before changing or deactivating a plan. A typical join retrieves the action type and message for a plan:

• SELECT a.plan_char_action_id, a.message, a.status_code, act.action_type
  FROM qa.qa_plan_char_actions a, qa.qa_actions act
  WHERE a.action_id = act.action_id;
• Trace actions back to their trigger: join PLAN_CHAR_ACTION_TRIGGER_ID to QA_PLAN_CHAR_ACTION_TRIGGERS to list the condition each action responds to.
• Report on Oracle Alert integrations using ALR_ACTION_SET_ID / ALR_ACTION_ID to reconcile QA actions with Alert definitions.
• Audit configuration changes via CREATED_BY and LAST_UPDATE_DATE for compliance or release migration reviews.

Related Objects

• QA.QA_PLAN_CHAR_ACTION_TRIGGERS — joined on PLAN_CHAR_ACTION_TRIGGER_ID; the parent trigger definition.
• QA.QA_ACTIONS — joined on ACTION_ID; supplies action type semantics.
• QA.QA_CAR_TYPES — joined on CAR_TYPE_ID; reserved for the corrective action module.
• QA.QA_PLAN_CHAR_ACTION_OUTPUTS — child table referencing PLAN_CHAR_ACTION_ID; stores output values produced by the action.
• Standard QA collection plan setup forms and the QA/Alert public APIs that create and maintain plan actions depend on this table.