Search Results qa_plan_char_actions_v




Overview
Explore in AI Chat

Overview

The QA_PLAN_CHAR_ACTIONS_V view is a denormalized reporting object within the Oracle E-Business Suite Quality (QA) module. It presents the complete configuration of collection plan actions, joining collection plans, plan elements (chars), triggers, and the actions that fire when specified conditions are met. The view is owned by the APPS schema and is marked VALID in both 12.1.1 and 12.2.2 environments. Its principal value lies in exposing human-readable names alongside the internal surrogate identifiers used by the action engine, which makes it suitable for ad hoc reporting, data extraction, and integration interfaces that must resolve an action's assigned element without performing additional lookups against QA_CHARS.

The view is particularly relevant to the "assigned_char_name" search term, since it aliases QC1.NAME as ASSIGNED_CHAR_NAME, allowing consumers to display the name of the character (element) assigned to a collection plan action directly from a single query.

Underlying Base Objects

The view text defines inner joins across four base objects and one outer join:

All referenced objects are documented as synonyms within the APPS schema in the 12.2.2 ETRM metadata, indicating the view relies on standard seeded synonym resolution rather than direct table references.

Key Columns

The view exposes the ROW_ID pseudo-column and the full set of audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN). Functional columns of interest include:

Common Use Cases and Queries

Typical usage includes auditing which actions are attached to a collection plan, verifying the element assigned to each action, and feeding downstream systems that require resolved names rather than IDs. A representative query to list all actions for a named plan, including assigned element names, is:

  • SELECT plan_name, char_name, trigger_sequence, action_description, assigned_char_name, assign_type FROM qa_plan_char_actions_v WHERE plan_name = :plan ORDER BY plan_id, trigger_sequence;
  • SELECT plan_char_action_id, plan_name, action_description FROM qa_plan_char_actions_v WHERE assigned_char_name IS NULL;
  • SELECT action_description, COUNT(*) FROM qa_plan_char_actions_v GROUP BY action_description;

Because CAR_TYPE_NAME and CAR_OWNER_NAME are defined as NULL, reports requiring those values must join to the relevant lookup or CAR master tables separately. Filtering on ASSIGNED_CHAR_NAME should account for the outer join, which returns null for actions with no assigned character.