Results for “ar_bill_drawee_address_v”

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

Overview

AR_BILL_DRAWEE_ADDRESS_V is a Receivables (AR) reporting view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It consolidates bill-to draw-to address information across the Trading Community Architecture (TCA) and Receivables data model, presenting customer name, account number, and formatted address elements for customer site uses flagged with the site use code DRAWEE. The view joins customer account sites, party sites, locations, territories, lookups, and account roles, producing a denormalized result set suitable for statements, dunning correspondence, invoice presentment, and integration extracts.

Because it is a view rather than a table, it carries no independent storage and is always read in real time from the TCA base objects. The status marker in the ETRM registry is VALID, confirming the object compiles and resolves against its referenced dependencies in the documented environment.

Underlying Base Objects

The view is defined over eleven documented referenced objects, predominantly TCA entities exposed through APPS synonyms, plus two views.

• HZ_CUST_SITE_USES (synonym) — drives the primary filter (SITE_USE_CODE = 'DRAWEE' and STATUS = 'A'), supplying SITE_USE_ID, LOCATION, PRIMARY_FLAG, TERRITORY_ID, and STATUS (aliased SU_STATUS).
• HZ_CUST_ACCT_SITES (synonym) — the account site record providing ADDRESS_ID (CUST_ACCT_SITE_ID), CUSTOMER_ID (CUST_ACCOUNT_ID), and A_STATUS.
• HZ_CUST_ACCOUNTS (synonym) — supplies the CUSTOMER_NUMBER (ACCOUNT_NUMBER).
• HZ_CUST_ACCOUNT_ROLES (synonym) — supplies CUST_ACCOUNT_ROLE_ID and, via HZ_PARTIES, contact name components.
• HZ_PARTY_SITES and HZ_LOCATIONS (synonyms) — provide address lines (ADDRESS1 through ADDRESS4), CITY, COUNTY, STATE, PROVINCE, COUNTRY, and POSTAL_CODE.
• HZ_LOC_ASSIGNMENTS (synonym) — links location to operating unit via the ORG_ID correlation, contributing LOCATION_ID.
• HZ_PARTIES (synonym, referenced twice) — PARTY.PARTY_NAME yields CUSTOMER_NAME; PARTY_CONT yields contact first and last names.
• HZ_RELATIONSHIPS (synonym) — links the party to its contact party records.
• AR_LOOKUPS (view) — resolves ARL.MEANING for the lookup-coded meaning column.
• FND_TERRITORIES_VL (view) — matches LOC.COUNTRY to TERRITORY_CODE, providing TERRITORY_SHORT_NAME.

Key Columns

• SITE_USE_ID — unique identifier of the draw-to site use; the primary handle for drill-down.
• ADDRESS_ID — the CUST_ACCT_SITE_ID of the associated account site.
• CUSTOMER_ID / CUSTOMER_NUMBER / CUSTOMER_NAME — customer account identifiers and formatted party name (truncated to 50 characters).
• ADDRESS — concatenated, character-limited address string suitable for printed correspondence.
• CITY, COUNTY, STATE, PROVINCE, COUNTRY, POSTAL_CODE — discrete address components.
• SU_STATUS — status of the site use record, returned as 'A' by the fixed filter.
• A_STATUS — status of the parent account site (ACCT_SITE.STATUS), which may differ from the site use status.
• PRIMARY_FLAG — indicates whether the site use is the primary draw-to address.
• PRIMARY_SALESREP_ID, TERRITORY_ID, LOCATION_ID, CUST_ACCOUNT_ROLE_ID — supporting identifiers for sales and territory context.

The user search term site_use_status maps directly to the SU_STATUS column exposed from HZ_CUST_SITE_USES.STATUS, which the view constrains to active records.

Common Use Cases and Queries

Typical consumers include billing statement generation, customer correspondence, and data migration or integration extracts that require draw-to addresses. A representative query filters by customer:

• SELECT customer_name, customer_number, address, city, state, postal_code FROM ar_bill_drawee_address_v WHERE customer_id = :p_customer_id ORDER BY primary_flag DESC;
• SELECT site_use_id, address_id, location_id, su_status, primary_flag FROM ar_bill_drawee_address_v WHERE customer_number = :p_account_number;
• SELECT customer_id, COUNT(*) FROM ar_bill_drawee_address_v GROUP BY customer_id HAVING COUNT(*) > 1; — identifying customers with multiple draw-to sites.

Queries should be constrained by CUSTOMER_ID or CUSTOMER_NUMBER where possible, since the view performs multi-table joins across TCA and is not optimized for unrestricted full scans.