Search Results hz_group




Overview
Explore in AI Chat

Overview

WF_HZ_GROUP_ROLES is a read-only database view owned by the APPS schema in Oracle E-Business Suite, classified under the FND – Application Object Library product. Its documented purpose is to serve as a Bulk Sync Directory Service Role View for the originating system identified as HZ_GROUP. In practical terms, the view projects TCA party records that represent groups into the column layout expected by the Oracle Workflow directory services integration, which synchronizes EBS users and roles with an external Lightweight Directory Access Protocol (LDAP) directory such as Oracle Internet Directory or Oracle Unified Directory.

The view is a denormalized, non-updatable projection rather than a stored table. It exists so the bulk synchronization process can retrieve a uniform set of role attributes—name, notification preference, language, e-mail address, and status—without embedding multi-table join logic directly in the synchronization program. It carries no seeded data of its own; all content is derived at query time from the TCA parties model. The view is marked VALID and is present in both 12.1.1 and 12.2.2 releases, though the partition-related column reflects the later multi-tenant (partitioned) data model.

Underlying Base Objects

The ETRM metadata documents four referenced base objects, all resolved through APPS synonyms: HZ_PARTIES, HZ_PERSON_LANGUAGE, HZ_CONTACT_POINTS, and FND_LANGUAGES. Each source column in the view text has an explicit correspondence to these objects.

  • HZ_PARTIES is the driving table, filtered to PARTY_TYPE = 'GROUP' and STATUS in ('A','I'). It supplies PARTY_ID, PARTY_NAME, MISSION_STATEMENT, EMAIL_ADDRESS, and STATUS.
  • HZ_CONTACT_POINTS is outer-joined on OWNER_TABLE_NAME = 'HZ_PARTIES' with a contact point type of EMAIL, PRIMARY_FLAG = 'Y', and STATUS = 'A'. This retrieves the primary e-mail contact point and the preferred e-mail format.
  • HZ_PERSON_LANGUAGE is outer-joined on PARTY_ID with PRIMARY_LANGUAGE_INDICATOR = 'Y' and STATUS = 'A', providing the party's preferred language name.
  • FND_LANGUAGES is outer-joined on LANGUAGE_NAME to the HZ_PERSON_LANGUAGE record, resolving the installed language code to its NLS language and territory values.

Because the three peripheral joins use the Oracle outer-join operator, a group party still appears in the view even when it has no e-mail contact point, no primary language, or no matching FND_LANGUAGES row. The ORIG_SYSTEM value is hard-coded to the literal 'HZ_GROUP', which is what distinguishes this role view from analogous views for other originating systems.

Key Columns

  • NAME – The role identifier, constructed as the concatenation 'HZ_GROUP:' with the party identifier, giving each group a globally unique directory key.
  • DISPLAY_NAME – Sourced from PARTY_NAME; the human-readable directory entry.
  • DESCRIPTION – Sourced from MISSION_STATEMENT on the party record.
  • NOTIFICATION_PREFERENCE – Derived from EMAIL_FORMAT with a default of 'MAILTEXT' via NVL.
  • LANGUAGE and TERRITORY – Taken from NLS_LANGUAGE and NLS_TERRITORY in FND_LANGUAGES.
  • EMAIL_ADDRESS – The primary e-mail value from HZ_CONTACT_POINTS; FAX is returned as NULL.
  • ORIG_SYSTEM / ORIG_SYSTEM_ID – Literal 'HZ_GROUP' and the underlying PARTY_ID.
  • STATUS – DECODE of party status, mapping 'I' to INACTIVE and everything else to ACTIVE.
  • START_DATE, EXPIRATION_DATE, SECURITY_GROUP_ID, USER_FLAG, PARTITION_ID – Returned as NULL, NULL, NULL, 'N', and 8 respectively. USER_FLAG = 'N' indicates these are group roles, not individual user accounts.

Common Use Cases and Queries

The principal use case is diagnostic and troubleshooting work on bulk directory synchronization. Administrators and developers query this view to confirm exactly which groups the synchronization program will publish and with what attributes, before or after running the bulk sync concurrent program.

Listing all active group roles with their notification e-mail:

SELECT name, display_name, email_address, status
FROM   apps.wf_hz_group_roles
WHERE  status = 'ACTIVE';

Identifying groups that have no reachable e-mail and would therefore synchronize without a delivery address:

SELECT orig_system_id, display_name
FROM   apps.wf_hz_group_roles
WHERE  email_address IS NULL;

Joining back to HZ_PARTIES for the unprojected party attributes, or filtering on the ORIG_SYSTEM literal when comparing this role view against other directory role views in the same integration, are also common patterns. Because the view exposes PARTITION_ID as a constant, it is safe to query in a multi-tenant 12.2.2 environment without additional partition predicates. No DML should ever be issued against the view.