Search Results argument_string

Overview

QA_ERES_PLAN_CHAR_ACTIONS_V is a PL/SQL view owned by the APPS schema in Oracle E-Business Suite, defined under the Quality Management (QA) product. Its documented purpose is to serve as the "plan element actions view for electronic records" within the Electronic Records and Electronic Signatures (ERES) framework. The view consolidates action definitions configured against quality plan characteristics together with the notification and distribution attributes maintained in the Alert (ALR) module, producing a single denormalized result set suited to reporting and integration.

The view is a reporting and data-access construct rather than a transactional entity. It exposes the metadata required to render, audit, or export the actions that a quality plan element (characteristic) triggers, including the message tokens, status, assigned characteristic, workflow linkage, and e-mail distribution parameters. Because the object is VALID and registered in ETRM, it is safe to reference in custom queries within EBS 12.1.1 and 12.2.2, subject to the standard APPS read privileges.

Underlying Base Objects

The view is defined over a fixed set of documented base objects, joined with outer-join semantics so that actions without a matching characteristic, alert, or workflow row still appear:

• QA_PLAN_CHAR_ACTIONS (QPCA) — driving table holding the plan characteristic action records.
• QA_ACTIONS (QA) — action definitions; supplies ACTION_DESCRIPTION.
• QA_CHARS (QC) — characteristic definitions; supplies ASSIGNED_CHAR_NAME.
• ALR_ACTIONS (ALRA) — alert action bodies and distribution parameters, filtered to APPLICATION_ID = 250 with active end dates by default.
• ALR_DISTRIBUTION_LISTS (DL) — distribution list names, restricted to APPLICATION_ID = 250 and ENABLED_FLAG = 'Y'.
• FND_APPLICATION_TL (FA) — translated application name for the alert program.
• WF_ITEM_TYPES_TL (WF) — workflow display name when ACTION_ID = 28.
• QA_ERES_PKG — package supplying COLLAPSE_MSG_TOKENS, used to normalize message and alert body text.

Key Columns

• PLAN_CHAR_ACTION_ID / PLAN_CHAR_ACTION_TRIGGER_ID — primary identifier and trigger linkage for the plan characteristic action.
• ACTION_ID / ACTION_DESCRIPTION — the action type and its descriptive text.
• CAR_NAME_PREFIX, CAR_TYPE_ID, CAR_TYPE_NAME, CAR_OWNER, CAR_OWNER_NAME — corrective/preventive action (CAR) context; CAR_TYPE_NAME and CAR_OWNER_NAME are returned as NULL.
• MESSAGE — collapsed message token string from QA_ERES_PKG.COLLAPSE_MSG_TOKENS.
• STATUS_CODE / STATUS_ID — action status indicators.
• ASSIGNED_CHAR_ID / ASSIGNED_CHAR_NAME, ASSIGN_TYPE — the characteristic to which the action is assigned.
• WORKFLOW_NAME — workflow display name, populated only when ACTION_ID = 28.
• ALR_ACTION_SET_ID / ALR_ACTION_ID / ALR_ACTION_BODY — alert action identity and collapsed body text.
• PROGRAM_APPLICATION_NAME, FILE_NAME, ARGUMENT_STRING, LIST — alert program and distribution list attributes.
• TO_RECIPIENTS, CC_RECIPIENTS, BCC_RECIPIENTS, SUBJECT, REPLY_TO — notification addressing; REPLY_TO is the return address used when recipients reply to generated e-mails.

Common Use Cases and Queries

Typical usage includes auditing ERES action configuration, extracting notification routing for a plan characteristic, and migrating action definitions between environments. A representative query retrieving the reply-to address and notification fields is shown below.

• Notification routing audit: SELECT PLAN_CHAR_ACTION_ID, ASSIGNED_CHAR_NAME, ACTION_DESCRIPTION, SUBJECT, REPLY_TO, TO_RECIPIENTS FROM QA_ERES_PLAN_CHAR_ACTIONS_V WHERE REPLY_TO IS NOT NULL.
• Workflow-linked actions: SELECT PLAN_CHAR_ACTION_ID, WORKFLOW_NAME, MESSAGE FROM QA_ERES_PLAN_CHAR_ACTIONS_V WHERE ACTION_ID = 28.
• Distribution list extract: SELECT ALR_ACTION_ID, LIST, SUBJECT, REPLY_TO FROM QA_ERES_PLAN_CHAR_ACTIONS_V WHERE LIST IS NOT NULL.
• Status reporting: SELECT STATUS_CODE, COUNT(*) FROM QA_ERES_PLAN_CHAR_ACTIONS_V GROUP BY STATUS_CODE.

Because the underlying joins restrict alert rows to APPLICATION_ID 250 and active distribution lists, result sets reflect only currently effective alert definitions unless the view text is altered.