Results for “as_invalid_addr_account_v”

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

Overview

The view AS_INVALID_ADDR_ACCOUNT_V belongs to the Oracle E-Business Suite AS – Sales Foundation product family. Its documented purpose is to present accounts with invalid addresses, giving implementers, support analysts, and reporting developers a single denormalized result set that combines customer master information with address detail and territory reference data. Rather than requiring a report to join RA_CUSTOMERS, RA_ADDRESSES, and the territory lookup independently, the view performs those joins and pre-filters to only those addresses flagged as invalid. This makes it a convenient source for data-quality reporting, address cleansing initiatives, and integration extracts — for example, feeding an external address verification service (AVS) with the records that require remediation.

In ETRM documentation for 12.1.1 and 12.2.2, the view is annotated as Not implemented in this database, meaning it is documented at the metadata level but may not be deployed in every environment. Its availability should therefore be confirmed against the target instance before being referenced by custom concurrent programs or BI Publisher reports.

Underlying Base Objects

The view definition references four underlying objects:

• AS_INVALID_ADDR — the driving table holding address identifiers that have been determined to be invalid. The join to RA_ADDRESSES is performed on ADDRESS_ID, which is what restricts the result set to invalid addresses.
• RA_ADDRESSES (aliased ADDR) — the address table supplying street, city, state, province, county, postal code, and country information.
• RA_CUSTOMERS (aliased CUST) — the customer master, joined on CUSTOMER_ID, supplying customer name, number, and status.
• FND_TERRITORIES_TL (aliased TERR) — the territory (country) translation table, supplying TERRITORY_SHORT_NAME. This is joined with an outer join ((+)) on COUNTRY = TERRITORY_CODE and restricted by LANGUAGE = USERENV('LANG').

Note that the ETRM metadata lists no documented referenced base objects for 12.2.2, so the relationships above are derived from the view text itself. The view carries no owner information and is described as Oracle proprietary and confidential.

Key Columns

• ADDRESS_ID — unique identifier of the address record; primary linkage key.
• CUSTOMER_ID — foreign key linking the address to its owning customer.
• ADDRESS1–ADDRESS4 — the structured address lines.
• CITY, STATE, PROVINCE, COUNTY, POSTAL_CODE, COUNTRY — geographic components used for validation and cleansing.
• TERRITORY_SHORT_NAME — localized territory name resolved from FND_TERRITORIES_TL based on the user's session language.
• CUSTOMER_NAME, CUSTOMER_NUMBER — customer identification for reporting.
• STATUS (customer) and ADDRESS_STATUS — status flags for the customer and the address respectively.

Common Use Cases and Queries

Typical uses include identifying customers whose addresses failed validation so that they can be corrected or sent to an address verification service, and building exception reports for data governance.

SELECT cust.customer_number,
       cust.customer_name,
       addr.address1,
       addr.city,
       addr.state,
       addr.postal_code,
       terr.territory_short_name
FROM   as_invalid_addr_account_v addr,
       ... 

A simpler query selecting directly from the view:

SELECT customer_number,
       customer_name,
       address1,
       city,
       state,
       postal_code,
       territory_short_name
FROM   as_invalid_addr_account_v
WHERE  address_status = 'A'
ORDER  BY customer_name;

Because the view already filters to invalid addresses, no additional predicate on validity is required. Standard EBS multi-org and localization considerations still apply, and the view should be treated as read-only for reporting and integration purposes.