Search Results ra_remit_tos




Overview
Explore in AI Chat

Overview

APPS.AR_ACTIVE_REMIT_TO_ADDRESSES_V is an Oracle E-Business Suite receivables view that exposes the set of active remit-to addresses configured for a customer account. In Oracle Receivables, remit-to addresses represent the locations to which a customer directs payments, and they are stored in RA_REMIT_TOS on the HZ_CUST_ACCT_SITES (customer account site) layer. The view resolves those remit-to rows into a single, ready-to-report record set by joining the customer account site, party site, location, and territory reference data, and by formatting the address through ARH_ADDR_PKG.ARXTW_FORMAT_ADDRESS according to the address style defined for the location.

The view is consumed in customer and receipt reporting and in integration interfaces that must resolve the remit-to address of a given customer account site. Because the view filters on active status at both the remit-to and account site level and returns formatted plus component address fields, it is the natural access point when the calling logic does not need the underlying RA_REMIT_TOS configuration rows but only the active, descriptive address information.

Underlying Base Objects

  • RA_REMIT_TOS — the remit-to configuration table. The view does not join to it row by row; instead it restricts HZ_CUST_ACCT_SITES to those CUST_ACCT_SITE_ID values appearing in the RA_REMIT_TOS subquery where STATUS = 'A'.
  • HZ_CUST_ACCT_SITES — the customer account site, supplying CUST_ACCT_SITE_ID (aliased ADDRESS_ID) and PARTY_SITE_ID, and filtered to STATUS = 'A'.
  • HZ_PARTY_SITES — links the account site to a party site, which carries the LOCATION_ID.
  • HZ_LOCATIONS — provides the raw address attributes (ADDRESS1–ADDRESS4, CITY, COUNTY, STATE, PROVINCE, POSTAL_CODE, COUNTRY, ADDRESS_STYLE).
  • FND_TERRITORIES_VL — supplies TERRITORY_SHORT_NAME, joined on LOC.COUNTRY = TERRITORY_CODE.
  • ARH_ADDR_PKG — a PL/SQL package whose ARXTW_FORMAT_ADDRESS function produces the single formatted address string for the address style.

Key Columns

  • ADDRESS_ID — the customer account site identifier (HZ_CUST_ACCT_SITES.CUST_ACCT_SITE_ID). This is the effective primary key of the view.
  • Formatted address — the ARH_ADDR_PKG output, DECODE-protected so that a null ADDRESS_ID yields null. This is the display-ready address line.
  • ADDRESS1, ADDRESS2 — street-level address components from HZ_LOCATIONS.
  • City/State/Postal line — a concatenation of CITY, comma, NVL(STATE, PROVINCE), POSTAL_CODE, and TERRITORY_SHORT_NAME, aliased ADDRESS3 (note the alias collides with the underlying ADDRESS3 column, so aliased selection is advisable).
  • CITY, COUNTY, STATE, PROVINCE, POSTAL_CODE — individual location attributes.
  • NVL(STATE, PROVINCE) — a normalized state-or-province value, useful for reporting where the two are treated as one field.
  • TERRITORY_SHORT_NAME — the country/territory short name from FND_TERRITORIES_VL.

Common Use Cases and Queries

The view is typically queried to display the active remit-to address for a customer account site, or to enumerate remit-to addresses for receipt and statement processes. A representative query retrieves the formatted address for a known account site:

SELECT address_id, address1, address2, address3,
       city, state, province, postal_code, territory_short_name
FROM   apps.ar_active_remit_to_addresses_v
WHERE  address_id = :p_cust_acct_site_id;

To list all active remit-to addresses with their formatted representation, selecting the formatted column by position or with an explicit alias avoids ambiguity with the component ADDRESS3 column:

SELECT v.address_id,
       arh_addr_pkg.arxtw_format_address(...) AS formatted_address,
       v.city, v.state, v.postal_code, v.territory_short_name
FROM   apps.ar_active_remit_to_addresses_v v;

Typical consumers include customer master reports, statement and dunning formats, and receipt application interfaces that must print or transmit the correct remit-to destination. Because the view already enforces STATUS = 'A' on both RA_REMIT_TOS and HZ_CUST_ACCT_SITES, downstream code does not need to reapply those filters; however, integrations requiring historical or inactive remit-to rows must query RA_REMIT_TOS directly rather than this view.