Results for “aso_i_acct_site_addr_v”

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

Overview

ASO_I_ACCT_SITE_ADDR_V is an Oracle E-Business Suite 12.1.1 and 12.2.2 seeded database view owned by the APPS schema and registered under the ASO (Order Capture) product family. Its documented purpose is to expose the address information of customers as it is required by Oracle Order Capture and its integration interface logic. The view is classified as VALID in the ETRM repository and is part of the public APPS data model that customers, integrators, and reporting tools are expected to reference rather than querying the underlying customer master tables directly.

The view presents a single flat row per customer site-use, combining the customer account identifier, the physical address identifier, the site-use identifier and code, the free-form address lines, the geographic attributes, and the resolved country. This makes it useful for order entry, shipping and billing validation, address-driven reporting, and any extract or interface that must carry a normalized customer address alongside its site-use context. Because it is a view and not a table, it carries no data of its own and always reflects the current state of the base objects at query time.

Underlying Base Objects

The documented view text defines ASO_I_ACCT_SITE_ADDR_V over three principal sources: RA_ADDRESSES_MORG (aliased ADDR), RA_SITE_USES_MORG (aliased SITE), and FND_TERRITORIES_VL (aliased COUNTRY). The join is driven by ADDR.ADDRESS_ID = SITE.ADDRESS_ID, with the country name resolved through ADDR.COUNTRY = COUNTRY.TERRITORY_CODE. In the 12.2.2 documented metadata, the referenced base objects are recorded as FND_TERRITORIES_VL (VIEW) together with the HZ synonyms HZ_CUST_ACCT_SITES_ALL, HZ_CUST_SITE_USES_ALL, HZ_LOCATIONS, HZ_LOC_ASSIGNMENTS, and HZ_PARTY_SITES, reflecting the TCA (Trading Community Architecture) model that the RA_%_MORG objects resolve to.

In practical terms, the customer account site and site-use information originates from HZ_CUST_ACCT_SITES_ALL and HZ_CUST_SITE_USES_ALL, the physical address attributes come from HZ_LOCATIONS, and the assignment of a location to a party site is held in HZ_LOC_ASSIGNMENTS with HZ_PARTY_SITES. FND_TERRITORIES_VL supplies the territory short name and translated country description.

Key Columns

• CUST_ACCT_ID / CUSTOMER_ID — the customer account identifier (SITE.CUST_ACCT_ID as selected in the view text), linking the row to the customer account.
• ADDRESS_ID — the location identifier, the key that ties the address to the site-use.
• SITE_USE_ID — the unique site-use identifier; the primary transactional handle for a specific use of an address.
• SITE_USE_CODE — the purpose of the site use, for example BILL_TO, SHIP_TO, or other seeded codes defined in HZ_CUST_SITE_USES_ALL.
• ADDRESS1 through ADDRESS4 — the free-form address lines.
• CITY, STATE, POSTAL_CODE, PROVINCE, COUNTY — the remaining geographic attributes of the location.
• COUNTRY / COUNTRY_CODE — the country attribute returned by the view; the view text selects ADDR.COUNTRY and TERRITORY_SHORT_NAME, and the column list documents COUNTRY and COUNTRY_CODE as the exposed country values.

Common Use Cases and Queries

Typical usage includes populating shipping and billing information during order capture, validating that a customer has an active SHIP_TO or BILL_TO site, and producing address extracts for downstream systems. The view is also commonly joined to order lines by CUST_ACCT_ID and SITE_USE_ID.

A representative query retrieving all ship-to addresses for a customer account:

• SELECT cust_acct_id, site_use_id, site_use_code, address1, city, state, postal_code, country_code FROM aso_i_acct_site_addr_v WHERE cust_acct_id = :p_cust_acct_id AND site_use_code = 'SHIP_TO';

Because the view depends on the TCA and territory objects, query performance is best when filters are applied on CUST_ACCT_ID or SITE_USE_ID, and the view should always be accessed through the APPS schema with the standard EBS responsibility and MOAC (Multi-Org Access Control) context in place, since the underlying _MORG objects are organization-sensitive.