Results for “identifying_address_flag”

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

Overview

The ASO_I_PARTY_ADDRESSES_V view is a public Oracle E-Business Suite database object owned by the APPS schema and registered under the ASO (Order Capture) product family. It exposes party address information — the physical locations associated with trading partners, customers, and other parties defined in Oracle's Trading Community Architecture (TCA) — in a denormalized, reporting-friendly form. In the documented ETRM metadata for Release 12.2.2, the object is marked VALID, meaning the view compiles cleanly against its base objects and is safe to consume in downstream logic.

Because it is a view rather than a table, no data is stored in it. The definition simply joins address, party site, territory, and site-use data so that consumers do not have to reconstruct the TCA relationships themselves. Its role is therefore that of a read-only reporting and integration surface: concurrent programs, Oracle Reports, Oracle Forms LOVs, and custom PL/SQL or BI Publisher queries reference it to retrieve formatted address and country information without depending directly on the underlying HZ tables.

Underlying Base Objects

The view is defined over four documented referenced objects:

• HZ_PARTY_SITES (SYNONYM) — the central TCA entity linking a party to a location and providing site-level attributes such as active dates and the identifying address flag.
• HZ_LOCATIONS (SYNONYM) — the address master, supplying address lines, city, postal code, state, province, county, and country code.
• HZ_PARTY_SITE_USES (SYNONYM) — the site-use assignments that classify how a party site may be used (for example, bill-to or ship-to).
• FND_TERRITORIES_VL (VIEW) — the multilingual territories view, which resolves the country code into a displayable territory short name.

The join predicates are documented: PARTY_SITE.LOCATION_ID = LOC.LOCATION_ID, LOC.COUNTRY = TERR.TERRITORY_CODE, and PARTY_SITE.PARTY_SITE_ID = USES.PARTY_SITE_ID. The final column in the SELECT list is a literal NULL, which is surfaced as the PRIMARY_PER_TYPE column in the documented column list.

Key Columns

The documentation lists the view's columns explicitly. The identifiers and flags are the primary linkage points:

• PARTY_ID, PARTY_SITE_ID, LOCATION_ID — the TCA keys relating the row back to the party, its site, and the location record.
• IDENTIFYING_ADDRESS_FLAG — indicates whether the party site is the party's identifying address.
• START_DATE_ACTIVE / END_DATE_ACTIVE — effective dating for the party site.
• ADDRESS1 through ADDRESS4, CITY, POSTAL_CODE, STATE, PROVINCE, COUNTY — formatted address components.
• COUNTRY_CODE — the country code from HZ_LOCATIONS; COUNTRY — the territory short name from FND_TERRITORIES_VL.
• SITE_USE_TYPE — the use classification from HZ_PARTY_SITE_USES.
• PRIMARY_PER_TYPE — exposed in the column list but populated as NULL in the view definition.

Common Use Cases and Queries

Typical scenarios include populating address LOVs in Order Capture flows, feeding address blocks into order and quote documents, and generating reports that require the sale-to or ship-to address for a given party.

To retrieve all addresses for a known party:

SELECT party_id, party_site_id, address1, city, state, postal_code, country
FROM   aso_i_party_addresses_v
WHERE  party_id = :p_party_id;

To list identifying addresses only:

SELECT party_id, party_site_id, address1, city, country
FROM   aso_i_party_addresses_v
WHERE  identifying_address_flag = 'Y'
AND    site_use_type = 'BILL_TO';

Because PRIMARY_PER_TYPE is returned as NULL, any logic requiring the primary address per use type must derive it externally rather than relying on this column.