Search Results wsh_carrier_sites

Overview

HZ_PARTY_SITES is the central TCA (Trading Community Architecture) table that links a party record in HZ_PARTIES to a physical address record in HZ_LOCATIONS. It resides in the AR schema and is classified as VALID in Oracle EBS 12.1.1 and 12.2.2. The table acts as the association layer between a person or organization and the place at which that party conducts business, receives goods, or is invoiced. A single party may be associated with many party sites, and a single location may be referenced by multiple party sites, making this one of the most heavily joined tables in the E-Business Suite.

From a Data Vault modeling perspective, the metadata heuristic classifies HZ_PARTY_SITES as a hub. In practice it behaves as a durable association entity: it owns its own surrogate key (PARTY_SITE_ID), carries EDW-style audit and WHO columns, and serves as the parent for numerous descriptive child tables such as HZ_PARTY_SITES_EXT_B and HZ_PARTY_SITE_USES.

Key Information Stored

The table exposes 75 documented columns. The most consequential are summarized below.

• PARTY_SITE_ID — Surrogate primary key, enforced by HZ_PARTY_SITES_PK and by unique index HZ_PARTY_SITES_U1. Every downstream foreign key references this column.
• PARTY_SITE_NUMBER — Business-key candidate, enforced by unique index HZ_PARTY_SITES_U2. This is the user-facing site identifier.
• PARTY_ID — Foreign key to HZ_PARTIES, identifying the owning party.
• LOCATION_ID — Foreign key to HZ_LOCATIONS, pointing to the normalized address.
• STATUS — Controls whether the site is active and usable for transactions.
• IDENTIFYING_ADDRESS_FLAG — Marks the primary identifying address for the party.
• START_DATE_ACTIVE / END_DATE_ACTIVE — Effective-dating range for the site association.
• PARTY_SITE_NAME — Descriptive label for the site (for example, a branch or plant name).
• ADDRESSEE — Name of the recipient at the site, used on documents and correspondence.
• REGION and MAILSTOP — Sub-location details within a larger facility.
• ORIG_SYSTEM_REFERENCE — Legacy or external-system identifier for the site.
• DUNS_NUMBER_C and GLOBAL_LOCATION_NUMBER — Global trade identifiers for the site.
• OBJECT_VERSION_NUMBER — Optimistic locking column used by the TCA APIs.
• ATTRIBUTE1–20 and GLOBAL_ATTRIBUTE1–20 — Extensible descriptive flexfields.
• CREATED_BY_MODULE and APPLICATION_ID — Ownership and multi-org context indicators.

Common Use Cases and Queries

HZ_PARTY_SITES is queried whenever an application must resolve a party to a usable address. Typical reporting scenarios include customer address listings, supplier site directories, ship-to and bill-to assignments, and tax jurisdiction lookups.

A basic join returns the party name alongside its address details:

• SELECT ps.party_site_id, ps.party_site_number, hp.party_name, hl.address1, hl.city, hl.state, hl.postal_code FROM hz_party_sites ps, hz_parties hp, hz_locations hl WHERE ps.party_id = hp.party_id AND ps.location_id = hl.location_id AND ps.status = 'A';

To identify the identifying address for a party, add the predicate IDENTIFYING_ADDRESS_FLAG = 'Y'. To find sites active on a given date, filter on START_DATE_ACTIVE and END_DATE_ACTIVE. To locate a customer account site, join through HZ_CUST_ACCT_SITES_ALL on PARTY_SITE_ID, and then through HZ_CUST_SITE_USES_ALL to determine whether the site is used as a bill-to, ship-to, or statement site.

Related Objects

The FK metadata shows HZ_PARTY_SITES is referenced by well over one hundred tables across modules. The most significant relationships include:

• HZ_PARTIES and HZ_LOCATIONS — The two parent tables referenced by PARTY_ID and LOCATION_ID.
• HZ_CUST_ACCT_SITES_ALL — Links customer accounts to party sites via PARTY_SITE_ID; the primary path from AR customers to addresses.
• HZ_PARTY_SITE_USES — Defines the business purpose (bill-to, ship-to) of each site.
• HZ_CONTACT_POINTS — Phone, email, and other contact data attached through OWNER_TABLE_ID.
• HZ_PARTY_SITES_EXT_B and HZ_PARTY_SITES_EXT_TL — Extension and translatable attribute child tables.
• AP_INVOICE_PAYMENTS_ALL — References INVOICING_PARTY_SITE_ID for supplier payments.
• OE_HEADERS_IFACE_ALL, OE_LINES_IFACE_ALL, ASO_QUOTE_HEADERS_ALL, ASO_SHIPMENTS — Order and quotation ship-to, invoice-to, and sold-to references.
• WSH_CARRIER_SITES — Carrier site definitions via CARRIER_SITE_ID.
• ZX_PARTY_TAX_PROFILE — E-Business Tax profile linkage.

Because of this breadth, HZ_PARTY_SITES should be treated as a foundational reference object in any EBS data model, and joins to it should use the indexed PARTY_SITE_ID column wherever possible.