Results for “member_guid”

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

Overview

WF_AGENT_GROUPS is an Oracle Workflow agent relationship table owned by the APPLSYS schema and registered under the FND – Application Object Library product in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented description, "Agent Group Relations," describes its purpose precisely: it stores the membership mapping that defines which agents belong to a given agent group. An agent group in Oracle Workflow is a named collection of individual agents (users, roles, responsibilities, or other groups) that can be notified, routed to, or resolved as a single logical recipient. WF_AGENT_GROUPS records the individual group-to-member associations that make up those collections, and it therefore underpins notification resolution, routing expansion, and workload assignment throughout the workflow engine.

The documented structure consists of only four columns and is therefore narrow, but it participates in the core agent model. Based on the foreign key topology supplied in the metadata, the table is best characterized as a link table in a Data Vault modeling sense: it connects two references to WF_AGENTS (the group and the member) and a security group reference, making it a many-to-many relationship resolver rather than an entity or descriptive satellite.

Key Information Stored

• GROUP_GUID – Identifies the agent group. This is a foreign key to WF_AGENTS.GROUP_GUID and forms part of both the primary key and the unique business key.
• MEMBER_GUID – Identifies the member agent contained in the group. It also references WF_AGENTS and forms the second component of the composite keys.
• SECURITY_GROUP_ID – References FND_SECURITY_GROUPS, providing multi-org/security-group isolation for the relationship row.
• ZD_EDITION_NAME – The editioning column used in 12.2.x Edition-Based Redefinition, included in the WF_AGENT_GROUPS_U1 unique index.

The documented primary key is WAP_PK, a composite surrogate key over (GROUP_GUID, MEMBER_GUID). The business-key candidate is the unique index WF_AGENT_GROUPS_U1 over (GROUP_GUID, MEMBER_GUID, ZD_EDITION_NAME). Because the surrogate key columns and the business key columns overlap almost entirely, the practical distinctness of a group-member pair is guaranteed by the unique index rather than by any independently generated identifier.

Common Use Cases and Queries

Typical requirements include expanding a group to its members for notification delivery, verifying a group's composition, and identifying all groups to which a given agent belongs.

• List members of a group:

  SELECT member_guid FROM wf_agent_groups WHERE group_guid = :p_group;

• Find all groups containing an agent:

  SELECT group_guid FROM wf_agent_groups WHERE member_guid = :p_member;

• Resolve group and member names by joining twice to WF_AGENTS:

  SELECT g.display_name group_name, m.display_name member_name FROM wf_agent_groups ag, wf_agents g, wf_agents m WHERE ag.group_guid = g.guid AND ag.member_guid = m.guid;

Reporting uses include auditing group membership for approval hierarchies, detecting orphaned or stale memberships, and supporting security-group-scoped extracts filtered on SECURITY_GROUP_ID.

Related Objects

• WF_AGENTS – Referenced twice: WF_AGENT_GROUPS.GROUP_GUID → WF_AGENTS.GROUP_GUID and WF_AGENT_GROUPS.MEMBER_GUID → WF_AGENTS.MEMBER_GUID. This is the principal join target for resolving names and agent types.
• FND_SECURITY_GROUPS – Referenced by WF_AGENT_GROUPS.SECURITY_GROUP_ID for security-group isolation.
• WF_AGENT_GROUP_MEMBERS and related workflow agent APIs – Workflow agent resolution APIs read group membership through this table when expanding notification lists.
• WF_NOTIFICATIONS / WF_ROLES – Downstream notification and role resolution consumes the expanded membership produced from this table.

Because the table is a narrow link, most dependencies are expressed through the WF_AGENTS and FND_SECURITY_GROUPS foreign keys, and administration is normally performed through Oracle Workflow administrator functions rather than direct DML.