Search Results bill_location




Overview
Explore in AI Chat

Overview

APPS.AR_SHIP_ADDRESS_V is a shipping and billing address resolution view in the Oracle E-Business Suite Receivables (AR) schema. It exists to present, in a single flat result set, the address of a customer's ship-to site use together with the corresponding bill-to site use, derived from the Trading Community Architecture (TCA) model. The view is a standard reporting and integration object used by Receivables forms, reports, and interface programs where a human-readable, pre-formatted mailing address is required.

The view is significant because it flattens the multi-level TCA hierarchy — party, party site, customer account, account site, and site use — into a denormalized structure, and because it applies formatting logic through FND_GLOBAL.LOCAL_CHR to insert the locale-appropriate comma and space separators into concatenated address lines. It also joins to FND_TERRITORIES_VL to substitute the territory short name for the country, producing addresses suitable for display and printing. In the context of a search for site_use_id, this view is relevant because HZ_CUST_SITE_USES is one of its core base objects, and site use identifiers are what distinguish a ship-to address from a bill-to address for the same account site.

Underlying Base Objects

The documented base objects for this view are:

  • FND_GLOBAL (PACKAGE) — supplies LOCAL_CHR, used to build locale-aware delimiters.
  • FND_TERRITORIES_VL (VIEW) — provides TERRITORY_SHORT_NAME for the formatted address text.
  • HZ_CUST_ACCT_RELATE (SYNONYM) — customer account relationship data used to resolve billing relationships.
  • HZ_CUST_ACCT_SITES (SYNONYM) — the customer account site, aliased A, providing account-site status.
  • HZ_CUST_SITE_USES (SYNONYM) — the site uses, aliased SU for the ship-to use and SU_BILL / SU_BILL2 for bill-to uses; this is the object that carries SITE_USE_ID.
  • HZ_LOCATIONS (SYNONYM) — the address itself, aliased A_LOC for the ship-to location and A_BILL_LOC for the bill-to location.
  • HZ_PARTY_SITES (SYNONYM) — links the party to the location.
  • DUAL (SYNONYM) — used for constant/derived expressions.

The view therefore sits on top of the HZ_* TCA tables, not on the legacy AR address tables, and its joins are driven by site use records within an account site.

Key Columns

  • SITE_USE_ID — through the underlying HZ_CUST_SITE_USES rows; the ship-to use supplies the primary address, and SU_BILL2.SITE_USE_ID controls whether a bill-to address is returned.
  • ADDRESS1, ADDRESS2 — first two address lines from HZ_LOCATIONS.
  • ADDRESS3 — formatted address: ADDRESS3 and ADDRESS4 concatenated with city, state/province, postal code, and territory short name, using LOCAL_CHR separators.
  • ADDRESS3_DB — the raw, unformatted ADDRESS3 value.
  • ADDRESS — fully concatenated address built from 25-character substrings of each line.
  • LOCATION, PRIMARY_FLAG, TERRITORY_ID, SU_STATUS — carried from the site use record.
  • CITY, COUNTY, STATE, PROVINCE, COUNTRY, POSTAL_CODE — individual address attributes.
  • A_STATUS — status of the customer account site.
  • BILL_LOCATION, BILL_ADDRESS1, BILL_ADDRESS2, and the bill-to ADDRESS3 expression — bill-to counterparts, resolved via SU_BILL/SU_BILL2 and DECODE logic so that null bill-to site uses yield null bill-to values.

Common Use Cases and Queries

Typical uses include printing ship-to and bill-to addresses on Receivables documents, resolving the mailing address for a given site use, and reconciling ship-to versus bill-to assignments on an account. A representative query filtering by site use is:

  • SELECT site_use_id, address1, address2, address3, city, state, postal_code, bill_address1 FROM apps.ar_ship_address_v WHERE site_use_id = :p_site_use_id;
  • SELECT location, primary_flag, su_status, a_status FROM apps.ar_ship_address_v WHERE city = 'SAN FRANCISCO' AND status = 'A';

Because the view exposes both ship-to and bill-to data in the same row, it is frequently joined back to HZ_CUST_SITE_USES or HZ_CUST_ACCT_SITES on SITE_USE_ID to obtain the surrounding account context for reporting.