Results for “plan_element_action_id”

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

Overview

QAFV_COLPLNELAC is a read-only Oracle EBS view owned by the APPS schema in the Quality (QA) module. Its name is an abbreviation of "Collection Plan Element Action," and its documented status is VALID. The object carries the description "- Retrofitted," indicating it was introduced or renamed as part of an upgrade or localization retrofit and retained for backward compatibility. In practice, the view exposes a denormalized, user-readable projection of the QA_PLAN_CHAR_ACTIONS table, joining action triggers to collection elements and quality action types. Its principal role is to support reporting, concurrent programs, and integration extracts that need collection plan element actions in a business-friendly form rather than a raw identifier-only structure. Because the view is defined WITH READ ONLY, it is intended strictly for query access; no DML should be attempted against it.

Underlying Base Objects

The view is defined over three base objects, all referenced through APPS synonyms:

• QA_PLAN_CHAR_ACTIONS (aliased QPCA) — the driving table, holding plan character actions and their triggers.
• QA_CHARS (aliased COLLECTION_ELEMENT) — the quality character or collection element master, joined with an outer join (+) on ASSIGNED_CHAR_ID = CHAR_ID.
• QA_ACTIONS (aliased QUALITY_ACTION_TYPE) — the action definition master, supplying the action description via an inner join on ACTION_ID.

The join uses Oracle outer-join syntax, so rows in QA_PLAN_CHAR_ACTIONS with no matching collection element are still returned, with the collection element columns null. Because the join to QA_ACTIONS is not outer, only rows with a valid action definition are exposed. The view performs no aggregation and applies no WHERE clause filter.

Key Columns

• PLAN_ELEMENT_ACTION_ID — renamed from QPCA.PLAN_CHAR_ACTION_ID; the unique identifier of the plan element action.
• MESSAGE — descriptive message text associated with the action.
• STATUS_CODE — status of the plan element action.
• PLAN_ELEMENT_ACTION_TRIGGER_ID — renamed from PLAN_CHAR_ACTION_TRIGGER_ID; identifies the trigger record.
• ACTION_ID / ACTION_DESCRIPTION — the action identifier and its translated description from QA_ACTIONS.
• ASSIGNED_COLLECTION_ELEMENT_ID / ASSIGNED_COLLECTION_ELEMENT — renamed from ASSIGNED_CHAR_ID and resolved to the character NAME from QA_CHARS.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY — standard EBS audit columns for change tracking.

Note the naming convention: "CHAR" identifiers are surfaced as "COLLECTION_ELEMENT," reflecting later Quality terminology, which aids readability in reports.

Common Use Cases and Queries

Typical scenarios include auditing which actions are attached to collection plan elements, generating action-trigger listings for quality plans, and feeding downstream extracts. A representative query is:

• SELECT plan_element_action_id, action_description, assigned_collection_element, status_code, message FROM apps.qafv_colplnelac WHERE status_code = 'ACTIVE';
• SELECT assigned_collection_element, COUNT(*) FROM apps.qafv_colplnelac GROUP BY assigned_collection_element; — distribution of actions across collection elements.
• SELECT * FROM apps.qafv_colplnelac WHERE assigned_collection_element_id IS NULL; — isolates plan element actions lacking a collection element, exploiting the outer join.

Because the view is read only and unindexed itself, performance depends on indexes on QA_PLAN_CHAR_ACTIONS and the joined master tables; filtering on status or action identifiers is advisable for large volumes.