Search Results cust_acct_status




Overview
Explore in AI Chat

Overview

APPS.OE_CUSTOMER_ADDRESSES_V is a seeded Oracle E-Business Suite database view owned by the APPS schema and registered under FND Design Data as ONT.OE_CUSTOMER_ADDRESSES_V. In both Release 12.1.1 and 12.2.2 it retains a status of VALID and is classified as an internal view, meaning Oracle Corporation does not support direct access to application data through this object except from standard Oracle Applications programs. Despite that restriction, the view is widely encountered in reporting, data extraction, and integration work because it presents a denormalized, read-only projection of customer address information originating from the Oracle Trading Community Architecture (TCA) and Receivables customer model.

Its principal value lies in joining party, customer account, account site, site use, and location data into a single flattened row set. Consumers therefore avoid reconstructing the multi-table TCA relationship chain manually. The view surfaces the address attributes most often needed by order management, shipping, billing, and receivables reports, including the five free-form address lines (ADDRESS_LINE_1 through ADDRESS_LINE_5), the customer name and number, site and account statuses, and the operating unit identifier.

Underlying Base Objects

The ETRM dependency metadata documents that APPS.OE_CUSTOMER_ADDRESSES_V references six base objects, each represented through APPS synonyms: HZ_CUST_ACCOUNTS, HZ_CUST_ACCT_SITES, HZ_CUST_SITE_USES_ALL, HZ_LOCATIONS, HZ_PARTIES, and HZ_PARTY_SITES. No database object references the view itself, confirming it is a terminal, read-only presentation layer.

The relationship chain is characteristic of TCA. HZ_PARTIES stores the party record that carries the customer name. HZ_CUST_ACCOUNTS holds the customer account and customer number. HZ_CUST_ACCT_SITES associates an account with a specific site, while HZ_PARTY_SITES links that site to a location. HZ_LOCATIONS supplies the actual address line and location code attributes. HZ_CUST_SITE_USES_ALL contributes the site use code and site use status, allowing the view to distinguish ship-to, bill-to, and other purposes.

Key Columns

  • ADDRESS_LINE_1 through ADDRESS_LINE_5 — The free-form address lines sourced from HZ_LOCATIONS. ADDRESS_LINE_5 is documented as VARCHAR2(246), slightly wider than the 240-character lines above it, reflecting the underlying location column definition. Users searching for address_line_5 typically need the fifth address line for mailing, shipping, or localization scenarios.
  • LOCATION — The concatenated or descriptive location value (VARCHAR2, 40).
  • LOCATION_CODE — A short code identifying the location (VARCHAR2, 40).
  • CUSTOMER_NAME — The party name (VARCHAR2, 360).
  • CUSTOMER_ID / CUSTOMER_NUMBER — The customer account identifier and its display number.
  • ORGANIZATION_ID / ORG_ID — Organization and operating unit identifiers used to scope queries by business unit.
  • CUST_ACCT_SITE_ID — The account site identifier, useful for joining to other site-level data.
  • ACCT_SITE_STATUS, CUST_ACCT_STATUS, SITE_STATUS — Status flags for the account site, customer account, and site use respectively.
  • SITE_USE_CODE — The purpose of the site, for example SHIP_TO or BILL_TO (VARCHAR2, 30).

Common Use Cases and Queries

Typical uses include customer master extracts, address validation reports, shipping label feeds, and reconciliation of site use assignments across operating units. Because the view already flattens the TCA hierarchy, a single query can retrieve address data for a given customer or site use without explicit joins.

  • Retrieve all address lines, including the fifth line, for a specific customer: 
    SELECT customer_number, customer_name,
       address_line_1, address_line_2, address_line_3,
       address_line_4, address_line_5, site_use_code
FROM   apps.oe_customer_addresses_v
WHERE  customer_number = :p_customer_number
AND    site_use_code  = 'SHIP_TO';
  • List active bill-to sites for an operating unit: 
    SELECT customer_name, location_code, address_line_5
FROM   apps.oe_customer_addresses_v
WHERE  org_id = :p_org_id
AND    site_use_code = 'BILL_TO'
AND    site_status = 'A';
  • Detect records where the fifth address line is populated, often for international or multi-line mailing formats: 
    SELECT customer_id, customer_number, address_line_5
FROM   apps.oe_customer_addresses_v
WHERE  address_line_5 IS NOT NULL;

Because the object is flagged Oracle Internal Use Only, production integrations should preferably consume supported public APIs or documented interface views rather than relying on OE_CUSTOMER_ADDRESSES_V directly.