Search Results wf_agents

Overview

The WF_AGENTS table is a core repository within the Oracle E-Business Suite (EBS) Application Object Library, specifically for the Workflow and Business Event System infrastructure. It serves as the master definition table for all agents configured in the system. An agent, in this context, is a logical entity that can send or receive business event messages. It acts as an addressable endpoint for event communication, enabling the decoupled, asynchronous integration of application logic both within and outside the EBS instance. The table's role is fundamental to the operation of Oracle Workflow and the Advanced Queuing-based Business Event System, managing the metadata that defines how events are routed between systems, responsibilities, and users.

Key Information Stored

The table is designed around a Globally Unique Identifier (GUID) as its primary key, ensuring uniqueness across distributed systems. The critical columns include the GUID for the agent's primary key, the NAME which identifies the agent, and the SYSTEM_GUID which links the agent to its parent system definition in the WF_SYSTEMS table. This structure allows for the hierarchical organization of agents within systems. The table's design supports complex agent relationships, including grouping, as evidenced by its foreign key relationships with the WF_AGENT_GROUPS table.

Common Use Cases and Queries

A primary use case is troubleshooting event subscription failures or investigating the configuration of integration points. Database administrators and functional consultants query this table to list all defined agents, identify their associated system, and trace subscription configurations. A common diagnostic query is to join with WF_EVENT_SUBSCRIPTIONS to see which agents are designated as recipients or senders for specific events.

• Listing All Agents: SELECT name, guid, system_guid FROM apps.wf_agents ORDER BY name;
• Finding Subscriptions for an Agent: SELECT sub.* FROM apps.wf_event_subscriptions sub, apps.wf_agents ag WHERE ag.name = '&AGENT_NAME' AND (sub.out_agent_guid = ag.guid OR sub.to_agent_guid = ag.guid);
• Validating Agent Group Membership: Queries often join WF_AGENTS, WF_AGENT_GROUPS, and WF_SYSTEMS to resolve the complete addressing path for an event.

Related Objects

The WF_AGENTS table has integral relationships with several other Workflow tables, forming the backbone of the event model. As per the provided metadata, key related objects include:

• WF_SYSTEMS: Linked via the SYSTEM_GUID foreign key, defining the logical system to which an agent belongs.
• WF_AGENT_GROUPS: Has two foreign key relationships with WF_AGENTS (GROUP_GUID, MEMBER_GUID), enabling agents to be members of groups and groups to themselves be treated as agents.
• WF_EVENT_SUBSCRIPTIONS: Contains foreign keys for OUT_AGENT_GUID (the sending agent) and TO_AGENT_GUID (the receiving agent), directly linking event rule definitions to the agents involved in the messaging.

Direct manipulation of this table is strongly discouraged. Configuration should be performed through the Oracle Workflow Builder or the appropriate Business Event System administrative APIs to maintain data integrity.