Results for “alr_alert_installations”

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

Overview

ALR_ALERT_INSTALLATIONS is a core configuration table owned by the ALR (Alert) schema in Oracle E-Business Suite, present in both 12.1.1 and 12.2.2. It records the installation and registration of Oracle Alert definitions against specific database users and data groups, effectively binding an alert to the execution context in which it is intended to run. In Oracle Alert, an alert definition stored in ALR_ALERTS must be installed against one or more database users (Oracle IDs) so that the alert can be evaluated by the Alert Manager concurrent program within a particular application and data group. This table is the persistent registry of those installations, and the ENABLED_FLAG column governs whether a given installation is active.

The heuristic Data Vault classification mined from the foreign key structure is link. This is a modeling suggestion: the table resolves a many-to-many association between alert definitions and the Oracle user IDs and data groups against which they are installed, and it carries descriptive state (the enabled flag and audit columns), so it behaves as an associative or link entity rather than a hub or a satellite.

Key Information Stored

The documented table contains 12 columns. The composite primary key, ALR_ALERT_INSTALLATIONS_PK, comprises APPLICATION_ID, ALERT_ID, ORACLE_ID, and DATA_GROUP_ID. A separate unique index, ALR_ALERT_INSTALLATIONS_U1, extends this with ZD_EDITION_NAME and is the business-key candidate that supports edition-aware lookups in 12.2.2.

• APPLICATION_ID — identifies the application owning the alert definition; joins to ALR_ALERTS.
• ALERT_ID — the alert definition being installed; also joins to ALR_ALERTS.
• ORACLE_ID — the database user against which the alert is installed; joins to FND_ORACLE_USERID.
• DATA_GROUP_ID — the data group scoping the installation; joins to FND_DATA_GROUPS.
• ENABLED_FLAG — indicates whether this particular installation is active for Alert Manager processing.
• SECURITY_GROUP_ID — the security group under which the row is visible; joins to FND_SECURITY_GROUPS.
• ZD_EDITION_NAME — the edition identifier used by the 12.2.2 editioning model.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — standard EBS audit columns.

Common Use Cases and Queries

Typical use cases include auditing which alerts are installed and enabled, troubleshooting why an alert does not fire for a given user, and migrating alert installations between environments. A representative listing query joins the table to its parents:

• SELECT ai.application_id, ai.alert_id, aa.alert_name, ai.oracle_id, ai.data_group_id, ai.enabled_flag FROM alr.alr_alert_installations ai, alr.alr_alerts aa WHERE ai.application_id = aa.application_id AND ai.alert_id = aa.alert_id AND ai.enabled_flag = 'Y';
• Filtering by ORACLE_ID isolates all alerts installed for a specific database user.
• Filtering by DATA_GROUP_ID supports data-group–scoped reviews during a clone or patching cycle.
• Counts grouped by APPLICATION_ID and ALERT_ID reveal alerts with multiple or missing installations.

Related Objects

• ALR_ALERTS — parent definition table; joined on APPLICATION_ID and ALERT_ID.
• FND_ORACLE_USERID — the installed database user; joined on ORACLE_ID.
• FND_DATA_GROUPS — the data group context; joined on DATA_GROUP_ID.
• FND_SECURITY_GROUPS — security scope; joined on SECURITY_GROUP_ID.
• ALR_ALERT_INSTALLATIONS_PK / ALR_ALERT_INSTALLATIONS_U1 — the primary and unique indexes that enforce key integrity.

Together these objects form the installation and enablement layer of the Oracle Alert subsystem.