Search Results address_status




Overview
Explore in AI Chat

Overview

APPS.AR_BILL_DRAWEE_ADDRESS_V is a supplementary view in the Oracle E-Business Suite Receivables (AR) module, owned by the APPS schema and registered under the FND Design Data container AR.AR_BILL_DRAWEE_ADDRESS_V. Its documented status is VALID across EBS 12.1.1 and 12.2.2. Oracle classifies the object as a "supplementary view used to simplify forms coding," and the documentation carries an explicit warning that Oracle does not recommend querying or altering data through this view because its definition may change dramatically across minor or major releases. Consequently it should be treated as a forms-support artifact rather than a supported public interface. The view's functional purpose is to present bill-to drawee address information: a consolidated projection of customer identity (name and number), the formatted address lines, geography elements, and the status attributes of the underlying site use. The presence of the ADDRESS_STATUS and SITE_USE_STATUS columns is directly relevant to users searching on "address_status," since the view surfaces status indicators for both the address itself and the associated customer site use.

Underlying Base Objects

The view is defined over a mixture of Oracle Receivables and Oracle Trading Community Architecture (TCA) / HZ objects. Documented references include AR_LOOKUPS and FND_TERRITORIES_VL, both themselves views, plus the HZ synonyms: HZ_CUST_ACCOUNTS, HZ_CUST_ACCOUNT_ROLES, HZ_CUST_ACCT_SITES, HZ_CUST_SITE_USES, HZ_LOCATIONS, HZ_LOC_ASSIGNMENTS, HZ_PARTIES, HZ_PARTY_SITES, and HZ_RELATIONSHIPS. HZ_CUST_ACCOUNTS supplies the customer_name and customer_number, HZ_CUST_ACCT_SITES and HZ_CUST_SITE_USES supply the bill-to site use and its status, HZ_LOCATIONS supplies the raw address attributes, HZ_PARTY_SITES and HZ_LOC_ASSIGNMENTS bridge party and location records, and HZ_RELATIONSHIPS plus HZ_CUST_ACCOUNT_ROLES support contact (drawee/contact) derivation. FND_TERRITORIES_VL resolves territory and country descriptions, while AR_LOOKUPS decodes lookup meanings such as the primary flag meaning. Because the dependencies are almost entirely TCA-based, the view remains consistent in structure between 12.1.1 and 12.2.2 even as the underlying HZ package logic evolves.

Key Columns

The view exposes approximately twenty-nine columns. Identity columns include CUSTOMER_NAME (VARCHAR2 50), CUSTOMER_NUMBER (VARCHAR2 30), CUSTOMER_ID, and CUSTOMER_NAME. Address columns include ADDRESS1, ADDRESS2, ADDRESS3 (263), ADDRESS3_DB (240), the concatenated ADDRESS (306), LOCATION, CITY, COUNTY, STATE, PROVINCE, COUNTRY, POSTAL_CODE, and TERRITORY_ID. Status-related columns are SITE_USE_STATUS, which reflects the status of the customer site use record, and ADDRESS_STATUS, which reflects the status of the associated address; these are typically decoded through AR_LOOKUPS and are the primary targets of "address_status" inquiries. PRIMARY_FLAG and PRIMARY_FLAG_MEANING indicate whether the address is the primary bill-to location. Contact columns include CONTACT_ID, CONTACT_NAME, CONTACT_FIRST_NAME, CONTACT_LAST_NAME, and PRIMARY_SALESREP_ID. Key identifiers include ROW_ID (ROWID), SITE_USE_ID, ADDRESS_ID, LOCATION_ID, and TERRITORY_ID, all of which allow joins back to TCA tables for further detail.

Common Use Cases and Queries

Typical usage is diagnostic or reporting-oriented: identifying the bill-to address for a customer, checking whether an address is active or inactive, and reconciling contact/primary flags. A basic query filtered on address status might read:

  • SELECT customer_number, customer_name, address, city, state, postal_code, address_status, site_use_status FROM apps.ar_bill_drawee_address_v WHERE customer_number = :p_customer_number;
  • SELECT customer_id, address_id, site_use_id, primary_flag, primary_flag_meaning, address_status FROM apps.ar_bill_drawee_address_v WHERE primary_flag = 'Y';
  • SELECT COUNT(*) FROM apps.ar_bill_drawee_address_v WHERE address_status = 'A' AND site_use_status = 'A';

Because Oracle explicitly discourages direct querying of this forms-support view, equivalent results for production integrations should be obtained from the documented TCA base tables (HZ_CUST_ACCOUNTS, HZ_CUST_ACCT_SITES, HZ_CUST_SITE_USES, HZ_LOCATIONS). The view remains useful for ad hoc analysis and debugging of Receivables forms behavior around bill-to addresses and their statuses.