Results for “wf_systems”

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

Overview

WF_SYSTEMS is the master definition table for the Business Event System (BES) in Oracle E-Business Suite, owned by the APPLSYS schema and registered under the FND – Application Object Library product. Each row in WF_SYSTEMS represents a logical system known to the Business Event System, such as a local EBS instance, a remote EBS instance, or an external application that participates in event propagation, subscription routing, or agent communication. Because every WF_AGENTS record and every WF_EVENT_SUBSCRIPTIONS record must resolve to a defined system, WF_SYSTEMS functions as the identity registry that anchors the entire event messaging topology in Oracle Workflow.

From a dimensional modeling perspective, the documented foreign key structure—specifically the self-referencing MASTER_GUID column and the inbound references from WF_AGENTS and WF_EVENT_SUBSCRIPTIONS—suggests a hub-leaning Data Vault classification. WF_SYSTEMS holds stable, relatively low-volatility business keys (GUID, NAME) and is referenced by multiple dependent tables, which is characteristic of a hub entity. Attributes such as DISPLAY_NAME and DESCRIPTION would typically be modeled as satellite data around that hub.

Key Information Stored

The table contains seven documented columns. The surrogate primary key is GUID, enforced through the WSM_PK constraint. Two unique indexes serve as business-key candidates: WF_SYSTEMS_U1 on (GUID, ZD_EDITION_NAME) and WF_SYSTEMS_U2 on (NAME, ZD_EDITION_NAME), indicating that NAME is the human-recognizable unique identifier for a system within an edition.

• GUID – Globally unique identifier and primary key; the internal handle referenced by dependent agents and subscriptions.
• NAME – The unique system name used in subscription and agent definitions; a documented business-key candidate via WF_SYSTEMS_U2.
• MASTER_GUID – Self-referencing foreign key pointing back to WF_SYSTEMS, used to relate a system record to its master (for example, in replicated or editioned configurations).
• DISPLAY_NAME – User-facing label presented in Workflow administrator and Business Event System setup screens.
• DESCRIPTION – Free-text explanation of the system's purpose or scope.
• SECURITY_GROUP_ID – Foreign key to FND_SECURITY_GROUPS, controlling which security group may access the system definition.
• ZD_EDITION_NAME – Editioning column supporting Online Patching in EBS 12.2.x; it participates in both unique indexes.

Common Use Cases and Queries

Typical use cases include identifying the local system during event subscription setup, auditing which systems participate in cross-instance event propagation, and troubleshooting agent or subscription failures caused by missing system definitions. A standard lookup by name returns the surrogate key needed to join downstream tables:

SELECT guid, name, display_name, description FROM applsys.wf_systems WHERE name = :p_system_name;

To enumerate all agents belonging to a given system, join on the documented foreign key WF_AGENTS.SYSTEM_GUID:

SELECT a.agent_guid, a.name FROM applsys.wf_agents a, applsys.wf_systems s WHERE a.system_guid = s.guid AND s.name = :p_system_name;

Subscriptions can be reported similarly through WF_EVENT_SUBSCRIPTIONS.SYSTEM_GUID. Resolving the self-referencing MASTER_GUID hierarchy is useful when reconciling replicated system definitions.

Related Objects

• WF_AGENTS – References WF_SYSTEMS via SYSTEM_GUID; holds agents that communicate on behalf of each system.
• WF_EVENT_SUBSCRIPTIONS – References WF_SYSTEMS via SYSTEM_GUID; defines event subscriptions scoped to a system.
• WF_SYSTEMS (self) – MASTER_GUID references the parent system record.
• FND_SECURITY_GROUPS – Referenced by SECURITY_GROUP_ID; governs access to the system definition.