Results for “action_type_meaning”

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

Overview

The ALR_RESPONSE_ACTIONS_VIEW is a reporting and integration view within the Oracle E-Business Suite ALR – Alert product module. It resides in the APPS schema and carries a VALID status in both Oracle EBS 12.1.1 and 12.2.2. The view is documented as presenting "All the defined action plus the pre-defined action 'Return Original Mail'." In practical terms, it consolidates the set of user-configured Alert response actions with a single synthetic, pre-seeded entry representing the built-in "Return Original Mail" capability, exposing them through a uniform structure suitable for inbound/outbound integration and custom reporting.

The view exists to simplify consumer access to Alert action metadata. Rather than requiring callers to resolve lookup meanings, filter disabled rows, and separately model the pre-defined return-mail action, the view performs these operations once and returns a clean, ready-to-query result set keyed on APPLICATION_ID, ALERT_ID, and ACTION_ID.

Underlying Base Objects

The ETRM metadata documents the view as being defined over two base objects, both referenced through synonyms: ALR_ACTIONS and ALR_LOOKUPS. The view text confirms this relationship through a UNION ALL of two branches:

• First branch (defined actions): Joins ALR_ACTIONS to ALR_LOOKUPS to retrieve only database-level actions (ACTION_LEVEL_TYPE = 'D') whose ACTION_TYPE resolves to a lookup with LOOKUP_TYPE = 'ACTION_TYPE', and that are currently enabled (ENABLED_FLAG = 'Y').
• Second branch (pre-defined action): Derives the "Return Original Mail" row by cross-joining the RETURN_MAIL_ACTION lookup (R) with the ACTION_TYPE lookup (A) restricted to LOOKUP_CODE = 'M', emitting fixed sentinel values of -2 for the numeric identifiers and 'Y' for ENABLED_FLAG.

This dual-branch design is why the view's row population depends jointly on the configuration stored in ALR_ACTIONS and the lookup definitions maintained in ALR_LOOKUPS.

Key Columns

• APPLICATION_ID – Identifies the application context for the action.
• ALERT_ID – The Alert to which the action belongs.
• NAME – The action name; for the pre-defined branch this is drawn from the RETURN_MAIL_ACTION lookup meaning.
• ACTION_ID – Unique action identifier (-2 for the synthetic return-mail row).
• ACTION_TYPE – The raw action type code.
• ACTION_TYPE_MEANING – The decoded, human-readable meaning of the action type, obtained by joining to the ACTION_TYPE lookup. This is the column most frequently targeted by users searching for "action_type_meaning."
• DESCRIPTION – Descriptive text for the action.
• ENABLED_FLAG – Indicates whether the action is active.

Common Use Cases and Queries

Typical scenarios include enumerating all valid response actions for a given Alert, resolving action type codes to readable labels, and reporting on enabled actions while automatically including the built-in return-mail option.

• List all enabled actions with their meanings:

  SELECT action_id, name, action_type, action_type_meaning
  FROM   apps.alr_response_actions_view
  WHERE  enabled_flag = 'Y';

• Filter to a specific alert:

  SELECT name, action_type_meaning, description
  FROM   apps.alr_response_actions_view
  WHERE  alert_id = :alert_id
  AND    application_id = :app_id;

• Confirm the availability of the pre-defined "Return Original Mail" action using its sentinel identifier:

  SELECT name, action_type_meaning
  FROM   apps.alr_response_actions_view
  WHERE  action_id = -2;

Because the view applies the enabled filter itself, downstream queries need not re-apply it, though explicit filtering remains good practice for clarity.