Results for “child_alert_id”

18 results




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

Overview

The ALR_PERIODIC_SET_MEMBERS table is a core data object within the Oracle Alert (ALR) application of Oracle E-Business Suite, present in both release 12.1.1 and 12.2.2. Oracle Alert provides proactive, event-driven and scheduled notification capabilities across the EBS instance, and this table stores the definitional membership of periodic alert sets. Specifically, it records which individual alerts and which nested periodic sets belong to a given parent periodic set, along with the ordering in which those members should be evaluated and delivered.

The object is owned by the ALR schema and carries a VALID status. Its documented description — "Member alerts and periodic sets of periodic sets" — highlights its recursive design: a periodic set can contain standalone alerts as well as references to other periodic sets, enabling hierarchical grouping of alert definitions. From a heuristic Data Vault modeling perspective, mined from the foreign key structure, this table is best classified as a link entity. It resolves a many-to-many relationship between parent periodic sets and their member components (alerts and subordinate periodic sets), rather than representing an independent business entity (hub) or a descriptive attribute history (satellite).

Key Information Stored

The table comprises 15 documented columns. The most significant are the composite identifiers and control attributes:

The surrogate primary key is ALR_PERIODIC_SET_MEMBERS_PK, defined across APPLICATION_ID, PERIODIC_SET_ID, CHILD_APPLICATION_ID, CHILD_ALERT_ID, CHILD_PERIODIC_SET_ID, and SEQUENCE. A separate unique index, ALR_PERIODIC_SET_MEMBERS_U1, extends this with ZD_EDITION_NAME, representing the business-key candidate under EBR.

Common Use Cases and Queries

Typical usage centers on resolving the composition and ordering of periodic alert sets. A frequent query enumerates the alerts contained in a set:

  • Dependency analysis: Join ALR_PERIODIC_SET_MEMBERS to ALR_PERIODIC_SETS and ALR_ALERTS to determine which alerts fire for a given scheduled set.
  • Hierarchy traversal: Follow CHILD_PERIODIC_SET_ID recursively to expand nested periodic-set structures.
  • Ordering reports: Sort by SEQUENCE to reproduce the runtime evaluation order.
  • Effectivity auditing: Filter on ENABLED_FLAG and END_DATE_ACTIVE to identify stale or inactive memberships.
  • Security-scoped extracts: Constrain by SECURITY_GROUP_ID for multi-org reporting.

A representative pattern: SELECT m.PERIODIC_SET_ID, m.SEQUENCE, m.CHILD_ALERT_ID FROM ALR.ALR_PERIODIC_SET_MEMBERS m WHERE m.APPLICATION_ID = :app AND m.PERIODIC_SET_ID = :set AND m.ENABLED_FLAG = 'Y' ORDER BY m.SEQUENCE;

Related Objects

  • ALR_PERIODIC_SETS — parent set definition; joined on APPLICATION_ID and PERIODIC_SET_ID.
  • ALR_ALERTS — member alert definitions; joined on CHILD_APPLICATION_ID and CHILD_ALERT_ID.
  • FND_SECURITY_GROUPS — security partitioning referenced via SECURITY_GROUP_ID.
  • ALR_PERIODIC_SET_MEMBERS_PK / _U1 — primary key and unique index enforcing member uniqueness and edition awareness.

These relationships make ALR_PERIODIC_SET_MEMBERS the structural join point linking alert definitions into the periodic sets executed by the Oracle Alert scheduler.