Search Results ship_to_site




Overview
Explore in AI Chat

Overview

APPS.OE_CUSTOMER_SITE_CONTACTS_V is a reporting view in the Oracle E-Business Suite Order Management and Receivables schema that consolidates customer party information, customer account details, site-level address data, and contact (role) information into a single denormalized result set. It is defined as a join across the HZ (Trading Community Architecture) customer model and exposes account, site use, and role context for a customer site.

The view is particularly relevant when working with the various site use codes — BILL_TO, SHIP_TO, and SOLD_TO — which determine how a customer site is classified for order entry, invoicing, and shipping purposes. Within the view, dedicated derived columns such as BILL_TO_SITE, SHIP_TO_SITE, and SOLD_TO_SITE return "Yes" or "No" flags indicating whether the associated customer account site carries each respective use code with an active status. Because the ROLE_TYPE column also decodes the role responsibility into SHIP_TO or BILL_TO where applicable, the view serves as a convenient reporting surface for consumers needing to identify billing-related sites and contacts without writing multi-table joins against the HZ tables directly.

Its purpose is primarily diagnostic and reporting-oriented: it flattens address, party, account role, and site use information, letting developers and functional analysts query a single object for customer site and contact lookups instead of assembling the HZ_CUST_ACCOUNTS, HZ_CUST_ACCT_SITES, HZ_CUST_SITE_USES_ALL, HZ_LOCATIONS, and HZ_PARTIES joins manually.

Underlying Base Objects

The documented base objects referenced by this view are: AR_LOOKUPS (VIEW), HZ_CUST_ACCOUNTS (SYNONYM), HZ_CUST_ACCOUNT_ROLES (SYNONYM), HZ_CUST_ACCT_SITES (SYNONYM), HZ_CUST_SITE_USES_ALL (SYNONYM), HZ_LOCATIONS (SYNONYM), HZ_PARTIES (SYNONYM), HZ_PARTY_SITES (SYNONYM), HZ_RELATIONSHIPS (SYNONYM), and HZ_ROLE_RESPONSIBILITY (SYNONYM).

  • HZ_CUST_ACCOUNTS supplies the customer account identifiers and account numbers (CUST_ACCOUNT_ID, account_number) and account-level status.
  • HZ_CUST_ACCT_SITES provides the account site record (CUST_ACCT_SITE_ID) and its status.
  • HZ_CUST_SITE_USES_ALL holds the SITE_USE_CODE and status used for the BILL_TO, SHIP_TO, and SOLD_TO derived flags and subqueries.
  • HZ_LOCATIONS and HZ_PARTY_SITES provide the address components (ADDRESS1 through ADDRESS4, CITY, STATE, POSTAL_CODE, COUNTRY).
  • HZ_PARTIES supplies the party name and email for both the customer and the contact party.
  • HZ_CUST_ACCOUNT_ROLES and HZ_RELATIONSHIPS link the contact parties to the account.
  • HZ_ROLE_RESPONSIBILITY provides RESPONSIBILITY_TYPE, which drives the ROLE_TYPE and ROLE_TYPE_CODE columns.
  • AR_LOOKUPS is referenced to resolve lookup meanings used in the contact name concatenation.

Key Columns

Common Use Cases and Queries

A frequent requirement is locating all bill-to sites for a customer. The BILL_TO_SITE derived column makes this straightforward:

  • SELECT customer_number, customer_name, address_line_1, role_type FROM oe_customer_site_contacts_v WHERE bill_to_site = 'Yes';
  • SELECT customer_number, contact_name, contact_email FROM oe_customer_site_contacts_v WHERE role_type = 'BILL_TO';
  • SELECT customer_name, ship_to_site, bill_to_site FROM oe_customer_site_contacts_v WHERE site_status = 'A';

These queries support auditing site use configuration, building billing contact lists for invoice distribution, resolving party/address details during integrations, and diagnosing discrepancies where a customer appears to lack an active bill-to site. Because the view already pre-resolves the BILL_TO, SHIP_TO, and SOLD_TO logic, it is preferable to direct HZ table joins when the objective is simply to report on site use classification and associated contacts.