Results for “alr_profile_options_pk”

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

Overview

ALR.ALR_PROFILE_OPTIONS is a table in the Oracle Alert (ALR) product module of Oracle E-Business Suite, holding Alert profile options and their configured values. Alert is the EBS event-monitoring and notification engine; this table stores the internal profile settings that govern how Alert behaves, including option names, current values, descriptive text, and handling hints such as long-value flags and password encryption. It exists in both 12.1.1 and 12.2.2, where in 12.2.2 the presence of the ZD_EDITION_NAME column reflects the Edition-Based Redefinition (EBR) infrastructure introduced with Online Patching.

From a heuristic Data Vault modeling perspective, the mined FK structure classifies this object as standalone. Because it carries a natural business key and descriptive attributes with no dependent child tables identified, it is best treated as a satellite-like reference object rather than a hub or link. This is a modeling suggestion derived from the FK topology, not a physical constraint.

Key Information Stored

The table is documented with 14 columns. The most operationally important are:

• PROFILE_OPTION_NAME — the surrogate primary key (ALR_PROFILE_OPTIONS_PK) and the definitive business identifier for each Alert profile option.
• PROFILE_OPTION_VALUE — the currently effective, short-form value assigned to the option.
• PROFILE_OPTION_LONG — a companion column holding extended or long-form values when the setting exceeds the short value column.
• LONG_FLAG — indicates whether the option's value is stored in the long column, steering readers to the correct logical value.
• LOOKUP_TYPE — identifies the lookup type constraining valid values for a list-of-values profile option.
• ENCRYPTED_PASSWORD — storage for sensitive settings requiring encryption, relevant to admin and security review.
• DESCRIPTION — free-text narrative of the option; also a documented unique business-key candidate via ALR_PROFILE_OPTIONS_UK1.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, scoping the row to a security group.
• Audit columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, and LAST_UPDATE_LOGIN provide standard who/when lineage.
• ZD_EDITION_NAME — the edition discriminator participating in ALR_PROFILE_OPTIONS_U1 and U2, marking EBR-aware sets.

Business-key candidates are PROFILE_OPTION_NAME (either standalone or paired with ZD_EDITION_NAME) and DESCRIPTION (paired with ZD_EDITION_NAME). The surrogate primary key is PROFILE_OPTION_NAME.

Common Use Cases and Queries

Typical uses include auditing Alert configuration, validating option values across environments, and reporting on settings migrated between instances.

• Listing effective values, resolving the long flag: SELECT PROFILE_OPTION_NAME, CASE WHEN LONG_FLAG = 'Y' THEN PROFILE_OPTION_LONG ELSE PROFILE_OPTION_VALUE END AS EFFECTIVE_VALUE FROM ALR.ALR_PROFILE_OPTIONS;
• Reviewing options constrained by a lookup: SELECT PROFILE_OPTION_NAME, PROFILE_OPTION_VALUE, LOOKUP_TYPE FROM ALR.ALR_PROFILE_OPTIONS WHERE LOOKUP_TYPE IS NOT NULL;
• Security scoping against groups: SELECT p.PROFILE_OPTION_NAME, g.SECURITY_GROUP_NAME FROM ALR.ALR_PROFILE_OPTIONS p JOIN FND_SECURITY_GROUPS g ON p.SECURITY_GROUP_ID = g.SECURITY_GROUP_ID;
• Change monitoring: filter on LAST_UPDATE_DATE to detect recent configuration drift between patches.

Related Objects

• FND_SECURITY_GROUPS — referenced via ALR_PROFILE_OPTIONS.SECURITY_GROUP_ID; the sole documented foreign key target.
• ALR_PROFILE_OPTIONS_PK — primary key constraint on PROFILE_OPTION_NAME.
• ALR_PROFILE_OPTIONS_UK1 / U1 / U2 — unique index and business-key constraints on option name and description.
• FND_PROFILE_OPTIONS — the general EBS profile-option registry that conceptually parallels this Alert-specific store.
• Other ALR tables — sibling Alert configuration and runtime objects that share the ALR schema and consume these settings.