Results for “user_orig_system”

4 results




Overview
Explore in AI Chat

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

Overview

HZ_PARTY_WF_USER_ROLES_V is an APPS-owned database view in Oracle E-Business Suite, shipped under the Receivables (AR) product family and validated in releases 12.1.1 and 12.2.2. The view presents workflow user and role assignment data drawn from the partitioned synonym WF_LOCAL_ROLES, restricted to the HZ_PARTY partition. Its purpose is to expose party-related workflow role membership — the association between a workflow user, the originating system that owns that user, and the role the user is assigned — in a form suitable for reporting, integration, and diagnostic queries.

Users typically search for this object by the column role_orig_system, which identifies the source system owning a given role assignment. This reflects the view's primary utility: resolving where a role originated (Oracle Trading Community Architecture, CRM, or another registered origin system) and correlating that assignment with the corresponding party record in the TCA model.

Underlying Base Objects

The single documented base object is WF_LOCAL_ROLES, referenced through a synonym in the APPS schema. The view definition selects from WF_LOCAL_ROLES PARTITION (HZ_PARTY), meaning it reads only the partition that stores party-derived workflow roles rather than the entire local roles table.

WF_LOCAL_ROLES is the Workflow directory table that stores users, roles, and groups along with their origin system and origin identifiers. Because the view reads a named partition, its results are inherently scoped to party records synchronized from the TCA layer. No joins, filters, or aggregations appear in the definition; the view is a straight projection with two columns derived as constants (SECURITY_GROUP_ID set to NULL and PARTITION_ID set to 9).

Key Columns

  • USER_NAME — the name of the workflow user; sourced from the NAME column of WF_LOCAL_ROLES.
  • USER_ORIG_SYSTEM — the origin system that owns the user, exposed from ORIG_SYSTEM.
  • USER_ORIG_SYSTEM_ID — the primary key of the user within that origin system.
  • ROLE_NAME — the name of the assigned role, also mapped from NAME.
  • ROLE_ORIG_SYSTEM — the origin system owning the role; this is the column users search for as role_orig_system.
  • ROLE_ORIG_SYSTEM_ID — the role's identifier within its origin system.
  • START_DATE / EXPIRATION_DATE — the effective period of the role assignment, useful for time-bounded analysis.
  • SECURITY_GROUP_ID — always NULL in this view, as defined literally in the view text.
  • PARTITION_ID — a constant value of 9, identifying the HZ_PARTY partition.

Common Use Cases and Queries

Typical scenarios include auditing which roles a party-linked user holds, identifying assignments by origin system, and detecting assignments that have expired or not yet started. The view is also convenient for integration extracts where a flat user-to-role mapping with origin metadata is required.

Sample query listing active party role assignments for a specific origin system:

  • SELECT user_name, user_orig_system, role_name, role_orig_system, role_orig_system_id FROM hz_party_wf_user_roles_v WHERE role_orig_system = 'TCA' AND (expiration_date IS NULL OR expiration_date > SYSDATE) ORDER BY user_name, role_name;
  • SELECT role_orig_system, COUNT(*) FROM hz_party_wf_user_roles_v GROUP BY role_orig_system;
  • SELECT user_name, role_name FROM hz_party_wf_user_roles_v WHERE start_date BETWEEN :p_from AND :p_to;

Because SECURITY_GROUP_ID is returned as NULL and PARTITION_ID is fixed at 9, these columns carry no filtering value; consumers should rely on the origin system, origin identifiers, and date columns for meaningful restriction.