Search Results sub_party_number




Overview
Explore in AI Chat

Overview

CSD_HZ_REL_V is an APPS-owned database view in Oracle E-Business Suite Release 12.1.1 and 12.2.2, delivered as part of the CSD (Depot Repair) product family. Its documented purpose is to present the details of Related, Subject, and Object parties — the three-party relationship construct used by the Oracle Trading Community Architecture (TCA) — for consumption within the Depot Repair Workbench. The view flattens the relational model of HZ_RELATIONSHIPS and the party attributes held in HZ_PARTIES into a single, wide result set, so that depot repair forms, LOVs, and workbench regions can retrieve relationship and address information without issuing multiple joins of their own.

The view is reported as VALID in the ETRM metadata repository. Because it is a view rather than a table, it stores no data; it is a read-only projection over the TCA entities. Column names carry a REL_ prefix for the related party and a SUB_ prefix for the subject party, allowing a consumer to distinguish the two sides of a relationship in one row. The user search term "rel_address" maps directly to the REL_ADDRESS column, which is a concatenated, single-line rendering of the related party's address elements.

Underlying Base Objects

The ETRM 12.2.2 metadata documents three referenced base objects: HZ_PARTIES (SYNONYM), HZ_RELATIONSHIPS (SYNONYM), and AR_LOOKUPS (VIEW). HZ_PARTIES is the master TCA party entity holding PARTY_ID, PARTY_NUMBER, PARTY_NAME, PARTY_TYPE, person name components, status, and language. HZ_RELATIONSHIPS supplies the association between the subject party, the object party, and the related party, together with the relationship code and direction. AR_LOOKUPS provides the seeded lookup values used to decode relationship types and other reference codes surfaced by the workbench. The view is therefore a join-driven projection, not a materialized or denormalized store.

The published view text confirms this construction: party attributes are drawn from the party source and aliased with REL_ and SUB_ prefixes. Address columns are taken directly (ADDRESS1 through ADDRESS4, CITY, STATE, PROVINCE, POSTAL_CODE, COUNTY, COUNTRY), and REL_ADDRESS is generated by concatenating ADDRESS1 with semicolon-delimited DECODE branches for ADDRESS2, ADDRESS3, and ADDRESS4, suppressing NULL elements.

Key Columns

Common Use Cases and Queries

The view supports depot repair workbench display of customer and contact relationships, validation of the subject party on a repair order, and reporting on related-party address data. A typical query retrieves the related party and its formatted address for a given subject party.

SELECT rel_party_id, rel_party_name, rel_party_type, rel_address
FROM apps.csd_hz_rel_v
WHERE sub_party_id = :p_sub_party_id;

To search by address fragment, the concatenated REL_ADDRESS column can be filtered directly: WHERE UPPER(rel_address) LIKE '%'||UPPER(:p_address)||'%'. Join the view to the depot repair order tables on REL_PARTY_ID to enrich workbench enquiries. Because the view is read-only and defined over TCA synonyms, it should be queried through the APPS schema or a synonym, and never updated directly.