Search Results site_active

Overview

SO_BILL_TO_LOCATIONS_V is a reporting and integration view in the Oracle E-Business Suite Order Entry (OE) module. It consolidates bill-to site usage information into a single, denormalized result set by joining customer master data with site use and address records. The view answers a recurring functional question: which addresses are valid bill-to locations for a given customer, and what is the current status of each associated entity (customer, site use, and address). In Oracle EBS 12.1.1 and 12.2.2, this view is commonly consumed by order management extensions, custom reports, interfaces, and third-party integrations that need to resolve a bill-to address without navigating the underlying Receivables and Customer relationships themselves. It is not a base table or an interface table; it is a read-only projection intended for query and reporting. A user searching for "ra_addresses" is typically tracing back from this view to the source address table, RA_ADDRESSES, which supplies the physical address attributes exposed here.

Underlying Base Objects

The ETRM metadata documents no separately listed base objects, but the view text itself defines the dependency set directly. The view is a three-table join over RA_ADDRESSES, RA_SITE_USES, and RA_CUSTOMERS, all in the Oracle Receivables / Trading Community schema family. RA_ADDRESSES (aliased RA) provides the address components and address status. RA_SITE_USES (aliased RSU) provides the site use record, the site use identifier, and the GSA indicator, filtering to SITE_USE_CODE = 'BILL_TO'. RA_CUSTOMERS (aliased RAC) supplies customer identity and status, and enforces that the record belongs to an actual customer rather than a prospect through NVL(RAC.CUSTOMER_PROSPECT_CODE, 'CUSTOMER') = 'CUSTOMER'. The join conditions tie ADDRESS_ID across RA_ADDRESSES and RA_SITE_USES, and CUSTOMER_ID across RA_CUSTOMERS and RA_ADDRESSES. Because the documentation notes the view is "Not implemented in this database" in some environments, availability depends on whether the Receivables and Order Entry schemas have been installed and the view deployed.

Key Columns

• SITE_USE_ID — primary identifier of the bill-to site use record.
• LOCATION — the location identifier associated with the site use.
• SITE_ACTIVE, CUSTOMER_ACTIVE, ADDRESS_ACTIVE — status flags returned as '*' when status is 'A', otherwise blank; used for visual or conditional filtering.
• GSA_INDICATOR — indicates whether the site use carries a GSA designation.
• CUSTOMER_ID, CUSTOMER_NAME, CUSTOMER_NUMBER — the customer identity triplet.
• ADDRESS_ID — foreign key to the underlying address record in RA_ADDRESSES.
• ADDRESS1–ADDRESS4 — structured address lines.
• ADDRESS5 — concatenation of CITY, STATE, and POSTAL_CODE.
• CITY, STATE, POSTAL_CODE — individual components for structured reporting and validation.

Common Use Cases and Queries

Typical use cases include bill-to address validation during order entry, populating bill-to information on custom order reports, and building integrations that resolve a customer's active bill-to address. The following query retrieves active bill-to locations for a specific customer:

SELECT site_use_id, customer_name, address1, address2, city, state, postal_code FROM so_bill_to_locations_v WHERE customer_number = :p_customer_number AND site_active = '*' AND address_active = '*' ORDER BY address1;

Because the view exposes the address identifier, it also serves as a bridge when tracing from a bill-to site back to RA_ADDRESSES, which matches the original "ra_addresses" search. When the view is not deployed in a given instance, the equivalent result set can be reproduced by querying RA_ADDRESSES, RA_SITE_USES, and RA_CUSTOMERS directly with the same join and filter conditions documented in the view text.