Results for “postal_code”

50+ results




Overview
Explore in AI Chat

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

Overview

RA_CUSTOMER_BILL_VIEW is a read-only database view owned by the APPS schema in Oracle E-Business Suite Releases 12.1.1 and 12.2.2. It belongs to the Oracle Receivables (AR) product family and is registered in the E-Business Suite Tables and Views Repository (ETRM) with a VALID status. The view is described in the repository as presenting "information about customer who is billed," which precisely characterizes its scope: it exposes the billing identity and bill-to address attributes of a customer account for a given site use.

Functionally, the view acts as a convenience layer over the Oracle Trading Community Architecture (TCA) model, collapsing the multi-table party, account, site, and location structure into a single denormalized result set. Rather than forcing report authors and integrators to join four TCA tables and apply the SITE_USE_CODE = 'BILL_TO' filter manually, the view encapsulates that logic. This makes it suited to ad hoc reporting, custom concurrent programs, and outbound integration extracts where only billed customer and bill-to address information is required. Because it is a view and not a table, it stores no data of its own and inherits the security and data model of the underlying TCA tables.

Underlying Base Objects

The view is defined over four TCA tables, all referenced through APPS synonyms in the documented 12.2.2 metadata:

The joins are driven from HZ_CUST_ACCT_SITES_ALL to HZ_CUST_SITE_USES_ALL on CUST_ACCT_SITE_ID, from HZ_CUST_ACCT_SITES_ALL to HZ_PARTY_SITES on PARTY_SITE_ID, and from HZ_PARTY_SITES to HZ_LOCATIONS on LOCATION_ID. The predicate SITE_USES.SITE_USE_CODE = 'BILL_TO' restricts the output to bill-to site uses, which is the defining filter of the view. No other site use codes, such as SHIP_TO or STATEMENT, are returned. The documented column list in the ETRM excerpt includes CUSTOMER_ID, BILL_ID, TERRITORY_ID, ADDRESS1, CITY, STATE, POSTAL_CODE, and STATUS, with BILL_ID corresponding to the underlying SITE_USE_ID exposed in the view text.

Key Columns

  • CUSTOMER_ID — the customer account identifier sourced from HZ_CUST_ACCT_SITES_ALL.CUST_ACCOUNT_ID. This is the account-level key, not the party identifier.
  • BILL_ID — the bill-to site use identifier (SITE_USE_ID). This distinguishes multiple bill-to sites belonging to the same customer account.
  • TERRITORY_ID — the territory associated with the bill-to site use, used in territory-based and sales organization reporting.
  • ADDRESS1, CITY, STATE, POSTAL_CODE — the formatted bill-to address components drawn from HZ_LOCATIONS.
  • STATUS — the status flag of the customer account site, indicating whether the site assignment is active.

Common Use Cases and Queries

Typical uses include resolving the default bill-to address for a customer during invoice or statement processing, populating address blocks in custom reports, and validating bill-to configuration during data migration or reconciliation. The following query lists active bill-to sites for a specific customer account:

  • SELECT customer_id, bill_id, address1, city, state, postal_code, status FROM apps.ra_customer_bill_view WHERE customer_id = :p_customer_id AND status = 'A';
  • SELECT customer_id, bill_id, territory_id, city, state FROM apps.ra_customer_bill_view WHERE territory_id = :p_territory_id;
  • SELECT customer_id, COUNT(*) bill_to_sites FROM apps.ra_customer_bill_view GROUP BY customer_id HAVING COUNT(*) > 1;

Because the view is restricted to BILL_TO site uses, it should not be used to retrieve ship-to or statement addresses; those require direct queries against HZ_CUST_SITE_USES_ALL with the appropriate site use code.