Results for “fnd_events”

40 results




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

Overview

FND_EVENTS is a core Oracle Application Object Library (FND) table owned by the APPLSYS schema. It functions as the central repository for the Oracle E-Business Suite event and business event system runtime, capturing system-generated, workflow-related, and subscription-driven events that flow through the event manager. Each row represents a single event instance, recording its source, payload context, originating session, and processing state. The table is central to Oracle Workflow Business Event System (BES) processing, the Oracle Alert engine, and various system monitoring and notification mechanisms in Release 12.1.1 and 12.2.2.

Based on the heuristic Data Vault classification derived from its foreign key structure, FND_EVENTS is modeled as a standalone table rather than a hub, link, or satellite. It carries no dependent child relationships in the documented FK graph, which suggests its primary role is as a transactional event log or queue rather than a shared master-data anchor. It references FND_SECURITY_GROUPS via SECURITY_GROUP_ID, providing the only documented outbound relationship.

Key Information Stored

The table contains 21 documented columns. The surrogate primary key is EVENT_ID, enforced through the unique index FND_EVENTS_U1 and the constraint FND_EVENTS_UK1. Several columns describe the origin and nature of the event:

  • EVENT_ID – Surrogate primary key and unique business-key candidate.
  • SOURCE_APPLICATION_ID – Application that generated the event.
  • SOURCE_ID and SOURCE_TYPE – Identify the specific source object and its entity type.
  • DEST_TYPE – Target entity category for downstream delivery.
  • MESSAGE_APPL_SHORT_NAME and MESSAGE_NAME – Locate the event's message definition within the FND message dictionary.
  • TIME – Timestamp when the event was raised.
  • SEVERITY – Priority or urgency classification of the event.
  • PROCESSED – Flag indicating whether the event has been consumed by its subscriber(s).
  • TOKENS – Payload parameter tokens carrying event data (typically CLOB/LONG).
  • MODULE – Functional module responsible for the event.
  • USER_ID, RESP_APPL_ID, RESPONSIBILITY_ID – Application user and responsibility context active when the event was raised.
  • SESSION_ID, NODE, DB_INSTANCE, AUDSID – Session and database instance identifiers useful for tracing concurrency and multi-node deployments.
  • SEC_GROUP_ID and SECURITY_GROUP_ID – Security grouping context, with SECURITY_GROUP_ID foreign-keyed to FND_SECURITY_GROUPS.

Common Use Cases and Queries

Administrators and developers query FND_EVENTS to diagnose why a business event did not trigger a subscription, to audit which events were raised by a module, or to measure event backlog and throughput. Typical patterns include unprocessed event detection, per-application event volume reporting, and session-level tracing.

  • Backlog check: SELECT EVENT_ID, MESSAGE_NAME, TIME FROM FND_EVENTS WHERE PROCESSED = 'N' ORDER BY TIME;
  • Application activity: SELECT SOURCE_APPLICATION_ID, COUNT(*) FROM FND_EVENTS GROUP BY SOURCE_APPLICATION_ID;
  • Session forensics: SELECT EVENT_ID, MESSAGE_NAME, USER_ID, NODE, AUDSID FROM FND_EVENTS WHERE SESSION_ID = :session_id;
  • Security-group scoping: join to FND_SECURITY_GROUPS on SECURITY_GROUP_ID to resolve group names in audit reports.

Related Objects

  • FND_SECURITY_GROUPS – Joined via FND_EVENTS.SECURITY_GROUP_ID = FND_SECURITY_GROUPS.SECURITY_GROUP_ID.
  • FND_USER – Enriches USER_ID with user names and status in event audits.
  • FND_APPLICATION – Resolves SOURCE_APPLICATION_ID and RESP_APPL_ID to application short names.
  • FND_RESPONSIBILITY – Resolves RESPONSIBILITY_ID for responsibility-level reporting.
  • WF_EVENT_T – Workflow object type associated with business event payload processing.
  • WF_EVENTS / WF_EVENT_SUBSCRIPTIONS – Define event subscribers that consume rows raised in FND_EVENTS.
  • FND_MESSAGES / FND_MESSAGE_TOKENS – Message dictionary definitions referenced by MESSAGE_NAME and MESSAGE_APPL_SHORT_NAME.