Search Results user_flag




Overview

HZ_GROUP_WF_ROLES_V is an Oracle E-Business Suite (EBS) view owned by the APPS schema in the Receivables (AR) product family. Defined in the Trading Community Architecture (TCA) / Oracle Workflow integration layer, its role is to expose party records of type GROUP as Workflow roles, presenting each group as an addressable notification target. The view flattens the relationship between a party group, its preferred language, and its primary e-mail contact point into a single row so that Workflow notification subsystems and Receivables-driven routing logic can query a uniform role directory without joining the underlying TCA tables themselves.

In the ETRM documentation the object is listed with status VALID and is referenced across the 12.1.1 and 12.2.2 releases. The view name carries the WF (Workflow) prefix, indicating it participates in the Oracle Workflow / Notification role-resolution mechanism. The NAME column is constructed by concatenating the literal string 'HZ_GROUP:' with the party identifier, giving each group role a deterministic, name-space-qualified key such as HZ_GROUP:1234.

Underlying Base Objects

HZ_GROUP_WF_ROLES_V is defined over four base objects, all referenced through public synonyms in the APPS schema:

All three non-driving joins are outer joins, so a group is returned even when it has no primary e-mail contact point or no language preference.

Key Columns

  • NAME — the Workflow role name; 'HZ_GROUP:' || TO_CHAR(PARTY_ID).
  • DISPLAY_NAME — the party name used as the human-readable role label.
  • DESCRIPTION — the party mission statement, truncated to 1000 bytes via SUBSTRB.
  • NOTIFICATION_PREFERENCE — derived: if an e-mail address exists, the contact point's e-mail format (first 8 bytes) or 'MAILTEXT'; otherwise 'QUERY'.
  • LANGUAGE / TERRITORY — NLS language and territory from FND_LANGUAGES.
  • EMAIL_ADDRESS — party e-mail truncated to 320 bytes; FAX is always NULL.
  • ORIG_SYSTEM / ORIG_SYSTEM_ID — constant 'HZ_GROUP' and the party identifier, respectively.
  • STATUS — decoded from the party status: 'I' maps to 'INACTIVE', otherwise 'ACTIVE'.
  • USER_FLAG — hard-coded to 'N', indicating the roles exposed are system-defined (non-user) Workflow roles. This is the column most often located when users search for user_flag.
  • PARTITION_ID — constant 8. START_DATE, EXPIRATION_DATE, SECURITY_GROUP_ID are all NULL.

Common Use Cases and Queries

Typical scenarios include resolving group notification addresses for Workflow mailers, validating that a group has a usable e-mail contact point, and reporting on active group roles by language. The USER_FLAG column distinguishes these system-derived roles from user-defined Workflow roles; because it is a literal 'N', any filter on it returns every row.

Sample query — list active group roles with e-mail notifications:

SELECT name, display_name, email_address, notification_preference, language
FROM hz_group_wf_roles_v
WHERE status = 'ACTIVE' AND email_address IS NOT NULL;

Sample query — enumerate roles excluding user-defined entries:

SELECT orig_system_id, display_name, user_flag
FROM hz_group_wf_roles_v
WHERE user_flag = 'N';