Search Results edi_location




Overview
Explore in AI Chat

Overview

APPS.ARFV_LOCATIONS is a Business Intelligence System (BIS) view in the Oracle E-Business Suite APPS schema. It exposes customer and site address information maintained in the Oracle Receivables and Oracle Trading Community Architecture (TCA) model in a flattened, reporting-friendly form. The view is registered under FND Design Data object AR.ARFV_LOCATIONS and carries a status of VALID in both EBS 12.1.1 and 12.2.2. Its purpose is to provide a denormalized projection of location data — customer name, operating unit, territory, and the physical address elements — so that reports, extracts, and integrations can retrieve address detail without navigating the normalized TCA entity relationships directly.

The view is particularly relevant to searches for street_address: the STREET_ADDRESS column is a core member of the projection and is the primary attribute through which postal addresses are surfaced. The ARFV prefix denotes the Receivables family of views, indicating that the view belongs to the Oracle Receivables reporting layer rather than to the transactional base tables themselves.

Underlying Base Objects

The view is defined over the following documented base objects, listed in the ETRM dependency metadata. All are referenced as APPS synonyms except FND_TERRITORIES_VL, which is itself a view:

  • HZ_LOCATIONS — the TCA table that stores the raw address attributes (street address, city, state, postal code, province, country).
  • HZ_PARTY_SITES and HZ_LOC_ASSIGNMENTS — link party sites to locations and to the owning party.
  • HZ_CUST_ACCOUNTS and HZ_CUST_ACCT_SITES — supply the customer account and account-site relationship, including the primary bill-to designation.
  • HZ_PARTIES — provides the customer name associated with the account.
  • HR_ALL_ORGANIZATION_UNITS — supplies the operating unit to which the record belongs.
  • FND_TERRITORIES_VL — supplies territory validation and description information.
  • RA_TERRITORIES — the Receivables territories table, used for territory name and territory identifiers.

The ETRM metadata records that APPS.ARFV_LOCATIONS is not referenced by any database object; it functions purely as a read-only reporting projection and consumes the objects above without serving as a dependency for other views or packages.

Key Columns

Common Use Cases and Queries

Typical uses include customer address extracts for mailing or EDI, month-end billing-address verification, territory-to-address reconciliation, and operational reports filtered by operating unit. Because the view already exposes STREET_ADDRESS alongside CUSTOMER_NAME and OPERATING_UNIT, it removes the need for multi-table joins across the TCA entity model.

SELECT ADDRESS_ID,
       CUSTOMER_NAME,
       STREET_ADDRESS,
       CITY,
       STATE,
       POSTAL_CODE,
       COUNTRY,
       OPERATING_UNIT
FROM   APPS.ARFV_LOCATIONS
WHERE  ORG_ID = :p_org_id
AND    UPPER(STREET_ADDRESS) LIKE UPPER('%Main%');

A second pattern identifies primary bill-to sites for a given customer, using the documented flag column:

SELECT CUSTOMER_ID,
       CUSTOMER_NAME,
       STREET_ADDRESS,
       CITY,
       POSTAL_CODE
FROM   APPS.ARFV_LOCATIONS
WHERE  CUSTOMER_ID = :p_customer_id
AND    "_LA:PRIMARY_BILL_TO_FLAG" = 'Y';

Because column names such as _LA:STATUS and _LA:PRIMARY_BILL_TO_FLAG contain special characters, they must be referenced with double quotation marks, as shown. Queries should generally be restricted by ORG_ID or CUSTOMER_ID, since the view spans all operating units and customers and can return very large result sets.