Results for “per_name”

22 results




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

Overview

APPS.HZ_PARTY_WF_ROLES_V is an Oracle E-Business Suite view that exposes parties registered in the Trading Community Architecture (TCA) registry as Oracle Workflow roles. It is the primary source used by the Workflow Notification System to resolve a party (a person or a party relationship) into a notification address, a language, and a territory so that outbound Workflow messages can be delivered correctly. The view is owned by the APPS schema and is available in both 12.1.1 and 12.2.2 with identical structure.

The view is a join-based, non-key-preserved view built on top of HZ_PARTIES, HZ_RELATIONSHIPS, HZ_CONTACT_POINTS, HZ_PERSON_LANGUAGE and FND_LANGUAGES. It exposes data in the flat shape expected by the WF_ROLES columns (NAME, DISPLAY_NAME, NOTIFICATION_PREFERENCE, LANGUAGE, TERRITORY, EMAIL_ADDRESS, STATUS, and so on), allowing Workflow and custom integrations to treat TCA parties as first-class Workflow roles.

The NAME column is constructed as 'HZ_PARTY:'||to_char(per_id), which is the Workflow role identifier for a party.

Underlying Base Objects

  • HZ_PARTIES — referenced twice (aliases p and subj); supplies the party ID, party name, email address, and status, and the subject party name (subj_name) for relationship rows.
  • HZ_RELATIONSHIPS — outer-joined to HZ_PARTIES via party_id; its subject/object type and directional flag determine which relationships qualify.
  • HZ_CONTACT_POINTS — outer-joined on owner (EMAIL contact points only), supplying the primary email format and address.
  • HZ_PERSON_LANGUAGE — outer-joined to give the primary language of the party.
  • FND_LANGUAGES — outer-joined on language_code to resolve the NLS language and territory codes.

Eligible rows are constrained to parties of type PERSON or PARTY_RELATIONSHIP with status A or I, and to relationships where the subject is a PERSON linked to an ORGANIZATION, a directional PERSON-to-PERSON relationship, or where no subject type is defined. Relationships in status M or D are excluded.

Key Columns

  • NAME — Workflow role name in the form HZ_PARTY:<party_id>.
  • DISPLAY_NAME / DESCRIPTION — party name, defaulting to subj_name when present.
  • NOTIFICATION_PREFERENCE — 'MAILTEXT' if an email address exists, otherwise 'QUERY'.
  • EMAIL_ADDRESS, FAX — contact delivery channels; FAX is always NULL here.
  • LANGUAGE, TERRITORY — NLS values from FND_LANGUAGES.
  • ORIG_SYSTEM / ORIG_SYSTEM_ID — 'HZ_PARTY' and the party ID.
  • START_DATE, EXPIRATION_DATE, STATUS — role validity window and active/inactive flag.
  • USER_FLAG, PARTITION_ID — 'Y' and 9 respectively, required by Workflow.

Common Use Cases and Queries

Typical uses include resolving a party's notification email and language for Workflow, and reporting on parties that are valid Workflow roles.

SELECT name, display_name, notification_preference
FROM   apps.hz_party_wf_roles_v
WHERE  status = 'ACTIVE'
AND    email_address IS NOT NULL;
SELECT orig_system_id, display_name, language, territory
FROM   apps.hz_party_wf_roles_v
WHERE  display_name LIKE :subj_name;

Because the search term subj_name appears as an inner-alias column in the view definition, it is commonly filtered via DISPLAY_NAME or DESCRIPTION, which carry that value to the outer query.