Search Results subscription_guid

Overview

The view WF_ACTIVE_SUBSCRIPTIONS_V, owned by the APPS schema and shipped with the FND – Application Object Library product, exposes the set of currently active Oracle Workflow event subscriptions. It is a reporting and diagnostic construct rather than a transactional entity: no data is stored within the view itself, and all content is derived at runtime from the underlying Workflow event and subscription tables. The view filters aggressively so that only enabled, licensed subscriptions against enabled, licensed events are surfaced, presenting the effective subscription configuration that the Workflow Business Event System will actually evaluate when an event is raised. In Oracle EBS 12.1.1 and 12.2.2 environments it is widely used during integration troubleshooting, subscription auditing, and impact analysis, because it collapses the raw subscription records into a single, human-readable result set that includes event names and resolved handler identifiers. The presence of the wf_process_type column is significant for developers searching on that term, as it indicates that the view reports the Workflow process type associated with process-based subscriptions.

Underlying Base Objects

The ETRM metadata documents three referenced base objects, all reached through APPS synonyms: WF_EVENTS, WF_EVENT_GROUPS, and WF_EVENT_SUBSCRIPTIONS. Functionally, the view joins WF_EVENT_SUBSCRIPTIONS to WF_EVENTS on the event filter GUID, applying predicates that require STATUS = 'ENABLED' and LICENSED_FLAG = 'Y' on both sides, and that restrict events to TYPE = 'EVENT'. A UNION ALL branch is present, consistent with the standard definition that combines event-level subscriptions with those associated with event groups, so that group-scoped subscriptions are reported alongside direct ones. Because the view is defined over synonyms, its object dependencies are recorded against the APPS synonyms rather than the underlying WF tables; this is normal for seeded EBS views and does not affect query behaviour.

Key Columns

• EVENT_NAME – the name of the enabled, licensed business event to which the subscription is attached.
• GENERATE_FUNCTION – the event's generation routine, prefixed with JAVA:// when the Java implementation is used; NULL when no generator exists.
• SYSTEM_GUID / SUBSCRIPTION_GUID – identifiers for the owning system and the subscription record itself.
• SUBSCRIPTION_SOURCE_TYPE / SUBSCRIPTION_SOURCE_AGENT_GUID – how and by which agent the subscription was created (local, remote, external).
• SUBSCRIPTION_PHASE – the phase within which the subscription fires; defaults to 0 via NVL.
• SUBSCRIPTION_RULE_FUNCTION – the rule function evaluated to decide whether the subscription executes, with the same JAVA:// decoding logic.
• WF_PROCESS_TYPE / WF_PROCESS_NAME – the Workflow item type and process invoked by the subscription; this is the column of interest for wf_process_type searches.
• SUBSCRIPTION_PARAMETERS – the parameter string passed to the subscribed function or process.
• SUBSCRIPTION_ON_ERROR_TYPE – the error-handling code applied when the subscription fails.
• SUBSCRIPTION_EXPRESSION, SUBSCRIPTION_RULE_DATA, SUBSCRIPTION_PRIORITY, SUBSCRIPTION_OUT_AGENT_GUID / SUBSCRIPTION_TO_AGENT_GUID – filter expression, rule payload, priority, and outbound routing targets.

Common Use Cases and Queries

The most frequent query is a lookup of subscriptions by event, used to confirm exactly which handlers will fire and in what order:

• SELECT event_name, wf_process_type, wf_process_name, subscription_priority FROM wf_active_subscriptions_v WHERE event_name = 'oracle.apps.wf.notification.send';
• SELECT event_name, wf_process_type, subscription_rule_function, subscription_phase FROM wf_active_subscriptions_v WHERE wf_process_type = 'APINVAPR';
• SELECT wf_process_type, COUNT(*) FROM wf_active_subscriptions_v GROUP BY wf_process_type ORDER BY 2 DESC;

These statements support impact analysis before disabling a process type, auditing custom versus seeded subscriptions, and diagnosing events that fail to invoke their expected Workflow. Because only enabled and licensed rows are returned, the view reflects production behaviour and is unsuitable for reviewing disabled or unlicensed configuration.