Results for “as_cust_account_codes_active_v”

4 results




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

Overview

The view AS_CUST_ACCOUNT_CODES_ACTIVE_V belongs to the Oracle E-Business Suite Sales Foundation (AS) product family and exposes active customer account address information together with validated territory data. It is a reporting and integration-oriented view that presents a denormalized, human-readable projection of customer addresses, allowing callers to retrieve a customer's address components alongside the territory short name derived from the country code.

Because the view filters on STATUS = 'A', only active (non-obsolete) address records are surfaced. In Oracle EBS 12.1.1 and 12.2.2, this view serves reporting layers, concurrent programs, and interface extracts that require the customer account code in combination with the physical address. The name itself references customer account codes, and the view's column list includes ACCOUNT_CODE, indicating it is intended to correlate an address to the customer account code context for downstream use in Sales Foundation processes.

Per the ETRM metadata provided, the view is documented but marked as "Not implemented in this database," and no referenced base objects are recorded. The view text nonetheless defines its behavior unambiguously.

Underlying Base Objects

The view is defined over two underlying objects, as shown in the documented view text:

  • RA_ADDRESSES ADDR — the Receivables/eBTax address repository that stores customer address records, including address lines, city, state, province, postal code, county, country, and status.
  • FND_TERRITORIES_VL TERR — the territory (country) validation view used across Oracle EBS Applications Foundation.

These two objects are joined on ADDR.COUNTRY = TERR.TERRITORY_CODE, which restricts results to rows whose country value resolves to a valid territory definition. Combined with the ADDR.STATUS = 'A' predicate, the view returns only active addresses with a recognized territory.

The ETRM documentation records no referenced base objects and states the view is not implemented in the reference database, so this analysis relies on the supplied view text as the authoritative definition. In a functioning instance, the view would be a standard SQL layer over the two objects above.

Key Columns

  • ACCOUNT_CODE — the account code column documented in the view's column list, associating the address with its customer account context.
  • ADDRESS_ID — unique identifier of the address record; the view text lists it twice in the projection, and it is the primary join key to other address-related objects.
  • CUSTOMER_ID — the owning customer's identifier, linking the address to the customer master.
  • ADDRESS1 through ADDRESS4 — the physical address lines.
  • CITY, STATE, PROVINCE, POSTAL_CODE, COUNTY — standard geographic components.
  • STATE_PROVINCE — a derived, formatted concatenation: STATE || DECODE(...) || PROVINCE, producing "STATE/PROVINCE" when both are present.
  • COUNTRY — the territory short name (from TERR.TERRITORY_SHORT_NAME).

Common Use Cases and Queries

Typical uses include customer address extracts, territory validation reporting, and integration feeds requiring active addresses. A representative query:

SELECT account_code, customer_id, address_id, address1, city, state_province, postal_code, country
FROM AS_CUST_ACCOUNT_CODES_ACTIVE_V
WHERE customer_id = :p_customer_id;

To obtain all active addresses for a given territory:

SELECT address_id, customer_id, address1, city, postal_code
FROM AS_CUST_ACCOUNT_CODES_ACTIVE_V
WHERE country = 'US'
ORDER BY postal_code;

Because the view already restricts to active records and valid territories, consumers avoid re-implementing those filters. Note that the ETRM marks the view as not implemented in the reference database; confirm availability in the target instance before depending on it in production extracts.