Results for “irep_annotation”

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

Overview

WF_EVENTS is the core definition table for the Oracle EBS Business Event System (BES), owned by the APPLSYS schema and registered under the FND – Application Object Library product. Each row defines a single business event or system event that the Workflow engine can raise, subscribe to, or propagate across applications. In Oracle EBS 12.1.1 and 12.2.2 the table anchors the event-driven integration framework used by Workflow, Oracle Alert, XML Gateway, and inter-application messaging.

From a Data Vault modeling perspective, the metadata's heuristic classification places WF_EVENTS as a hub. It stores the unique business keys (event name and GUID) around which subscriptions, groups, and dependent service registrations revolve, making it a natural candidate for a hub entity with satellites or links attached to it.

Key Information Stored

The table contains 13 documented columns. The most significant are:

• GUID – the surrogate primary key (constraint WET_PK) uniquely identifying each event row; also participates in unique index WF_EVENTS_U1 with ZD_EDITION_NAME.
• NAME – the business-key event name (for example, oracle.apps.fnd.…), enforced by unique index WF_EVENTS_U2 together with ZD_EDITION_NAME.
• TYPE – classifies the event (for example, business event versus system/notification event).
• STATUS – controls whether the event is enabled and can be raised.
• GENERATE_FUNCTION – names the PL/SQL function invoked to generate or raise the event.
• JAVA_GENERATE_FUNC – the Java equivalent where the event is generated from Java code.
• OWNER_NAME and OWNER_TAG – identify the owning application or product team for the event.
• SECURITY_GROUP_ID – foreign key to FND_SECURITY_GROUPS, governing visibility and access control.
• CUSTOMIZATION_LEVEL – determines whether the event definition may be extended or overridden at customer sites.
• LICENSED_FLAG – indicates licensing status for the event's owning component.
• IREP_ANNOTATION – annotation metadata used during integrated repository (iRep) generation.
• ZD_EDITION_NAME – editioning column supporting Online Patching in 12.2.x.

The surrogate key (GUID) and the business key (NAME) are cleanly distinguished: WET_PK anchors referential integrity, while WF_EVENTS_U1 and WF_EVENTS_U2 enforce uniqueness of the natural keys.

Common Use Cases and Queries

Typical scenarios include auditing the event catalog, diagnosing missing or suppressed subscriptions, and confirming that a custom event has been defined correctly before subscriptions are raised.

Listing enabled business events:

SELECT name, type, status, owner_name
FROM   applsys.wf_events
WHERE  status = 'ENABLED';

Locating the GUID for a named event (used when joining to subscriptions):

SELECT guid, name, generate_function
FROM   applsys.wf_events
WHERE  name = :event_name;

Tracing which subscriptions listen to an event:

SELECT s.event_filter_guid, s.subscription_name
FROM   applsys.wf_event_subscriptions s, applsys.wf_events e
WHERE  s.event_filter_guid = e.guid
AND    e.name = :event_name;

Reporting events grouped by owner or product area is also common, using OWNER_NAME as the aggregation dimension.

Related Objects

• WF_EVENT_SUBSCRIPTIONS – joins on EVENT_FILTER_GUID to WF_EVENTS.GUID; defines listeners for each event.
• WF_EVENT_GROUPS – joins via GROUP_GUID and MEMBER_GUID, allowing events to be bundled and subscribed to collectively.
• CS_SR_EVENT_CODES_B – references WF_BUSINESS_EVENT_ID, linking Service Request event codes to BES events.
• UMX_REG_SERVICES_B – references WF_NOTIFICATION_EVENT_GUID, tying notification registration to events.
• FND_SECURITY_GROUPS – parent of SECURITY_GROUP_ID, providing the access-control context for each event.

These relationships confirm WF_EVENTS as the central hub of the Business Event System, with subscriptions, groups, and service registrations all depending on its GUID and NAME keys.