Search Results bic_site_address_v

Overview

BIC_SITE_ADDRESS_V is a reporting view historically associated with the Oracle E-Business Suite BIC — Customer Intelligence product, a module now classified as obsolete in the ETRM documentation. The view exposes a simplified, read-only projection that links a customer site use to a formatted contact address. Its purpose was to provide downstream Customer Intelligence reporting and integration processes with a stable, denormalized access point for customer site addresses without requiring those consumers to join the full Trading Community Architecture (TCA) hierarchy themselves.

The view is defined with a WITH READ ONLY clause, meaning it cannot be used as the target of DML statements. It carries no documented owner in the 12.2.2 metadata and is not implemented in the reference database, which is consistent with the deprecation of the Customer Intelligence module. In both Oracle EBS 12.1.1 and 12.2.2 the same status applies: the object may survive as a legacy artifact in upgraded instances even though no current functionality depends on it.

Underlying Base Objects

The ETRM metadata documents no referenced base objects at the object level, but the view text itself reveals the join path across four TCA entities:

• HZ_CUST_SITE_USES_ALL — customer site uses, supplying the SITE_USE_ID identifier.
• HZ_CUST_ACCT_SITES_ALL — customer account sites, joined on CUST_ACCT_SITE_ID.
• HZ_PARTY_SITES_ALL — party sites, joined on PARTY_SITE_ID.
• BIC_ADDRESS_V — a further Customer Intelligence address view, joined on LOCATION_ID and supplying the formatted CONTACT_ADDRESS.

The join sequence therefore resolves from a site use through its account site and party site to the underlying location, from which the BIC address view returns the formatted address string. The final join to BIC_ADDRESS_V is the element most likely to fail on a system where the Customer Intelligence schema objects have been removed, since that dependency sits outside the standard TCA table set.

Key Columns

• SITE_USE_ID — the primary site use identifier inherited from HZ_CUST_SITE_USES_ALL. This is the natural key for consumer queries and can be used to correlate the view back to the customer site use record.
• CONTACT_ADDRESS — the formatted address string returned by BIC_ADDRESS_V for the location associated with the site use. This is the sole descriptive payload of the view and is intended for display or reporting rather than for structural processing.

The two-column projection reflects the view's narrow reporting intent: it answers only "what is the address for this site use?" It does not expose address usage flags, primary indicators, or the individual address component attributes available in the underlying HZ tables.

Common Use Cases and Queries

The view was intended for Customer Intelligence extracts where a site use identifier must be resolved to a display-ready address. A representative query is:

• SELECT site_use_id, contact_address FROM bic_site_address_v WHERE site_use_id = :p_site_use_id;
• SELECT site_use_id, contact_address FROM bic_site_address_v ORDER BY site_use_id;

Because the object is obsolete and absent from current databases, implementations requiring equivalent output should substitute a direct join across HZ_CUST_SITE_USES_ALL, HZ_CUST_ACCT_SITES_ALL, HZ_PARTY_SITES, and HZ_LOCATIONS, using the standard address formatting packages in place of BIC_ADDRESS_V. Any existing code that references BIC_SITE_ADDRESS_V should be treated as legacy and re-pointed before an upgrade, since the absence of the view — and of the BIC schema generally — will cause runtime errors on 12.2.2 instances where Customer Intelligence was never installed.