Results for “hz_wsrvc_rel_types_v”

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

Overview

HZ_WSRVC_REL_TYPES_V is an Oracle E-Business Suite internal view owned by the APPS schema and registered under the Receivables (AR) product family. It exposes relationship type definitions maintained by the Trading Community Architecture (TCA) party model, presenting the rows of HZ_RELATIONSHIP_TYPES in a form that resolves both the forward and backward semantics of each relationship. Although the view is classified as internal, it is a documented ETRM object and is valid in both 12.1.1 and 12.2.2.

The distinguishing characteristic of this view is its self-join construction. Each physical relationship type row is matched against sibling rows of the same relationship type to derive the paired forward and backward role definitions. Because of this, the view is principally intended for components that must render a relationship from both perspectives — for example, a party relationship UI that displays "Employee of" alongside "Employer of". The HIERARCHICAL_FLAG column, which was the term the user searched for, indicates whether a relationship type is organized as a hierarchy, and therefore whether parent-child traversal, multiple-parent validation, and circularity checks apply.

Underlying Base Objects

The view is defined over a single referenced base object, HZ_RELATIONSHIP_TYPES, exposed to the APPS schema as a synonym. Internally the SELECT references that table twice, using aliases A and B, joined on RELATIONSHIP_TYPE. Base object identifier carried in the view definition is 9960.

The join predicate restricts output to rows where either the relationship is genuinely bidirectional — that is, the A and B rows share reciprocal forward/backward relationship codes, opposite subject and object types, and a direction code of 'P' (parent) or 'C' (child) — or the forward and backward relationship codes are identical, meaning the relationship is inherently symmetric. Column A supplies the primary attribute set, while column B contributes only the backward role.

Key Columns

• RELATIONSHIP_TYPE_ID / RELATIONSHIP_TYPE — Primary key and internal name of the relationship type.
• FORWARD_REL_CODE / BACKWARD_REL_CODE — The directional codes used when traversing the relationship in each direction.
• FORWARD_ROLE / BACKWARD_ROLE — Human-readable role labels sourced from the A and B aliases respectively.
• DIRECTION_CODE — Governs whether the relationship is directional; values include 'P' and 'C'.
• HIERARCHICAL_FLAG — Indicates that the relationship type participates in a hierarchy, enabling parent-child structures.
• MULTIPLE_PARENT_ALLOWED / ALLOW_CIRCULAR_RELATIONSHIPS — Constraints governing hierarchy integrity.
• CREATE_PARTY_FLAG / ALLOW_RELATE_TO_SELF_FLAG — Control whether a party is auto-created and whether self-linking is permitted.
• SUBJECT_TYPE / OBJECT_TYPE — The party types on either side of the relationship.
• STATUS — Active/inactive state of the relationship type.
• OBJECT_VERSION_NUMBER and the standard WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) support concurrency and audit.
• INCL_UNRELATED_ENTITIES and APPLICATION_ID / CREATED_BY_MODULE identify ownership and scope.

Common Use Cases and Queries

Typical consumers include Customer Relationship Management and Resource Manager modules that need to enumerate valid relationship types together with their reciprocal role labels. The following query lists hierarchical relationship types with both roles:

• SELECT relationship_type, forward_role, backward_role, hierarchical_flag FROM hz_wsrvc_rel_types_v WHERE hierarchical_flag = 'Y';
• SELECT relationship_type, subject_type, object_type, multiple_parent_allowed FROM hz_wsrvc_rel_types_v WHERE direction_code = 'P';
• SELECT relationship_type, allow_circular_relationships FROM hz_wsrvc_rel_types_v WHERE hierarchical_flag = 'Y' AND allow_circular_relationships = 'N';

Because the view is joined and internal, it is recommended primarily for read-only reporting and LOV population rather than transactional writes. Consumers should reference it as APPS.HZ_WSRVC_REL_TYPES_V and expect the forward/backward pairing to reflect the reciprocal rows present in HZ_RELATIONSHIP_TYPES.