Search Results user_orig_system




Overview
Explore in AI Chat

Overview

WF_HZ_PARTY_UR is an APPS-owned database view in Oracle E-Business Suite, registered under the FND — Application Object Library product. Its name follows the Oracle Workflow naming convention for "user role" views derived from the WF_LOCAL_ROLES family. The suffix "HZ_PARTY" identifies the underlying partition of WF_LOCAL_ROLES from which the view draws its rows, and the "UR" suffix denotes the user-role projection that Workflow and Oracle Trading Community Architecture (TCA) components consume.

Functionally, WF_HZ_PARTY_UR presents a normalized view of party records that are usable as Workflow roles or as notification recipients. For each qualifying party, it surfaces the party name, its originating system, and the originating system identifier, mapped simultaneously into a "user" alias set and a "role" alias set. This dual projection allows callers to treat the same underlying row both as an individual user and as a role, which is the standard pattern employed by the Workflow directory services and by TCA's party/role integration layer. The view is defined in both EBS 12.1.1 and 12.2.2 and is reported with a status of VALID in the ETRM repository.

Underlying Base Objects

The documented base object for WF_HZ_PARTY_UR is WF_LOCAL_ROLES, referenced through a synonym, with an explicit partition reference of HZ_PARTY. WF_LOCAL_ROLES is the Workflow runtime cache of directory roles and users; it stores resolved role names, originating system values, and start/expiration metadata used by the Workflow notification and directory services. The HZ_PARTY partition isolates rows whose source is the TCA party model, so the view exposes only the TCA-sourced subset of the role cache.

The view delegates entirely to that base object rather than performing joins of its own. It does not aggregate, filter beyond the partition, or transform the underlying identifiers; its SELECT list is a direct projection with column aliasing. Consequently, its freshness, cardinality, and row-level security characteristics are inherited from WF_LOCAL_ROLES and its HZ_PARTY partition.

Key Columns

  • USER_NAME — the party name, aliased for user-oriented consumption.
  • USER_ORIG_SYSTEM — the originating system of the party, aliased for user-oriented consumption.
  • USER_ORIG_SYSTEM_ID — the originating system identifier of the party, aliased for user-oriented consumption. This is the column most frequently referenced by the search term "user_orig_system_id" and is the primary lookup key for resolving a party back to its source application record.
  • ROLE_NAME, ROLE_ORIG_SYSTEM, ROLE_ORIG_SYSTEM_ID — the same three values projected under role-oriented aliases, supporting role-based address resolution.
  • START_DATE and EXPIRATION_DATE — projected as TO_DATE(NULL), indicating that this branch of the view supplies no effective-dating information.
  • SECURITY_GROUP_ID — projected as NULL, reflecting that the HZ_PARTY partition does not populate this attribute.
  • PARTITION_ID — a literal constant of 9, used internally to tag the row as belonging to the HZ_PARTY partition.

Common Use Cases and Queries

The view is principally used when resolving a TCA party to a Workflow role, or when reconciling Workflow directory entries against TCA origin data. Typical queries select the user-oriented aliases and filter on the originating system:

  • Listing all TCA-sourced Workflow roles and their origin identifiers: SELECT user_name, user_orig_system, user_orig_system_id FROM apps.wf_hz_party_ur;
  • Resolving a specific party by its originating system identifier: SELECT user_name, role_name FROM apps.wf_hz_party_ur WHERE user_orig_system = :orig_system AND user_orig_system_id = :orig_system_id;
  • Auditing the correspondence between the user and role projections: SELECT user_name, role_orig_system, role_orig_system_id FROM apps.wf_hz_party_ur WHERE user_name LIKE :pattern;

Because START_DATE, EXPIRATION_DATE, and SECURITY_GROUP_ID are not populated by this projection, consumers requiring effective dating or security group scoping must query WF_LOCAL_ROLES directly or the corresponding TCA party tables. All access should be performed through the APPS schema or a synonym, consistent with standard EBS customization practice.