Search Results arfv_locations




Overview
Explore in AI Chat

Overview

ARFV_LOCATIONS is a Receivables (AR) module view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It provides a consolidated, reporting-oriented representation of customer location and address data, denormalizing information that in the underlying data model is distributed across the Oracle Receivables and Oracle Trading Community Architecture (TCA) tables. The view surfaces the party site, account site, location, territory, and organization context required to identify and describe a customer's bill-to, ship-to, and general-purpose addresses.

The "FV" naming convention indicates a "flexfield view," a class of EBS views designed to expose descriptive flexfield values and lookup-derived coded meanings alongside their base columns. In ARFV_LOCATIONS this appears as literal lookup directives embedded in the SELECT list, such as '_LA:ADDRA.STATUS:AR_LOOKUPS:CODE_STATUS:MEANING', which instruct reporting and OA Framework layers to resolve the stored status code to its display meaning. The view is thus primarily consumed by Oracle Receivables forms, concurrent reports, and custom reporting integrations rather than by transactional processing.

Underlying Base Objects

Per ETRM documentation, ARFV_LOCATIONS is defined over the following base objects:

The view text joins these through an inline subquery on HZ_CUST_ACCT_SITES, HZ_PARTY_SITES, HZ_LOCATIONS, and HZ_LOC_ASSIGNMENTS, then resolution joins to the organization units, FND territories, and Receivables territories. The resulting primary key is exposed as ADDRESS_ID, derived from CUST_ACCT_SITE_ID.

Key Columns

  • ADDRESS_ID — unique identifier (CUST_ACCT_SITE_ID) for the account site.
  • ADDRESS1..ADDRESS4 — concatenated address lines, space-delimited.
  • CITY, STATE, POSTAL_CODE, PROVINCE — physical location attributes.
  • STATUS — account site status code, resolved through AR_LOOKUPS (CODE_STATUS).
  • TERRITORY_SHORT_NAME — territory short name from FND_TERRITORIES_VL.
  • ORIG_SYSTEM_REFERENCE, ECE_TP_LOCATION_CODE — origin and e-commerce location identifiers.
  • NAME (ALOU.NAME), CUSTOMER_NAME, TERR.NAME — resolved organization, customer, and territory names.
  • ORG_ID, CUSTOMER_ID, LOCATION_ID, TERRITORY_ID — foreign keys to operating unit, customer account, location, and territory.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY — standard WHO audit columns.

Common Use Cases and Queries

Typical uses include customer address validation reports, bill-to/ship-to reconciliation, territory assignment analysis, and integrations that require a flattened customer location model. A representative query retrieving active bill-to addresses for an operating unit:

  • SELECT address_id, address1, city, state, postal_code, customer_name, territory_short_name, status
  • FROM apps.arfv_locations
  • WHERE org_id = :p_org_id AND status = 'A';

For territory-oriented analysis, filter on TERRITORY_ID or group by TERRITORY_SHORT_NAME to summarize customer locations per territory. Because the view already resolves lookup meanings and foreign-key names, it reduces the join complexity otherwise required against the TCA tables, making it suitable for custom concurrent programs and BI Publisher reports in EBS 12.1.1 and 12.2.2.