Search Results relation_party_id




Overview
Explore in AI Chat

Overview

APPS.WSH_CARRIER_CONTACTS_V is a read-only database view in the Oracle E-Business Suite Applications schema that exposes the association between shipping carriers and their designated contact persons. It is owned by the APPS schema and registered under the Oracle Applications design data as WSH.WSH_CARRIER_CONTACTS_V. Within the Shipping Execution (WSH) module, carriers represent the freight and logistics providers responsible for transporting goods. Each carrier organization retains a list of contacts — individuals to whom shipping notifications, tracking inquiries, and documentation can be addressed. This view flattens the underlying party model into a single denormalized result set that joins the carrier's relationship record to the person identity details, providing direct access to the contact person's name components and activity status.

The view is classified as Oracle Internal Use Only and is not supported for direct customer access except from standard Oracle Applications programs. Nevertheless, technical consultants routinely reference it for reporting and integration where a supported public API or concurrent program is unavailable. Because the view carries no mandatory columns and no filtering predicates (other than those implied by the joins), it returns every carrier-contact relationship recorded in the underlying tables, making it suitable as a base for custom extracts.

Underlying Base Objects

The view is defined over three synonym references resolved to base tables in the Trading Community Architecture (TCA) model:

  • HZ_ORG_CONTACTS — stores the relationship between an organization party (the carrier) and a person party (the contact), including contact-specific attributes such as job title and contact type.
  • HZ_PARTIES — the master TCA entity table holding party identity attributes for both organizations and persons; supplies the person name elements exposed by the view.
  • HZ_RELATIONSHIPS — holds the directional relationship records between parties; this is the source of RELATION_PARTY_ID and the association that ties a contact person to the carrier party.

No database object in the EBS schema references this view, confirming its position as a terminal reporting object. It does not itself act as a dependency for other shipped views or programs.

Key Columns

  • RELATION_PARTY_ID (NUMBER, 15) — the party identifier representing the relationship context; when users search this term, this column is the primary navigation key linking a carrier relationship to the exposed contact records.
  • CARRIER_ID (NUMBER, 15) — identifier of the carrier organization party. This is the join key back to carrier/freight tables and is the value most commonly used in WHERE clauses.
  • CONTACT_PERSON_ID (NUMBER, 15) — the unique party identifier of the contact person, suitable for joining to HZ_PARTIES or person-related tables.
  • PERSON_PRE_NAME_ADJUNCT (VARCHAR2, 30) — honorific or prefix such as Mr., Ms., or Dr.
  • PERSON_FIRST_NAME (VARCHAR2, 150) and PERSON_LAST_NAME (VARCHAR2, 150) — the given and family names of the contact.
  • ACTIVE (VARCHAR2) — status flag indicating whether the contact association is currently active.

Common Use Cases and Queries

Typical applications include carrier notification reports, address-book extraction for transportation integration, and validation of contact coverage per carrier. Because RELATION_PARTY_ID and CARRIER_ID are the operative keys, queries frequently filter on one of these values.

To retrieve all contacts for a specific carrier:

SELECT relation_party_id, carrier_id, contact_person_id,
       person_first_name, person_last_name, active
FROM   apps.wsh_carrier_contacts_v
WHERE  carrier_id = :p_carrier_id
AND    active = 'Y';

To locate a contact by name or party identifier:

SELECT carrier_id, contact_person_id,
       person_pre_name_adjunct, person_first_name, person_last_name
FROM   apps.wsh_carrier_contacts_v
WHERE  relation_party_id = :p_relation_party_id;

In integration scenarios, the CONTACT_PERSON_ID value returned here is passed to shipping or communication workflows that require a validated person party reference for the carrier. Consultants should treat the view as read-only and remember that Oracle does not support direct application access, so any production use should be justified and validated against Oracle's support policy.