Results for “fnd_event_tokens”

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

Overview

FND_EVENT_TOKENS is a table owned by the APPLSYS schema within the Oracle E-Business Suite Application Object Library (FND) product. It stores the individual name/value tokens associated with Business Events raised through the Oracle EBS Event Management framework. Business Events are the underlying mechanism by which the application publishes business activity — such as an order being booked, an invoice being validated, or an employee record changing — so that subscribing programs, workflows, and external integrations can react to it. Each Business Event carries a defined payload, and the payload structure is expressed as a collection of tokens. FND_EVENT_TOKENS persists that payload definition: one row exists for every token belonging to a given event.

From a data modeling perspective, the metadata classifies this object heuristically as standalone, meaning no foreign-key relationships were mined from its structure. Where a Data Vault style model is used, this table is best treated as a standalone structure rather than a classic hub, link, or satellite, because it does not present a dependent child relationship in the mined metadata. Its primary key, FND_EVENT_TOKENS_UK1, is defined over the combination of EVENT_ID and TOKEN, which gives each token a unique identity within its parent event.

Key Information Stored

The documented physical schema for release 12.2.2 contains four columns, and these are the attributes of interest:

• EVENT_ID — Identifies the Business Event to which the token belongs. This is the leading column of the primary key and the anchor for any lookup by event.
• TOKEN — The name of the individual payload token. Combined with EVENT_ID it forms the business-key candidate.
• TYPE — The data type assigned to the token, describing the nature of the value (for example character, number, or date) so subscribers can interpret the payload correctly.
• VALUE — The value associated with the token at the time the event was raised.

Two indexes are documented: the primary key FND_EVENT_TOKENS_UK1 and the unique index FND_EVENT_TOKENS_U1, both defined over (EVENT_ID, TOKEN). Because these two columns serve as the unique business key, they function as the natural identifier, while EVENT_ID alone acts as the grouping parent for each event's set of tokens.

Common Use Cases and Queries

The most frequent requirement is to enumerate all tokens for a specific event, typically after locating the Event ID of interest. A representative query pattern is:

• SELECT event_id, token, type, value FROM fnd_event_tokens WHERE event_id = :event_id ORDER BY token;

Administrators and developers also search by token name to find which events expose a particular payload element:

• SELECT event_id, token, type, value FROM fnd_event_tokens WHERE token = :token_name;

Typical scenarios include auditing the payload expected by a subscription, debugging why a workflow notification or integration did not receive the value it needed, and documenting the interface between EBS and external systems during integration design. Reporting uses include producing an inventory of tokens per event, verifying that TYPE assignments match subscriber expectations, and confirming that VALUE is populated consistently.

Related Objects

The following objects are most significant in relation to this table:

• FND_EVENTS — the parent event definition, joined on EVENT_ID.
• FND_EVENT_GROUPS — groups events for subscription and management purposes.
• FND_EVENT_SUBSCRIPTIONS — links events to subscribing programs, workflows, and agents.
• WF_EVENTS — the Workflow Business Event system view over event definitions.
• WF_EVENT_SUBSCRIPTIONS — Workflow-side subscription definitions that consume event payloads.
• FND_EVENT_RAISES — records of raised event instances that reference these tokens.

In each case the join key is EVENT_ID. The Event Management and Workflow Business Event APIs read these token definitions when constructing and delivering event payloads, making FND_EVENT_TOKENS a supporting definition table for the wider event infrastructure.