Results for “asf_addresses_v”

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

Overview

ASF_ADDRESSES_V is a reporting and integration view belonging to the ASF – Sales Online product family in Oracle E-Business Suite. Its purpose is to present a consolidated, denormalized picture of party addresses by joining party, party site, party site use, and location records into a single address-oriented result set. The view exposes the identifying and descriptive attributes of an address together with the party it belongs to and the site use that governs how that address is employed.

The view is documented in ETRM for both Oracle EBS 12.1.1 and 12.2.2, reflecting the shared data model introduced with the Oracle Trading Community Architecture (TCA) HZ schema. In practice, ASF_ADDRESSES_V is used wherever an application or report requires address data keyed by party and location without having to re-implement the multi-table TCA joins. The view does not store data itself; it is a read-only projection over the HZ tables. Note that the ETRM record indicates "Not implemented in this database," meaning the object is documented as part of the reference data model but is not necessarily deployed in every environment.

Underlying Base Objects

The view is defined over four TCA tables:

• HZ_PARTY_SITES (aliased SITE) — the association between a party and a physical location, carrying the site status, active dates, and identifying address flag.
• HZ_PARTY_SITE_USES (aliased SITE_USE) — the purpose for which a party site is used, such as billing or shipping.
• HZ_LOCATIONS (aliased LOC) — the actual street address components.
• HZ_PARTIES (aliased PARTY) — the party that owns the address, which may be an organization or a person.

The joins are constructed with outer joins on the location and site use relationships, and decoded status filters restrict results to active or inactive records. Specifically, the party status must be 'A' or 'I', and the DECODE logic on SITE.STATUS and SITE_USE.STATUS admits 'A', 'I', and NULL values. An ORDER BY LOC.LOCATION_ID sequences the output by location.

Key Columns

The view exposes identity, address, and status information through the following columns:

• PARTY_ID, PARTY_SITE_ID, PARTY_SITE_USE_ID, LOCATION_ID — the primary keys linking the party, site, site use, and location records.
• ADDRESS1 through ADDRESS4, CITY, STATE, PROVINCE, POSTAL_CODE, COUNTY, COUNTRY — the descriptive address components sourced from HZ_LOCATIONS.
• START_DATE_ACTIVE, END_DATE_ACTIVE — the effective date range of the party site.
• SITE_USE_TYPE — the purpose of the site use (for example, billing or shipping).
• IDENTIFYING_ADDRESS_FLAG, STATUS — flags indicating whether the address is the identifying one for the party and the record's status.
• PARTY_TYPE, PARTY_NAME, PERSON_FIRST_NAME, PERSON_LAST_NAME — party classification and naming attributes.
• LOC_LAST_UPDATE_DATE, SITE_LAST_UPDATE_DATE, SITE_USE_LAST_UPDATE_DATE — audit timestamps supporting incremental extraction.

Common Use Cases and Queries

The most frequent use is address lookup for a given party, often filtered to active, identifying addresses for billing or shipping. A representative query is:

• SELECT PARTY_NAME, ADDRESS1, CITY, STATE, POSTAL_CODE, COUNTRY FROM ASF_ADDRESSES_V WHERE PARTY_ID = :p_party_id AND IDENTIFYING_ADDRESS_FLAG = 'Y';

Integrations may extract address changes since a given date using the audit columns:

• SELECT PARTY_ID, LOCATION_ID, SITE_LAST_UPDATE_DATE FROM ASF_ADDRESSES_V WHERE SITE_LAST_UPDATE_DATE > :p_last_run;

Reports commonly join the view to order or customer data on PARTY_ID or PARTY_SITE_ID to resolve ship-to or bill-to addresses. Because the view consolidates the TCA structures, it reduces development effort and ensures consistent interpretation of party address data across Sales Online and related applications.