Search Results oe_lines_iface_all




Overview
Explore in AI Chat

Overview

The HZ_PARTY_SITE_USES table is a core data object within the Oracle Trading Community Architecture (TCA) model, residing in the AR (Receivables) schema. It defines the specific business purposes for which a party utilizes a given physical location or address, as stored in HZ_PARTY_SITES. A single party site can have multiple associated uses, such as "Bill To," "Ship To," "Market of Origin," or "Statement." This table is fundamental to establishing the functional context of addresses across Oracle E-Business Suite, enabling precise transactional relationships in modules like Order Management, Receivables, Service, and Cash Management.

Key Information Stored

The table's primary key is PARTY_SITE_USE_ID, a unique identifier for each site-use assignment. The critical foreign key is PARTY_SITE_ID, which links to the HZ_PARTY_SITES table to identify the specific address. The SITE_USE_TYPE column is paramount, storing the coded purpose (e.g., 'BILL_TO', 'SHIP_TO', 'MARKET_OF_ORIGIN'). Other significant columns include STATUS, indicating if the site use is 'A'ctive or 'I'nactive, START_DATE_ACTIVE and END_DATE_ACTIVE for dating the validity of the use, and CREATED_BY/CREATION_DATE for auditing. The table also contains a LOCATION_ID column, which can optionally link to a more granular location definition.

Common Use Cases and Queries

A primary use case is validating and retrieving the appropriate transactional address for a customer order or invoice. For instance, when processing an order interface record from OE_LINES_IFACE_ALL, the system references the DELIVER_TO_PARTY_SITE_USE_ID to determine the correct delivery address. Common queries involve joining to HZ_PARTY_SITES and HZ_PARTIES to get a complete address profile. A sample query to find all active 'SHIP_TO' addresses for a customer would be:

  • SELECT hp.party_name, hps.party_site_name, hps.address1
  • FROM hz_parties hp, hz_party_sites hps, hz_party_site_uses hpsu
  • WHERE hp.party_id = hps.party_id
  • AND hps.party_site_id = hpsu.party_site_id
  • AND hpsu.site_use_type = 'SHIP_TO'
  • AND hpsu.status = 'A'
  • AND hp.party_number = 'CUST123';

Reporting on address usage across customers or analyzing the assignment of site use types are also frequent operational and analytical tasks.

Related Objects

HZ_PARTY_SITE_USES sits at the center of a wide relational network. Its primary parent is HZ_PARTY_SITES. As evidenced by the foreign key metadata, it is referenced by numerous transactional and interface tables across the application. Critically for the user's search context, OE_LINES_IFACE_ALL references it four times for different address roles (DELIVER_TO, END_CUSTOMER, INVOICE_TO, SHIP_TO). OE_HEADERS_IFACE_ALL references it for the end customer site use. Other key referencing objects include CS_INCIDENTS_ALL_B for service requests, IBY_CREDITCARD and related tables for payment processing addresses, and AMS_ACT_COMMUNICATIONS for marketing communications. This extensive referencing underscores its role as the definitive source for qualified address usage.