Search Results hz_group




Overview
Explore in AI Chat

Overview

APPS.WF_HZ_GROUP_ROLES is a reporting and integration view that exposes Oracle Trading Community Architecture (TCA) group parties in a normalized, role-oriented format consumed by the Oracle Workflow directory services layer. Its purpose is to present records that describe "HZ_GROUP" entities — that is, parties whose PARTY_TYPE is 'GROUP' — together with their email routing attributes and primary language preferences. The view is one member of a family of Workflow directory views (the WF_*_ROLES series) that collectively populate the Oracle Workflow notification and directory schema used by the Workflow Notification System, the Workflow Directory Services APIs, and related administrative functions in Oracle E-Business Suite 12.1.1 and 12.2.2.

Because Oracle Workflow requires a uniform, denormalized representation of notification recipients, this view flattens selected columns from the TCA party model into the positional column layout expected by the Workflow directory structure. Each row represents a single group party, identified by a synthetic key prefixed with 'HZ_GROUP:', and is tagged with the literal role value 'HZ_GROUP'. This makes group parties addressable as notification targets within Workflow-driven processes without requiring consumers to join directly against the underlying TCA tables.

Underlying Base Objects

The view is defined over four referenced base objects, all accessed through APPS synonyms:

  • HZ_PARTIES — the driving table; supplies the group party identity, name, mission statement, email address, and status.
  • HZ_CONTACT_POINTS — supplies the primary active email contact point for the party, including the email format attribute.
  • HZ_PERSON_LANGUAGE — supplies the primary active language of the party.
  • FND_LANGUAGES — supplies the NLS language and territory codes corresponding to that language name.

All joins to HZ_CONTACT_POINTS, HZ_PERSON_LANGUAGE, and FND_LANGUAGES are outer joins, so a group party is returned even when it lacks a primary email contact point or a primary language assignment. The predicates restrict the result set to parties of type 'GROUP' with status 'A' (active) or 'I' (inactive), and further constrain contact points to type 'EMAIL', primary flag 'Y', and status 'A', and person languages to primary indicator 'Y' and status 'A'.

Key Columns

  • Role/Key (column 1) — Synthetic identifier formed as 'HZ_GROUP:'||TO_CHAR(p.party_id), uniquely addressing the group within the Workflow directory.
  • Party Name — P.PARTY_NAME, the display name of the group.
  • Mission Statement — P.MISSION_STATEMENT, optional descriptive text carried into the directory record.
  • Email Format — NVL(CP.EMAIL_FORMAT,'MAILTEXT'), the notification mail format, defaulting to MAILTEXT when unspecified.
  • NLS Language / NLS Territory — L.NLS_LANGUAGE and L.NLS_TERRITORY, derived from the party's primary language.
  • Email Address — P.EMAIL_ADDRESS from the party record.
  • Role Literal — the constant 'HZ_GROUP' identifying the record type.
  • Party ID — P.PARTY_ID, the underlying TCA identifier.
  • Status — DECODE(P.STATUS,'I','INACTIVE','ACTIVE'), presenting the internal status code in readable form.
  • Positional Nulls and Constant 8 — placeholder columns and a type indicator required by the consuming Workflow directory structure.

Common Use Cases and Queries

Typical consumers include Workflow notification configuration, directory synchronization routines, and diagnostic reports that must enumerate group parties eligible for notification. A simple listing query follows:

  • SELECT party_name, email_address, nls_language FROM apps.wf_hz_group_roles WHERE status = 'ACTIVE' ORDER BY party_name;
  • SELECT * FROM apps.wf_hz_group_roles WHERE party_id = :p_party_id; — retrieving the Workflow-format record for a specific TCA group.
  • SELECT COUNT(*) FROM apps.wf_hz_group_roles WHERE email_address IS NULL; — identifying active groups without a routable primary email contact point.

Because the view performs outer joins, records with null email addresses or null NLS values remain visible, which is useful when auditing TCA data completeness for Workflow notification readiness.