Results for “relation_party_id”

18 results




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

Overview

The APPS.WSH_CARRIER_SITECONTACT_INFO_V view is a Shipping Execution (WSH) reporting object that exposes telephone contact point information for carrier-related parties stored in the Oracle Trading Community Architecture (TCA) model. In Oracle EBS 12.1.1 and 12.2.2, WSH relies on TCA to hold carrier and site-level contact data, and this view provides a denormalized, shipping-oriented projection of that data. Rather than requiring report authors, integrations, or PL/SQL routines to join the TCA contact point and party tables directly, the view presents a pre-joined result set keyed on party identifier and contact point identifier.

Its principal role is to support lookups of carrier contact telephone details — country code, area code, extension, and phone number — together with status and primary flags that indicate which number should be used for a given carrier party or site. This makes it suitable for shipping documentation, carrier notification extracts, dispatch reports, and any integration that needs to retrieve a carrier's phone contact without navigating the full TCA schema.

Underlying Base Objects

The view is defined in the APPS schema over two documented TCA base objects, accessed through synonyms:

  • HZ_CONTACT_POINTS (alias HCP) — the TCA table storing individual contact points, including phone, email, and other contact mechanisms. The view restricts this table to rows where CONTACT_POINT_TYPE = 'PHONE' and OWNER_TABLE_NAME = 'HZ_PARTIES'.
  • HZ_PARTIES (alias HP) — the TCA table storing party records such as carriers, organizations, and persons. The join is established through HCP.OWNER_TABLE_ID = HP.PARTY_ID.

Consequently, the view only surfaces contact points owned directly by a party record and of the PHONE type; contact points owned by other entity types (for example, locations or organizations) are excluded by the filter predicates.

Key Columns

The view exposes the following columns, which map to the underlying TCA attributes:

  • RELATION_PARTY_ID — the party identifier from HZ_PARTIES; identifies the carrier or related party.
  • CONTACT_POINT_ID — the unique identifier of the phone contact point in HZ_CONTACT_POINTS.
  • COUNTRY_CODE — the telephone country code (from PHONE_COUNTRY_CODE).
  • AREA_CODE — the telephone area or city code (from PHONE_AREA_CODE).
  • EXTENSION — the telephone extension (from PHONE_EXTENSION).
  • PHONE_NUMBER — the primary telephone number digits.
  • CONTACT_POINT_TYPE — the contact point type; effectively 'PHONE' due to the view filter.
  • PRIMARY — indicates whether the contact point is the primary number for the party.
  • ACTIVE — the status of the contact point, used to exclude inactive records.

Common Use Cases and Queries

Typical usage includes retrieving a carrier's primary phone contact for shipping notifications, generating carrier contact listings for warehouse or dispatch staff, and extracting contact data for outbound integrations. A common pattern is to filter on the primary and active flags to obtain the single best number per party:

  • Carrier phone lookup for a known party identifier.
  • Listing all active phone contacts for a carrier.
  • Joining the view to WSH carrier tables by party identifier to enrich shipment or carrier records.

Illustrative SQL:

SELECT relation_party_id, contact_point_id, country_code, area_code, phone_number, extension, primary, active
FROM apps.wsh_carrier_sitecontact_info_v
WHERE relation_party_id = :p_party_id
  AND active = 'Y';

SELECT relation_party_id, country_code, area_code, phone_number
FROM apps.wsh_carrier_sitecontact_info_v
WHERE primary = 'Y'
  AND active = 'Y';

Because the view applies no site-level restriction in its documented text, users should treat it as a carrier party phone contact view and apply any additional site or organization filtering through joins to the relevant WSH or TCA entities as required by the business scenario.